Retire musher-dev/specs — ADR 0001 §1 says it is superseded and will be deleted

[justinmerrell]

Problem

ADR 0001 §1 states:

musher-dev/specs is superseded and will be deleted. It is not renamed — its only content described a retired concept.

It is still public. Its README describes a bundle-definition schema for the agent-bundle format the platform no longer ships, and its schemas.musher.dev URLs were never served — which is now actively confusing, because that hostname is being stood up for this repository (#49).

It is also still the name carried in the org-level pr-workflow ruleset (id 14207433), while spec is not:

$ gh api orgs/musher-dev/rulesets/14207433 --jq '.conditions.repository_name.include'
["infra","mush","bundles","musher-cli","python-sdk","typescript-sdk","specs"]

Action (org owner)

1. Archive or delete musher-dev/specs.
2. In the same act, drop specs from ruleset 14207433.

musher-dev/infra has already recorded both halves of this in terraform/platform/github-governance/variables.tf, which no longer lists specs and documents the divergence from live until the archive happens. No IaC layer can create or destroy a repository — github-governance/rulesets.tf deliberately declares no github_repository resource — so step 1 is necessarily manual.

Not doing

Adding spec to that org ruleset. This repo self-manages .github/rulesets/main-branch.json, which is strictly stronger (PR + code-owner review + linear history + four required checks + squash-only). GitHub aggregates rulesets most-restrictive-wins, so listing it at the org level would buy nothing and would re-arm the same trap that got platform removed: a blanket required_approving_review_count = 1 silently overriding a repo's own selective code-owner gate.

[justinmerrell]

Status, 2026-08-19.

Ruleset — done. specs is dropped from pr-workflow (14207433). The change was surgical; diffing the ruleset before and after shows one line:

         "typescript-sdk",
-        "specs"

enforcement, rules, bypass_actors and ref_name are byte-identical, and per this issue's "Not doing", spec was not added. musher-dev/infra's github-governance/variables.tf and live are now in agreement, so the divergence note there can go.

Live membership is now ["infra","mush","bundles","musher-cli","python-sdk","typescript-sdk"].

Record — in review. #58 adds ADR 0014, superseding ADR 0012 §5 ("archived, not deleted") and closing its follow-up 2.

Worth flagging, since this issue predates it: the repository is already archived, and ADR 0012 §5 had decided archived was the end state, on the grounds that deletion 404s every inbound reference — including ADR 0001's own account of why this repository exists. ADR 0014 reverses that rather than ignoring it, and states the cost under Consequences instead of arguing it away. ADR 0001 and ADR 0012 are left as written.

Remaining, and yours. Deleting musher-dev/specs. One suggestion before you do: git clone --mirror it somewhere first if the history is wanted at all. After deletion there is nothing left to clone, and the decision does not assume a mirror was taken.