AASES計画を本来目的から再構成-2 (#453)

[satoshiamenomori]

Closes #453

Outcome

Adds the minimal opt-in agmsg app lifecycle for one project-owned managed tmux session:

• explicit Start session for the selected team's exact director
• seven-field inventory for registration/process/pane/worktree/generation/active turn/final ACK
• Detach, app close, and Reconnect without ending the director
• runtime-enforced refusal for active turn, pending ACK, dirty worktree, and UNKNOWN
• graceful End only after clean + idle + final ACK

Scope

The app calls the external Issue #22 runtime only when both AASES_SESSION_BIN and AASES_SESSION_RUNTIME_ROOT are explicitly configured. It does not vendor the runtime or add distribution, generic shell execution, browser/crawler, incident, or rollout infrastructure.

Managed panes are tmux attach clients. Existing direct-agent pane behavior remains unchanged. A narrow PTY detection-type override lets the existing state detector classify the director behind tmux without changing the launched command.

Evidence

Final candidate 572498737b7cd015c9fa49629a4c85d55a74d1c3:

• managed-session TypeScript test: 5 passed
• frontend TypeScript/Vite build: passed
• cargo test managed_session: 2 passed, 59 filtered out
• git diff --check: passed
• real macOS app canary with one Codex director: passed
  • explicit start and all seven inventory fields
  • active-turn End denied with ACTIVE_TURN
  • idle/unacknowledged End denied with ACK_PENDING
  • dirty End denied with DIRTY
  • pane detach and app close preserved the tmux session
  • app restart found ACTIVE state and reconnected without respawn
  • final ACK followed by graceful End returned INACTIVE and removed the exact tmux session

Review was limited to one change-diff review, one mandatory correction, and one focused confirmation.

Deferred

Runtime distribution/installer, release packaging, all-project rollout, browser/crawler, generic Git/shell control, incident framework, and broad conformance suites remain out of scope.