kami 76da8c40b7 End the implementer's trajectory when Orchestra reopens the phase
Run 20 showed the leak precisely: the reopen rotated the session, and 31
seconds later the planning session that replaced it recorded phase-2 of the
plan being replaced. The implementer's .orchestra/plan-progress.json had
outlived it in the worktree, and the successor executed it.

Two changes. Phase verification now belongs to the implement phase and is
refused anywhere else, which covers every worker and every path rather than
the one that produced it. The rotation also drops the ended session's
request files, so a successor never inherits work from a trajectory
Orchestra has already invalidated.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CVbaKucEYBjMqVeUgJUsc1
2026-08-30 05:46:11 +04:00

orchestra ui mockups

final/ contains the nine accepted/current screen directions:

  1. dashboard
  2. task detail
  3. terminal live pane
  4. tasks
  5. decisions
  6. workers
  7. projects
  8. review
  9. settings

iterations/ contains every generated mockup from the design session, including superseded variants.

orchestra-ui-spec.md is the accompanying implementation/design specification.

S
Description
No description provided
Readme 32 MiB