finishing: TS-prefix epic releases, lockstep verification, and close-out

[rahlk]

PROBLEM

The TS-prefix epic spans two analyzer releases, an SDK pin lockstep, and three doc repos; without a finishing pass the pieces can land individually while the coordination invariants (release ordering, pin timing, announcement accuracy, issue close-out) silently fail.

SCOPE BOUNDARY

Verification, releases, and close-out only — no feature code.

GOALS

1. Stage-1 release: cut the analyzer minor (graph schema 1.1.0) with CHANGELOG entries naming the dual-label addition; verify schema.neo4j.json in the tag matches the emitter; tidy the auto-posted release announcement.
2. Stage-2 release (with the v2 contract): breaking notes lead with the rename + one-line migration (re-analyze; Callable→TSCallable, CALLS→TS_CALLS); confirm python-sdk's pin moves only after this release exists.
3. Verify epic-level DoD: dual-label count parity on the fixture (stage 1), zero bare labels/rel types (stage 2), SDK tests green against each pinned release, convention doc updated in all three repos.
4. Close Namespace Neo4j node labels with a TS prefix #8, Namespace Neo4j relationship types with a TS_ prefix #9, Bump graph schema contract to 2.0.0 and regenerate published artifacts #10 against their delivering children; close the epic when the checklist is complete.

DEFINITION OF DONE

• Both releases tagged with accurate CHANGELOGs and cleaned announcements.
• Every epic checklist item ticked; Namespace Neo4j node labels with a TS prefix #8/Namespace Neo4j relationship types with a TS_ prefix #9/Bump graph schema contract to 2.0.0 and regenerate published artifacts #10 closed with a pointer to the delivering PR; epic closed.

Part of #64