lsm / neokai / 25589170979 / 11
82%
dev: 82%

DEFAULT BRANCH: dev
Ran
Files 278
Run time 13s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 18.006% (+0.002%) from 18.004%
25589170979.11

push

github

web-flow 
fix: plan & decompose workflow runtime, gate, and prompt issues (#1828)

* fix: plan & decompose workflow runtime, gate, and prompt issues

Six interlocking issues prevented the Plan & Decompose workflow from
completing on its own:

- ChannelRouter.deliverMessage activated the target node before
  evaluating the channel's gate, so the tick loop spawned sessions for
  blocked nodes (e.g. Task Dispatcher firing before all 4 reviewers
  had voted on plan-approval-gate). Gate evaluation now runs first;
  activation only happens once the gate is open.
- Auto-gate-write in send_message used GateDataRepository.merge, which
  shallow-merges. For map-type fields (like plan-approval-gate's
  `approvals`) each reviewer's vote replaced the whole map. The
  auto-write now deep-merges entries for any field whose definition
  has type:'map' before delegating to the repo's shallow merge, so
  each reviewer's lens entry accumulates.
- The planner prompt previously said the plan-pr-gate would "verify"
  the PR automatically without telling the planner to send the
  pr_url. Without an explicit send, the gate stayed closed and Plan
  Review never started. The prompt now mandates
  `send_message(target="Plan Review", data: { pr_url })` and notes
  the resetOnCycle behaviour.
- Reviewer prompts claimed the terminal-action tools were
  unavailable, which is incorrect — they are registered for every
  node-agent session. The wording now states they are technically
  available but STRICTLY off-limits for reviewers (calling them would
  close the run prematurely) and reserves them for the Task
  Dispatcher.
- Lens-specific reviewer prompts and the central PD_PLAN_REVIEW_PROMPT
  now describe the gate-write payload as
  `data: { approvals: { "<lens>": "approved" } }` matching the actual
  field schema, instead of the legacy `reviewer_name`/`approved`
  scalar shape that the auto-gate-write would silently strip.
- plan-approval-gate's description spells out the deep-merge contra... (continued)

13415 of 74502 relevant lines covered (18.01%)

9.3 hits per line

Source Files on job daemon-online-websocket - 25589170979.11