Repository navigation
feat(gateway): upstream 2.100 AR rebuild with .27 parity regressions - #46
vadymhimself wants to merge 2 commits into
Conversation
Reauthor hosted pinning, canonical Messages fidelity, pool policy, physical accounting, analytics and provider/state contracts against upstream 6bae884. Preserve generic fixes and drop carried historical port debt. Add AR parity and trust-boundary regressions plus a required local CI gate; document paired upstream and hosted validation and release boundaries. Origin: hosted fork v2.65.0-vadymhimself.27; per-feature attribution and validation are recorded in FORK-DELTA.md and FORK-VERIFICATION.md. Includes upstream recovery-attempt PR lidge-jun#8882 and sidecar unused-hop refund lidge-jun#8899. Co-authored-by: Gauge <gauge@agentradar-house.staging.agentradar.com> Co-Authored-By: Claude Code <noreply@anthropic.com>
|
The reviewed candidate source is 4b7bf23. A packaged build was produced and locally delivered as opencodex-2.100.0-vadymhimself.1.tgz, SHA-256 07c8fa0a861180823628f19ecd19882f36fbe51cead07c901c9f1932d0eeef81. The extracted package reports the fork version and serves /healthz and the built dashboard from an isolated home. All 13 stale gateway PRs now link here and direct new work to port/ar-on-upstream-2026-11-18. No tag, merge, publication or deployment was performed. GitHub has created no check runs for this head; Actions remains an external blocker, not passing CI. |
|
HOLD: final bounded trust-boundary review found 2 verified blockers after candidate packaging: (1) strict SSE EOF tail bypasses frame validation; (2) queued hosted OAuth count_tokens lacks the generation path’s immediately-before-dispatch account-authority recheck, so a paused/removed/replaced pin can still send its captured credential. The locally delivered tarball 07c8fa0a8611… is NOT approved for installation. Fixes with controlled regressions are in progress; no running gateway was changed. |
Reject malformed strict SSE tails before relay. Preserve a read-only OAuth binding for token counts and revalidate after pacing; queued pause/removal/cancellation cannot dispatch stale authority and replacements use only the new credential. Bound Retry-After through the existing formatter. Add controlled regressions and supersede held build .1 with 2.100.0-vadymhimself.2. Co-Authored-By: Claude Code <noreply@anthropic.com>
|
REPAIRED candidate delivered: 2.100.0-vadymhimself.2, commit 6a14467. SHA-256 a9f2e6b07b59e3558920d5c62aea3889b77da1338ba2d0be677abb02d8e589a7. EOF tails now validate before relay; queued OAuth count_tokens rechecks account authority after pacing (pause/remove/cancel send nothing, replacement sends only the new credential). Count Retry-After is bounded. Focused regressions 35 pass; AR gate 534 pass; typecheck/structure/privacy/ratchet/diff pass. The extracted .2 package reports the correct version and serves health + dashboard in an isolated home. Initial .1 artifact remains HOLD. No merge, tag, publication, installation or deployment was performed; missing Actions checks are not passing CI. |
Repaired candidate delivered
Current build:
2.100.0-vadymhimself.2, commit6a1446797247680fa4dfb88e3f41caeeb034d746. SHA-256:a9f2e6b07b59e3558920d5c62aea3889b77da1338ba2d0be677abb02d8e589a7. The initial.1artifact remains HOLD and must not be installed.Summary
Rebuilds the AgentRadar gateway on current upstream
lidge-jun/opencodexdev (6bae884cbc, package 2.100.0) instead of the accumulated 2.65 fork history. The AR behavior that upstream lacks or deliberately differs on is re-authored on top. Future refreshes can start from this upstream-derived line rather than replaying the historical port bundles. This is still a substantive overlay, not a conflict-free maintenance promise.baseline/ar-upstream-2026-11-18is pristine upstream6bae884cbc, so this PR's diff is the entire AR overlay: about 2,900 source lines, 9,400 test lines and docs.OPENCODEX_AGENTRADAR=1(hosted gateways). Generic defect fixes apply to all installs.FORK.mddocuments the maintenance contract.FORK-DELTA.mdlists everything carried, replaced by upstream or dropped, with the reason for each.release/2.65.0-vadymhimself.15line is renamed[STALE: REBASE FROM NEW FORK]. New gateway work should branch from this line.Carried from
.27(details and commit origins in FORK-DELTA)count_tokens. The served-account header and log are written only after a physical send.api.anthropic.comgets this. Response headers are limited to Content-Type and a bounded Retry-After.web_searchkeeps its fallbackphysicalBreakdown/redAlerts, physical-attempt accounting,p<hex6>labels,comboTargetAdvanced, cache-TTL attribution.xai-apikey, response-store environment bounds, credit-journal expiry, Kimi usages, quota explanation, a 20-minute Antigravity paste window, a 60s API-key 429 cap,--codealias.Fixed versus
.27.27hostedcount_tokenscounted on an unpinned pool account even for pinned requests. It now uses only the pinned account.account_uuid/device_idto a pooled account.Verification
Pinned Bun 1.4.4, isolated
HOME/OPENCODEX_HOME, synthetic credentials and loopback providers. The separate, user-authorized laptop cache probe hit Anthropic 429s and produced no Claude cache-parity evidence. No running build was replaced on the laptop, Mini or hosted gateways.AR test oracle. Every test case AR added (369) or changed (103) relative to its fork base was taken from
.27and run against pure upstream: 96 passed unchanged. The remaining 376 were reviewed through per-case ledgers:.27regressions or equivalent current-handler tests fail without the relevant fix and pass here; compatibility changes to fixtures/imports are recorded in the ledgersFull suite,
OPENCODEX_AGENTRADARunset. 70,276 pass / 753 skip / 32 fail. The failing-test set is a subset of the pristine-upstream baseline; no new flag-off failure. Every failure also fails on pristine upstream6bae884cbcon the same machine (69,990 pass / 33 fail baseline). These are the environment failures listed in FORK.md.Full suite,
OPENCODEX_AGENTRADAR=1(production mode). 69,985 pass / 753 skip / 323 fail; 288 unique hosted-only failing assertions were mapped to the documented hosted contract or test-fixture differences. This is not a green full-suite claim. Three read-only triage slices classified hosted-only failures by root cause. Confirmed regressions were fixed with focused regressions (including mutation checks where recorded); security findings included:The remaining flag-only failures are upstream tests asserting upstream-only behavior that hosted mode deliberately replaces with
.27behavior. Examples: verbatim bytes instead of rewritten ones, 504 for a stall, the 10-minute combo cap, the roster of 16, hash placement.bun run test:gateway-quota(new AR gate, 29 files, runs in the existing CIgatesjob): 534 pass / 0 fail (final boundary-repaired sources; only the.2version stamp followed).bun run typecheck,bun run structure:check,bun run privacy:scan,git diff --check, file-size ratchet: pass.Real loopback gateway e2e for the pin on fake and real-host base URLs. The real-host case asserts that the native lane served it, and fails if routing falls back to translation.
The GUI build and extracted-package smoke passed: packaged CLI reports
2.100.0-vadymhimself.2,/healthzreturns 200 and the built dashboard serves HTML. The last small carry (lidge-jun#8899 unused-hop refund, Error/AbortError), the final boundary repairs and version stamp were validated by focused tests and the final gate; the earlier complete suites predate those isolated changes. Final review found strict SSE EOF-tail and queued OAuth count authority defects in the initial package. Both are now fixed: EOF tails validate before relay; token counts revalidate after pacing and never use paused/removed/cancelled authority or a replaced token. Focused repair tests: 35 pass, 0 fail; mutation checks fail 3 EOF-tail tests without the guard and 4 pacing-barrier tests without the authority check. Count Retry-After is also bounded. No second independent review was requested.Not covered here: live Anthropic cache-hit rates and real provider traffic. A live cache-parity probe on this laptop was blocked by Anthropic 429s on every Claude account. GitHub Actions is disabled on this fork, so no CI result exists for this head.
Release boundary
This PR does not publish, tag or deploy. The old
fork-release.ymlpublisher is not copied: it requires exact-SHA push CI, which upstream's CI policy no longer provides. Creatingrelease/2.100.0-vadymhimselfis blocked by the existing requiredcistatus while fork Actions is disabled; the PR instead targets a non-release pristine baseline reference. No rule was bypassed or relaxed. Cutting over AR deployments and adapting the publisher need a separate, explicit decision.Checklist
Co-authored-by: Gauge gauge@agentradar-house.staging.agentradar.com
🤖 Generated with Claude Code