Change Type

• chore (build/toolchain/dependency, not included in Changelog)

Change Description

Option A from the naming discussion: align the trunk's package references with the npm reality — the six packages are published as @liu_wentao/cptf-* (0.2.0), and the bare @cptf/* names can never exist on npm (the cptf org/scope is taken). Keeping dead names in source meant every publish required a sed-rename branch and permanent source/registry drift.

What changes (57 files):

• package.json name/dependencies for all six packages -> @liu_wentao/cptf-framework, cptf-schema, cptf-benchmark, cptf-benchmark-rn, cptf-native-harmony, cptf-plugin-rn
• All source imports (framework internal imports, benchmark collectors, plugin-rn probes, benchmark-rn components), root script filters, the lazy-scanner test fixture (must match the real package name), READMEs, BUILD docs and the spec/guide docs
• Architecture svgs that reference the real @cptf/benchmark package
• Version fields: 0.1.0 -> 0.2.0 (matches the registry version line)
• nativeharmony oh-package name/version follow
• CHANGELOG rename-sync entry under today's date

Intentionally unchanged:

• CHANGELOG history lines (they record the @cptf/* names as they were at the time)
• detox analysis docs + design-phase svgs whose @cptf/* names are unimplemented placeholders, not references to real packages

Effect: the publish branch no longer needs any renaming step — source and published artifacts are name-identical (zero diff). The published packages live at https://www.npmjs.com/package/@liu_wentao/cptf-framework (all six under the same scope).

Note for maintainers: the @liu_wentao scope is the current npm publishing identity (the cptf org name is unavailable on npm). When a permanent org scope is decided (e.g. @cpf-rn), this rename repeats once — the cptf- prefix on package names is designed to survive that migration unchanged.

Test Steps

Test reference: test case: full verification chain on the renamed graph

1. pnpm install resolves the renamed graph
2. schema build + framework build + pnpm typecheck — clean
3. jest excluding the four upstream-known-broken suites (ws-rpc-client / android-native-driver / harmony-native-driver / ui-comparator, broken on the trunk itself since 3550729) — 271 suites / 6829 passed
4. Zero @cptf/* six-package references remain outside CHANGELOG history and detox placeholder docs (grepped)
5. prettier + cspell green over all 57 touched files (37 project-dictionary words added — the docs had never been spell-scanned before)

Test Status

• Passed local comprehensive testing (unit tests/integration tests)
• Complies with the corresponding coding standards.
• Does not involve documentation updates, or documentation has been updated.

Pre-merge Self-Check

• Does not involve incompatible changes
• No sensitive information leakage