feat: admin dedicated pages, pool key management, keypool quotas (#1350)
shinmentakezo07
9b71fd0
- Admin UI becomes a Vite build under frontend/ with hash-routed
dedicated pages (#/providers, #/model-config, #/messaging); the
providers view renders only on its page.
- Pool fields support reveal/edit/remove of individual keys via a
new loopback-only GET /admin/api/pools/{field_key} endpoint;
apply resolves tokens mixed with raw edits against stored keys.
- admin assets now serve Cache-Control: no-store, fixing stale-bundle
breakage after the frontend migration.
- ApiKeyPool gains per_key_quota rotation plus transient HTTP
429/5xx/overload failover rotation with mark_failure.
- CI runs the frontend build and verifies committed admin assets.
## Problem
Python 3.14 provides native lazy annotations, but the codebase still
relied on legacy future annotation imports. Those imports also made
type-only import cycles easier to hide instead of fixing ownership
boundaries.
## Changes
| Before | After |
| --- | --- |
| Python files used `from __future__ import annotations`. | Python files
rely on Python 3.14 native lazy annotations. |
| Some runtime modules used `TYPE_CHECKING` or local imports for
required dependencies. | Runtime modules use top-level owner-module
imports with explicit boundaries. |
| Local and GitHub guardrails only rejected type ignore suppressions. |
Local and GitHub guardrails reject type ignore suppressions and legacy
future annotation imports. |
| Agent docs only documented the no-type-ignore rule. | Agent docs
document the Python 3.14 annotation and import-boundary rules. |
<!-- greptile_comment -->
<details open><summary><h3>Greptile Summary</h3></summary>
This PR moves the codebase to Python 3.14 nat…