Skip to content

chore(verify): remove seeded runs from the verification skill - #74

Merged
Upd4ting merged 1 commit into
mainfrom
chore/remove-seeded-runs
Nov 5, 2026
Merged

Upd4ting merged 1 commit into
mainfrom
chore/remove-seeded-runs

Conversation

@Upd4ting

@Upd4ting Upd4ting commented Nov 5, 2026

Copy link
Copy Markdown
Member

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-verify has no seeded, seeded-doors or containments; map and verdict no longer read breaks, doors or containment journeys) and @antelopejs/dms@0.17.0 (dms-control has no seeded). 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-configs moved to 0.3.0 (and @antelopejs/dms to 0.17.0 where dms-control is used); lockfile updated.
  • antelopejs-sync re-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 checks and CI green on the PR head.
  • A PR against main whose body holds this snapshot and the counts it removed, copied from command output.

What changed

  • @antelopejs/tooling-configs ^0.2.17 to ^0.3.0 in package.json; pnpm-lock.yaml updated. @antelopejs/dms is not used here.
  • antelopejs-sync rewrote the shared SKILL.md (seeded sections, trust clause and verdict rules gone), features/README.md and AGENTS.md.
  • Hand edits: removed the containments: ["streams/stream-shape"] key from the Format door in verify.config.ts, and the "containment journey" clause from features/streams.md. stream-shape is listed by the streams feature and checks real stage recording, so it stays as an ordinary journey.
  • The containment prose column of a door row stays, as in chore(dms-control): remove seeded runs and containment journeys from verification dms#774.

Removed

== remove-seeded counts ==
tooling-configs bumped to 0.3.0 in: package.json
dms bumped to 0.17.0 in: (not used with dms-control)
seeded-breaks files removed: 20
seeded-doors files removed: 3
empty containments entries removed: 2

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

  • Sync adoption steps, kept as written: test-job: true in .github/workflows/ci.yml, "agentFiles": true in guardrails.suppressions.json (no number raised), types: ["node"] in the skill's tsconfig.json, the new technical-writing and unslop skills under .agents/skills/ with their .claude/skills/ links, and an AGENTS.md "While you work" section and rule-table row.
  • No manifests outside the root workspace exist in this repository.

Related issue

None. Part of the seeded-runs removal across AntelopeJS repositories (see AntelopeJS/dms#774).

Checklist

  • The pull request title follows Conventional Commits.
  • I added or updated tests when behavior changed. No behavior changed.
  • I updated documentation when users or contributors are affected.
  • I documented breaking changes and migration steps. None.
  • I did not include credentials or unrelated changes.

@Upd4ting
Upd4ting merged commit 74b96d9 into main Nov 5, 2026
8 checks passed
@Upd4ting
Upd4ting deleted the chore/remove-seeded-runs branch November 5, 2026 22:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant