Prototype: find the client-independent harness boundary

[joaomj]

Parent map: #1

Blocked by: #5

Decision to resolve

Can the native agent loop support both terminal and browser clients without duplicating behavior or first rewriting the application?

Prototype question

Find the smallest throwaway extraction or seam that routes one native turn through a client-neutral event and approval interface while leaving terminal behavior intact.

Evaluate

• Coupling among agent.rs, session_turn.rs, AppState, renderer, approvals, persistence, hooks, and tools.
• Whether callback/events, a service boundary, or another seam is the least disruptive route.
• Which native features become difficult or unsafe under each option.
• Whether the same core can later serve Telegram.

Output

A prototype finding and recommendation. Prototype code is disposable unless separately approved.

Resolves when

The map has a credible client-independence boundary that preserves the native terminal experience.