Skip to content

feat(runtime): unify durable retained interactions - #31

Draft
drewstone wants to merge 25 commits into
mainfrom
feat/exact-interactive-session-20260816
Draft

feat(runtime): unify durable retained interactions#31
drewstone wants to merge 25 commits into
mainfrom
feat/exact-interactive-session-20260816

Conversation

@drewstone

Copy link
Copy Markdown
Contributor

Outcome

Braid now uses one retained interaction path for CLI Bridge and Tangle Sandbox runs. Exact process identity, control claims, restart recovery, detach, reconnect, cancellation, and interaction state survive a Braid restart.

The TUI hides response actions when the installed runtime cannot execute them. This keeps unsupported plan, question, and approval actions fail-closed until the upstream response operation releases.

Architecture

  • Domain interaction state owns canonical interaction identity.
  • Retained execution adapters own provider recovery and control.
  • Shared TUI actions stay independent from provider routing.
  • No second terminal transport or provider execution path was added.

Proof

  • TypeScript check passed.
  • Biome lint passed across 769 files.
  • Module boundaries passed across 496 modules with zero cycles.
  • Dependency audit passed across 92 production packages with no high or critical finding.
  • Retained and interactive tests passed: 42 of 42.
  • TUI tests passed: 147 of 147.
  • Live proof scripts redact credentials and bind evidence to the exact run.

Open upstream checks

  • Sandbox 0.29.0 does not expose exact claimControl and stopLifecycle methods. Sandbox 0.30.0 is in review.
  • The released runtime has no native structured response operation. The source fix is in progress.

Visual proof

Braid live TUI

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant