# feat\(orchestration-v2\): route Codex thread feedback uploads through v2 \(\#7949\) · stienswout/t3code

[View on GitCafe](https://git.cafe/stienswout/t3code/commit/77d64e5ce4cb5c88ce0f9a083d6dc4061826c157)

Repository: [stienswout/t3code](https://git.cafe/stienswout/t3code)

Visibility: public

Requested revision: 77d64e5ce4cb5c88ce0f9a083d6dc4061826c157

Requested commit: 77d64e5ce4cb5c88ce0f9a083d6dc4061826c157

Commit: 77d64e5ce4cb5c88ce0f9a083d6dc4061826c157

Tree: ffd7425b0a1e877ad5d6076b36e26ed47fe238e1

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
feat(orchestration-v2): route Codex thread feedback uploads through v2 (#7949)

The round-10 rebase stubbed providerUploadFeedback to an explicit error
because its v1 ProviderService route died with the v2 rewrite. The route
now goes through the v2 runtime: session runtimes may expose an optional
uploadFeedback capability, the Codex adapter implements it against the
app-server's feedback/upload request, and the WS handler resolves the
thread's live provider session through ProviderSessionManagerV2 —
failing with a plain-language reason when no session has run, the session
is gone, or the driver has no feedback channel. This also un-blocks the
dormant mobile feedback UI.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

```

## Parents

- [13ba775496ff2907054fbb96e413a74e48793067](https://git.cafe/stienswout/t3code/commit/13ba775496ff2907054fbb96e413a74e48793067?format=markdown)

[Source at this commit](https://git.cafe/stienswout/t3code/tree/77d64e5ce4cb5c88ce0f9a083d6dc4061826c157?format=markdown)