docs(agentos): mark completed projection follow-up slots

[shaun0927]

Summary

Updates docs/agentos/projection-followups.md so the "Next safe PR slots" table reflects which slots have already shipped vs. which remain open. The Wave 1 plan in #1131 treated this table as a list of "next safe slots" to schedule, but it actually lists eligible slots regardless of implementation state — so #1061 (Artifact/Verdict populator) and #1064 (Status JSON CLI) were planned again even though they had already shipped.

Refs #1131, #946 (parent: #946).

Changes

• Mark Artifact/Verdict projection as ✅ shipped via feat(harness): project artifact and verdict records #1061.
• Mark Status JSON CLI as ✅ shipped via feat(cli): expose status run projection JSON #1064.
• Clarify Mechanical-evaluation fixture as open in PR test(harness): add mechanical-evaluation projection fixture #1132 until that PR merges, and remove the stale wording that implied the slot had already landed.
• Add a short note above the table explaining the ✅ convention so future planners see the shipped vs open distinction at a glance.
• Preserve the remaining slots (StepSnapshot/session/runtime views, Context/checkpoint anchors, Optional exporter sinks) and the "Explicit anti-actions" / "Review checklist" boundaries.

Out of scope

• No code changes.
• No other doc files touched.
• No change to slot semantics, boundary rules, or v1 scope.
• No new slots added.
• No new AgentOS surface or source of truth.

Test plan

• git diff --check -- docs/agentos/projection-followups.md
• Local invariant check confirms the test(harness): add mechanical-evaluation projection fixture #1132 row says "Open in PR test(harness): add mechanical-evaluation projection fixture #1132 until merged", preserves "EventStore remains the source of truth", and says the slot does not create a new AgentOS surface.
• GitHub Actions on head f5732096fb80a00db001fa679484add848868b43: Ruff Lint, MyPy Type Check, Bridge TypeScript, Python 3.12/3.13/3.14 tests, enforce-envelope, and enforce-boundary all passed.

[shaun0927]

Re-review requested for current head f5732096fb80a00db001fa679484add848868b43 after the follow-up docs commit.

What changed after the first push:

• Removed the ambiguous Mechanical-evaluation fixture wording that said open PR #1132 in one cell while the Boundary cell implied it had already landed.
• The row now explicitly says PR test(harness): add mechanical-evaluation projection fixture #1132 remains open until merged.
• The boundary now reiterates that this is an offline/local read-model fixture slot, EventStore remains the source of truth, and no new AgentOS surface is created.

Validation:

• git diff --check -- docs/agentos/projection-followups.md
• Local invariant check for the test(harness): add mechanical-evaluation projection fixture #1132 row / EventStore SSOT / no-new-surface wording.
• GitHub Actions are green on this head.

Please re-run any Ouroboros/design-note/warden review against this head.

[shaun0927]

Merge-readiness assessment for PR #1136

This PR is merge-ready from the AgentOS roadmap/SSOT perspective.

What this PR changes

PR #1136 is a narrow docs-only correction to docs/agentos/projection-followups.md. It clarifies that the "Next safe PR slots" table is an eligible-slot queue companion, not a second source of truth and not a list of only unimplemented work.

The current head (f5732096fb80a00db001fa679484add848868b43) now:

• marks Artifact/Verdict projection as ✅ shipped via feat(harness): project artifact and verdict records #1061;
• marks Status JSON CLI as ✅ shipped via feat(cli): expose status run projection JSON #1064;
• clarifies Mechanical-evaluation fixture as open in PR test(harness): add mechanical-evaluation projection fixture #1132 until merged;
• tightens the test(harness): add mechanical-evaluation projection fixture #1132 boundary to an offline/local read-model fixture only;
• explicitly preserves the invariant that EventStore remains the source of truth;
• explicitly states that this slot does not create a new AgentOS surface.

Alignment with #961 / AgentOS SSOT

This matches the direction established by #961 because it reduces scheduling ambiguity without changing AgentOS semantics. The PR does not introduce a new roadmap authority, projection schema, evidence model, runtime behavior, cache, exporter, or execution/resume authority. It keeps projection-followups.md as a non-authoritative companion to #961, #946, and the canonical projection scope docs.

Over-engineering / design risk review

I do not see over-engineering here. The change is deliberately small: one docs file, 8 additions and 3 deletions. It fixes stale/ambiguous status labels that previously made completed and still-open follow-up slots look equivalent. That is exactly the kind of minimal roadmap hygiene needed to prevent duplicate worker dispatches and misread Wave 1 sequencing.

The follow-up commit also removed the only ambiguity I found during review: the Mechanical-evaluation fixture row previously said open PR #1132 while the boundary cell implied the fixture had already landed. The current wording is internally consistent and safer for both humans and automation.

Validation

• GitHub Actions are green on head f5732096fb80a00db001fa679484add848868b43:
  • Ruff Lint
  • MyPy Type Check
  • Python 3.12 tests
  • Python 3.13 tests
  • Python 3.14 tests
  • Bridge TypeScript
  • enforce-envelope
  • enforce-boundary
• git diff --check -- docs/agentos/projection-followups.md passes locally.
• Local invariant check passes for the corrected test(harness): add mechanical-evaluation projection fixture #1132 wording, EventStore SSOT wording, and no-new-AgentOS-surface wording.
• PR merge state is CLEAN / mergeable.

Verdict

APPROVE / merge-ready. The PR is a bounded docs-only correction aligned with #961 and the AgentOS SSOT direction, with no blocking design, implementation, or test concerns.

[shaun0927]

PR review analysis

Verdict: APPROVE

Scope reviewed

• PR: docs(agentos): mark completed projection follow-up slots #1136
• Head: f5732096fb80a00db001fa679484add848868b43
• Changed file: docs/agentos/projection-followups.md
• Diff size: 1 file, 8 additions, 3 deletions
• Related SSOT context: Meta SSOT: AgentOS roadmap sequencing (#920–#960) #961 AgentOS roadmap sequencing, [Feature] Define Run/Step/Artifact projections as the canonical harness vocabulary #946 projection follow-up lane, AgentOS Wave 1: implement #946 S1/S2/S3 + #956 N1/N2 + #939 PR E #1131 Wave 1 planning thread, feat(harness): project artifact and verdict records #1061, feat(cli): expose status run projection JSON #1064, test(harness): add mechanical-evaluation projection fixture #1132

Findings

Blocking issues

None.

Major issues

None.

Minor issues

None.

Nits

None.

Review rationale

The current diff is a minimal documentation correction that improves the projection follow-up queue without expanding scope. It keeps docs/agentos/projection-followups.md explicitly subordinate to #961 and the canonical #946/projection scope sources. The ✅ convention makes shipped slots distinguishable from still-open slots, which directly addresses the stale roadmap interpretation that caused already-shipped work (#1061 and #1064) to be treated as schedulable again.

The Mechanical-evaluation fixture row is now correctly bounded: PR #1132 remains open until merged, the fixture is offline/local/read-model-only, EventStore remains the source of truth, and no new AgentOS surface is created. This resolves the previous internal inconsistency between "open PR #1132" and wording that implied the slot had already landed.

Because this PR changes documentation only, it does not affect runtime behavior, persistence semantics, projection authority, evidence/verifier policy, plugin permissions, HITL resume behavior, Workflow IR dispatch, or exporter/caching behavior. The anti-actions and review checklist remain intact.

Validation reviewed

• GitHub Actions: all required checks are successful on the current head.
• Local formatting/sanity: git diff --check -- docs/agentos/projection-followups.md passes.
• Local invariants: corrected test(harness): add mechanical-evaluation projection fixture #1132 row, EventStore SSOT wording, and no-new-AgentOS-surface wording are present.
• Mergeability: PR reports CLEAN / mergeable.

Final recommendation

APPROVE. This PR is safe to merge as a docs-only AgentOS roadmap hygiene fix.

[shaun0927]

@ouroboros-agent re-review

[shaun0927]

@ouroboros-agent re-review current head 48811ab15c7169598d27d1b3792b295a2ef8d2d6.

This is a no-op retrigger commit after no bot/design-note response was observed on the previous request. Please check the AgentOS/#961 alignment and design-note/warden concerns for PR #1136 against this exact head.

[Q00]

Re review ping

[Q00]

Re review ping

[Q00]

Roadmap-gate check: this docs-only PR is aligned with #961 / #946 as a status correction for projection follow-up slots. It does not advance gated Tier 2+ implementation, does not reopen the closed agentos-substrate-wiring milestone, and does not stale the canonical SSOT. No warden gate block.

Posted by agentos-roadmap-warden — bot. Reply with /warden ignore to suppress further comments on this thread.

[shaun0927]

@ouroboros-agent re-review current head ea6e14dca719 / ea6e14dca71983d71ba372f4d53f3679f7194bdf.

This is a no-op retrigger commit after the latest bounded AgentOS/#961 audit. Please check PR #1136 against the AgentOS SSOT, design-note concerns, and roadmap/warden gate:

• docs-only status correction in docs/agentos/projection-followups.md;
• keeps the note explicitly non-authoritative under Meta SSOT: AgentOS roadmap sequencing (#920–#960) #961 and [Feature] Define Run/Step/Artifact projections as the canonical harness vocabulary #946;
• marks feat(harness): project artifact and verdict records #1061 and feat(cli): expose status run projection JSON #1064 as shipped;
• keeps test(harness): add mechanical-evaluation projection fixture #1132 explicitly open until merged;
• preserves EventStore as the source of truth and creates no new AgentOS surface.

Local/Codex audit found no changes needed; please emit the current-head design-note / approval verdict if clean.

[ouroboros-agent]

Review — ouroboros-agent[bot]

Verdict: APPROVE

Reviewing commit ea6e14d for PR #1136

Review record: 7b172738-6a4c-4b93-b611-8a520925f23c

Blocking Findings

No in-scope blocking findings remained after policy filtering.

Non-blocking Suggestions

None.

Design Notes

Unable to assess architecture or changed behavior because the local source snapshot and patch could not be read in this environment.

Policy Notes

• Omitted 1 finding(s) that referenced files outside the current PR changed-files scope.

Recovery Notes

First recoverable review artifact generated from codex analysis log.

---

Reviewed by ouroboros-agent[bot] via Codex deep analysis

[shaun0927]

Merge-readiness assessment for PR #1136

I re-reviewed PR #1136 against the current head ea6e14dca719 (ea6e14dca71983d71ba372f4d53f3679f7194bdf) and the #961 AgentOS SSOT direction.

What this PR changes

This is a narrow docs-only correction to docs/agentos/projection-followups.md:

• clarifies that the "Next safe PR slots" table lists eligible slots, not only unimplemented slots;
• marks Artifact/Verdict projection as shipped via feat(harness): project artifact and verdict records #1061;
• marks Status JSON CLI as shipped via feat(cli): expose status run projection JSON #1064;
• keeps Mechanical-evaluation fixture explicitly open in PR test(harness): add mechanical-evaluation projection fixture #1132 until that PR merges;
• preserves the boundaries that projection follow-ups are read-model-only, EventStore remains the source of truth, and this note is subordinate to Meta SSOT: AgentOS roadmap sequencing (#920–#960) #961 / [Feature] Define Run/Step/Artifact projections as the canonical harness vocabulary #946 rather than a second roadmap SSOT.

AgentOS / #961 alignment

This PR is aligned with the AgentOS roadmap direction in #961. It reduces scheduling ambiguity in a non-authoritative queue companion, while preserving the canonical authority of #961 and the #946 projection lane. It does not introduce a new AgentOS surface, projection schema, evidence/verifier policy, cache, exporter behavior, runtime behavior, resume authority, or planning/dispatch authority.

Over-engineering / implementation direction

I do not see over-engineering or an odd implementation direction. The effective code review scope is one Markdown file with 8 additions and 3 deletions. The change fixes stale roadmap/status labels that could otherwise cause already-shipped work (#1061/#1064) to be scheduled again. The #1132 row is also bounded correctly as an offline/local read-model fixture until that PR merges.

Bot / design-note status

• ouroboros-agent[bot] approved the current head ea6e14d with Verdict: APPROVE, no blocking findings, and no non-blocking suggestions.
• The roadmap warden review reported no gate block for the docs-only Meta SSOT: AgentOS roadmap sequencing (#920–#960) #961/[Feature] Define Run/Step/Artifact projections as the canonical harness vocabulary #946 status correction.
• The bot design-note section included a recoverable environment caveat about not reading the local snapshot, but it did not identify any in-scope design problem; the formal verdict is still current-head APPROVED.

Validation

• GitHub checks on current head: Ruff Lint, Python 3.12/3.13/3.14 tests, MyPy, Bridge TypeScript, enforce-envelope, and enforce-boundary all completed successfully.
• Local validation run on the isolated worktree:
  • git diff --check b6169f82a12407722522cc5cf04e1a85a4ac5de7..HEAD -- docs/agentos/projection-followups.md
  • invariant check for Meta SSOT: AgentOS roadmap sequencing (#920–#960) #961/[Feature] Define Run/Step/Artifact projections as the canonical harness vocabulary #946 non-authoritative wording, feat(harness): project artifact and verdict records #1061/feat(cli): expose status run projection JSON #1064 shipped markers, test(harness): add mechanical-evaluation projection fixture #1132 open-until-merged wording, EventStore SSOT wording, and no-new-AgentOS-surface wording.

Recommendation

Merge-ready. This PR is a minimal roadmap hygiene correction, has current-head bot approval, has green checks, and preserves the AgentOS SSOT boundaries needed for safe sequencing.

[shaun0927]

PR Review Summary

Verdict

Approve

Scope Reviewed

• PR intent: docs-only status correction for docs/agentos/projection-followups.md, keeping the projection follow-up queue aligned with Meta SSOT: AgentOS roadmap sequencing (#920–#960) #961 / [Feature] Define Run/Step/Artifact projections as the canonical harness vocabulary #946.
• Main changed areas: one Markdown table and its explanatory preface in docs/agentos/projection-followups.md.
• Tests reviewed: no new runtime tests are required for this docs-only PR; reviewed current GitHub check rollup and local documentation invariants instead.
• Checks considered: current-head GitHub checks all successful; local git diff --check; local invariant scan for shipped/open slot wording and AgentOS boundary wording.

Blocking Issues

None.

Warnings

None.

Mutation-Test Thinking

• Likely mutants that should be killed: stale status wording that marks an open slot as landed; removal of EventStore-as-SSOT wording; removal of shipped markers for feat(harness): project artifact and verdict records #1061/feat(cli): expose status run projection JSON #1064; wording that turns this companion document into a second roadmap authority.
• Mutants current tests may not catch: because this is documentation-only, runtime tests would not catch semantic drift in the roadmap text.
• Additional tests recommended: no committed test needed for this small docs-only correction. The local invariant scan covered the relevant contract phrases for this review.

Complexity / CRAP-style Risk

• High-risk functions/modules: None; no source code changed.
• Complexity increase: None; the diff adds a small status convention and three clarified table rows.
• Test coverage concern: None for runtime behavior. Documentation semantic drift remains a review concern rather than a code-coverage concern.
• Refactoring recommendation: None.

Test Quality Assessment (6/7)

• Strong tests: Existing CI remains green across lint, type, Python matrix, boundary, and envelope checks.
• Weak tests: Runtime tests are not meaningful for this Markdown-only status correction.
• Missing edge cases: No runtime edge cases introduced.
• Mocking concerns: None.

Security / Operational Risk

None. The PR does not touch runtime behavior, persistence, evidence policy, plugin permissions, HITL resume authority, Workflow IR dispatch, exporters, caching, secrets, or provider payload handling.

Looks Good

• Keeps projection-followups.md explicitly subordinate to Meta SSOT: AgentOS roadmap sequencing (#920–#960) #961 and the canonical [Feature] Define Run/Step/Artifact projections as the canonical harness vocabulary #946 projection scope.
• Correctly distinguishes shipped slots (feat(harness): project artifact and verdict records #1061/feat(cli): expose status run projection JSON #1064) from still-open follow-up work.
• Correctly bounds test(harness): add mechanical-evaluation projection fixture #1132 as open until merged and read-model-only.
• Preserves the EventStore source-of-truth boundary and avoids creating a new AgentOS surface.
• Current-head ouroboros-agent[bot] verdict is APPROVE with no blocking findings and no non-blocking suggestions.

Final Recommendation

Approve / merge-ready. The PR is a minimal, well-bounded documentation hygiene update that reduces roadmap scheduling ambiguity without changing AgentOS semantics or creating a second SSOT.