feat(gatorwalk-factory): the swamp-club Lab is the swamp-club team's own, and the shipped docs say so (swamp-club #2842) #413

Merged
seth merged 1 commit from cue/2842-gatorwalk-factory-scrub into main 2026-10-01 15:44:48 +00:00
Owner

Closes swamp-club #2842.

The swamp-club Lab tracker is the swamp-club team's own. swamp-club is not a secret, but nobody else can use the Lab, so the shipped skill and README must never present it as an option.

What changed

  • Skill: names only the built-in tracker and Linear.
    • SKILL.md and driving.md lose the swamp-club example, the Lab ticket-key example, the Lab-only claim refusal, the Lab type list and the Lab publisher notes. Retarget uses built-in externalRefs.
    • scenarios.md's example externalRefs are built-in.
    • authoring.md keeps one paragraph: the Lab tracker is for the swamp-club team's own repositories and needs a team account.
  • Examples:
    • swamp-club-swamp-extensions.yaml and .md are deleted. The team's definition lives in its own factory model (#2884).
    • starter and build-swamp-extension use the built-in tracker's default statuses (open instead of triaged) and neutral example.com URLs.
  • README:
    • Examples and status keys are built-in only.
    • The Lab section is now "swamp-club Lab (swamp-club team only)" and opens by saying so.
    • The claim example uses the built-in tracker.
  • DESIGN.md:
    • Tracker sections are rewritten around the built-in tracker.
    • "The swamp-club Lab adapter" opens with a team-only paragraph.
    • Figures that cited the team's definition are restated.
    • New decision-log entry.
  • Guard: integration/extension/skill_test.ts fails on any paragraph in the skill or README that names swamp-club or the Lab without saying it is for the swamp-club team, and on any skill file named for swamp-club. An unlabelled sentence added to driving.md made it fail.
  • The swamp-club adapter still ships, unchanged. Moving it to a team-only extension is left for later.

Tests

  • Deleted: tests that pinned the swamp-club process.
    • The block in factories_test.
    • The three Lab-entry tests in tracker/examples_test.
    • The claim-to-notify walk in integration/tracker/tracker_test.
    • The examples gate-message test, which factory_test and scenario_test already cover.
    • The cli validate-and-start case, which duplicated an existing test.
  • Kept: the Lab adapter's own tests, and the real-CLI test of claim's issue-lifecycle guard.
  • Moved to build-swamp-extension: tests that used the swamp-club example only as a large definition.
    • The design page tests.
    • The studio acceptance, nav and changes tests.
    • The work_item_test walk, which keeps CLI string inputs and a retarget partway through.
    • The cli scenario-failure and stored design-page tests.
  • Graph pruning cap test: now uses an inline chain of seven self-loops (175,780 count states unpruned, 8 pruned). No remaining definition gets past the 100,000 cap.
  • tracker/examples_test: checks example status keys against the built-in tracker's DEFAULT_STATUSES.
  • Rebased onto #2840, #2873 and #2816. #2873 edited the deleted example and its walk test. The deletion is kept, and #2873's plan-feedback assertion lines in factories_test are taken as they are.

deno task check, lint, fmt:check, test (691 passed) and test:integration (42 passed) all pass. verify-build and verify-reviews passed, and the attestation is posted for the head commit.

🤖 Generated with Claude Code

Closes swamp-club #2842. The swamp-club Lab tracker is the swamp-club team's own. swamp-club is not a secret, but nobody else can use the Lab, so the shipped skill and README must never present it as an option. ## What changed - **Skill:** names only the built-in tracker and Linear. - SKILL.md and driving.md lose the swamp-club example, the Lab ticket-key example, the Lab-only claim refusal, the Lab type list and the Lab publisher notes. Retarget uses built-in `externalRefs`. - scenarios.md's example `externalRefs` are built-in. - authoring.md keeps one paragraph: the Lab tracker is for the swamp-club team's own repositories and needs a team account. - **Examples:** - `swamp-club-swamp-extensions.yaml` and `.md` are deleted. The team's definition lives in its own factory model (#2884). - `starter` and `build-swamp-extension` use the built-in tracker's default statuses (`open` instead of `triaged`) and neutral `example.com` URLs. - **README:** - Examples and status keys are built-in only. - The Lab section is now "swamp-club Lab (swamp-club team only)" and opens by saying so. - The claim example uses the built-in tracker. - **DESIGN.md:** - Tracker sections are rewritten around the built-in tracker. - "The swamp-club Lab adapter" opens with a team-only paragraph. - Figures that cited the team's definition are restated. - New decision-log entry. - **Guard:** `integration/extension/skill_test.ts` fails on any paragraph in the skill or README that names swamp-club or the Lab without saying it is for the swamp-club team, and on any skill file named for swamp-club. An unlabelled sentence added to driving.md made it fail. - **The swamp-club adapter still ships, unchanged.** Moving it to a team-only extension is left for later. ## Tests - **Deleted:** tests that pinned the swamp-club process. - The block in `factories_test`. - The three Lab-entry tests in `tracker/examples_test`. - The claim-to-notify walk in `integration/tracker/tracker_test`. - The examples gate-message test, which `factory_test` and `scenario_test` already cover. - The cli validate-and-start case, which duplicated an existing test. - **Kept:** the Lab adapter's own tests, and the real-CLI test of `claim`'s issue-lifecycle guard. - **Moved to `build-swamp-extension`:** tests that used the swamp-club example only as a large definition. - The design page tests. - The studio acceptance, nav and changes tests. - The `work_item_test` walk, which keeps CLI string inputs and a retarget partway through. - The cli scenario-failure and stored design-page tests. - **Graph pruning cap test:** now uses an inline chain of seven self-loops (175,780 count states unpruned, 8 pruned). No remaining definition gets past the 100,000 cap. - **`tracker/examples_test`:** checks example status keys against the built-in tracker's `DEFAULT_STATUSES`. - **Rebased onto #2840, #2873 and #2816.** #2873 edited the deleted example and its walk test. The deletion is kept, and #2873's plan-feedback assertion lines in `factories_test` are taken as they are. `deno task check`, `lint`, `fmt:check`, `test` (691 passed) and `test:integration` (42 passed) all pass. verify-build and verify-reviews passed, and the attestation is posted for the head commit. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
feat(gatorwalk-factory): the swamp-club Lab is the swamp-club team's own, and the shipped docs say so (swamp-club #2842)
All checks were successful
CI / Review Integrity (pull_request) Successful in 53s
CI / Validate Attestation (pull_request) Successful in 59s
a50dc6f442
The skill, README and examples name only the built-in tracker and Linear.
The swamp-club-swamp-extensions example and the tests that pinned its
process are deleted; tests that used it as a large fixture move to
build-swamp-extension, and the graph pruning cap test to an inline chain
of self-loops. The examples use the built-in tracker's default statuses.
The swamp-club adapter still ships, and the README and DESIGN say it is
for the swamp-club team. A skill_test guard fails on any paragraph of the
skill or README that names swamp-club or the Lab without saying so.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
seth merged commit ef45b3beb9 into main 2026-10-01 15:44:48 +00:00
seth deleted branch cue/2842-gatorwalk-factory-scrub 2026-10-01 15:44:49 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
swamp-club/swamp-extensions!413
No description provided.