7dee729ef7
Scheduling agent.continue() inside navigateTree started a post-prompt task before the interactive /tree handler rebuilt its transcript, so a fast provider's agent_start/turn_start could render against the stale pre-rebuild UI and then be clobbered by renderInitialMessages. navigateTree now reports the commit via askReanswerCommitted instead of resuming, and SelectorController.showTreeSelector calls the new AgentSession.resumeAfterAskReanswer() only after renderInitialMessages + reloadTodos, so the resumed turn always renders against the rebuilt transcript. Addresses chatgpt-codex-connector review on #6484. Fixes #6483