Recover durable continuation, approval, and observability fixes from historical branches - #211
Merged
Merged
Conversation
# Conflicts: # CONTEXT.md
# Conflicts: # CONTEXT.md # docs/architecture.md
# Conflicts: # CONTEXT.md # docs/architecture.md
# Conflicts: # CONTEXT.md # docs/architecture.md
# Conflicts: # docs/architecture.md
# Conflicts: # evals/validation-authority-foundation.ts
…-recovery-20260912
…ckpit-accessibility-20260912
…ccessibility-20260912
…-recovery-20260912
…ckpit-accessibility-20260912
justsml
marked this pull request as ready for review
September 12, 2026 21:23
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
1 participant
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.
Historical branches contained recovery fixes that were absent from current main: rejected PostgreSQL approvals, durable continuation and tool budgets, persisted model identity, oversized context handling, final provider failures, and serialized observability writes. This wave salvages those changes on top of #210 while retaining newer main behavior and dependency security repairs.
Integration review tightened projection to completed assistant tool-result turns, normalized recovery digests to persisted JSON, retained current controller stopping, and added the canonical provider-alias companion fix. Historical paid probes, judge fallbacks, pool/timeout tuning, and unsafe command canonicalization remain excluded. Source provenance and held branches are recorded in
docs/branch-integration-2026-09-12.md.Focused recovery, controller, transport, model-admission and observability regressions pass. The rejected-approval regression also passed against a real isolated PostgreSQL 17 instance, which was removed afterward. Frozen installation, typecheck and Biome pass (existing warnings remain). The fresh production build and all 27 Chromium browser tests passed. The combined local suite passed: 201 unit, 1,161 integration, 859 eval and 50 package tests. Seven optional integration cases were skipped in that suite; the PostgreSQL case passed separately against PostgreSQL 17. All six hosted gates passed on
371697bc7869b6b370c1e2fc30b7eb3efd9631e4in run 34719578844. Merged asefc28abea7f847946d4e6340f1d0cc99eedf3d5f. The fetched main tree matches the tested PR head exactly. No paid model calls or human approvals were simulated.