# Impact analysis

## Target

Abort and ordinary follow-up submission flow across the Bridge registry, Tauri
wrapper, workspace reducer, and conversation composer.

## Dependents (6)

- `src/bridge/service.js`: exposes registry routing through the local socket.
- `ui/src-tauri/src/bridge.rs`: proxies submit/abort to the Bridge.
- `ui/src-tauri/src/lib.rs`: exposes Tauri commands to the frontend.
- `ui/src/App.tsx`: submits prompts and coordinates abort UI state.
- `ui/src/workspace/reducer.ts`: tracks runtime activity, queues, and pending
  submissions.
- `ui/src/components/ConversationWorkspace.tsx`: renders composer actions and
  pending submission labels.

## Affected stories

No release plan or epic capsules exist.

## Test coverage

- `test/agent-registry.test.js`: existing busy submission routes to Pi
  `follow_up`.
- `ui/src/workspace/reducer.test.ts`: existing optimistic-message
  reconciliation.
- `ui/src/components/components.test.tsx`: existing composer component wiring.
- Gap: abort priority/feedback, returned delivery mode, duplicate follow-ups,
  and authoritative queue counts are untested.

## Risk: Medium

This changes command scheduling and message acknowledgement at the Pi RPC
boundary; an incorrect transition could lose or mislabel user follow-ups.

## Recommended action

Use one normal submit action with Bridge-selected delivery, make abort
out-of-band and visibly pending, then add regression tests for queue and
message reconciliation.