feat(routing): choose quota window for earlier reset

[Komzpa]

Summary

Rebases and repairs #644 on current main, preserving the original feature from @wuchao05 while resolving the merge conflicts and migration-head drift.

This keeps the existing weekly-quota default for prefer earlier reset routing, and adds an operator setting to choose whether that preference is driven by the primary 5h quota window or the secondary weekly window.

Supersedes and credits #644.

Changes

• Store prefer_earlier_reset_window in dashboard settings with API/schema support.
• Thread the selected reset window through account selection, proxy routing, Codex control, HTTP bridge, and websocket selection paths.
• Track primary reset timestamps in balancer account state.
• Add dashboard controls and payload/schema/test coverage for 5h quota vs Weekly quota.
• Add a current-main Alembic merge revision so the migration graph has a single head again.
• Preserve compatibility for internal/test helper callers that predate the new reset-window kwarg.

Validation

• uv run pytest -q -ra -n 8 -o faulthandler_timeout=300 -o faulthandler_exit_on_timeout=true --timeout=180 --timeout-method=thread --durations=20 tests/unit/test_load_balancer.py tests/unit/test_proxy_http_bridge.py tests/unit/test_proxy_utils.py tests/integration/test_settings_api.py tests/integration/test_http_responses_bridge.py::test_v1_responses_http_bridge_creation_honors_prefer_earlier_reset — 559 passed
• cd frontend && bun run test src/features/settings/components/routing-settings.test.tsx src/features/settings/schemas.test.ts src/features/settings/hooks/use-settings.test.ts src/features/settings/payload.test.ts — 14 passed
• uv run codex-lb-db --db-url <tmp sqlite> upgrade head && uv run codex-lb-db --db-url <tmp sqlite> check — migration_policy=ok, schema_drift=none
• uvx ruff check app tests && uvx ruff format --check app tests

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e30fef5140

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[Komzpa]

@codex review

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: abc675fe13

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[Komzpa]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Hooray!

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[Komzpa]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Can't wait for the next one!

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[Soju06]

Hermes blocker: this PR changes behavior/API/schema/UI but has no OpenSpec change folder.

Evidence:

• AGENTS.md:24-28 requires an openspec/changes/** change when behavior, requirements, contracts, or schema change.
• .github/CONTRIBUTING.md:235-239 makes an OpenSpec change folder a merge gate for non-exempt behavior changes.
• PR feat(routing): choose quota window for earlier reset #795 adds persisted/API/dashboard behavior (app/db/models.py, app/modules/settings/schemas.py, frontend/src/features/settings/components/routing-settings.tsx) and a DB migration, but git diff --name-only origin/main...HEAD -- openspec is empty.

Requested fix: add the appropriate openspec/changes/<slug>/ proposal/tasks/spec delta for the reset-window preference (and run strict OpenSpec validation), or have the maintainer explicitly waive this gate. Until then this is not merge-ready despite green CI/Codex.

[Komzpa]

Superseded by #871, which carries the reset-window routing repair on a current base with the OpenSpec change and migration-head reconciliation. Closing this older dirty repair branch to keep the queue focused on the active replacement.