Outcome
Make every pending Function required action visible and navigable in the Session composer.
Current behavior
When Core returns multiple Function actions, Web renders only the first action and shows 1 / N. The first action can still be submitted correctly, so this is a follow-up interaction gap rather than a blocker for the current capability milestone.
Acceptance criteria
- Show the pending Function-action queue and let the operator switch between actions.
- Preserve a separate result draft for each exact Turn ID and call ID while switching.
- Submit only the explicitly selected action with its original identity.
- Reconcile against refreshed durable Session state after submission.
- Never auto-execute, auto-approve, or automatically retry an uncertain result write.
- Add focused component tests for switching, draft retention, removal after durable refresh, and stale-action invalidation.
Non-goals
- Executing tools in the browser.
- Changing Parsar Core or its protocol.
- Adding automatic approval policy.
Outcome
Make every pending Function required action visible and navigable in the Session composer.
Current behavior
When Core returns multiple Function actions, Web renders only the first action and shows
1 / N. The first action can still be submitted correctly, so this is a follow-up interaction gap rather than a blocker for the current capability milestone.Acceptance criteria
Non-goals