Repository navigation
chore(verify): remove seeded runs from the verification skill - #74
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Seeded runs are gone from every AntelopeJS repository. They are not part of the verification-skill shape (SKILL.md, features/README.md, one file per feature, journeys, verify.config.ts), they slowed every verification, and they drifted from maintain-verification-skill. The tools are already released without them:
@antelopejs/tooling-configs@0.3.0. This repository's skill has to follow.Goal and done means (snapshot)
Goal. Antony removed seeded runs from every AntelopeJS repo on 2026-11-05. The tools are released without them:
@antelopejs/tooling-configs@0.3.0(antelopejs-verifyhas noseeded,seeded-doorsorcontainments;mapandverdictno longer read breaks, doors or containment journeys) and@antelopejs/dms@0.17.0(dms-controlhas noseeded). The repository's verification skill ends in the standard shape: SKILL.md, features/README.md, one file per feature, journeys, verify.config.ts. Formal checks and one-way door detection (antelopejs-verify doors, api-diff--doors) stay.Done means.
@antelopejs/tooling-configsmoved to 0.3.0 (and@antelopejs/dmsto 0.17.0 where dms-control is used); lockfile updated.antelopejs-syncre-run so the shared verify layer matches 0.3.0.seeded-breaks/,seeded-doors/and containment journeys deleted;verify.config.ts, SKILL.md and features no longer mention them; nothing else in the skill changes.pnpm run checksand CI green on the PR head.mainwhose body holds this snapshot and the counts it removed, copied from command output.What changed
@antelopejs/tooling-configs^0.2.17to^0.3.0inpackage.json;pnpm-lock.yamlupdated.@antelopejs/dmsis not used here.antelopejs-syncrewrote the sharedSKILL.md(seeded sections, trust clause and verdict rules gone),features/README.mdandAGENTS.md.containments: ["streams/stream-shape"]key from the Format door inverify.config.ts, and the "containment journey" clause fromfeatures/streams.md.stream-shapeis listed by thestreamsfeature and checks real stage recording, so it stays as an ordinary journey.containmentprose column of a door row stays, as in chore(dms-control): remove seeded runs and containment journeys from verification dms#774.Removed
Verification
pnpm run checks:Checks: 8 passed, 0 failed.pnpm exec antelopejs-verify map: exit 0.grep -rnIiE 'seeded-(breaks|doors)|containments' .agents .claude AGENTS.md docs: no hits.Attention
test-job: truein.github/workflows/ci.yml,"agentFiles": trueinguardrails.suppressions.json(no number raised),types: ["node"]in the skill'stsconfig.json, the newtechnical-writingandunslopskills under.agents/skills/with their.claude/skills/links, and anAGENTS.md"While you work" section and rule-table row.Related issue
None. Part of the seeded-runs removal across AntelopeJS repositories (see AntelopeJS/dms#774).
Checklist