Repository navigation
Conversation
SaladDay
deleted the
codex/diagnostics-observations-integration-20260928
branch
October 10, 2026 05:05
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Records deployment-default model usage and supported provider failures only after a root Turn outcome commits. New Sessions freeze the exact encrypted provider revision; later settings changes cannot attribute older results to a new credential. The three observation fields remain nullable, are throttled using database time, and cannot delay completion beyond the bounded best-effort update.
Also preserves E2B field parameters only for the agreed exact status/code/parameter combinations while retaining fixed safe messages and uncertain-write behavior.
Validation: real PostgreSQL API/store/execution tests, generated OpenAPI/docs/sqlc checks, 740 combined client tests and typecheck passed. An official SDK CI failure exposed shared database state left by a provider-resolution test; it now uses an isolated fixture and verifies shared state is unchanged. The corrected API gate, unchanged official Python SDK test, CI Go SDK subset and official sessions CI passed. A later CI typecheck exposed one onboarding fixture missing the required nullable fields; that shared fixture now includes them, and Web typecheck plus its targeted tests passed. A new independent full-delta blind review found no issues (static review; earlier focused real-DB verification remains separate).
The combined frontend/backend server repository gate passed on source52fcd3f1. The browser fixture also returns the required null observation fields for both initial state and provider PUT/GET responses; a real local fixture HTTP probe passed. The preceding CI run passed 60 browser cases and failed three provider flows against the incomplete fixture. Full core-check and official sessions CI on corrected source8ab68e08 both passed; real model and installed-artifact observation acceptance remain pending. No public API shape or production Web implementation changes.