eggpool 0.3.3__tar.gz → 0.3.4__tar.gz

{eggpool-0.3.3 → eggpool-0.3.4}/AGENTS.md

@@ -90,6 +90,7 @@ Use the hierarchy in `errors.py`. Chain exceptions with `raise ... from err` or
 
 - Configuration changes require a service restart; live reload is intentionally not supported
 - No pre-commit hooks are configured in this repo; CI runs ruff, pyright, and pytest via GitHub Actions
+- **`static_models` is the source of truth for provider-specific protocol** — `FAMILY_PROTOCOLS` (`src/eggpool/catalog/protocols.py`) is a global fallback that applies when no explicit override exists. Providers like `minimax-cn` that serve MiniMax models on the OpenAI-compatible surface **must** ship `[[providers.<id>.static_models]]` rows with `protocol = "openai"`, otherwise the live `/v1/models` fetch resolves `MiniMax-M*` via the `minimax-` family prefix to `anthropic` and the provider protocol constraint check (`src/eggpool/catalog/service.py:533-545`) clears the protocol to `None`, producing `ModelUnavailableError("Model 'MiniMax-M3' has unresolved protocol")` instead of the more obvious 400 `ProtocolMismatchError`. Static seeds with `protocol_source = "static_config"` survive the live merge via `ModelCatalogCache._preserve_static_fields` (`src/eggpool/catalog/cache.py:146-187`). The same model ID may also be flipped on a per-provider basis via `[providers.<id>.model_overrides."<model-id>"].protocol = "openai"` for operator overrides that go beyond the bundled template.
 - `Database.vacuum()` is the only sanctioned path for `VACUUM` in production code
 - Every DML write must run inside `async with db.transaction():`
 - SQLite transactions are serialized across concurrent tasks via a single connection lock + ContextVar

{eggpool-0.3.3 → eggpool-0.3.4}/CHANGELOG.md

@@ -7,6 +7,13 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.3.4] - 2026-06-27
+
+### Fixed
+
+- **Exclusion taxonomy empty-state**: the Routing page's doughnut chart now shows `<p class="empty">No exclusion data in this period.</p>` instead of an invisible Chart.js ring when no exclusions have been recorded in the selected period. The previous behaviour rendered a zero-data doughnut whose legend was visible but the chart itself was not, producing a "key but no graph" artefact.
+- **`circuit_breaker` classification**: `SUPPRESSIVE_EXCLUSION_REASONS` now includes `circuit_breaker`, the only exclusion reason the coordinator actually writes to `exclude_reasons_json`. Previously every real-world exclusion landed in the `unknown` bucket because the frozenset only contained the legacy `circuit_open` name.
+
 ### Added
 
 - **Sticky dashboard topbar**: `header.topbar` is `position: sticky; top: 0; z-index: 5` with a subtle backdrop blur, so the page navigation stays visible while scrolling on desktop. Mobile layout is unchanged (the topnav disclosure still wraps cleanly under 480px).

{eggpool-0.3.3 → eggpool-0.3.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: eggpool
-Version: 0.3.3
+Version: 0.3.4
 Summary: A lightweight proxy that aggregates multiple LLM provider accounts behind one OpenAI-compatible endpoint
 Project-URL: Homepage, https://github.com/eggstack/eggpool
 Project-URL: Repository, https://github.com/eggstack/eggpool

{eggpool-0.3.3 → eggpool-0.3.4}/docs/providers.md

@@ -170,11 +170,28 @@ Live model discovery fetches the catalog from the MiniMax `/v1/models`
 endpoint using the documented Anthropic-compatible listing. The static
 seeds serve only as a fallback when live discovery is unavailable.
 
-`minimax-cn` (China console) is intentionally still configured as plain
+`minimax-cn` (China console) is intentionally configured as plain
 OpenAI-compatible in the bundled template because the China endpoint
 family and auth shape have not been confirmed against `api.minimaxi.com`.
 Do not assume parity with the international Anthropic-compatible
-template without live testing.
+template without live testing. `minimax-cn` ships with
+`[[providers.minimax-cn.static_models]]` rows pinning `MiniMax-M3`,
+`MiniMax-M2.7`, and `MiniMax-M2.5` to `protocol = "openai"` so the
+global `FAMILY_PROTOCOLS["minimax-"] = "anthropic"` mapping does not
+clear the protocol at the provider constraint check. Route MiniMax
+through `minimax-cn` on `/v1/chat/completions` (OpenAI), not
+`/v1/messages`.
+
+### Endpoint routing by MiniMax provider
+
+| Provider            | Base URL                                | Endpoint                | Auth style   |
+| ------------------- | --------------------------------------- | ----------------------- | ------------ |
+| `minimax`           | `https://api.minimax.io/anthropic`      | `POST /v1/messages`     | `x-api-key`  |
+| `minimax-cn`        | `https://api.minimaxi.com/v1`           | `POST /chat/completions`| `Bearer`     |
+
+Requests that hit the wrong endpoint receive a `400 ProtocolMismatchError`
+("Model 'MiniMax-M3' uses the X protocol. Use /v1/..."). Hit the row
+that matches the provider you configured.
 
 ### GeneralCompute PAYG (Plain OpenAI-Compatible)
 

{eggpool-0.3.3 → eggpool-0.3.4}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "eggpool"
-version = "0.3.3"
+version = "0.3.4"
 description = "A lightweight proxy that aggregates multiple LLM provider accounts behind one OpenAI-compatible endpoint"
 readme = "README.md"
 requires-python = ">=3.11"

{eggpool-0.3.3 → eggpool-0.3.4}/src/eggpool/dashboard/render.py

@@ -94,6 +94,13 @@ _STATUS_BADGE_TOOLTIPS: dict[str, str] = {
 # signals).  This split lets the dashboard verify the design rule that
 # upstream-observed failures control exclusion while local accounting
 # only influences priority.
+#
+# ``circuit_breaker`` is the only reason the coordinator actually writes
+# to ``exclude_reasons_json`` (see
+# ``eggpool.request.coordinator._score_and_select``).  ``circuit_open``
+# is kept for backwards compatibility with rows written before the
+# coordinator rename and to align semantically with the
+# ``_STATUS_BADGE_TOOLTIPS`` mapping above.
 SUPPRESSIVE_EXCLUSION_REASONS: frozenset[str] = frozenset(
     {
         "authentication_failed",
@@ -107,6 +114,7 @@ SUPPRESSIVE_EXCLUSION_REASONS: frozenset[str] = frozenset(
         "account_disabled",
         "protocol_mismatch",
         "circuit_open",
+        "circuit_breaker",
     }
 )
 
@@ -459,12 +467,17 @@ def _render_layout(
     script_block = (
         _render_auto_refresh_script(refresh_interval_s) if auto_refresh else ""
     )
+    # `dashboard.js` is intentionally always-on: it wires the mobile
+    # burger menu, the update-command copy affordance, and the
+    # timeseries controls. Its init functions guard themselves with
+    # empty-result DOM queries so they are no-ops on pages that do not
+    # use charts or timeseries. Only `chart.js` is gated behind
+    # `include_chart_js` because it is ~200 KB and we want to keep it
+    # off the critical path for non-chart pages.
     chart_script = (
-        '<script defer src="/static/chart.js"></script>'
-        '<script defer src="/static/dashboard.js"></script>'
-        if include_chart_js
-        else ""
+        '<script defer src="/static/chart.js"></script>' if include_chart_js else ""
     )
+    dashboard_script = '<script defer src="/static/dashboard.js"></script>'
     update_indicator = _render_update_indicator(update_info)
     return f"""<!DOCTYPE html>
 <html lang="en">
@@ -508,6 +521,7 @@ def _render_layout(
 </footer>
 {script_block}
 {chart_script}
+{dashboard_script}
 </body>
 </html>"""
 
@@ -3630,6 +3644,9 @@ def _render_exclusion_taxonomy_chart(
         category = _classify_exclusion(reason)
         category_totals[category] = category_totals.get(category, 0) + count
 
+    if sum(category_totals.values()) == 0:
+        return '<p class="empty">No exclusion data in this period.</p>'
+
     labels = json.dumps(["Suppressive", "Advisory", "Unknown"])
     datasets = json.dumps(
         [

{eggpool-0.3.3 → eggpool-0.3.4}/src/eggpool/providers/_templates.toml

@@ -113,6 +113,34 @@ probe_model = "MiniMax-M2.5"
 probe_protocol = "openai"
 require_models = false
 
+# MiniMax China serves the same model IDs as MiniMax International but
+# via an OpenAI-compatible surface. Pin the protocol here so the global
+# FAMILY_PROTOCOLS["minimax-"] = "anthropic" mapping does not clear the
+# protocol during the provider protocol constraint check (see
+# CatalogService._fetch_and_process_account). Without these seeds
+# MiniMax-M* would be served with protocol = None and rejected at
+# RequestCoordinator._validate_endpoint.
+[[providers.minimax-cn.static_models]]
+id = "MiniMax-M3"
+display_name = "MiniMax-M3"
+protocol = "openai"
+supports_tools = true
+supports_vision = false
+
+[[providers.minimax-cn.static_models]]
+id = "MiniMax-M2.7"
+display_name = "MiniMax-M2.7"
+protocol = "openai"
+supports_tools = true
+supports_vision = false
+
+[[providers.minimax-cn.static_models]]
+id = "MiniMax-M2.5"
+display_name = "MiniMax-M2.5"
+protocol = "openai"
+supports_tools = true
+supports_vision = false
+
 [providers.generalcompute]
 # GeneralCompute — plain OpenAI-compatible PAYG.
 # Treat as standard OpenAI surface (GET /models, POST /chat/completions,

{eggpool-0.3.3 → eggpool-0.3.4}/uv.lock

@@ -196,7 +196,7 @@ wheels = [
 
 [[package]]
 name = "eggpool"
-version = "0.3.2"
+version = "0.3.4"
 source = { editable = "." }
 dependencies = [
     { name = "aiosqlite" },