/kbd-child-exit
Close the active child loop and return to the parent — the counterpart to
/kbd-new-child. With --enter, descend into the selected child instead.
What this does
exit (default)
- Requires the active child to have a
reflection.md(run/kbd-reflectfor the child first; refuses otherwise). - Writes
handoff-out.mdin the child dir — deliverables, goal completion status, unresolved items, recommendations to the parent. - Rolls the child's progress up the ancestor chain (
lib/kbd/rollup.mjs): each parent node'sprogress.jsongains achildren{}block (status, canonical implementation counters, legacy counter aliases, certification status, handoff, and completion timestamp). - Pops the last element of
path[], clearschildPointer, and restores the parent's cursor — the parent loop resumes with the child's result visible. - Fires
child:after.
--enter
Descends into the currently selected childPointer: sets path[] to the child
chain and clears childPointer, so the next /kbd-new-child nests under
this child. Enter and exit are the child-navigation pair: select with
/kbd-next-child, descend with /kbd-child-exit --enter, return with
/kbd-child-exit.
Progress Signals (MANDATORY)
Before any other action, emit:
Starting kbd-child-exit — <child chain>
When the child is closed (or entered), emit:
Completed kbd-child-exit — exited <child chain>
Use the canonical chain from path[]. Emit to plain response text.
How to invoke
node scripts/kbd-child-exit.mjs # exit
node scripts/kbd-child-exit.mjs --enter # descend
Prerequisites: the waypoint path[] must have depth > 1 to exit; a
childPointer must be selected to --enter.
Examples
/kbd-next-child auth-refactor # select the child
/kbd-child-exit --enter # descend into it (new children nest here)
# … run the inner loop, /kbd-reflect it …
/kbd-child-exit # write handoff-out, roll up, return to parent
Hook integration
Fires child:after for the closing child. The opening child:before is fired
by /kbd-new-child.
Selected-method recovery and authority
Before dependent work, run node <pack-root>/scripts/kbd-method-context.mjs --project <project-root> --phase <canonical-phase-id> --write (or read the phase-local method-context.md when Node is unavailable) and act on its status:
RESOLVED_REFERENCES— continue with the recovered method, contract and stage authority; preserve the same references in role inputs, dispatch and handoff read order.BLOCKED— the contract, its binding, a calibration reference, a supersession or a deviation's cadence/reason is missing or changed, or canonical status is unavailable; resolve it explicitly. Prior commands, memory and tool inventories are not fresh authority.CONFLICT— a governing rule file the active harness loads grants an exception VLBV forbids (for example a compiler check or an hourly integration gate during generation). Stop before dependent work and show the conflict; continue only after the operator records aKBD-POLICY-ACKdecision for that file's current hash. Never rewrite operator-owned policy, and never treat an exception as authority for tests, builds, dry-runs or generated-code verification.
VLBV is the method for every phase (project default verificationMethod: "VLBV"); a deviation exists only as a signed KBD-METHOD decision naming the method, its execution cadence and its reason, and it is disclosed in the closure packet. Define acceptance before generation; generated code executes only at the value-phase boundary (B4) and, after an authorized repair, at B5 — see kbd-process-orchestrator/references/boundaries.md. Tasks, hours, commits, reviewer requests and compiler problems create no boundary. Preserve original evidence, consumed budgets and unresolved effects across resume and supersession; reconcile an uncertain effect before any retry. Full rules: kbd-process-orchestrator/references/method-context.md.