2 Commits

Include renames

Author	SHA1	Message	Date
jpmschweitzerandClaude Opus 4.7	8310730506	document the stream-json control protocol + D-78 ... Empirical spike against claude 2.1.150 (driving the real CLI over stdin/stdout + reading the shipped binary's zod schemas) pinned the wire shapes for the stream-json control protocol: the can_use_tool permission request, the control_response envelope, the --permission-prompt-tool stdio enabler (without it "ask" tools silently auto-deny), the allow-requires-updatedInput quirk, and AskUserQuestion answered via updatedInput.answers. Captured in a version-pinned spike note with a resilience section (detection canaries + a ranked fallback menu) so a future Anthropic change to this undocumented contract doesn't leave us at a blank slate. D-78 records the decision: permissions ride the stdio control channel, not MCP (MCP is reserved for capability/tool provision); refines D-77. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-25 08:40:05 +02:00
jpmschweitzerandClaude	3f2e5ad9a9	spike T-134: Claude Code team/transcript internals (pinned to 2.1.148) ... Findings note for the tmux agent-team work (epic T-132), validated from real on-disk artifacts (42 past team configs, real team + subagent transcripts, current-version .meta.json) plus a synthetic control-mode test and the tmux manual — no live team run / quota needed. Key results: teammates get tmux panes (config tmuxPaneId) and write transcripts at <munged>/<sid>/subagents/agent-<hex>.jsonl + .meta.json; tmux 3.6a has no %pane-died (use %window-close/%layout-change), and polling list-panes -a is the reliable lifecycle baseline; the real risk is identity linkage — pane/teammate (config: name@team, agentType, %pane) joins to the transcript only via agentType (config <-> .meta.json), ambiguous for same-type teammates, so T-139 needs a joinedAt/mtime or lead-transcript tiebreaker. Co-Authored-By: Claude <noreply@anthropic.com>	2026-05-22 19:52:00 +02:00