#2820 stagecraft: publish @swamp/stagecraft: manifest, Lab exclusion, real-tree checks, packaged install, merge

Publish @swamp/stagecraft: the final PR that adds the manifest, runs every publication check on the real tree, and merges. CI publishes on merge.

Rewritten 2026-10-02 (Seth). The earlier body predates the rename to stagecraft (#2932), the publication prep (#2947) and the decisions below; it is kept in this issue's history.

Where things stand

• Manifest. It's held on branch cue/2947-stagecraft-manifest (commit 90131cd47), six commits behind main when this was written. It adds stagecraft/manifest.yaml, deletes no_manifest_test.ts and adds manifest_test.ts. Merging it to main publishes (.forgejo/workflows/publish.yml).
• #2947 got quality to 12/12, passed fmt and a dry-run push on a scratch copy, and installed the packaged archive into a fresh repo, running it to a first human stop with the studio and skill.
• swamp blockers are cleared. #2949 (push's eval check) ships in swamp 20261002.182915 (e2b0a082), so the real tree can be dry-run pushed for the first time. #2952 (token-count fields flagged as secrets) is merged in swamp (d7714fef); its warnings never block a push.
• Linear has been tested against a real workspace by Seth, and it works.
• Waits on: #2891 (Simulate follow-ups) and #2956 (work-item page follow-ups), both in progress. Seth wants them landed before this merges.
• #2821 (software-factory's future and deprecation) is deferred and doesn't block this.

Checklist

1. Rebase the manifest branch onto origin/main.

2. Exclude the swamp-club Lab tracker from the package (Seth, 2026-10-02). It stays in the repo for possible team use but must not ship.

   • Remove tracker/swamp_club.ts from the manifest's models:. It's listed today.
   • Break the built-in tracker's import from the Lab backend: tracker/builtin.ts:36-39 imports CredentialSources and DEFAULT_SOURCES from _lib/tracker/backends/swamp_club.ts, the auth.json reader. Move what the built-in tracker needs into tracker core (_lib/tracker/core/) and have both trackers import it from there.
   • Check that every shipped module refers to the Lab only in strings, never in imports. Candidates include _lib/engine/tracker_binding.ts, _lib/tracker/core/adapter.ts, relations.ts, ticket_view.ts and the studio bundle. A boundary test should enforce it, as boundary_test.ts does for the engine/tracker seam.
   • manifest_test.ts asserts the Lab adapter, its backend, its fake and the auth test data are not in the manifest.
   • The adapter's own tests keep passing from source.
   • Add a DESIGN.md decision-log entry: kept, not shipped, with delete-or-move decided after launch.

3. Version. Re-read it with swamp extension version @swamp/stagecraft and set it in the manifest.

4. Metadata.

   • Replace the sdlc label: stagecraft is for any process, not only software. Consider workflow or process.
   • Check the description against the README, since the registry's Readme tab renders the manifest description.
   • Keep repository: as the repo's other manifests have it.

5. swamp's checks on the real tree, with no scratch rewrites, recorded in the PR:

   • swamp extension fmt stagecraft/manifest.yaml
   • swamp extension quality stagecraft/manifest.yaml: expect 12/12
   • swamp extension push stagecraft/manifest.yaml --dry-run

   Use a swamp that includes #2949. If a release with #2952 is out, use it, so the token-count warnings disappear too.

6. Packaged install. Install the dry-run archive into a fresh repo and run from zero to a first human stop: init --from a starter, validate, the studio (Design, Simulate, Board, a work-item page), and a work item driven to its first human stop on the built-in tracker. Confirm the skill arrives with the extension, and that swamp model type search stagecraft lists no @swamp/stagecraft/swamp-club.

7. Verification. Run the repo's verify-build and verify-reviews on the PR and post the attestation; no attestation covers the manifest yet.

8. Channel: confirm with Seth before merging. Stable (CI's default) or beta (swamp extension push --channel beta). Check whether publish.yml can pass a channel; beta may need it wired up.

9. Merge: Seth merges. Merging publishes. Then confirm the registry shows @swamp/stagecraft, and that swamp extension pull @swamp/stagecraft into a fresh repo works.

10. Announce. Release notes and changelog, plus a short announcement Seth can post. The team overview artifact may help.

Done when

@swamp/stagecraft is published, a fresh repo can pull it and run getting started, the Lab adapter isn't in the package, and every check above is recorded in the PR.

Out of scope: #2821 (deferred), and anything after launch (#2583, #2913, #2847, #2978, #2800, #2774, #2775, #2809, #2665, #2908, #2912).