Repository navigation
Organize Byobu and psmux attachments without changing session identity #402
Description
Parent
What to build
List/show and explicitly authorized attachment organization/control with generation pinning, structured stdio ownership and visible bounded terminal fallback.
Acceptance criteria
- List/show and explicitly authorized attachment organization/control with generation pinning, structured stdio ownership and visible bounded terminal fallback.
- Demonstrate the stated end-to-end behavior through public operations and every capable CLI/API/MCP surface.
- Cover authorized success, stale/unsupported/unauthorized targets and relevant crash/reconnect or uncertain-effect cases.
- Record source/package evidence and preserve existing work, authority and cumulative accounting; production effects need separate authorization.
Existing upgrade reconciliation
New controller capability; reuse the existing owners and the specification’s recorded decisions. No existing completed acceptance is invalidated.
Delivery boundary
Use public-seam TDD and exact red/green receipts. Source, integration, installed disposable acceptance and production activation are distinct. No provider experiment, credential copying, shared restart, governor activation or resource renewal is implied.
Activity
ecochran76 commentedon Oct 30, 2026
Implemented/qualified on
feat/controller-393: workera9ef6d8, integrated8a20e6e.Fixed host-declared adapters organize Byobu/tmux and psmux attachment presentations without changing logical session identity. Exact snapshots fence changed process/socket/server/layout generations. Stable workspace grants survive apply→fresh snapshot→undo; each operation still pins its current exact target. Capture/input deny private/draft/working/unknown privacy; structured stdin uses the existing client broker, never reopens/steals its pipe. Terminal fallback is explicit and bounded. Durable intents retain uncertain outcomes without replay.
Worker installed proof passed local CLI, remote CLI, API, OAuth MCP and native MCP with actual isolated tmux. Nine attachment tests, nine legacy organization tests and the flow surface test passed; primary independently reran nine attachment tests plus the flow surface test after integration. Evidence:
docs/dev/evidence/plan0190/tabs402-public.json.Synthetic psmux protocol coverage is source/adapter qualification; actual Windows psmux matrix remains #405. No production tabs, provider calls, shared restart, governor activation or new resource limits were touched. The single broad review remains scheduled after all children close.