create --type bugfix
Published manifest schema carries internal tracker codes in 33 descriptions; sweep + widen the no-internal-codes gate
The generated manifest.schema.json — a docs-site asset and release artifact adapter authors validate against — carries internal tracker codes (REQ-*, ADR-*, releases#*) in 33 of its 129 descriptions. The xtask check no-internal-codes gate scans only the generated CLI reference; the schema is the same publication class and sits outside that gate's population.

Found by todlando during CONDUIT W1 (releases#157; spt-bs-core PR #171 removed exactly one code, in the sentence it was already rewriting, and reported the rest instead of sweeping unilaterally).

Ruled at the W1 gate (doyle, PR #171 comment 5458378678): ALL internal codes leave the schema descriptions — ADR cross-refs included, since docs/adr is not a published surface and those references are dead pointers to an adapter author — and the no-internal-codes gate widens to manifest.schema.json in the same change, so the class stays shut rather than resurfacing one doc comment at a time.

Shape note for the builder: the codes originate in manifest.rs doc comments that generate into the schema; the sweep edits those comments (published sentence stays, tracker code goes) and regenerates. The existing manifest_schema_shape drift test plus the widened gate are the coverage.