orchestrator-workflow 0.11.0 → 0.13.0

package/CHANGELOG.md

@@ -5,6 +5,61 @@ All notable changes to `orchestrator-workflow` are documented here.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.13.0] - 2026-07-18
+
+### Changed
+
+- `05-review-findings.md`'s findings-table placeholder/legend row
+  (`| low/medium/high/critical | ... | accepted/defer |`) now carries a
+  comment stating its fail-closed semantics: replace this row when
+  transferring reviewer findings (step 7), or delete it outright for a
+  genuine zero-findings review (a header row with no data rows is valid; a
+  leftover legend row next to real finding rows is also fine). `SKILL.md`'s
+  step 7 gains a matching one-sentence rule. This is the contract half of a
+  fix for a mixed-state bypass in grounding-mcp's orchestrator-workflow
+  completeness reader: the reader identifies a real finding row by its
+  Severity cell carrying a single concrete value, so the shipped slash-list
+  legend row was never counted as a finding — a run that filled the
+  `acceptance-recommendation` marker with `accept` but left this row
+  byte-for-byte as shipped read as `complete: true` with zero findings,
+  indistinguishable from a genuine zero-findings review. The runtime half
+  (the reader treating a survived, unaccompanied placeholder row as an
+  explicit format blocker instead of silently reporting zero findings) is a
+  lockstep sibling change in grounding-mcp's own release, outside this
+  package. In this package the change is docs/template/test-only: no
+  runtime behavior changes here, the completeness reader itself is not part
+  of this package, and the fail-closed enforcement only takes effect once
+  grounding-mcp ships its lockstep sibling change (agent-tasks task
+  8f173547); do not tag/publish this 0.13.0 release before that change ships
+  (release ordering). A template-markers test pins the placeholder row's
+  literal wording (mutation-checked, matching the reader's literal match) and
+  that the replace/delete rule is documented next to it. Motivated by
+  agent-tasks task fa0eca65.
+
+## [0.12.0] - 2026-07-16
+
+### Added
+
+- `SKILL.md`'s Hand off step (9) gains an optional bundle-upkeep hook,
+  symmetric to the 0.8.0 discovery-side rule: when the repo carries a
+  curated knowledge bundle (for example a `docs/okf/` directory with an
+  index), the orchestrator checks before handoff whether the change touches
+  paths any bundle doc claims as sources, and if so either updates the
+  affected docs (re-verify and re-stamp) or records a follow-up task, and
+  runs the bundle validator when one is available (for example `okf-kit
+  check`). The hook is optional guidance, never a gate: repos without a
+  bundle are unaffected. `06-handoff.md` gained a matching optional
+  "Knowledge Bundle" section so the outcome (updated / not affected /
+  follow-up filed) is recorded alongside the rest of the handoff. Motivated
+  by the OKF initiative's Phase 3 evidence: four upkeep sweeps on 2026-07-16
+  found 48/24/11/8 stale claims accumulated in the four oldest bundles, with
+  warn-only drift CI already live in 8 repos — discovery-side consumption
+  shipped in 0.8.0 and named this hook as its symmetric, still-missing,
+  loop-closer. Docs-consistency tests pin the hook's source-overlap check,
+  its two responses, the validator run, and its explicit non-gate
+  optionality, plus the handoff template's new section and outcome
+  vocabulary.
+
 ## [0.11.0] - 2026-07-16
 
 ### Added

package/assets/skill/SKILL.md

@@ -118,6 +118,10 @@ directory and the subagents.
    transfer each finding from the reviewer output contract into the table's
    columns as-is, keeping the Severity and Decision headers unchanged, since
    those two are what the orchestrator-workflow completeness reader verifies.
+   Replace the shipped placeholder/legend row with the transferred findings;
+   for a genuine zero-findings review, delete that row instead of leaving it
+   in place, since the completeness reader treats an untouched placeholder
+   row with no finding rows as the template never having been filled in.
 8. **Decide acceptance.** Accept, request fixes, defer, or escalate to the
    operator. High or critical findings block acceptance until fixed or
    explicitly waived: critical findings require operator sign-off; high
@@ -125,8 +129,15 @@ directory and the subagents.
    or critical finding counts as a waiver and follows the same rules. Record
    all decisions and waivers in `03-decisions.md` and summarize waivers in
    the Accepted Waivers section of `06-handoff.md`.
-9. **Hand off.** Fill `06-handoff.md` and report to the operator: what changed,
-   why, how it was verified, known risks, accepted waivers, suggested next step.
+9. **Hand off.** Before filling `06-handoff.md`, apply this optional
+   guidance: when the repo carries a curated knowledge bundle (for example a
+   `docs/okf/` directory with an index), check whether the change touches
+   paths any bundle doc claims as sources; if so, update the affected docs
+   (re-verify and re-stamp) or record a follow-up task, and run the bundle
+   validator when one is available (for example `okf-kit check`). Repos
+   without a bundle are unaffected. Then fill `06-handoff.md` and report to the
+   operator: what changed, why, how it was verified, known risks, accepted
+   waivers, suggested next step.
 
 When finalizing `05-review-findings.md` and `06-handoff.md`, replace the `TODO`
 in each `<!-- solution-acceptance: ... = TODO -->` marker with the chosen enum

package/assets/templates/05-review-findings.md

@@ -11,6 +11,7 @@
 | Severity | Category | Description | Suggested Fix | Decision |
 |---|---|---|---|---|
 | low/medium/high/critical | correctness/architecture/security/tests/maintainability/performance/docs | <!-- finding --> | <!-- fix --> | accepted/defer |
+<!-- This row is the shipped template placeholder, not a finding: the orchestrator-workflow completeness reader fails the completeness gate closed when this exact row survives untouched and no concrete finding row has been added, the same way a `TODO` marker does. During findings transfer (step 7), replace this row with each reviewer finding. For a genuine zero-findings review, delete this row instead — a header row with no data rows is a valid, complete table; leaving this row next to real finding rows is also fine. This mirrors grounding-mcp's placeholder-row detection; keep the two in sync. -->
 
 ## Missing Tests
 

package/assets/templates/06-handoff.md

@@ -24,6 +24,14 @@
 |---|---|---|---|
 | <!-- finding --> | high/critical | <!-- rationale --> | operator/orchestrator |
 
+## Knowledge Bundle
+
+<!-- Optional: only applies when the repo carries a curated knowledge bundle
+     (for example a docs/okf/ directory). Outcome: updated | not affected |
+     follow-up filed. -->
+
+- <!-- outcome and brief note, or omit this section when the repo carries no bundle -->
+
 ## Follow-Ups
 
 - <!-- next steps or none -->

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "orchestrator-workflow",
-  "version": "0.11.0",
+  "version": "0.13.0",
   "description": "Installer for an orchestrator-led agent workflow: .ai/ run state, an AGENTS.md policy section, and per-harness subagent definitions for Claude Code, OpenAI Codex, and opencode",
   "main": "dist/index.js",
   "type": "module",