#2932 gatorwalk-factory: rename to stagecraft (@swamp/stagecraft) for first release

Rename the extension from its code name, gatorwalk-factory, to its public name, stagecraft, before first release.

Why

Decided by Seth on 2026-10-01, after meeting with Paul. The product is a factory maker: you use it to build your own factories, where agents do the work or drive a process. That could be software, web posts, incident reviews, swamp models or extensions, or anything else expressed as stages that produce artifacts and evidence, with gates that set the rules for moving between them. "gatorwalk-factory" was always a code name (README.md:1-6), and go-live (#2820) needs the final one.

Names considered: meta-factory (taken by @atalanta/meta-factory), millwright, lockkeeper, workshop, and plain factory (it reads too close to @swamp/software-factory, and the type would be @swamp/factory/factory).

Scope

• Model types. @swamp/gatorwalk-factory/<type> becomes @swamp/stagecraft/<type>: factory, work-item, studio, builtin, linear, swamp-club, and any others on main. Also rename the report type (work-item-summary) and every string-literal type in the model files, plus the tests that compare them to their constants.
• The inner vocabulary stays: factory, factory definition, work item, stage, gate, product, tracker. Stagecraft is the thing that makes factories, so @swamp/stagecraft/factory reads correctly.
• Directory. gatorwalk-factory/ becomes stagecraft/ at the repo root, including deno.json tasks and import paths, the integration harness, the scripts and the studio build.
• The skill. .claude/skills/gatorwalk-factory/ becomes .claude/skills/stagecraft/, including its name, description and triggers. Check that the triggers still don't steal swamp's own skills, and every command in SKILL.md and the references.
• Docs. README, DESIGN.md (add a decision-log entry recording the name and why), the examples' header text and the scenarios docs. Drop "code name" language.
• Repo wiring. verification/checks.yaml, verification/workflow-verify.yaml, verification/workflow-verify-reviews.yaml (the adversarial-review path guard list; see #2583), scripts/audit_deps.ts if #2850 has landed, and any CI path filters.
• The datastore. Records written under the old type names are not migrated. There are no users before go-live and the extension has never been published, so say so in the decision log. Seth's local dogfood and test factories get recreated.
• Search for leftovers. Grep the whole repo for gatorwalk (any case) and leave only intentional history: DESIGN.md's decision log and old issue numbers. Decide whether scripts/rename_lifecycle_to_factory.ts stays or goes now that it has served its purpose.

How (lessons from #2785)

Other work is running in gatorwalk-factory right now: #2703, #2911, #2912 and #2931, plus test sessions. Write the rename as a script that can be re-run on the latest origin/main. #2785 did this with scripts/rename_lifecycle_to_factory.ts. Plan to land it at a quiet point after rebasing, and tell Seth when you're ready so he can hold other merges briefly. After it lands, every open branch rebases onto it.

Done when

• No gatorwalk remains outside intentional history.
• Every test, deno task and verification workflow passes under stagecraft/.
• swamp model type search stagecraft lists the types from a fresh repo that adds stagecraft/ as an extension source.
• The skill loads as stagecraft and its commands pass skill_test.ts.

Out of scope: adding manifest.yaml and publishing (#2820), and rewriting the README for users (separate). Rename only.