Skip to content

Validate late research context refusals for upstream #912 - #17

Draft
cwschroeder wants to merge 1 commit into
validation/pr912-f622d935from
codex/pr912-late-context-20261017
Draft

cwschroeder wants to merge 1 commit into
validation/pr912-f622d935from
codex/pr912-late-context-20261017

Conversation

@cwschroeder

@cwschroeder cwschroeder commented Oct 17, 2026 •

Copy link
Copy Markdown
Owner

A streamed request can fit initially but exceed its window after Cortheon adds research results. At upstream ashhart#912 head 8f874288, that late context refusal becomes HTTP 400 with no SSE error, while initial context refusals remain streamed. This patch routes only unopened Refused + context_length through the existing context-error stream. Capacity errors keep HTTP 503.

Candidate 393e5c7d contains a two-window regression using the actual scripted Cortheon path. It fails before the fix and passes afterward in Debug and Fast. The CPU server target passes 378/378 tests; whole-tree formatting, whitespace and lean pass (517/517 against main, zero new). Astra reviewed the exact two-file fix without another material finding.

This validation PR isolates those two files on composition f622d935, which merges upstream ashhart#912 unchanged onto main 6ee828c2, preserving authorship. The patch also applies to 8f874288. Complete candidate CI is green at 393e5c7d: the Linux No GPU workflow ran zig build test, test-kernel-contract, test-golden, fuzz-cortheon and lean (517/517, zero new). Whole-tree format and both app/mobile workflows also pass. The draft validation PR isolates these two files on f622d935; it is an adoption aid for this PR.

The first PR desktop run failed in the unchanged guest.test.ts output-limit case with Operation not permitted; its failed-job rerun passed without source changes. The same commit’s push desktop run and the unchanged composition base’s app workflow had passed already. Thirty focused base probes did not reproduce that error, so its cause remains undiagnosed. No device/model, performance or deployment qualification is claimed. Upstream review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant