kimi-code/apps
Kaiyi 946b8ec03d feat(flow): FlowJump — stage jumps with per-flow approval policy
The supervisor can now move an active run to another stage: backward
to redo work whose conclusion was invalidated, forward to skip stages
that do not apply to the task. The definition's frontmatter governs
it via jumps: approval (default — every jump goes through a user
review), free (unsupervised), or disabled (strictly linear, the old
behavior).

- New FlowJump tool (to + reason, both required): validated like the
  other flow tools, solo-response only, supervisor-only, flag-gated.
- A durable FlowJumped event moves the undoable stage pointer and
  appends a kind: 'jump' record (from/to/reason/decidedBy) to the
  retained audit trail; the run epoch bumps on every jump so verdicts
  and reminders prepared before it are void, and a revisited stage
  re-discloses its reminder.
- The approval flow reuses the gate-review machinery: a new
  flow_jump_review display (protocol + kap-server + engine schemas),
  epoch-bound reviews, observed-rejection provenance, and no
  session-wide approval anywhere (TUI choices, ACP options, VS Code
  downgrade all treat jumps like gates).
- GET /sessions/{id}/flow exposes run.jump_policy and the audit
  records as a verdict/jump union.
- The supervisor contract's Order rule now teaches FlowJump instead
  of mandating abort-and-restart.
2026-08-19 14:48:23 +08:00
..
kimi-code feat(flow): FlowJump — stage jumps with per-flow approval policy 2026-08-19 14:48:23 +08:00
kimi-inspect feat(kap-server): add workspace fs:suggest file completion endpoint (#3019) 2026-08-18 11:53:48 +08:00
vis feat(agent-core): add tower command to orchestrate multi-agents (#2633) 2026-08-16 15:13:42 +08:00
vscode feat(flow): FlowJump — stage jumps with per-flow approval policy 2026-08-19 14:48:23 +08:00