Stage issue-reference guard N+1 rollout after parser narrowing #381

New issue

Closed

opened 2026-07-09 18:44:04 +00:00 by coilyco-ops · 4 comments

coilyco-ops commented

2026-07-09 18:44:04 +00:00

Member

After agentic-os#341 landed, the issue-reference guard is narrower and AOS passes, but downstream scratch opt-in is still not enforcement-ready.

Fresh check on 2026-07-09 after commit 1fc55a7 fix: narrow issue-reference guard:

agentic-os itself: passes issue-reference-guard.
coilyco-flight-deck/ward scratch opt-in: 400 violations, down from 799 before #341.
coilyco-flight-deck/infrastructure scratch opt-in: 142 violations, down from 241 before #341.

This means the parser/policy fix helped, but N+1 rollout still needs a staged report-only baseline and repo-specific cleanup/allowlist decision.

Acceptance:

Choose one N+1 repo for a report-only adoption issue, likely infrastructure because the hit count is smaller and it exercises docs/scripts/systemd/Ansible surfaces.
Add a repo-owned issue that captures current hit count, generated-file exclusions, and actual cleanup categories.
Do not enable enforcement on that repo until the count is intentionally driven to zero or an allowlist is explicit and reviewed.
Feed any generic false-positive category back into AOS before broader rollout.

After `agentic-os#341` landed, the issue-reference guard is narrower and AOS passes, but downstream scratch opt-in is still not enforcement-ready. Fresh check on 2026-07-09 after commit `1fc55a7 fix: narrow issue-reference guard`: * `agentic-os` itself: passes `issue-reference-guard`. * `coilyco-flight-deck/ward` scratch opt-in: 400 violations, down from 799 before #341. * `coilyco-flight-deck/infrastructure` scratch opt-in: 142 violations, down from 241 before #341. This means the parser/policy fix helped, but N+1 rollout still needs a staged report-only baseline and repo-specific cleanup/allowlist decision. Acceptance: * Choose one N+1 repo for a report-only adoption issue, likely `infrastructure` because the hit count is smaller and it exercises docs/scripts/systemd/Ansible surfaces. * Add a repo-owned issue that captures current hit count, generated-file exclusions, and actual cleanup categories. * Do not enable enforcement on that repo until the count is intentionally driven to zero or an allowlist is explicit and reviewed. * Feed any generic false-positive category back into AOS before broader rollout.

coilyco-ops commented

2026-07-09 18:52:05 +00:00

Author

Member

Selected coilyco-flight-deck/reddit-mcp as the first N+1 rollout repo, instead of ward or infrastructure.

Reason: the post-agentic-os#341 scratch opt-in found only 5 hits, so it should exercise the rollout path without becoming a large historical cleanup. Filed the repo-owned work as coilyco-flight-deck/reddit-mcp#5.

Other measured candidates from the same scratch pass:

coilysiren/website: 92 hits.
coilyco-flight-deck/backend: 17 hits.
coilyco-flight-deck/node-stats-mcp: 7 hits.
coilyco-flight-deck/reddit-mcp: 5 hits.

Selected `coilyco-flight-deck/reddit-mcp` as the first N+1 rollout repo, instead of `ward` or `infrastructure`. Reason: the post-`agentic-os#341` scratch opt-in found only 5 hits, so it should exercise the rollout path without becoming a large historical cleanup. Filed the repo-owned work as `coilyco-flight-deck/reddit-mcp#5`. Other measured candidates from the same scratch pass: * `coilysiren/website`: 92 hits. * `coilyco-flight-deck/backend`: 17 hits. * `coilyco-flight-deck/node-stats-mcp`: 7 hits. * `coilyco-flight-deck/reddit-mcp`: 5 hits.

coilyco-ops commented

2026-07-09 19:28:19 +00:00

Author

Member

Next recommended N+1 after reddit-mcp is coilyco-flight-deck/node-stats-mcp.

Filed coilyco-flight-deck/node-stats-mcp#4 and dispatched it. Rationale: it is the next-smallest measured candidate, with about 7 hits, and it exercises the same docs/source-docstring boundary that made reddit-mcp useful without jumping to the larger backend or website cleanups.

Next recommended N+1 after `reddit-mcp` is `coilyco-flight-deck/node-stats-mcp`. Filed `coilyco-flight-deck/node-stats-mcp#4` and dispatched it. Rationale: it is the next-smallest measured candidate, with about 7 hits, and it exercises the same docs/source-docstring boundary that made `reddit-mcp` useful without jumping to the larger `backend` or `website` cleanups.

coilyco-ops commented

2026-07-09 19:46:13 +00:00

Author

Member

Follow-up on the second N+1 rollout: node-stats-mcp#4 landed, but Kai spotted two rollout quirks in commit 136a21e.

Filed coilyco-flight-deck/node-stats-mcp#5 to correct them:

Do not exempt the catalog-trifecta files from issue-reference-guard.
Pin the AOS hook by release tag, not raw commit SHA. The SHA used in the commit is tagged as v0.230.0.

The issue also notes that catalog-trifecta needs the durable features-release-tooling.md citation, not the old agentic-os#59 issue footer, so the two hooks should be made to pass together.

Follow-up on the second N+1 rollout: `node-stats-mcp#4` landed, but Kai spotted two rollout quirks in commit `136a21e`. Filed `coilyco-flight-deck/node-stats-mcp#5` to correct them: * Do not exempt the catalog-trifecta files from `issue-reference-guard`. * Pin the AOS hook by release tag, not raw commit SHA. The SHA used in the commit is tagged as `v0.230.0`. The issue also notes that `catalog-trifecta` needs the durable `features-release-tooling.md` citation, not the old `agentic-os#59` issue footer, so the two hooks should be made to pass together.

coilyco-ops commented

2026-07-09 21:33:12 +00:00

Author

Member

Triage pass on 2026-07-09: this staging issue has served its purpose.

N+1 selection happened:

reddit-mcp#5 was filed as the first N+1 adoption issue.
node-stats-mcp#4 landed as the second N+1.
node-stats-mcp#5 captured Kais two follow-up corrections: do not exempt catalog-trifecta, and pin the AOS hook tag rather than the commit hash.

The broader fleet count moved to coilysiren/inbox#187, with cli-guard cleanup started in coilyco-flight-deck/cli-guard#213. Closing this AOS staging tracker so remaining rollout work lives in the repo-owned cleanup issues plus inbox#187.

Triage pass on 2026-07-09: this staging issue has served its purpose. N+1 selection happened: * reddit-mcp#5 was filed as the first N+1 adoption issue. * node-stats-mcp#4 landed as the second N+1. * node-stats-mcp#5 captured Kais two follow-up corrections: do not exempt catalog-trifecta, and pin the AOS hook tag rather than the commit hash. The broader fleet count moved to coilysiren/inbox#187, with cli-guard cleanup started in coilyco-flight-deck/cli-guard#213. Closing this AOS staging tracker so remaining rollout work lives in the repo-owned cleanup issues plus inbox#187.

coilyco-ops closed this issue

2026-07-09 21:33:21 +00:00