okstra 0.228.2 → 0.230.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (124) hide show
  1. package/README.md +1 -5
  2. package/dist/cli-registry.mjs +0 -18
  3. package/dist/cli-registry.mjs.map +1 -1
  4. package/dist/commands/lifecycle/doctor.mjs +0 -15
  5. package/dist/commands/lifecycle/doctor.mjs.map +1 -1
  6. package/dist/lib/skill-catalog.mjs +4 -4
  7. package/dist/lib/skill-catalog.mjs.map +1 -1
  8. package/docs/architecture/storage-model.md +179 -13
  9. package/docs/architecture.md +13 -14
  10. package/docs/contributor-change-matrix.md +5 -5
  11. package/docs/project-structure-overview.md +16 -21
  12. package/package.json +1 -2
  13. package/runtime/BUILD.json +2 -2
  14. package/runtime/bin/lib/okstra/interactive.sh +2 -1
  15. package/runtime/bin/okstra-provider-exec.py +53 -4
  16. package/runtime/prompts/duties/code-reviewer.json +5 -2
  17. package/runtime/prompts/launch.template.md +5 -5
  18. package/runtime/prompts/lead/convergence.md +4 -4
  19. package/runtime/prompts/lead/okstra-lead-contract.md +14 -13
  20. package/runtime/prompts/lead/phase-routing.md +1 -1
  21. package/runtime/prompts/lead/report-writer.md +3 -3
  22. package/runtime/prompts/lead/team-contract.md +3 -3
  23. package/runtime/python/okstra_ctl/agent/invocation.py +142 -5
  24. package/runtime/python/okstra_ctl/agent/prompt_cli/materialize.py +31 -1
  25. package/runtime/python/okstra_ctl/cmux.py +4 -2
  26. package/runtime/python/okstra_ctl/code_review_census.py +194 -0
  27. package/runtime/python/okstra_ctl/code_review_coverage.py +18 -5
  28. package/runtime/python/okstra_ctl/code_review_scope.py +11 -7
  29. package/runtime/python/okstra_ctl/code_review_target.py +79 -25
  30. package/runtime/python/okstra_ctl/conformance.py +61 -0
  31. package/runtime/python/okstra_ctl/conformance_evidence.py +235 -0
  32. package/runtime/python/okstra_ctl/correction_round.py +19 -13
  33. package/runtime/python/okstra_ctl/dispatch_core.py +1 -1
  34. package/runtime/python/okstra_ctl/dispatch_state.py +1 -0
  35. package/runtime/python/okstra_ctl/execution_mutation_audit.py +100 -2
  36. package/runtime/python/okstra_ctl/generated_input.py +21 -0
  37. package/runtime/python/okstra_ctl/ids.py +1 -41
  38. package/runtime/python/okstra_ctl/initial_prompt_materialization.py +30 -0
  39. package/runtime/python/okstra_ctl/interactive_cli.py +5 -0
  40. package/runtime/python/okstra_ctl/locks.py +28 -1
  41. package/runtime/python/okstra_ctl/model_io/renderers.py +17 -1
  42. package/runtime/python/okstra_ctl/paths.py +84 -31
  43. package/runtime/python/okstra_ctl/phases/catalog.py +3 -0
  44. package/runtime/python/okstra_ctl/phases/change_impact_analysis/spec.md +2 -2
  45. package/runtime/python/okstra_ctl/phases/discussion/spec.md +63 -63
  46. package/runtime/python/okstra_ctl/phases/discussion/wizard.py +2 -11
  47. package/runtime/python/okstra_ctl/phases/error_analysis/report_assets/error-analysis-input.template.md +1 -1
  48. package/runtime/python/okstra_ctl/phases/error_analysis/spec.md +2 -2
  49. package/runtime/python/okstra_ctl/phases/feature_analysis/spec.md +1 -1
  50. package/runtime/python/okstra_ctl/phases/final_verification/profile.md +4 -4
  51. package/runtime/python/okstra_ctl/phases/final_verification/report_assets/final-verification-input.template.md +1 -1
  52. package/runtime/python/okstra_ctl/phases/final_verification/spec.md +4 -4
  53. package/runtime/python/okstra_ctl/phases/implementation/host-rules.md +1 -1
  54. package/runtime/python/okstra_ctl/phases/implementation/instructions/_implementation-deliverable.md +2 -2
  55. package/runtime/python/okstra_ctl/phases/implementation/instructions/_implementation-executor.md +1 -1
  56. package/runtime/python/okstra_ctl/phases/implementation/instructions/_implementation-verifier.md +4 -4
  57. package/runtime/python/okstra_ctl/phases/implementation/report_assets/implementation-input.template.md +1 -1
  58. package/runtime/python/okstra_ctl/phases/implementation/spec.md +4 -4
  59. package/runtime/python/okstra_ctl/phases/implementation_option_selection/spec.md +2 -2
  60. package/runtime/python/okstra_ctl/phases/implementation_planning/instructions/plan-body-verification.md +11 -11
  61. package/runtime/python/okstra_ctl/phases/implementation_planning/plan_body.py +14 -0
  62. package/runtime/python/okstra_ctl/phases/implementation_planning/profile.md +4 -4
  63. package/runtime/python/okstra_ctl/phases/implementation_planning/report_assets/implementation-planning-input.template.md +1 -1
  64. package/runtime/python/okstra_ctl/phases/implementation_planning/spec.md +1 -1
  65. package/runtime/python/okstra_ctl/phases/project_analysis/spec.md +2 -2
  66. package/runtime/python/okstra_ctl/phases/release_handoff/entry.py +7 -3
  67. package/runtime/python/okstra_ctl/phases/release_handoff/report_assets/release-handoff-input.template.md +1 -1
  68. package/runtime/python/okstra_ctl/phases/release_handoff/spec.md +4 -4
  69. package/runtime/python/okstra_ctl/phases/technical_verification/spec.md +1 -1
  70. package/runtime/python/okstra_ctl/process_group.py +26 -3
  71. package/runtime/python/okstra_ctl/qa_commands.py +7 -2
  72. package/runtime/python/okstra_ctl/qa_procedures.py +60 -17
  73. package/runtime/python/okstra_ctl/recap.py +1 -2
  74. package/runtime/python/okstra_ctl/render.py +10 -2
  75. package/runtime/python/okstra_ctl/report_finalize.py +3 -3
  76. package/runtime/python/okstra_ctl/report_synthesis_packet.py +5 -0
  77. package/runtime/python/okstra_ctl/run.py +24 -20
  78. package/runtime/python/okstra_ctl/stage_command_commits.py +143 -0
  79. package/runtime/python/okstra_ctl/verification_capture.py +291 -0
  80. package/runtime/python/okstra_ctl/verification_conformance.py +182 -0
  81. package/runtime/python/okstra_ctl/verification_dispatch.py +130 -0
  82. package/runtime/python/okstra_ctl/verification_evidence.py +652 -0
  83. package/runtime/python/okstra_ctl/verification_generation.py +248 -0
  84. package/runtime/python/okstra_ctl/verification_input_ref.py +9 -0
  85. package/runtime/python/okstra_ctl/verification_input_types.py +23 -2
  86. package/runtime/python/okstra_ctl/verification_inputs.py +161 -23
  87. package/runtime/python/okstra_ctl/verification_invocation.py +139 -0
  88. package/runtime/python/okstra_ctl/verification_target.py +20 -5
  89. package/runtime/python/okstra_ctl/wizard/registry.py +2 -1
  90. package/runtime/python/okstra_ctl/wizard/render.py +2 -1
  91. package/runtime/python/okstra_ctl/wizard/sources.py +14 -3
  92. package/runtime/python/okstra_ctl/wizard/steps_identity.py +2 -1
  93. package/runtime/python/okstra_ctl/worker_runner.py +1 -1
  94. package/runtime/python/okstra_ctl/worktree_lock_cli.py +70 -17
  95. package/runtime/python/okstra_ctl/worktree_registry.py +4 -0
  96. package/runtime/skills/okstra-code-review/SKILL.md +84 -48
  97. package/runtime/skills/okstra-code-review/references/census-rules.md +10 -4
  98. package/runtime/skills/okstra-code-review/references/review-calibration.md +7 -4
  99. package/runtime/skills/okstra-explain-flow/SKILL.md +1 -1
  100. package/runtime/skills/okstra-run/SKILL.md +6 -6
  101. package/runtime/skills/okstra-schedule-gen/SKILL.md +3 -3
  102. package/runtime/skills/okstra-setup/SKILL.md +2 -3
  103. package/runtime/validators/validate-run.py +118 -52
  104. package/docs/cli.md +0 -1060
  105. package/docs/container.md +0 -100
  106. package/docs/follow-ups/2026-07-10-final-report-option-3.md +0 -51
  107. package/docs/performance-improvement-plan-v2.md +0 -369
  108. package/runtime/python/okstra_ctl/container.py +0 -702
  109. package/runtime/python/okstra_ctl/rollup.py +0 -241
  110. package/runtime/python/okstra_ctl/usage_report.py +0 -362
  111. package/runtime/skills/okstra-container-build/SKILL.md +0 -139
  112. package/runtime/skills/okstra-inspect/SKILL.md +0 -100
  113. package/runtime/skills/okstra-inspect/facets/cost.md +0 -84
  114. package/runtime/skills/okstra-inspect/facets/error-zip.md +0 -41
  115. package/runtime/skills/okstra-inspect/facets/errors.md +0 -69
  116. package/runtime/skills/okstra-inspect/facets/history.md +0 -86
  117. package/runtime/skills/okstra-inspect/facets/logs.md +0 -89
  118. package/runtime/skills/okstra-inspect/facets/recap.md +0 -167
  119. package/runtime/skills/okstra-inspect/facets/report.md +0 -57
  120. package/runtime/skills/okstra-inspect/facets/run-audit.md +0 -34
  121. package/runtime/skills/okstra-inspect/facets/status.md +0 -163
  122. package/runtime/skills/okstra-inspect/facets/time.md +0 -57
  123. package/runtime/skills/okstra-rollup/SKILL.md +0 -75
  124. package/runtime/skills/okstra-usage/SKILL.md +0 -71
@@ -6,11 +6,12 @@ description: >-
6
6
  unrelated to an okstra run. The tell is a review request over a diff:
7
7
  "review this stage", "review my branch", "code review", "leave the review
8
8
  in a file". The orchestrator censuses the diff into an explicit worklist,
9
- one to three reviewers (the user picks) each return a verdict for every cell
10
- against this project's coding-preflight rules, a coverage audit
11
- re-dispatches any gap, and the orchestrator settles what the reviewers
12
- disagree on. NOT for writing a PR body (okstra-pr-gen), starting a run
13
- (okstra-run), or inspecting a finished task (okstra-inspect).
9
+ one to three reviewers on distinct models (default two) each delegate structure, naming,
10
+ readability, general defects, state and tests to six same-model subagents.
11
+ Model reviewers consolidate their teams before the orchestrator settles the
12
+ combined findings. A coverage audit repeats missing checks on their original model and specialty slots,
13
+ and the orchestrator verifies and settles findings. NOT for writing a PR body (okstra-pr-gen), starting a run
14
+ (okstra-run).
14
15
  ---
15
16
 
16
17
  # OKSTRA Code Review
@@ -21,7 +22,7 @@ Review what a diff changed — one okstra implementation stage, or any branch
21
22
 
22
23
  A reviewer left to build its own worklist enumerates the diff differently every run, so every run finds different things. Here the worklist — the **census** — is built **once, by you, deterministically**, before any reviewer is dispatched. Reviewers receive their slice as input; they never rebuild, reinterpret, or extend it.
23
24
 
24
- Each reviewer accounts for every cell, so Step 3.5 can detect missing checks. Complete accounting does not prove that every defect was discovered. A follow-up keeps the full PR census but re-inspects only the correction's impact closure; unchanged verdicts require verified prior evidence and a current boundary attestation. Follow `references/census-rules.md#follow-up-review` before dispatch.
25
+ Each model reviewer owns the full census and delegates its rules to six specialty subagents. Each model's team covers the full census independently; another model's findings never substitute for missing checks. Complete accounting does not prove that every defect was discovered. A follow-up keeps the full PR census but re-inspects only the correction's impact closure; unchanged verdicts require verified prior evidence and a current boundary attestation. Reading full context is required even when only the correction is being re-evaluated. Follow `references/census-rules.md#follow-up-review` before dispatch. Assignment, context and retry boundaries are lead checks, not runtime guarantees.
25
26
 
26
27
  ## Rules
27
28
 
@@ -101,7 +102,7 @@ pass task manifests, target-CLI JSON, or arbitrary JSON fields to a reviewer.
101
102
 
102
103
  **The user owns the comparison base.** Both modes resolve the selected base to a fixed commit before returning `baseCommit`. Stage mode selects the recorded stage base unless the user explicitly overrides it. Carry the returned hash verbatim into every later command and the report. Do not substitute the default branch or an inferred parent.
103
104
 
104
- **Read the frozen head in both modes.** Run git in `worktreePath` when it is non-empty, otherwise in `projectRoot`; call that location `<gitRoot>`. Read every whole source file, caller and test with `git -C <gitRoot> show <headCommit>:<path>`, including clean observations. A checkout on the selected branch may contain uncommitted edits or move during review. `worktreePath` identifies a Git repository, not authority to read its working files. Branch targets leave it empty; a released stage can also have an empty path.
105
+ **Read the frozen head in both modes.** Run git in `worktreePath` when it is non-empty, otherwise in `projectRoot`; call that location `<gitRoot>`. Read every whole source file, caller and test with `git -C <gitRoot> show <headCommit>:<path>`, including clean observations. A checkout on the selected branch may contain uncommitted edits or move during review. `worktreePath` identifies a Git repository, not authority to read its working files. Branch targets leave it empty; a released stage can also have an empty path. Deleted targets are read with `git -C <gitRoot> show <baseCommit>:<path>`; surviving callers and contracts are still read at the head.
105
106
  **Then show the base and confirm it — branch mode and stage mode alike.** The CLI's answer is a recommendation the user has not seen yet, and a base nobody looked at is how unrelated commits slip into a review unnoticed. Print `baseCommit` verbatim next to `git -C <workdir> log -1 --oneline <baseCommit>` so the commit it names is legible, then ask with a 3-option picker:
106
107
 
107
108
  1. `Use <baseCommit>` — **the recommendation**, the value the CLI returned.
@@ -115,37 +116,54 @@ pass task manifests, target-CLI JSON, or arbitrary JSON fields to a reviewer.
115
116
  3. **Route the packs once, here — and fix both absolute paths the briefs carry.** `okstra paths --field home` prints the okstra home; read `<okstraHome>/prompts/coding-preflight/overview.md` and walk all three stages of its routed resource selection over the changed-file list. The result is the applied pack list — the absolute paths reviewers will read. This routing happens exactly once per run; no reviewer repeats it.
116
117
 
117
118
  The second path is this skill's own calibration file. A subagent has no "next to this file" coordinate, so the brief must spell it out: `okstra install` writes this skill to `~/.agents/skills/okstra-code-review/` on every machine (and to `~/.claude/skills/` only when `~/.claude` exists), making the literal path `~/.agents/skills/okstra-code-review/references/review-calibration.md` — the same string whether the skill was copied in or dev-linked. Carry it, together with the pack list, into every Step 3 brief.
118
- 4. Build the cells per `references/census-rules.md` and print, in this response: one cell table per axis, the exclusion list with a reason on every entry, and the applied pack list.
119
+ 4. Build the cells per `references/census-rules.md` with `okstra code-review census --project-root <projectRoot> --base <baseCommit> --head <headCommit> --rules <rules-path> --out <census-path>`, where `<rules-path>` holds the shared rule catalog for the routed packs; on a follow-up add `--previous-census <prior-census-path>` so identical targets keep their IDs. Exit 1 lists changed non-Python code under Unresolved function boundaries: add those function cells by hand before dispatch. Then print, in this response: one cell table per axis, the exclusion list with a reason on every entry, and the applied pack list.
119
120
  5. Restate both completion criteria and show they hold: censused files + exclusions = files in the diff, and every hunk maps to a censused function or to file-level code.
120
121
 
121
122
  **Membership is mechanical; judgment only ever decides a cell's verdict.** Never drop a cell because you doubt the rule applies to it — that doubt is the reviewer's answer, and its name is `clean`. Over-inclusion costs one line; a judged exclusion is the run-to-run variance this census exists to remove.
122
123
 
123
124
  A large census is never truncated. Report the cell count and confirm before dispatching — a silent cut is a false "I looked at everything" signal.
124
125
 
125
- ## Step 3 — Materialize and dispatch the reviewers in parallel
126
+ ## Step 3 — Select one to three model teams with six specialists each
126
127
 
127
- **Ask how many reviewers** with these choices:
128
+ Let the user choose one to three reviewers with distinct models at review start; the default is 2. Honor an explicit count without asking again. Otherwise offer 2 as the default/recommended choice, with 1 and 3 as alternatives. Carry the selected value as `<reviewerCount>`; use 2 when the user accepts the default or supplies no count. Keep that count for this review and its gap-fills. The instruction and its default are checked by the retired Python suite; the runtime count range is enforced by `resolve_operation_slots` and the retired Python suite. This skill is model-agnostic: do not hard-code provider names, model names or versions, preferred model order, or specialty-to-model mappings. Resolve the roster from the runtime's registered model pool for each new review:
128
129
 
129
- 1. `2 reviewers` — **the recommendation**: two different models each review the whole census.
130
- 2. `3 reviewers` — three different models each review the whole census; higher execution cost.
131
- 3. `1 reviewer` — cheaper; you adjudicate every finding it returns.
130
+ ```
131
+ okstra agent-prompt resolve-operation --operation code-review --count <reviewerCount>
132
+ ```
132
133
 
133
- Accept only `1`, `2` or `3`; a host may also allow direct text input.
134
+ It prints the duty, the role, the reviewer count, and one `slot` line per reviewer carrying that slot's
135
+ provider and model. The operation contract (`agents/operations/code-review.json`) owns the duty and count ceiling;
136
+ the duty supplies the role, and the runtime model pool supplies the provider/model assignments.
137
+ Always pass the selected count explicitly; the operation contract's count is the ceiling, not this skill's default.
138
+ A machine with too few distinct models fails here rather than quietly running fewer reviewers.
139
+ Dispatch exactly the returned slots; never replace them with a remembered or preferred model list.
140
+ Keep the resolved assignments within that review and its gap-fills. Child inheritance below refers to
141
+ the selected runtime assignment, never to a specific model required by this skill.
134
142
 
135
- Treat reviewer-count selection as authorization for the initial invocations only. Additional model calls require explicit authorization under Step 3.5; missing coverage or a formatting error does not authorize a retry. Instruction presence is checked by `tests/contract/test_standalone_agent_invocation_surfaces.py::test_code_review_dispatches_use_verified_standalone_invocations`; actual authorization remains a lead check.
143
+ Each returned slot is a model-team coordinator, not a specialty. Every coordinator receives the full census and delegates to six actual subagents using its exact provider/model assignment:
136
144
 
137
- Then ask the runtime what those reviewers run — do not choose the role or the providers here:
145
+ | Specialty within every model team | Assigned axis | Assigned rule IDs |
146
+ |---|---|---|
147
+ | Structure | `structural` | `S1`–`S4`, plus routed `S5`–`S10` |
148
+ | Naming | `semantic` | `M1` |
149
+ | Readability | `semantic` | `M2`, `M3` |
150
+ | General defects | `general` | `G1`–`G5` |
151
+ | State | `state-and-tests` | `T1` |
152
+ | Tests | `state-and-tests` | `T2`–`T4` |
138
153
 
139
- ```
140
- okstra agent-prompt resolve-operation --operation code-review --count <1|2|3>
141
- ```
154
+ Each model coordinator divides its received full census into six assigned censuses and passes each one to its responsible subagent. The orchestrator supplies the same full census to each coordinator; the coordinator owns division and delivery within its team. Copy the specialty's rules and all cells of its axis without changing IDs, targets, references or ordering. Naming/readability share semantic cell IDs; state/tests share state-and-tests cell IDs. Their rule subsets differ. Within each team, assigned `(cell ID, rule ID)` pairs are disjoint and their union equals the full census's pairs. Across models the entire assignment repeats independently. Never partition specialties between models. An empty specialty is recorded by its coordinator as not applicable without inventing checks or dispatching an empty review. Do not pass an empty census to `scope` or `check-coverage`, which require cells.
142
155
 
143
- It prints the duty, the role, the reviewer count, and one `slot` line per reviewer carrying that slot's
144
- provider and model. The contract owns those values (`agents/operations/code-review.json`, whose `count` is
145
- the ceiling), so a machine with too few distinct models fails here rather than quietly running fewer
146
- reviewers. Dispatch exactly the slots it prints.
156
+ Show all selected model teams and the six-specialty division policy before dispatching coordinators. Each coordinator records its concrete child assignments before spawning them. The initial review includes `reviewerCount` coordinator calls and up to `6 × reviewerCount` specialty subagent calls, plus automatic coverage gap-fills, format repairs and single provider retries under Step 3.5. Honor any user-set cost or call limit; an insufficient limit blocks dispatch rather than silently reducing the team. This authorization does not cover further provider retries, new scope, another model or a new implementation round. Instruction presence is checked by the retired Python suite; delegation, authorization and assignment accuracy remain lead checks.
157
+
158
+ Each selected model coordinator itself spawns its six specialty subagents through a supported delegation surface, collects their verified completions, requests any specialty gap-fills, and consolidates their results before returning its model report. The orchestrator launches the selected coordinators; it does not spawn their children on their behalf or consolidate raw child results. These are actual separate model calls, not six headings in one response. Preserve the verified provider/model binding and standalone evidence for every child. If a coordinator cannot spawn and collect its children under that binding, report an execution blocker rather than moving those responsibilities to the orchestrator, substituting a model or replacing the team with one serial review. Specialty subagents do not delegate further. Never share other model teams' verdicts before independent team reports are complete.
159
+
160
+ ### Shared test execution evidence
161
+
162
+ Before dispatch, inspect the project's test commands and applicable verification requirements. Reuse saved results only when their source tree, dependencies, configuration and test inputs match the fixed head. Otherwise the lead runs the relevant tests once in a checkout of that head isolated from user edits, preserving command, head, environment, exit code and full log. Run the project's required full gate at its prescribed stage; do not invent a universal test command or require every reviewer to rerun the same suite. External, paid or destructive tests keep their existing authorization boundary.
147
163
 
148
- Every reviewer and later gap-fill is a separate auditable standalone invocation. For each slot, create
164
+ Share the evidence with all model teams and subagents. Every model's Tests subagent independently checks whether tests discriminate the changed behavior, cover applicable failure and boundary cases, and avoid self-mocking; test success is not proof of correctness or rule conformance. A missing, failed or blocked required test stays explicit in the report. If review identifies a necessary additional local test, the lead runs it once and shares the result. Reviewers do not edit code, add tests or launch duplicate suites. Follow-up changes invalidate affected results; unchanged, matching evidence is reused. These are lead/reviewer checks, not enforced by the coverage parser.
165
+
166
+ Every coordinator, specialty subagent and later gap-fill is a separate auditable standalone invocation. Record its team slot, specialty (or coordinator), parent coordinator ID and assigned census path in the instructions. Use unique IDs for all calls. For each invocation, create
149
167
  `.okstra/agent-invocations/code-review/<invocation-id>.instructions.md` from that reviewer's brief, then run
150
168
  `okstra agent-prompt materialize --project-root <projectRoot> --invocation-id <invocation-id> --host-runtime <runtime> --provider <slot provider> --model <slot model> --model-role <role> --audience <duty> --purpose code-review --instruction <instructions-path> --prompt <prompt-path>`,
151
169
  copying `role`, `duty`, and the slot's `provider` and `model` verbatim from `resolve-operation` (`--model`
@@ -154,33 +172,35 @@ the instructions file; the returned assignment is authoritative. Run `okstra age
154
172
  invoking any model.
155
173
 
156
174
  For a native host call, pass the verified prompt body and `hostModelValue`. For a deterministic provider
157
- process, run the provider wrapper `~/.okstra/bin/okstra-<provider>-exec.sh <projectRoot> <modelExecutionValue> <prompt-path>`
175
+ process, run the provider wrapper `~/.okstra/bin/okstra-<provider>-exec.sh <projectRoot> <modelExecutionValue> <prompt-path> "" <role> --invocation-metadata <metadataPath>`
158
176
  with the verified prompt path (`okstra worker-dispatch` dispatches only a run manifest's assignments, not a
159
177
  standalone prompt). The wrapper records the provider's output in the prompt path with `.md` replaced by
160
178
  `.log`. Never substitute one model value for the other. Dispatch the verified calls in parallel when the host supports
161
- it. **Every reviewer receives the same full census** and independently owns its verdicts. On follow-ups, add that slot's verified previous results and scope decision as described below. Every brief carries:
179
+ it. **Every reviewer receives its assigned census** and independently owns its verdicts. On follow-ups, add that slot's verified previous results and scope decision as described below. Every brief carries:
162
180
 
163
181
  - the diff and the fixed-head read command `git -C <gitRoot> show <headCommit>:<path>`, where Step 1 resolved `<gitRoot>`
164
182
  - the project layout in one or two lines (where source, tests, and — if the routing found one — domain / ports / adapters live)
165
- - **the whole census** — the shared rule catalog once and every grouped cell of all four axes, verbatim
166
- - the absolute paths of every applied pack (from step 2's routing)
183
+ - **the assigned census** — its rule subset and grouped cells, verbatim, plus its model-team slot, specialty, parent coordinator ID and the full census path for context. Coordinators receive the full census and all six child assignments; children receive only their own verdict assignment
184
+ - the absolute paths of the packs allocated to its axes (from step 2's routing)
185
+ - shared test execution evidence, including missing or blocked verification
186
+ - the full-context inspection requirement: read whole target files, enclosing definitions, affected callers and callees, contracts, outcome consumers and related tests at the frozen head; follow transitive effects as needed. Read with targeted `git show` ranges and `git grep`; never print a whole generated report or graph dump (for example under `graphify-out/`) into a child's context. Specialty limits verdict ownership, not access to context. Report a suspected issue outside the assignment to the lead, who checks it and routes any required inspection to the owning specialist without duplicating or changing cells
167
187
  - the calibration path, written out in full as Step 2 fixed it — `~/.agents/skills/okstra-code-review/references/review-calibration.md`. The verdict format, the severity points, and the rules for a legitimate `clean` are defined there, not in the brief; a reviewer that cannot open this file cannot return a usable verdict, so never hand it a relative path or a "next to the skill" hint
168
188
 
169
189
  **Resolve each slot's inspection scope before materializing its prompt.** Run:
170
190
 
171
- Use `~/.agents/skills/okstra-code-review/SKILL.md` for `<skill-path>`, the calibration path fixed in Step 2 for `<calibration-path>`, and `<okstraHome>/prompts/duties/code-reviewer.json` for `<duty-contract-path>` using Step 2's resolved home. This installed duty source exists before materialization; invocation materialization still freezes its own duty snapshot. Keep the same ordered list of policy documents and applied project instructions across rounds. Policy content is matched by position; catalog references retain the rule-to-resource binding.
191
+ Use `~/.agents/skills/okstra-code-review/SKILL.md` for `<skill-path>`, the calibration path fixed in Step 2 for `<calibration-path>`, `~/.agents/skills/okstra-code-review/references/census-rules.md` for `<census-rules-path>`, and `<okstraHome>/prompts/duties/code-reviewer.json` for `<duty-contract-path>` using Step 2's resolved home. This installed duty source exists before materialization; invocation materialization still freezes its own duty snapshot. Keep the same ordered list of policy documents and applied project instructions across rounds. Policy content is matched by position; catalog references retain the rule-to-resource binding.
172
192
 
173
193
  ```bash
174
- okstra code-review scope --project-root <projectRoot> --base <baseCommit> --head <headCommit> --census <full-census-path> --policy <skill-path> --policy <calibration-path> --policy <duty-contract-path>
194
+ okstra code-review scope --project-root <projectRoot> --base <baseCommit> --head <headCommit> --census <assigned-census-path> --policy <skill-path> --policy <calibration-path> --policy <census-rules-path> --policy <duty-contract-path>
175
195
  ```
176
196
 
177
- For a follow-up, add `--previous-head <priorHead> --previous-census <prior-census-path>` and repeat `--completion <prior-completion-path>` for that slot's retained verified completions. Include every applied project instruction as another `--policy`. Use the same selected provider/model; a missing or changed slot starts with a full review. Never substitute another reviewer's evidence. Prior records remain immutable. An identical head, rules and completed adjudication need no new model call; reuse the existing report.
197
+ For a follow-up, add `--previous-head <priorHead> --previous-census <prior-assigned-census-path>` and repeat `--completion <prior-completion-path>` for that model team's same specialty's retained verified completions. Include every applied project instruction as another `--policy`. Use the same specialty and selected provider/model; a missing or changed assignment starts with full inspection of that specialty. Never substitute another team's or another specialty's evidence. Prior records remain immutable. An identical head, rules and completed adjudication need no new model call; reuse the existing report.
178
198
 
179
199
  Carry the fixed scope text into the brief. `Recheck` names mandatory inspections; `Carry candidates` are proposals, not automatic coverage. Each reviewer inspects the delta, searches changed symbols' callers and tests, checks the dependency inventory and expands Recheck for newly discovered effects before accepting any candidate. Unknown or unbounded effects require a full review. The full census remains unchanged; no candidate silently disappears. Return current coverage rows for both inspected and inherited cells, plus the baseline and dependencies in the calibration format. Only this current invocation's verified completion and gap-fills enter the current coverage audit; old completions are scope inputs, never current verdicts.
180
200
 
181
201
  Each axis is **one rule group**, so a cell is `target × <axis>` — never `target × <individual rule>`. The reviewer names the specific rule it found violated inside the verdict's `rule` field, and one cell may carry findings from several rules of its group.
182
202
 
183
- Axis scope — each reviewer works all four axes; the `Reads` column names each group's rules, and a brief never restates them; the bodies are in the packs:
203
+ Axis scope — each specialist works its assigned axes; the `Reads` column names each group's rules, and a brief never restates them; the bodies are in the packs:
184
204
 
185
205
  | Axis | Cell | Reads |
186
206
  |---|---|---|
@@ -199,23 +219,41 @@ review result and cannot contribute a verdict.
199
219
 
200
220
  ## Step 3.5 — Audit the coverage
201
221
 
202
- Audit responses against the [coverage format](references/review-calibration.md#compact-rule-coverage).
222
+ Each spawning coordinator owns this loop against the [coverage format](references/review-calibration.md#compact-rule-coverage):
223
+
224
+ 1. Collect each child's investigation of its assigned census, including evidence, findings and explicit rule accounting.
225
+ 2. Compare the collected results with the assigned subsets and the received full census; list missing cells and rules by responsible child.
226
+ 3. Return only those omissions or invalid verdicts to the same responsible subagent, preserving its logical child identity and original assignment. Resume that child when supported; otherwise use a linked continuation invocation with its prior verified results. Do not assign the omission to another reviewer or restart completed investigations.
227
+ 4. Collect the supplementary results and repeat the audit and requests until no cells or rules remain unaccounted for. A new invocation ID records each continuation without changing logical ownership.
228
+ 5. Only then consolidate the complete results and return the model report. A stopping condition below produces an explicitly incomplete status with its blocker, never a completed review.
203
229
 
204
- For each reviewer separately, audit its grouped rows and explicit rule-ID accounting using its verified completion marker:
230
+ For each model team's specialty subagent separately, audit its grouped rows against that child's assigned rule subset using its verified completion marker:
205
231
 
206
232
  ```bash
207
- okstra code-review check-coverage --project-root <projectRoot> --head <headCommit> --census <grouped-census-path> --completion <completion-path> [--completion <gap-fill-completion-path> ...]
233
+ okstra code-review check-coverage --project-root <projectRoot> --base <baseCommit> --head <headCommit> --census <assigned-census-path> --completion <completion-path> [--completion <gap-fill-completion-path> ...]
208
234
  ```
209
235
 
210
- Pass the `headCommit` that `okstra code-review target` returned. The command reads each evidence file as `<headCommit>` holds it (`git show <headCommit>:<path>`), never the project root's working tree, so a review run from a checkout on another commit audits the reviewed lines. The command reuses the existing completion verification boundary and refuses mixed model assignments. Exit 0 means every cell accounts for all rules in its group with valid source evidence and no unknown cell ID; exit 1 lists missing cells, missing rule IDs or invalid grouped verdicts; exit 2 reports invalid input or completion evidence. It validates the shared catalog and source anchors, but does not establish whether the selected references are exhaustive or a verdict is true.
236
+ Pass the `headCommit` that `okstra code-review target` returned. The command reads head evidence at `<headCommit>` and explicit `base:` evidence at `<baseCommit>`, never the project root's working tree, so a review run from a checkout on another commit audits the reviewed lines. The command reuses the existing completion verification boundary and refuses mixed model assignments. Exit 0 means every cell accounts for all rules in its group with valid source evidence and no unknown cell ID; exit 1 lists missing cells, missing rule IDs or invalid grouped verdicts; exit 2 reports invalid input or completion evidence. It validates the shared catalog and source anchors, but does not establish whether the selected references are exhaustive or a verdict is true.
237
+
238
+ Automatically fill missing verdicts, unaccounted rules and malformed rows within the authorized review. Preserve every raw response and completion. For each incomplete specialist, dispatch one gap-fill on its original slot and specialty carrying only its incomplete grouped cells, their assigned rule subset, the same range, rule paths and full-context requirements. Ask for a complete row per affected cell under that subset. Use a new invocation ID and repeat materialize → verify → dispatch → materialize-result → complete → verify-completion. Audit that child's initial and gap-fill markers against its entire assigned census. Earlier usable verdicts remain unchanged. Repeat while the incomplete cell count decreases, until every assigned cell passes. Do not rerun completed specialists or borrow another model team's verdicts.
239
+
240
+ Two cases get one bounded repeat before the no-progress rule applies. A row rejected only for its syntax (cell or rule separators, escaping, a column count, an observation form the calibration does not allow there) gets one format repair: a continuation on the same child that carries the parser's rejection text and asks for the same verdicts in the calibration row format. That repair does not count toward the no-progress stop. An invocation that exits non-zero without a returned body is retried once on the same slot and specialty under a new invocation ID; a second failure is a provider-execution stop. Each specialist's gap-fills, repair and retry are judged separately: one specialist's stop never stops another specialist that has not had its own gap-fill.
241
+
242
+ Stop with incomplete coverage when a gap-fill makes no progress, a user-set call/cost limit is reached, source evidence is unavailable, or an invocation fails authentication, billing, provider execution or integrity verification. Unknown cell IDs are invalid: preserve the response and report the blocker rather than relabeling IDs or retrying automatically. Do not treat infrastructure failures as missing inspections. A stopping condition fails the review instead of pausing it for authorization: dispatch no further gap-fills, continue to Step 3.6 with the verified results, and record every unaccounted `(cell ID, rule ID)` pair as a `must-fix` `now` coverage finding that names the pair, its responsible team and specialty, and the blocker. That finding stays open until a later review round accounts for the pair. A manual assessment does not satisfy reviewer coverage or create a verified completion. The lead checks these stopping conditions; the parser only checks accounting and source anchors.
211
243
 
212
- Do not automatically invoke a model for a format error, unknown ID, or missing coverage. Preserve the verified raw response and report the affected cells as incomplete; never fabricate a passing row or edit immutable evidence. The lead may inspect the cited source and record a separate manual assessment, but that assessment does not satisfy reviewer coverage or create a new verified completion. Request explicit authorization before any additional model call. If authorized for genuinely missing inspection, dispatch one gap-fill invocation per reviewer on that reviewer's original slot, carrying only its incomplete grouped cells, their shared catalog entries, the same range and rule paths. Ask for one complete row for each such cell, not separate replies per missing rule. Use a new invocation ID and repeat the full materialize → verify → dispatch → materialize-result → complete → verify-completion boundary. Re-run the audit with that reviewer's initial and gap-fill markers. Earlier usable verdicts remain unchanged. An invocation with unknown IDs is invalid; record its rejection and incomplete coverage without automatically requesting another invocation. Do not silently relabel IDs.
244
+ An isolated false observation reopens the affected cells and any dependent conclusions, not automatically every valid verdict. Record the excluded completion/cells and retain only independently valid evidence. Semantically rejected rows enter the same affected-cell gap-fill procedure; count them as incomplete when checking progress. If an older row is syntactically valid but disproved, pass the corrected completion first so the existing first-usable rule selects it; retain the older completion only for unaffected rows. If the error's extent cannot be bounded, report the unresolved extent; a full correction requires explicit authorization. Never edit an immutable response to make it pass.
213
245
 
214
- An isolated format error or false observation reopens the affected cells and any dependent conclusions, not automatically every valid verdict. Record the excluded completion/cells and retain only independently valid evidence. If an older row is syntactically valid but disproved, pass the corrected completion first so the existing first-usable rule selects it; retain the older completion only for unaffected rows. If the error's extent cannot be bounded, report the unresolved extent; a full correction requires explicit authorization. Never edit an immutable response to make it pass.
246
+ Before accepting a clean general cell, open its G2/G3/G5 observations and verify the result-meaning trace, the downstream workload and pre-work bound, and the applicable documented convention checks. If opened code contradicts an observation, record the affected cells and dependent conclusions as semantically rejected and use the bounded gap-fill procedure above. Exclude the entire completion only when the error's extent cannot be bounded; report the blocker instead of automatically requesting a full correction. Keep original artifacts immutable for the audit trail. The parser enforces presence and source locations; the lead checks truth. Keep these observations inside the existing Evidence column, without adding verdict rows.
215
247
 
216
- Before accepting a clean general cell, open its G2/G3/G5 observations and verify the result-meaning trace, the downstream workload and pre-work bound, and the applicable documented convention checks. If opened code contradicts an observation, record the affected cells and dependent conclusions as semantically rejected without automatically calling the reviewer again. Any explicitly authorized correction uses the same reviewer slot and the preceding paragraph's completion ordering. Exclude the entire completion only when the error's extent cannot be bounded; report the blocker instead of automatically requesting a full correction. Keep original artifacts immutable for the audit trail. The parser enforces presence and source locations; the lead checks truth. Keep these observations inside the existing Evidence column, without adding verdict rows.
248
+ ### Consolidate within each model, then across models
217
249
 
218
- Do not start Step 3.6 until every reviewer passes the audit. If evidence remains unavailable, report the specific blocker and incomplete coverage instead of writing a completed review.
250
+ After its six child assignments pass, the coordinator that spawned those children consolidates their verified results into one model report itself. It does not hand raw child results to the orchestrator for consolidation. Preserve every finding and its child completion provenance. Namespace finding IDs by team and specialty to avoid collisions. For a shared semantic or state-and-tests cell, combine the children's disjoint rule statuses into one complete grouped row; union their source observations and dependency files. Preserve inspected/inherited distinctions and the frozen baseline. Never convert an unaccounted rule to clean or silently discard a conflicting finding. Record conflicts for the lead to settle against the code.
251
+
252
+ The coordinator returns the full-census coverage, findings, and a child manifest listing each specialty, invocation/completion paths, assignment path and audit result, including empty-specialty acknowledgments. Publish and verify this coordinator completion through the same standalone boundary. The lead checks that every full-census `(cell ID, rule ID)` status is supported by the corresponding child's verified row and that all child findings survive consolidation. A coordinator's summary is not proof that its children ran. This provenance reconciliation is a lead check; the coverage parser does not enforce delegation or parent-child relationships.
253
+
254
+ Audit each coordinator's completion against the full census using `check-coverage`. Do not feed split-rule child completions directly into a full-census audit: the parser selects whole usable rows and does not merge partial rows. If consolidation loses a rule or finding, return the discrepancy to the spawning coordinator so it corrects its report from its saved child results; the orchestrator does not reconstruct the report. Do not rerun completed children. Preserve and verify the replacement coordinator response. Such consolidation corrections fall within authorized gap-fills and the same progress/cost stopping conditions.
255
+
256
+ Do not start Step 3.6 until all selected model reports independently pass full-census coverage and child provenance reconciliation, or a report has stopped under a Step 3.5 stopping condition. Never combine different model assignments in one `check-coverage` call. The lead then compares the selected independent model reports and settles their combined findings in Step 3.7. A stopped report contributes its verified verdicts and its coverage findings; the review is failed, never presented as complete coverage.
219
257
 
220
258
  ## Step 3.6 — Check every citation
221
259
 
@@ -225,7 +263,7 @@ Reviewers miscount lines. Pass every finding's `path:line` to one call:
225
263
  okstra code-review check-lines --project-root <projectRoot> --base <baseCommit> --head <headCommit> --cite <path:line> [--cite <path:line> ...]
226
264
  ```
227
265
 
228
- `ok` keeps the citation. A fully deleted file has no head-side citation; a deletion within a surviving file retains its anchor before the cut. For `not-changed` or `not-in-diff`, find the finding's `snippet` in `git -C <projectRoot> show <headCommit>:<path>`; if it sits on one of the changed lines the output lists, replace the line number with that line and say so in the finding. A finding whose snippet is on no changed line goes to `Rejected` as "cites no changed line". Re-run `check-lines` until every kept citation is `ok`.
266
+ `ok` keeps the citation. Use `base:<path>:<line>` for removed lines, reading the snippet with `git -C <gitRoot> show <baseCommit>:<path>`. Use `<path>:0` only for an empty file at the head; its snippet is the empty string and its evidence describes the removed behavior or empty-file consequence. A deletion within a surviving file may also retain its head anchor before the cut. For `not-changed` or `not-in-diff`, locate the snippet at its declared side and re-anchor it only to a changed location on that side. Otherwise move it to `Rejected` as "cites no changed line". Re-run `check-lines` until every kept citation is `ok`.
229
267
 
230
268
  ## Step 3.7 — Settle the findings
231
269
 
@@ -233,17 +271,15 @@ A formatting-only or minor correction does not automatically require another mod
233
271
 
234
272
  On follow-ups, retain the previous adjudication ledger: resolved, still open, parked and rejected. Recheck every fix and its affected paths. Reopening an unchanged verdict names the prior decision and new evidence: a reachable failure, a previously missed applicable rule with concrete impact, or a changed dependency/requirement. Classify each new finding as fix-introduced, previously missed, or newly in scope; do not count an old discovery as a new regression. A corrected rule interpretation can reopen a real defect; repeated preference or an alternative implementation cannot. Do not suppress a demonstrated failure because a prior reviewer marked it clean. Optional improvements remain parked and do not require a code change or another review round unless the user requests them. Keep existing severity/timing adjudication rules below.
235
273
 
236
- Before pairing findings, check every finding, including agreed ones, against the [kind-specific verdict criteria](references/review-calibration.md#separate-execution-errors-from-design-violations) and [finding requirements](references/review-calibration.md#every-finding-carries-its-fix). Record the specific reason for rejecting unsupported evidence. Then settle the findings according to the reviewer count below.
274
+ Before pairing findings, check every finding, including agreed ones, against the [kind-specific verdict criteria](references/review-calibration.md#separate-execution-errors-from-design-violations) and [finding requirements](references/review-calibration.md#every-finding-carries-its-fix). Record the specific reason for rejecting unsupported evidence. Then settle single and overlapping reports as below.
237
275
 
238
- **Two or three reviewers.** Group findings by the same `path:line` and defect. Inspect every reported finding, including one supported by only one of three reviewers; silence or a clean verdict is not a vote against it. Then:
276
+ **Selected independent model reports.** With one model, adjudicate its report directly against source evidence; do not require cross-model agreement. Group the consolidated findings by the same `path:line` and defect. Adjudicate every finding, including one reported by only one model or one of its children. Multiple children within one team count as one model's report, not independent model agreement. Missing inspection is never a clean verdict or a vote. For overlapping reports:
239
277
 
240
- - **Agreed** — every reviewer reports it with the same severity and timing. It keeps its severity and timing after the evidence and kind checks above; agreement does not replace those checks.
278
+ - **Agreed** — multiple model teams report the same defect with the same severity and timing. It keeps its severity and timing after the evidence and kind checks above; agreement does not replace those checks.
241
279
  - **Graded differently** — at least two report it with different severity or timing. Choose one reporting reviewer's severity/timing pair for that finding after reading the code, and record all reported values and your reason. Never choose an unreported value or use majority vote in place of evidence.
242
- - **One-sided** — fewer than all reviewers report it with no grading disagreement; the others returned `clean` for that cell or reported something else. Adjudicate it as below.
243
-
244
- **One reviewer.** Adjudicate every finding it returns.
280
+ - **Single report** — only one model team reports the defect. Check the other teams' corresponding rule verdicts, then adjudicate against source evidence as below; silence does not override a demonstrated defect.
245
281
 
246
- **Adjudicating** a finding: open each `evidence` location at `headCommit` and the definitions its claim depends on, then apply the verdict criteria linked above.
282
+ **Adjudicating** a finding: open each `evidence` location at its declared side (`baseCommit` for `base:` citations, otherwise `headCommit`) and the definitions its claim depends on, then apply the verdict criteria linked above.
247
283
 
248
284
  - **Confirmed** — the opened evidence satisfies the verdict criteria. The finding keeps its severity and timing.
249
285
  - **Rejected** — the code contradicts the claim (the called function never reads `this`, the value cannot be null there, the branch is unreachable). Move it to `Rejected` with the contradicting `path:line` and one sentence on what it shows.
@@ -41,7 +41,9 @@ Write targets under `## Cells`; each has a stable `C-CR-...` ID, the target and
41
41
  | C-CR-0002 | src/orders/totals.py | structural |
42
42
  ```
43
43
 
44
- The example is abbreviated; the actual catalog includes the named criteria above for every used group. Add `S5` through `S10` only for a routed architecture pack; otherwise the base catalog has 16 criteria. Freeze the catalog and cell IDs before dispatch and send the same census to each reviewer. The command `code-review check-coverage` enforces catalog membership, rule accounting and source-anchor validity against this saved census; the lead still checks that the catalog names the intended references and that verdicts are true.
44
+ The example is abbreviated; the actual catalog includes the named criteria above for every used group. Add `S5` through `S10` only for a routed architecture pack; otherwise the base catalog has 16 criteria. Freeze the full catalog and cell IDs before dispatch. Every model team receives that entire census independently, then delegates its rule subsets by the six-specialty mapping in SKILL.md. A child's assigned census retains only its specialty's rules and all cells of their group, preserving IDs, targets, references and order. Semantic cells appear in both naming and readability assignments; state-and-tests cells appear in both state and tests assignments. Their rule IDs are disjoint. Within each team, reconcile `(cell ID, rule ID)` pairs, not cell IDs alone, against the full census. Across models, repeat the full set independently.
45
+
46
+ The command `code-review check-coverage` enforces catalog membership, rule accounting and source-anchor validity against each child's subset census and, after consolidation, each coordinator's full census. It does not merge partial-rule rows across children. Coordinators combine complementary rule statuses into complete rows, preserving findings, observations, dependencies and child completion provenance. The lead checks delegation, pair coverage, aggregation fidelity, reference completeness and verdict truth; these are not enforced by the coverage parser.
45
47
 
46
48
  Do not omit a cell because a rule seems inapplicable. Record that criterion under `N/A` with its reason in the compact row. The normal case lists checked rule IDs once with one inspected source anchor for the cell. This preserves rule-level omission checks without repeating paths and explanations for every rule.
47
49
 
@@ -83,7 +85,7 @@ Two consequences:
83
85
 
84
86
  Test files (the project's test-path or test-suffix convention — `*_test.*`, `*.test.*`, `*.spec.*`, `tests/`, `spec/`) are censused on `state-and-tests` only. They are not excluded: they are covered by a different rule group.
85
87
 
86
- Enumerate functions from the frozen source and intersect their signature/body spans with the diff's changed lines. Include every matching enclosing or nested function, including same-line anonymous functions distinguished by column. Use base-side source spans to locate deletion-only changes and map surviving targets to their head positions. A removed function has no head target; account for its deletion in the surviving file's file-level cells. Changes outside functions (imports, module wiring, top-level declarations, class-level constants) also belong to file-level cells. If boundaries cannot be established, report the incomplete census and stop before dispatch instead of claiming the hunk criterion holds. Instruction presence is checked by `tests/contract/test_standalone_agent_invocation_surfaces.py::test_code_review_dispatches_use_verified_standalone_invocations`; boundary accuracy remains a lead check.
88
+ Enumerate functions from the frozen source and intersect their signature/body spans with the diff's changed lines. Include every matching enclosing or nested function, including same-line anonymous functions distinguished by column. Use base-side source spans to locate deletion-only changes and map surviving targets to their head positions. A removed function has no head target; account for its deletion in the surviving file's file-level cells. Changes outside functions (imports, module wiring, top-level declarations, class-level constants) also belong to file-level cells. If boundaries cannot be established, report the incomplete census and stop before dispatch instead of claiming the hunk criterion holds. Instruction presence is checked by the retired Python suite; boundary accuracy remains a lead check.
87
89
 
88
90
  ## Exclusions
89
91
 
@@ -132,19 +134,23 @@ Both must hold exactly, and both are shown in the response before dispatch:
132
134
 
133
135
  1. **Files:** distinct files censused (in any axis) + files excluded = files in the diff.
134
136
 
135
- One `git diff --name-status` row is one file, whatever its status letter. A rename row carries two paths (`R100 <old> <new>`) and still counts **once**: census the `<new>` path and never count `<old>` on either side of the equation. A delete row (`D <path>`) counts once too, and it is always an exclusion, with the reason `deleted — no remaining line to anchor a finding on`.
137
+ One `git diff --name-status` row is one file, whatever its status letter. A rename row carries two paths (`R100 <old> <new>`) and still counts **once**: census the `<new>` path and never count `<old>` on either side of the equation. A delete row (`D <path>`) counts once and follows the same source/test membership rules as a surviving file. Its file-level cells retain the deleted path; removed functions have no semantic cells. Inspect the base source and surviving head callers, consumers and contracts. Cite removed lines as `base:<path>:<line>`. An empty surviving source still has file-level cells, anchored by `path:0` or by removed base lines. A diff containing only deletions or empty files is not an empty review.
136
138
  2. **Hunks:** every hunk in a censused file maps either to a censused function or to file-level code (imports, module wiring, declarations).
137
139
 
138
140
  ## Follow-up review
139
141
 
140
142
  Keep the original PR base and rebuild its full net-diff census at the new head. Preserve IDs for identical targets/groups; never renumber unrelated cells to fill gaps. New or moved targets get new IDs and a fresh inspection. A delta is the previous reviewed head to the current head, not a replacement PR base.
141
143
 
142
- The `code-review scope` command proposes carry candidates per reviewer. It verifies prior completion integrity, role/model consistency within the prior results, complete prior coverage, ancestor history, exact base/head baseline, catalog references, and rule/policy content fingerprints. It reopens cells with prior findings, changed targets or changed recorded inputs. Missing dependency records reopen their cells. Any changed path outside the prior inventory, changed rules/base, rewritten history or missing baseline falls back to full review. Invalid completion integrity stops scope calculation. These checks are enforced by `code_review_scope.py::review_scope` and the standalone completion scope tests.
144
+ Keep all six specialty assignments stable within each selected model team. Run scope/coverage checks separately for each `(model-team slot, specialty)` against its current and previous subset census, then check each coordinator's consolidated report against the full census. Do not substitute another specialty's or model's completions. Each model independently covers the full census through its children. An empty assignment is acknowledged by its coordinator as described in SKILL.md, not passed to these commands.
145
+
146
+ The `code-review scope` command proposes carry candidates per reviewer. It verifies prior completion integrity, role/model consistency within the prior results, ancestor history, exact base/head baseline, catalog references, and rule/policy content fingerprints. It reopens cells with prior findings, changed targets or changed recorded inputs, and cells the prior results left unverified. Missing dependency records reopen their cells. A changed path outside the prior inventory reopens only the cells that list it and is named in the scope reason so reviewers search it for further effects. Changed rules/base, rewritten history, unknown prior cell IDs or a missing baseline fall back to full review. Invalid completion integrity stops scope calculation. These checks are enforced by `code_review_scope.py::review_scope` and the standalone completion scope tests.
143
147
 
144
148
  Record each inspected cell's repository-relative input files under `Review Dependencies`: its whole target file, definitions/callees, callers, outcome consumers, relevant tests and contracts read to justify the verdict. Include transitive dependencies. Paths describe files, not line ranges; changing any part reopens the dependent cell. An external rule or instruction belongs in the repeated `--policy` inputs instead. A gap-fill retains the same baseline and records dependencies for its inspected cells.
145
149
 
146
150
  The inventory's completeness is a reviewer/lead judgment, not mechanically proven. Before accepting carry candidates, independently search the delta's changed symbols and wiring for effects beyond that inventory. Include changed behavior, error/result mappings, state, test assumptions, public contracts and downstream work. Newly affected cells reopen even when their own bytes did not change. Reopen all affected axes for the target file; expand to callers/tests outside the original census as supporting inspection without dropping or inventing census cells. Unknown reachability, dynamic dispatch, configuration-driven wiring or unexplained test failures require broader inspection, up to full review.
147
151
 
152
+ Read whole target files, relevant callers/callees, contracts and tests on the first review and on follow-ups. A smaller re-evaluation scope never means reading only changed lines or ignoring another layer. Route newly affected cells in other specialties through the lead to their owners. Unknown impact expands inspection; obtain any required scope authorization before additional model calls. Reusing an unchanged verdict requires a current impact check, not just unchanged source bytes.
153
+
148
154
  Reviewers return the complete current coverage table, identifying inherited cells separately in `Review Carry`. They attest that the current impact inspection supports each inheritance. The lead verifies that attestation and the boundary evidence. Prior `checked` labels alone never satisfy current coverage. Continue using the existing current materialize/verify/result/complete/verify-completion and check-coverage boundaries; scope output cannot mark a cell clean. This boundary audit is a review criterion, not a machine guarantee of defect absence.
149
155
 
150
156
  A count that does not balance means a file was dropped, not that the diff was odd. Find it before dispatching.
@@ -23,7 +23,9 @@ A cell covers its whole rule group, so it can carry several findings from severa
23
23
  note: The same tier→rate table is already in `domain/tiers.py:18`; a rate change now has two homes. Call the existing lookup instead of re-expressing it here.
24
24
  ```
25
25
 
26
- Fields: `cell` (`target × axis`, exactly as the census wrote it — the axis is the rule group, and there is never one cell per individual rule), `verdict` (`finding` for a detailed finding), `rule` (the specific rule this finding violates, spelled as its pack spells it), `line` (a line **this diff changed**, numbered at the head commit), `severity`, `timing` (`now` | `park`, below), `snippet` (the quoted changed line, verbatim — the orchestrator locates the finding by it), `id` (a finding ID such as `F-001`), `kind` (`execution-error` | `design-violation`), `failure` (for an execution error: reachable input or state and the wrong result), `impact` (for a design violation: the concrete design or maintenance consequence of violating the applicable rule), `evidence` (the `path:line` locations opened to establish the claim, including definitions it depends on), `note` (1–2 sentences: what is wrong plus a concrete fix).
26
+ Fields: `cell` (`target × axis`, exactly as the census wrote it — the axis is the rule group, and there is never one cell per individual rule), `verdict` (`finding` for a detailed finding), `rule` (the specific rule this finding violates, spelled as its pack spells it), `line` (a location **this diff changed**, numbered at the head commit unless explicitly base-prefixed), `severity`, `timing` (`now` | `park`, below), `snippet` (the quoted changed line, verbatim — the orchestrator locates the finding by it), `id` (a finding ID such as `F-001`), `kind` (`execution-error` | `design-violation`), `failure` (for an execution error: reachable input or state and the wrong result), `impact` (for a design violation: the concrete design or maintenance consequence of violating the applicable rule), `evidence` (the `path:line` locations opened to establish the claim, including definitions it depends on), `note` (1–2 sentences: what is wrong plus a concrete fix).
27
+
28
+ For removals, use `base:path:line` to identify a removed base line and open its snippet at the frozen base. An empty regular file may use `path:0` with an empty snippet as a file-level anchor, not a source line. `check-lines` enforces changed locations; `check-coverage --base` validates base evidence and accepts line 0 only for empty regular files. Use the same citation forms in Evidence and G2/G3/G5 observations. Trace surviving callers and contracts at the head.
27
29
 
28
30
  **Open the definition before you claim its behaviour.** A claim about what a called function, method, or value does — that it reads `this`, throws, mutates its argument, returns `null` — cites that definition in `evidence`. A claim you could not check against its definition remains unevaluated: report the missing evidence and leave that rule unaccounted in the grouped row. Do not turn an inspection failure into `clean`. The orchestrator opens every `evidence` location and rejects a finding the code contradicts.
29
31
 
@@ -65,7 +67,7 @@ Return one compact Coverage Verdicts row per cell under `## Coverage Verdicts`.
65
67
 
66
68
  The example uses the base structural and state-and-tests catalogs. `Checked` means inspected and no actionable finding for those rules. A criterion includes all applicable subconditions in its references; one inapplicable subcondition does not make the entire criterion N/A. Explicitly list the IDs; `all`, counts and ID ranges are not verdicts. `N/A` assigns `rule=reason`; `Findings` assigns `rule=finding-id`. Separate assignments with semicolons and multiple finding IDs for one rule with commas. Only a semicolon followed by the next `RULE=` starts a new assignment; a semicolon inside a reason stays part of that reason. Use `-` for an empty field. Every expected rule appears exactly once across the three status fields. Never infer an omitted rule as clean.
67
69
 
68
- Every row supplies one literal repository-relative source `path:line` for that cell's target file. The citation may be backtick-quoted and followed by ` — ` and a short observation before any ` :: ` rule observations. Do not substitute a rule-pack citation such as `cc:5`, a global alias such as `E01`, or another target's path. The checker verifies that the file and line exist inside the project. Additional definitions and evidence remain in finding bodies.
70
+ Every row supplies one literal repository-relative source `path:line` for that cell's target file. The citation may be backtick-quoted and followed by ` — ` and a short observation before any ` :: ` rule observations. Do not substitute a rule-pack citation such as `cc:5`, a global alias such as `E01`, or another target's path. The checker verifies the declared source side and location; `base:` requires the frozen `--base`, and line 0 requires an empty regular file. These explicit forms override the head-line default above. Additional definitions and evidence remain in finding bodies.
69
71
 
70
72
  For `general` cells, checked G2, G3 and G5 each carry a compact observation in that same Evidence field: `target/path:line :: G2=source/path:line observed outcome mapping; G3=source/path:line observed workload and bound; G5=source/path:line applicable clauses and observed conformance`. Each observation begins with an existing project-source citation; it may cite a relevant callee. Keep rule-pack references in the catalog or the observation text, not in the project-source citation slot. Separate assignments with semicolons; the same `RULE=` boundary applies, so a semicolon inside an observation stays part of it. Findings and reasoned N/A already explain their criteria and need no duplicate clean observation.
71
73
 
@@ -110,7 +112,7 @@ Loose typing in test files (`any`, dynamic casts, untyped fixtures) is a **typin
110
112
 
111
113
  ## The report
112
114
 
113
- Merged and adjudicated by the orchestrator, written to `reviewPath`. Use the values resolved by Step 1 and the dispatched slots for the following YAML frontmatter fields, in this order. Include `taskKey` and `stage` only in stage mode, and `branch` only in branch mode.
115
+ Each spawning model coordinator consolidates its own subagents into a completed model report. The orchestrator receives the selected model teams' completed reports, verifies and adjudicates their findings, and writes the final report to `reviewPath`; it does not consolidate raw child results. Aggregation discrepancies return to the spawning coordinator for correction. Use the values resolved by Step 1 and the dispatched slots for the following YAML frontmatter fields, in this order. Include `taskKey` and `stage` only in stage mode, and `branch` only in branch mode.
114
116
 
115
117
  ```yaml
116
118
  mode: stage | branch
@@ -141,7 +143,8 @@ Sections, in this order, empty ones omitted except `Coverage` and `Score`:
141
143
  - **Parked** — `park` findings, with their severity, not scored.
142
144
  - **Rejected** — findings the orchestrator's adjudication disproved or that cite no changed line: the reviewer's claim in one line, then the contradicting `path:line` and what it shows. Not scored.
143
145
 
144
- - **Coverage** — the reviewers (`provider/model`, one to three); N changed files → S `structural` / F `semantic` / T `state-and-tests` / G `general` cells, all accounted for by every reviewer; M files excluded with reasons; applied/unavailable packs; and how findings were settled. Also show expected/covered grouped cells, missing rule IDs and reasoned applicability exclusions. On follow-ups, distinguish freshly inspected from inherited cells per reviewer, name the prior head and scope fallback/expansion reasons, and classify new findings by origin. Never describe inherited cells as newly inspected or rule flags as independent targets.
146
+ - **Coverage** — the selected one to three model teams (`provider/model`, default two), each team's six specialty subagents and verified child completion provenance; N changed files → S `structural` / F `semantic` / T `state-and-tests` / G `general` cells, independently accounted for in every model report; M files excluded with reasons; applied/unavailable packs; and how findings were settled. Show expected/covered cells and assigned rule IDs per child, empty-specialty acknowledgments, each team's complete `(cell ID, rule ID)` union, and each coordinator's full-census audit. Retain child-to-team-to-final finding provenance when deduplicating. Record gap-fill rounds and any no-progress, budget or execution blocker. On follow-ups, distinguish freshly inspected from inherited cells per model and specialty, name the prior head and scope fallback/expansion reasons, and classify new findings by origin. Never describe inherited cells as newly inspected or rule flags as independent targets.
147
+ - **Test evidence inside Coverage** — record each shared test command, tested head, environment, exit code and log path, identifying reused results and their matching inputs. Distinguish test-source inspection from actual execution. State failed, missing or blocked required checks; a completed code inspection does not imply the implementation passed its release gate. Do not claim an unexecuted test passed or count duplicate reviewer runs as independent evidence.
145
148
  - **Findings** — each one opens with `` `path/to/file.py:42` `` + the verdict's `rule` name + `kind` + severity + points, then the snippet as a blockquote, then the 1–2 sentence note with its fix, the execution `failure` or design `impact`, and supporting `evidence`. Its note then says how it was settled: `agreed`, `graded by orchestrator` (with every reporting reviewer's values), or `confirmed by orchestrator`.
146
149
  - **Score** — every confirmed or agreed `now` finding gets a row after passing the citation and evidence checks in Steps 3.6–3.7. Count each deduplicated finding once. The table is emitted even when there are none, with a single total row reading 0:
147
150
 
@@ -39,4 +39,4 @@ Read the returned human report. Explain the business findings, verified scope an
39
39
 
40
40
  The investigation reads source, configuration, test bodies and explicitly supplied existing results. Its policy forbids executing tests, starting services, deploying, migrating or editing investigated projects. The report distinguishes that policy and the before/after source audit from an enforced write boundary. A report and a shared fact use the same accepted evidence. New runs retain prior reports and source baselines.
41
41
 
42
- Enforcement: `business_flow.engine` validates the result schema, source evidence and source stability before contribution; `agent.invocation` verifies standalone completion; `business_flow.store` preserves claim provenance and source versions. These behaviors are covered by `tests/run/test_business_flow.py` and existing invocation/JSON-boundary contract tests.
42
+ Enforcement: `business_flow.engine` validates the result schema, source evidence and source stability before contribution; `agent.invocation` verifies standalone completion; `business_flow.store` preserves claim provenance and source versions. These behaviors are covered by the retired Python suite and existing invocation/JSON-boundary contract tests.
@@ -39,9 +39,9 @@ For settings, `kind: done` means the settings transaction finished: show `next.l
39
39
 
40
40
  ## When NOT to Use
41
41
 
42
- - User explicitly asks to spawn a new terminal / new agent session — use `okstra-inspect history.4` (resume command) or instruct them to run `okstra` in another terminal.
43
- - User wants status only — use `okstra-inspect status`.
44
- - User wants past runs — use `okstra-inspect history`.
42
+ - User explicitly asks to spawn a new terminal / new agent session — instruct them to run `okstra` in another terminal.
43
+ - User wants status only — use `okstra task-show <task-key>`.
44
+ - User wants past runs — use the task timeline.
45
45
 
46
46
  <!-- BEGIN FRAGMENT: wizard-relay-protocol -->
47
47
  ## How the wizard talks to you
@@ -176,7 +176,7 @@ This prints one absolute path on stdout (e.g. `/var/folders/.../okstra-wizard.Ab
176
176
 
177
177
  Then initialize the wizard with the literal `projectRoot` / `projectId` you parsed from Step 1 and the literal state-file path from above.
178
178
 
179
- For task continuity, pass `--preferred-task-key <project-id:task-group:task-id>` on every initialization when this conversation has a known task. Use the task explicitly requested in the current message first; otherwise use the last task the user selected in this conversation's wizard. Resolve abbreviated task IDs against the project catalog before passing the full key. If the ID is ambiguous, ask which matching task the user means. Never infer this conversation's selection from project-wide `latest-task.json`, catalog recency, or another session. With neither an explicit task nor a prior selection in this conversation, omit the flag. The runtime puts the preferred task first, including a completed task when explicitly carried in, and rejects a key absent from the catalog instead of substituting another task; ordering is covered by `tests/domain/wizard/test_task_selection.py`. The task picker still lets the user change tasks.
179
+ For task continuity, pass `--preferred-task-key <project-id:task-group:task-id>` on every initialization when this conversation has a known task. Use the task explicitly requested in the current message first; otherwise use the last task the user selected in this conversation's wizard. Resolve abbreviated task IDs against the project catalog before passing the full key. If the ID is ambiguous, ask which matching task the user means. Never infer this conversation's selection from project-wide `latest-task.json`, catalog recency, or another session. With neither an explicit task nor a prior selection in this conversation, omit the flag. The runtime puts the preferred task first, including a completed task when explicitly carried in, and rejects a key absent from the catalog instead of substituting another task; ordering is covered by the former Python suite; that regression check is now retired. The task picker still lets the user change tasks.
180
180
 
181
181
  After a successful task selection, retain the returned full task key in this conversation as its task context, including in continuation summaries, and carry it into the next initialization. A different selection replaces it. Selecting a brand-new task clears the previous selection; retain the new full key once its project, group, and task ID are resolved. This conversation carry-forward is a lead instruction, not automatic host-session discovery by the runtime.
182
182
 
@@ -447,7 +447,7 @@ When the user picks a waiver, append `--qa-waiver "<stageKey>:<reason>"` to the
447
447
  If `render-bundle` stdout carries an `okstra concurrent-run stages: <stages>` label line (another implementation run on the same task-key is occupying `<stages>`), the launch prompt has already been rendered with the "Concurrent-run marker" gate. If this line is absent it is not a concurrent run, so skip this branch. If present, before dispatch present a 3-option recommendation picker to the user (run-prompt recommendation rule: 1–2 recommendations + Enter directly; this picker is authored by the skill, so it is unconstrained by the wizard `options[]` rule):
448
448
 
449
449
  1. (recommended) Proceed as-is — use the already-rendered bundle. Each session uses its own implicit team, so concurrent runs have no team conflict and split-pane works fine.
450
- 2. Wait — hold the dispatch for now. The stage worktree·run-context are preserved, so after the other occupying run finishes, resuming the same stage takes the normal team path. Print the resume command (`okstra-inspect` history → resume) to the user.
450
+ 2. Wait — hold the dispatch for now. The stage worktree·run-context are preserved, so after the other occupying run finishes, resuming the same stage takes the normal team path. Tell the user to resume the same stage with `okstra-run` after the other run finishes.
451
451
  3. Enter directly.
452
452
 
453
453
  ### Stale git SHA recovery (git-reconcile gate)
@@ -554,4 +554,4 @@ Follow the rendered launch prompt's "Progress, remaining work, and recommendatio
554
554
  - Echo each captured answer (`result.echo`) on one short line so the user sees what was registered.
555
555
  - Name every file you show the user as a markdown link — `[<short label>](<absolute path>)`, with the absolute path inside the parentheses and a short label naming what the file is. A relative destination does not open from an external program. That is the only form the host renders as clickable; a path in backticks is text the user has to copy out. The `report-finalize` result's `reportPaths.markdown` carries the run's report, report record, and team state already in that form. Commands stay in backticks — a link is for a file, not for something to run.
556
556
  - Never invent identity; if a `text` prompt returns an empty answer where the wizard rejects it, the user must retry.
557
- - After Step 6, begin the lead workflow without re-summarizing the skill itself. For a single run, finish after Step 6 and any same-run recovery, unless the user has already authorized continuing the task through further phases. In an unattended chain where `orchestration.chainStages` has 2+ elements, repeat Step 6 per stage until Step 7's queue is empty (or it stops at a "not ready" / exception gate), then finish. When `report-finalize` returns `recovery.mode: same-run`, continue the authorized corrections in this run and execute `recovery.resumeCommand` before closeout; preserve approvals and model choices without reopening the wizard. The command and owner issues are supplied by `report_finalize._finalize_recovery`. When the lead (or this skill, after the lead returns) reports a successfully finalized run over, close with the user's next action — one command they can run now. A prohibition is not a next action. Take the pointer from the `report-finalize` result's top-level `nextRecommendedPhase` (`phase`, `status`, `rationale`; also on stderr as `next phase status:` / `next phase:` / `next phase rationale:`) — do not re-derive it from the report, and treat a `nextRecommendedPhaseError` as "pointer unreadable", said in one line before the `validate-run` branch. The same result also carries `nextCommand` — `{command, note}`, the table below already applied to this run. When `command` is non-empty it is the close; when it is empty the `note` says what to do with the `rationale` instead. After `implementation-planning`, open `blocks: approval` rows → `/okstra-user-response`. A recorded `accept-risk` / `select` / `answer` is not an open blocker. No open approval blocker → `/okstra-run` → `implementation` or `--approve` (do not start another planning run; do not say `/okstra-inspect`). For every other task type, quote the pointer's `rationale` in every branch — that sentence is the report's own reason and it is what the user asked to be analysed. Pointer `status: ready` → `/okstra-run` for that phase; `status: terminal` → say the task is finished, name any follow-up tasks this run registered, and do not say `/okstra-inspect`; `status: blocked` → issue the command the `rationale` calls for (`/okstra-user-response` for the `C-NNN` ids, `/okstra-run` for the phase it names); `validate-run` failed with `recovery.mode: phase-reentry` → name the cause and use `nextCommand` for the recorded earlier phase; otherwise `/okstra-inspect status`.
557
+ - After Step 6, begin the lead workflow without re-summarizing the skill itself. For a single run, finish after Step 6 and any same-run recovery, unless the user has already authorized continuing the task through further phases. In an unattended chain where `orchestration.chainStages` has 2+ elements, repeat Step 6 per stage until Step 7's queue is empty (or it stops at a "not ready" / exception gate), then finish. When `report-finalize` returns `recovery.mode: same-run`, continue the authorized corrections in this run and execute `recovery.resumeCommand` before closeout; preserve approvals and model choices without reopening the wizard. The command and owner issues are supplied by `report_finalize._finalize_recovery`. When the lead (or this skill, after the lead returns) reports a successfully finalized run over, close with the user's next action — one command they can run now. A prohibition is not a next action. Take the pointer from the `report-finalize` result's top-level `nextRecommendedPhase` (`phase`, `status`, `rationale`; also on stderr as `next phase status:` / `next phase:` / `next phase rationale:`) — do not re-derive it from the report, and treat a `nextRecommendedPhaseError` as "pointer unreadable", said in one line before the `validate-run` branch. The same result also carries `nextCommand` — `{command, note}`, the table below already applied to this run. When `command` is non-empty it is the close; when it is empty the `note` says what to do with the `rationale` instead. After `implementation-planning`, open `blocks: approval` rows → `/okstra-user-response`. A recorded `accept-risk` / `select` / `answer` is not an open blocker. No open approval blocker → `/okstra-run` → `implementation` or `--approve` (do not start another planning run). For every other task type, quote the pointer's `rationale` in every branch — that sentence is the report's own reason and it is what the user asked to be analysed. Pointer `status: ready` → `/okstra-run` for that phase; `status: terminal` → say the task is finished, name any follow-up tasks this run registered; `status: blocked` → issue the command the `rationale` calls for (`/okstra-user-response` for the `C-NNN` ids, `/okstra-run` for the phase it names); `validate-run` failed with `recovery.mode: phase-reentry` → name the cause and use `nextCommand` for the recorded earlier phase; otherwise `okstra task-show <task-key>`.
@@ -16,7 +16,7 @@ Generate a consolidated work schedule for the selected `implementation-planning`
16
16
  - User asks to generate a work schedule / plan / "schedule" for an entire `task-group`
17
17
  - User wants a single document that summarizes all non-done tasks with effort, risk, and dependencies
18
18
 
19
- **Do NOT use** for single-task analysis (use `okstra-inspect status`) or to execute one task (use `okstra-run`).
19
+ **Do NOT use** for single-task analysis or to execute one task (use `okstra-run`).
20
20
 
21
21
  Public invocation: `/okstra-schedule-gen [task-group]`. A title or directive may be supplied in the host conversation. If none is, name the schedule after the work itself — read the task titles in scope and write what they do (e.g. `폰트 업로드 경로 개선 — 작업 일정`). Never title it after the group token: that is a directory name, not what the work is.
22
22
 
@@ -103,7 +103,7 @@ One computation rule the template scaffold cannot carry inline:
103
103
 
104
104
  ### Step 2: Filter by workStatus
105
105
 
106
- For inference when `workStatus` is missing or empty, defer to the inference table in `skills/okstra-inspect/SKILL.md` (`status.4` → "Default value convention") — do not duplicate it here. Then filter: resolved `done` → exclude; everything else (`todo` / `in-progress` / `blocked` / `phase-done` / inferred non-done) → include.
106
+ When `workStatus` is missing or empty, infer `done` if `currentStatus` is `completed` and `workflow.nextRecommendedPhase.status` is `terminal`; infer `phase-done` if `currentStatus` is `completed` and `workflow.currentPhaseState` is `completed`; infer `blocked` if `currentStatus` is `contract-violated` or `workflow.currentPhaseState` is `blocked`; otherwise infer `in-progress`. Do not write inferred values back. Then filter: resolved `done` → exclude; everything else (`todo` / `in-progress` / `blocked` / `phase-done` / inferred non-done) → include.
107
107
 
108
108
  If 0 tasks remain, output `All tasks in this task-group are done. There is no schedule to generate.` and stop **without creating a file**.
109
109
 
@@ -305,7 +305,7 @@ Reached only after both Step 5.5 gates return `pass`. Promote the verified same
305
305
 
306
306
  | Case | Handling |
307
307
  |------|----------|
308
- | `workStatus` absent or empty | Resolve via the `okstra-inspect status.4` inference table; include unless resolved `done` |
308
+ | `workStatus` absent or empty | Apply the inference rules above; include unless resolved `done` |
309
309
  | Filtered task count is 0 | Emit the "all tasks are done" message; do NOT create a file |
310
310
  | No implementation-planning report | List with a `[NEEDS-PLANNING]` banner only; no stage picker / Gantt / day total |
311
311
  | 0 remaining stages (all done, workStatus unmarked) | `_Complete — no remaining stage_`, no forward computation |
@@ -20,8 +20,7 @@ machine, or when adopting okstra in a new project.
20
20
 
21
21
  ## When NOT to use
22
22
 
23
- - A task is already in flight → use [`okstra-run`](../okstra-run/SKILL.md) or
24
- [`okstra-inspect status`](../okstra-inspect/SKILL.md).
23
+ - A task is already in flight → use [`okstra-run`](../okstra-run/SKILL.md).
25
24
  - Day-to-day usage in a project that already has `project.json` — skip this skill.
26
25
 
27
26
  ## Prerequisites
@@ -56,7 +55,7 @@ Replace `<host-runtime>` with the resolved literal value before executing each
56
55
  command. Keep the same resolved host for installation, preflight, diagnostics,
57
56
  and retries, including retries against another project or npm cache directory.
58
57
  The runtime registry validates host IDs; the skill command contract is checked
59
- by `tests/contract/test_docs_runtime_contract.py::test_skills_declare_their_host_runtime_explicitly`.
58
+ by the former Python suite; that regression check is now retired.
60
59
 
61
60
  ```bash
62
61
  npx -y okstra@latest install --runtime <host-runtime>