Adopt issue-reference guard as first N+1 repo #5

New issue

Closed

opened 2026-07-09 18:51:52 +00:00 by coilyco-ops · 2 comments

coilyco-ops commented

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

Member

Use coilyco-flight-deck/reddit-mcp as the first N+1 rollout repo for the AOS issue-reference-guard hook after agentic-os#341 narrowed the parser.

Scratch measurement from 2026-07-09, using the post-agentic-os#341 hook implementation, found 5 hits:

AGENTS.md:49
README.md:5
README.md:50
docs/FEATURES.md:38
src/reddit_mcp/__init__.py:4

Acceptance:

Enable the hook in this repo with the normal AOS pre-commit configuration path.
Fix the five durable issue references instead of broadly excluding docs or source.
Add only narrow generated-file exclusions if a real generated surface appears.
Run the hook locally and leave the repo passing.
Feed any generic false-positive category back to coilyco-flight-deck/agentic-os#381 instead of hiding it locally.

This is intentionally not ward or infrastructure; those still have large downstream violation counts and are poor first N+1 candidates.

Use `coilyco-flight-deck/reddit-mcp` as the first N+1 rollout repo for the AOS `issue-reference-guard` hook after `agentic-os#341` narrowed the parser. Scratch measurement from 2026-07-09, using the post-`agentic-os#341` hook implementation, found 5 hits: * `AGENTS.md:49` * `README.md:5` * `README.md:50` * `docs/FEATURES.md:38` * `src/reddit_mcp/__init__.py:4` Acceptance: * Enable the hook in this repo with the normal AOS pre-commit configuration path. * Fix the five durable issue references instead of broadly excluding docs or source. * Add only narrow generated-file exclusions if a real generated surface appears. * Run the hook locally and leave the repo passing. * Feed any generic false-positive category back to `coilyco-flight-deck/agentic-os#381` instead of hiding it locally. This is intentionally not `ward` or `infrastructure`; those still have large downstream violation counts and are poor first N+1 candidates.

coilyco-ops commented

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

Author

Member

WARD-RESERVATION: held 🔒

reservation details

Holder: container engineer-codex-reddit-mcp-5 on host kais-macbook-pro-2.local.

Reserved by ward agent --harness codex (reserved 2026-07-09T18:52:06Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (1h TTL). --force overrides.

Do not comment on or edit this issue to steer the run while it is reserved. The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a new issue, dispatched fresh. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494).

run seed context — what this run is carrying (ward#609)

Resolved: coilyco-flight-deck/reddit-mcp#5 · branch issue-5 · harness codex · workflow direct-to-main
Run: engineer-codex-reddit-mcp-5 · ward v0.493.0 · dispatched 2026-07-09T18:52:06Z
Comment thread: 0 included in the pre-flight read, 0 stripped (ward's own automated comments).

Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.493.0).

— Codex, via ward agent

WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-codex-reddit-mcp-5` on host `kais-macbook-pro-2.local`. Reserved by `ward agent --harness codex` (reserved 2026-07-09T18:52:06Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (1h TTL). `--force` overrides. **Do not comment on or edit this issue to steer the run while it is reserved.** The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a **new issue, dispatched fresh**. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494). <details><summary>run seed context — what this run is carrying (ward#609)</summary> - **Resolved:** `coilyco-flight-deck/reddit-mcp#5` · branch `issue-5` · harness `codex` · workflow `direct-to-main` - **Run:** `engineer-codex-reddit-mcp-5` · ward `v0.493.0` · dispatched `2026-07-09T18:52:06Z` - **Comment thread:** 0 included in the pre-flight read, 0 stripped (ward's own automated comments). Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.493.0). </details> </details>  — Codex, via `ward agent`

coilyco-ops referenced this issue from a commit

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

feat: adopt issue reference guard

coilyco-ops closed this issue

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

coilyco-ops commented

2026-07-09 19:01:34 +00:00

Author

Member

WARD-OUTCOME: done ✅

details

workflow: direct-to-main; review summary: review gate skipped by ~/.ward/config.yaml default felt: a small but fussy rollout. The hook source pin, stage override, and footer reconciliation all had to line up. confidence: high surprises: the first agentic-os tag with the guard lived on the Forgejo canonical remote, not the GitHub mirror. follow-ups: none

WARD-OUTCOME: done ✅ <details><summary>details</summary> workflow: direct-to-main; review summary: review gate skipped by ~/.ward/config.yaml default felt: a small but fussy rollout. The hook source pin, stage override, and footer reconciliation all had to line up. confidence: high surprises: the first agentic-os tag with the guard lived on the Forgejo canonical remote, not the GitHub mirror. follow-ups: none </details>