sealed-repos.gitignore still names ward-mcp, so mcp-beaver is sealed by nothing #1091

New issue

Closed

opened 2026-08-16 05:53:51 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-16 05:53:51 +00:00

Owner

aos-cli/repositories/sealed-repos.gitignore lists coilyco-flight-deck/ward-mcp. That repository is now coilyco-flight-deck/mcp-beaver, so the entry matches nothing.

Why it is worth a fix rather than a note

The list is keyed by repository slug and the failure is silent. The file still names the repository, so a reader checking whether it is sealed sees an entry and stops looking. Nothing errors and no check goes red.

Also in scope

coilyco-flight-deck/umbra sits where coilyco-flight-deck/cli-guard used to, out of alphabetical order with everything around it. That is the same edit-in-place slip from one rename earlier.

Ordering in that block is inert: * seals everything above it and the negations are in their own block below. So this half is readability, not behaviour.

Acceptance

The sealed list names coilyco-flight-deck/mcp-beaver.
No entry names a slug that no longer resolves.

`aos-cli/repositories/sealed-repos.gitignore` lists `coilyco-flight-deck/ward-mcp`. That repository is now `coilyco-flight-deck/mcp-beaver`, so the entry matches nothing. ## Why it is worth a fix rather than a note The list is keyed by repository slug and the failure is silent. The file still names the repository, so a reader checking whether it is sealed sees an entry and stops looking. Nothing errors and no check goes red. ## Also in scope `coilyco-flight-deck/umbra` sits where `coilyco-flight-deck/cli-guard` used to, out of alphabetical order with everything around it. That is the same edit-in-place slip from one rename earlier. Ordering in that block is inert: `*` seals everything above it and the negations are in their own block below. So this half is readability, not behaviour. ## Acceptance * The sealed list names `coilyco-flight-deck/mcp-beaver`. * No entry names a slug that no longer resolves.

coilyco-ops referenced this issue from a pull request that will close it,

2026-08-16 05:53:54 +00:00

fix(aos-cli): seal mcp-beaver under the name it actually has #1092