[maxmad64bis]

⚠️ base-red inherited: #13866

Summary

When rotation passes over cooling-down accounts, traffic concentrates with no trace of why, and proxy log rows can't be tied to the request or the serving account. This names skipped accounts, exposes per-account rotation state, and carries the serving account plus the request correlation on proxy log rows, all behind a new off-by-default flag with no selection change.

Related Issues

No linked issue — operator observability follow-up, no upstream issue covers skipped-account attribution.

Validation

• Change type: provider
• Focused tests and category gates from the golden path
• npm run lint — ESLint 0 on the touched files; the full eslint . run is red on the base (🔴 Release branch not green: release/v3.8.51 #13866), unrelated to this diff.
• Reconciled with the current active release base; focused checks rerun afterward — rev-list --count HEAD..upstream/release/v3.8.51 = 0, gates re-run after the last amend.
• Production-code changes include a new or updated automated test in this PR — 6 new test files (17 tests, RED-then-GREEN).

Tests Added Or Updated

• New: rotation-attribution-snapshot (4), rotation-attribution-flag (2), rotation-attribution-skipped-lines (2), proxy-logger-attribution (4), migration-182-183-proxy-logs-attribution (3), resilience-connections-rotation (2); updated: feature-flags-settings (counter 74→75). Neighbors green (resilience 22, 8 suites 27).

Coverage Notes

• Three additive paths (skip log, rotation state, two journal columns) each covered by its own test file; migrations covered up-only with anti-cross-talk; no existing coverage removed.

Reviewer Notes

• New off-by-default flag ROTATION_ATTRIBUTION (fail-safe false, no restart) with two additive nullable journal columns (migrations 182/183, no index) and a read-only loopback-gated route extension. Local gates: typecheck:core 0, ESLint 0 on owned files, C4 re-run at push time.
• File-size rebaseline at this head (303fcb2103): _rebaseline_2026_09_20_14223_rotation_attribution_growth pins frozen at gate counts (chat.ts 2561, chatHelpers.ts 1257, proxyFetch.ts 1294, opencode.ts 1276); gate green locally. Counters use the gate measure (split("\n").length, one more than wc -l).
• CI reds are inherited from the red base (🔴 Release branch not green: release/v3.8.51 #13866): ESLint ✖ lines cite files outside this diff (git diff $mb empty on each), same 9 jobs on third-party fix(sse): treat antigravity empty completions with a normal stop as valid 200s (#14160) #14243. Non-blocking.

[diegosouzapw]

Maintainer note — pushed a reconciliation commit on top of your work (your commits are untouched).

Migrations renumbered 182/183 → 183/184. When this branch forked, 182 was still free; release/v3.8.51 has since shipped 182_request_cost_ledger_and_key_quota.sql (#13610). Two files under the same numeric prefix make getMigrationFiles() throw Migration version collision detected on the first database touch, so a fresh install would not boot. Renamed:

• src/lib/db/migrations/182_proxy_logs_rotation_account.sql → 183_proxy_logs_rotation_account.sql
• src/lib/db/migrations/183_proxy_logs_correlation_id.sql → 184_proxy_logs_correlation_id.sql

Everything keyed to those numbers moved with them:

• src/lib/db/migrationRunner.ts: the isSchemaAlreadyApplied arms case "182" / case "183" → case "183" / case "184". These are keyed by version only, so left at 182 the rotation_account check would have answered for 182_request_cost_ledger_and_key_quota and skipped it.
• tests/unit/migration-182-183-proxy-logs-attribution.test.ts → tests/unit/migration-183-184-proxy-logs-attribution.test.ts, with the copied SQL filenames, the _omniroute_migrations ledger expectations and the case names updated.
• The _rebaseline_2026_09_20_14223_... note in config/quality/file-size-baseline.json re-measured on the reconciled tree.

The existing tests/unit/migration-135-numbering-collision.test.ts is the end-to-end proof: its first case, "a fresh install applies all real on-disk migrations without a version collision", runs every real on-disk migration against a fresh temp DATA_DIR. It passes on this branch, and re-adding a duplicate 182_proxy_logs_rotation_account.sql makes it fail with Migration version collision detected: version=182 → [proxy_logs_rotation_account, request_cost_ledger_and_key_quota].

Also reconciled against the current tip while merging release/v3.8.51 in:

• open-sse/executors/opencode.ts: fix(opencode): complete refused tool subsets with previously accepted names #14464 replaced the free-tier-refusal exit with handleLoopFreeTierRefusal(). Kept the release shape and moved the skipped-account flush to just before that call.
• tests/unit/feature-flags-settings.test.ts: the expected count is now 76 (the registry gained one flag on the tip after the fork, plus ROTATION_ATTRIBUTION); counted from FEATURE_FLAG_DEFINITIONS, not guessed. ROTATION_ATTRIBUTION stays defaultValue: "false".
• config/quality/file-size-baseline.json: both sides' notes kept; ceilings re-measured on the reconciled tree — opencode.ts 1386, proxyFetch.ts 1287.

Focused tests green: 82/82 across the six attribution/migration/resilience/feature-flag files plus the collision guard. Two failures reproduce unchanged on the pure tip (30a83ee) and are not from this PR: check:open-sse-typecheck (open-sse/executors/auggie.ts TS2769/TS18047) and tests/unit/opencode-executor.test.ts → "omits accept header when stream is false".