[maxmad64bis]

⚠️ base-red inherited: #14547

Summary

A per-key token ceiling rejection (HTTP 429) now provably leaves both the serving connection and same-egress neighbors untouched: the decision skips the cooldown path and the client still gets its 429. This locks in the behavior introduced by #13606 with a neighbor-scoped regression test. No default or behavior change.

Related Issues

• Related to fix(connection-cooldown): skip cooldown for locally rejected token-budget 429s #13606
• Related to feat(providers): A subscription's tunnelled nodes all register as one proxy, so its pool has a single egress #13460

Validation

• Change type: sse
• Focused tests and category gates from the golden path
• npm run lint — ESLint on the touched files is clean (exit 0 with repo suppressions); the full run is red on the base (🔴 Release branch not green: release/v3.8.51 #14547 — cliproxyAccountHealth.ts TS2322, file outside this diff, identical on base)
• Reconciled with the current active release base; focused checks rerun afterward
• Production-code changes include a new or updated automated test in this PR

Tests Added Or Updated

• tests/unit/per-key-ceiling-skips-neighbor-cooldown.test.ts (new, 1 test): two connections sharing one egress address, exact Tier-2 refusal (429 + TOKEN_LIMIT_EXCEEDED) — serving and sibling stay active, client status stays 429. No production code changed, so no existing test needed updating.

Coverage Notes

• N/A — test-only change; no src/, open-sse/, electron/, or bin/ production file touched. The test pins the skip contract so a future regression of the shared skip table fails here first.

Reviewer Notes

• No behavior change: pure regression lock on top of fix(connection-cooldown): skip cooldown for locally rejected token-budget 429s #13606. Neighbors re-run green (local-token-budget-429-skips-cooldown 6/6, egress-ip-lock-10880 17/17).
• API Route Typecheck red is inherited, not from this PR: the 5 ✗ lines (auggie TS2769/TS18047, chatCore TS2304, projectCombo TS2459/TS2724) reproduce on the bare base (git diff $mb empty on all three files), same family as third-party fix(proxies): derive bulk import statuses from shared registry #14579 on the previous base. Base-red 🔴 Release branch not green: release/v3.8.51 #14547 cited.
• Remaining reds are inherited or unstable, not from this PR: Unit Tests ✖ lists contain zero hits of this PR's test on all 4 shards (local re-runs 1/1 + neighbors 6/6 + 17/17 green); Fast Quality Gates ✗ lines match the base pattern (auggie, intelligentRouting.ts TS2698, mutation drift over third-party modules — this PR's own test is registered, 0 per-key-ceiling hits locally); Docs Gates env-contract gap is untouched by this PR (git diff $mb empty on docs). Base-red 🔴 Release branch not green: release/v3.8.51 #14547 cited.

[diegosouzapw]

Thanks for locking this in — a dedicated neighbor-scoped regression test for the per-key
ceiling/cooldown-skip contract from #13606 is exactly the kind of coverage that keeps this area
honest as it evolves. Clean, single-purpose, no production change. Looks merge-ready.