1 Commits

Include renames

Author	SHA1	Message	Date
4 people	d872330c9e	docs: Phase 5 close-prep — README § Plan Usage + supported-provider matrix + live E2E artifact (#56) ... * docs: Phase 5 close-prep — README § Plan Usage + supported-provider matrix + live E2E artifact Pre-close documentation pass per ADR 0012 § Exit gate items 3 + 9. v0.5.0 close PR (package.json bump + CHANGELOG promotion + tag) is maintainer-triggered per CLAUDE.md release_kit.phase_close_trigger. What this PR ships: (1) README § What you get — added Plan-usage probe bullet with anchor to the new § Plan Usage section. (2) README § Supported Providers — table gained "Quota probe (v0.5.0+)" column. Anthropic ✅ live (13 anthropic-ratelimit-unified-* headers, opt-in via quota_probe_enabled). Codex ❌ no public quota API. Mistral ❌ per D84 spike 2026-05-26 (no /v1/usage at docs.mistral.ai/api). Others TBD (Phase 8+). (3) README new § Plan Usage (live quota probe) between § Configuration and § API Endpoints. Documents: how the probe works (POST /v1/messages with max_tokens:1 + headers-only parse), opt-in config block, OAuth token sources (env / .credentials.json / macOS Keychain), olp doctor integration, schema-drift protection (Path A `strings` over compiled binary + Path B live probe diff), full ADR cross-refs. Embeds the dashboard screenshot below. (4) README § API Endpoints — updated /dashboard / /v0/management/dashboard-data / /v0/management/quota rows to reflect Phase 5 changes: - /dashboard: Claude.ai-style Plan Usage section + 60s auto-refresh + manual button - /v0/management/dashboard-data: new quota_v2 field alongside legacy quota - /v0/management/quota: mirrors dashboard-data quota_v2 for scripted monitoring (5) docs/img/dashboard-v0.5.0.png — dashboard screenshot rendered from live MacBook server JSON (utilization_5h: 36%, utilization_7d: 34%, representative_claim: five_hour, overage: rejected) merged into D83 dashboard.html. Identifying IPs / hostnames / Tailscale nodes redacted from rendered output per public-repo hygiene rule (cc-rules AGENTS.md). (6) docs/exit-gates/phase-5-e2e.json — sanitized record of the Live MacBook E2E verification (exit-gate item 9). Confirms quota_v2 shape produced live, anthropic probe returned 12/13 fields (overage-reset absent per audit memory — only fires on active overage), opt-in mechanism verified end-to-end (config flag flipped → server probed → dashboard renders). Post-test cleanup noted: temp owner key revoked, config restored to baseline, test server terminated. Remaining exit-gate items for the v0.5.0 close PR (maintainer-triggered): - CHANGELOG.md "Unreleased" → "## v0.5.0 — <date>" promotion - package.json 0.4.4 → 0.5.0 - CLAUDE.md release_kit.phase_rolling_mode: Phase 5 → Phase 6, 0.5.0-phase5 → 0.6.0-phase6 - Tag v0.5.0 push (triggers .github/workflows/release.yml auto-release) Authority cited: - ADR 0012 § Exit gate items 3 + 9 - ADR 0012 Amendment 1 (D84 NO-GO rationale in Mistral row) - ADR 0002 Amendment 8 + ADR 0013 (the constitutional context for the Plan Usage section's "how it works" framing) - D80 commit 82d2e1c (probe producer cited in API Endpoints table) - D81 commit 5288493 (quota_v2 shape producer) - D82 commit a41420d (dashboard UI consumer) - D83 commit 2b07a3b (test coverage) Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * docs: PR #56 fold-in — 3 maintainer findings (F1 doctor kind / F2 Mistral / F3 SPOT) Maintainer review of PR #56 surfaced 3 valid accuracy issues. Folding in. F1 [P2] — README claim "fix_oauth on 401/403, fix_provider on 429/network" is wrong. The anthropic.quota_probe_reachable check has category: 'provider' (anthropic.mjs:999), so deriveKind() at lib/doctor.mjs:464 maps ALL failures to fix_provider regardless of underlying HTTP status. Furthermore, _probeOnce collapses 401/403 → null before reaching the doctor aggregate layer (anthropic.mjs:451), so the HTTP status isn't observable to deriveKind at all. README would have steered AI-repair loops toward an unreachable discriminator. Fix: README now accurately says all probe failures discriminate to kind: fix_provider, with the actionable text inside human_steps[] being auth-aware (re-login recipe for OAuth failures, wait-and-retry for rate-limit). Note that splitting the check across the provider/auth category boundary would let fix_oauth fire for OAuth-class failures specifically; deferred to v1.x pending consumer-reported ambiguity. F2 [P2] — README + ADR 0012 Amendment 1 said Mistral has "no programmatic quota API; only web console". Maintainer pointed to Mistral's Admin API (https://docs.mistral.ai/admin/security-access/admin-api) which DOES expose Billing and Usage queries — just gated to org-admin-scoped keys. The D84 NO-GO conclusion is still correct: OLP's deployment posture (maintainer's personal Le Chat Pro account, trusted-LAN per ADR 0011) uses Vibe / Le Chat member / La Plateforme keys, NOT org-admin keys. Provisioning + storing an org-admin token raises the credential-scope ceiling beyond the trusted-LAN design. Fix: tightened wording in 3 places (README Supported Providers table, README Plan Usage provider coverage table, ADR 0012 Amendment 1) to say "no public quota endpoint accessible to Vibe / Le Chat member / La Plateforme API keys" + acknowledge the Admin API surface + cite it as a forward re-entry point if OLP scope expands to org-admin context. F3 [P3] — Supported Providers table claims it's re-generated from models-registry.json, but the new "Quota probe (v0.5.0+)" column has values for OpenAI/Mistral/TBD that aren't in the registry (registry only had quota_probe.anthropic block before this PR). Fix: closed the SPOT drift formally by adding quota_probe.openai and quota_probe.mistral entries to the registry with {status, reason, re_entry_point} for each, plus an admin_api_reference for Mistral. Also added explicit "status": "live" field to quota_probe.anthropic for symmetry. Tightened README's source-of-truth statement to name BOTH the providers.<key> block (model metadata) and quota_probe.<key> block (probe status/reason/source). This makes the column fully derivable from the registry — when D84 ever becomes GO (Mistral Admin API integration, or OpenAI publishes a quota endpoint), the registry is the single edit point. Test impact: 756/756 still pass. Suite 37g (registry presence + 13 fields for anthropic) unchanged; the new openai/mistral quota_probe entries are additive and don't break any consumer. Authority: - F1: lib/doctor.mjs:464 deriveKind logic + anthropic.mjs:999 category - F2: https://docs.mistral.ai/admin/security-access/admin-api + ADR 0011 trusted-LAN deployment context for the "out of scope" framing - F3: CLAUDE.md release_kit overlay § "Supported Providers table sourced from models-registry.json" — same SPOT discipline applies to the new D81 column Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> --------- Co-authored-by: dtzp555 <dtzp555@gmail.com> Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>	2026-05-26 20:59:24 +10:00