Follow-ups from the Codex review of #124 at d966a09, left open on purpose so the PR could finish for the demo. Each is a P2 in tools/integration-viewer, and each thread on #124 has the detail.
- The synthetic outage misses long polls in flight. #124 thread. An events long poll that starts just before the synthetic API's 11 s dropout keeps waiting and can answer during the outage. The API should recheck the outage after each wait and drop the pending request. This affects only the synthetic demo of reconnection.
- A failing events poll blocks the result read. #124 thread. When the status read succeeds with a terminal status but the events read fails, the loop's
continue skips the result and preview reads. If only the events endpoint stays down, no outcome ever shows. The result read should run after a successful status read, whatever happens to the events read.
- A pending result can briefly show "Reading it…". This one is cosmetic, found while testing: during a refresh the model caption can flash the reading text. It needs no review cycle of its own.
These tests exist in tools/integration-viewer/test/, and node --test "test/*.test.js" runs them. CI does not run them yet.
Follow-ups from the Codex review of #124 at
d966a09, left open on purpose so the PR could finish for the demo. Each is a P2 intools/integration-viewer, and each thread on #124 has the detail.continueskips the result and preview reads. If only the events endpoint stays down, no outcome ever shows. The result read should run after a successful status read, whatever happens to the events read.These tests exist in
tools/integration-viewer/test/, andnode --test "test/*.test.js"runs them. CI does not run them yet.