codeanalyzer-ts backend page: audit Neo4j labels/Cypher for the TS-prefix schema stages

[rahlk]

PROBLEM

The TypeScript backend page (astro branch, backends/codeanalyzer-ts.mdx) documents the Neo4j projection. The analyzer is namespacing its graph labels in two stages (dual TS* labels at graph schema 1.1.0, prefixed-only + TS_* relationship types at 2.0.0 — see the epic); any label or Cypher example on the page will go stale.

SCOPE BOUNDARY

The TS backend page (and any cross-page Cypher examples touching TS labels). Python/Java backend pages are untouched.

GOALS

1. Audit the page for node-label / relationship-type mentions and Cypher snippets; update them per stage as the analyzer releases land (dual-label note at stage 1, prefixed-only forms at stage 2).
2. Add the schema-version note so readers can match page examples to the schema_version stamped on their :TSApplication node.

DEFINITION OF DONE

• Every label/rel-type mention and Cypher snippet on the page matches the released analyzer's schema at time of merge.
• The page states which graph schema version its examples target.

Part of codellm-devkit/codeanalyzer-typescript#64

[rahlk]

The TS-prefixed Neo4j vocabulary is now released: codeanalyzer-typescript v1.0.0 ships graph schema 2.0.0 — labels are TSModule/TSClass/TSCallable/…, relationship types are TS_CALLS/TS_HAS_MODULE/…, and nodes merge on the shared CanNode label + id. The backend page's label/Cypher audit can target this shipped vocabulary directly (no dual-label interim on main anymore). Release: https://github.com/codellm-devkit/codeanalyzer-typescript/releases/tag/v1.0.0