fix(voyage): dashboard reads fm.plan_critic + orchestrator doc-consistency (906f155d, bee33a69)
This commit is contained in:
parent
4910999198
commit
9909ce1066
3 changed files with 30 additions and 1 deletions
|
|
@ -431,6 +431,17 @@ After both complete:
|
|||
machine-checkable — a plan without verifiable manifests cannot drive
|
||||
deterministic execution.
|
||||
- Add a "Revisions" note at the bottom documenting changes
|
||||
- **Inject `plan_critic` verdict into plan frontmatter** (after dedup, after
|
||||
any blocker/major revisions). Read the verdict from
|
||||
`/tmp/plan-critic-out.json` and atomically update plan.md via
|
||||
`readAndUpdate` from `lib/util/markdown-write.mjs`:
|
||||
`frontmatter.plan_critic = criticVerdict`. Field semantics: one of
|
||||
`APPROVE`, `APPROVE_WITH_NOTES`, `REVISE`, or `BLOCK`. The
|
||||
`plan_critic` field is additive + optional — plans without it remain
|
||||
valid. Surfaces (notably `playground/voyage-playground.html`
|
||||
`buildArtifactKeyStat`) read this field directly without re-parsing
|
||||
the review JSON. Detailed contract documented in
|
||||
`commands/trekplan.md` Phase 9 (906f155d, bee33a69).
|
||||
|
||||
### Phase 7 — Completion
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue