Commit 138588d5 authored by Vacaliuc, Bogdan's avatar Vacaliuc, Bogdan
Browse files

plan: redesign §4.4 addendum (recap key) + §10 phase-1/2/3 status 



Phase 3 implementation pass (this session) discoveries and markers:

§4.4 addendum: the exact settings.json key for "disable inline
recap" in the current Claude Code schema is awaySummaryEnabled
(boolean; set to false). Schema description: "the session recap
(shown when you return after being away for 5+ minutes)". Marked
@internal in the schema — works today, name may change in a future
version. Each role's session-setup step should write this in
<clone>/.claude/settings.local.json alongside the .statusLine
install.

§11 resolution #2: annotated with the resolved key name pointing
to the §4.4 addendum.

§10 (NEW §10.0 status table): records that phases 0-3 are done
with commit pointers; phase 4 (second dry run) and phase 5
(production orchestration) remain. Per the [TIME-BOXED] aggressive
context persistence rule — gives the next session a fast pickup
point without having to re-derive what shipped.

Co-Authored-By: default avatarClaude Opus 4.7 (1M context) <noreply@anthropic.com>
parent 511590ff

plan/orchestration-v2-redesign.md

+23 −1
Original line number Diff line number Diff line
@@ -547,6 +547,17 @@ exact name in your Claude Code version): **flag this as one of the 
unknowns to verify with the `update-config` skill when applying the

plan.**



**Addendum (2026-05-02, Phase 3 implementation pass):** the exact

key in the current Claude Code settings schema is **`awaySummaryEnabled`**

(boolean; set to `false` to disable). Schema description: *"the

session recap (shown when you return after being away for 5+

minutes)"*. Note the schema marks it `@internal` ("Hidden from

public SDK types until external launch") — the key works today but

its name may change in a future version. Each role's session-setup

step (orchestration.md §9.1-§9.3, §9.6 step 2 of session setup)

should set this in `<clone>/.claude/settings.local.json` alongside

the `.statusLine` install.



### 4.5 Why a 4th agent helps even with great visibility



Statusline and state files give the user a per-agent view. A 4th
@@ -1099,6 +1110,17 @@ permissions. 


## 10. Implementation plan (phased)



### 10.0 Status (updated 2026-05-02 by Phase 1/2/3 implementation pass)



| Phase | Status | Commits on `lr_reduction-new_workflow-repairs` |

|---|---|---|

| 0 — review and approve | ✓ done (committed 2026-05-02 as `2c9761b plan: finalize v2 redesign — incorporate reviewer resolutions`) | n/a |

| 1 — protocol doc + prompts | ✓ done | `361da1c` orchestration.md v2; `305fc4c` Analyst/Developer/Integrator prompt sync; `33d8244` Administrator-prompt.md; `63a686e` dry-run.md F2/F4/F5 + cadence; `b8186ea` initialization.md §0 banner + §11 verification; `3fea979` Initialization-prompt.md (v1 fallback) + §0 banner |

| 2 — supporting scripts | ✓ done | `~/.claude/state/agent-statusline.sh` (user-scoped, mode 700, not committed); `511590f` plan/scripts/poll-wrapper-{Analyst,Developer,Integrator,Administrator}.sh (mode 700) |

| 3 — Stop hook + recap-key discovery | ✓ done | `~/.claude/settings.json` Stop hook + `~/.claude/state/restore-statusline.sh` (user-scoped, not committed); §4.4 addendum + §11.2 resolution annotation in this doc |

| 4 — second dry run | pending | (next session — do not start without re-reading §10.5) |

| 5 — production orchestration | pending | (after phase 4 is clean) |



### 10.1 Phase 0 — review and approve (this session, immediate)



1. Human reads this document.
@@ -1255,7 +1277,7 @@ these as authoritative on top of the §1-§10 design. 
| §11 # | Question | Resolution |

|---|---|---|

| 1 | Administrator clone | **4th dedicated clone** — `<path-to-session-4>` (proposal accepted) |

| 2 | Recap-suppression mechanism | Use the `update-config` skill against `<clone>/.claude/settings.local.json`. Reviewer's understanding of the skill is **correct**: it handles both `settings.json` and `settings.local.json` (including hooks like the Stop-restore in §10.4) — confirmed |

| 2 | Recap-suppression mechanism | Use the `update-config` skill against `<clone>/.claude/settings.local.json`. Reviewer's understanding of the skill is **correct**: it handles both `settings.json` and `settings.local.json` (including hooks like the Stop-restore in §10.4) — confirmed. **Exact key (resolved in Phase 3, 2026-05-02): `awaySummaryEnabled: false`** — see §4.4 addendum |

| 3 | Administrator autonomy | **Read-only on workers** in v2 (proposal accepted). Future v3 can revisit if pattern data justifies it |

| 4 | Discovery method default | **`git ls-remote` (portable)** — GitHub REST + ETag stays as documented opt-in alternative for high-frequency polling |

| 5 | Apply in this session? | **No — defer to a clean session.** Phase 1 prompt is in §16 below |