coilyco-flight-deck/node-stats-mcp
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Adopt issue-reference guard as second N+1 repo #4

New issue
Closed
opened 2026-07-09 19:28:12 +00:00 by coilyco-ops · 2 comments
coilyco-ops commented 2026-07-09 19:28:12 +00:00
Member
Copy link

Use coilyco-flight-deck/node-stats-mcp as the next N+1 rollout repo for the AOS issue-reference-guard hook after coilyco-flight-deck/reddit-mcp#5 landed.

Why this repo:

  • It is the next-smallest measured candidate from the scratch pass after reddit-mcp.
  • It has the same cleanup shape as reddit-mcp: durable docs/footer refs plus a small source docstring pattern.
  • It is more useful than jumping to backend or website, whose counts are larger and would turn the test into a broader cleanup.

Fresh spot-check on 2026-07-09 found these likely hits:

  • README.md:5 - coilyco-gaming/eco-app#42
  • README.md:33 - cross-reference footer to agentic-os#59
  • AGENTS.md:49 - cross-reference footer to agentic-os#59
  • docs/FEATURES.md:39 - cross-reference footer to agentic-os#59
  • src/node_stats_mcp/server.py:13 - eco-app#42
  • src/node_stats_mcp/__init__.py:3 - local #1 prose pattern
  • src/node_stats_mcp/__init__.py:4 - coilyco-gaming/eco-app#42

Acceptance:

  • Enable the hook in this repo with the normal AOS pre-commit configuration path.
  • Fix or rephrase the durable issue references instead of broadly excluding docs or source.
  • Treat the source docstring hits as a useful parser/policy check; if they are legitimate permanent provenance rather than stale tracker refs, document the narrow local decision or feed the false-positive category back to coilyco-flight-deck/agentic-os#381.
  • Run the hook locally and leave the repo passing.
  • Do not hide the rollout behind a broad repo-level disable.

Related:

  • coilyco-flight-deck/agentic-os#381
  • coilyco-flight-deck/reddit-mcp#5
Use `coilyco-flight-deck/node-stats-mcp` as the next N+1 rollout repo for the AOS `issue-reference-guard` hook after `coilyco-flight-deck/reddit-mcp#5` landed. Why this repo: * It is the next-smallest measured candidate from the scratch pass after `reddit-mcp`. * It has the same cleanup shape as `reddit-mcp`: durable docs/footer refs plus a small source docstring pattern. * It is more useful than jumping to `backend` or `website`, whose counts are larger and would turn the test into a broader cleanup. Fresh spot-check on 2026-07-09 found these likely hits: * `README.md:5` - `coilyco-gaming/eco-app#42` * `README.md:33` - cross-reference footer to `agentic-os#59` * `AGENTS.md:49` - cross-reference footer to `agentic-os#59` * `docs/FEATURES.md:39` - cross-reference footer to `agentic-os#59` * `src/node_stats_mcp/server.py:13` - `eco-app#42` * `src/node_stats_mcp/__init__.py:3` - local `#1` prose pattern * `src/node_stats_mcp/__init__.py:4` - `coilyco-gaming/eco-app#42` Acceptance: * Enable the hook in this repo with the normal AOS pre-commit configuration path. * Fix or rephrase the durable issue references instead of broadly excluding docs or source. * Treat the source docstring hits as a useful parser/policy check; if they are legitimate permanent provenance rather than stale tracker refs, document the narrow local decision or feed the false-positive category back to `coilyco-flight-deck/agentic-os#381`. * Run the hook locally and leave the repo passing. * Do not hide the rollout behind a broad repo-level disable. Related: * `coilyco-flight-deck/agentic-os#381` * `coilyco-flight-deck/reddit-mcp#5`
coilyco-ops commented 2026-07-09 19:28:24 +00:00
Author
Member
Copy link

WARD-RESERVATION: held 🔒

reservation details

Holder: container engineer-codex-node-stats-mcp-4 on host kais-macbook-pro-2.local.

Reserved by ward agent --harness codex (reserved 2026-07-09T19:28:22Z). 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/node-stats-mcp#4 · branch issue-4 · harness codex · workflow direct-to-main
  • Run: engineer-codex-node-stats-mcp-4 · ward v0.493.0 · dispatched 2026-07-09T19:28:22Z
  • 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-agent-reservation --> WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-codex-node-stats-mcp-4` on host `kais-macbook-pro-2.local`. Reserved by `ward agent --harness codex` (reserved 2026-07-09T19:28:22Z). 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/node-stats-mcp#4` · branch `issue-4` · harness `codex` · workflow `direct-to-main` - **Run:** `engineer-codex-node-stats-mcp-4` · ward `v0.493.0` · dispatched `2026-07-09T19:28:22Z` - **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> <!-- ward-agent-signature --> — Codex, via `ward agent`
coilyco-ops commented 2026-07-09 19:38:19 +00:00
Author
Member
Copy link

WARD-OUTCOME: done ✅

details

workflow: direct-to-main; review summary: review gate skipped by ~/.ward/config.yaml default
felt: mostly config cleanup, then one policy clash between catalog-trifecta and the new guard
confidence: high
surprises: the GitHub mirror lacked issue-reference-guard, so the canonical Forgejo remote was required
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: mostly config cleanup, then one policy clash between catalog-trifecta and the new guard confidence: high surprises: the GitHub mirror lacked issue-reference-guard, so the canonical Forgejo remote was required follow-ups: none </details>
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
issue-1
No results found.
Labels
Clear labels
  
coherence-core
Core review set for the warded control plane coherence milestone. These issues form the release spine; adjacent milestone issues are stretch or supporting work.

  
consult
A human decision, design, or external action must happen first. Fail-closed default for unlabeled/low-confidence.

  
headless
Agent can take it from open issue to merged change with no human in the loop. The auto-burndown queue.

  
interactive
Agent does the work but pauses at a human checkpoint mid-flight (design choice, destructive step, human-only verification).

  
P0
now / blocking / urgent

  
P1
next / important

  
P2
backlog / will do

  
P3
someday / low

  
P4
icebox / frozen / reopen if it becomes real

No labels
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
coilyco-flight-deck/node-stats-mcp#4
No description provided.