pi-harness-runtime 0.9.11 → 0.9.14

package/README.md

@@ -1,11 +1,11 @@
 # Pi Harness Runtime
 
-[![Beta](https://img.shields.io/badge/version-beta-orange?style=for-the-badge)](https://github.com/ManotLuijiu/pi-harness-runtime)
+[![Beta](https://img.shields.io/badge/version-0.9.13-orange?style=for-the-badge)](https://github.com/ManotLuijiu/pi-harness-runtime)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg?style=for-the-badge)](https://opensource.org/licenses/MIT)
 [![Platform](https://img.shields.io/badge/Platform-macOS%20|Linux-blue?style=for-the-badge)]()
 
 > ⚠️ **Beta Notice — Not Production Ready ⚠️**
-> This project is in active development. Core features work but E2E testing is not yet implemented.
+> This project is in active development. Core features work.
 
 **Autonomous AI coding harness for pi: local token tracking + provider mirror + task orchestration.**
 
@@ -31,7 +31,7 @@ Requires Pi v0.37.3+.
 
 ```bash
 /usage              # show full status (local tracking + provider mirror)
-/usage refresh     # force refresh quota from MiniMax console
+/usage refresh     # force refresh quota from provider console
 /usage today       # today's usage + 5h window
 /usage week        # this week's usage + lifetime totals
 /usage reset       # clear provider mirror
@@ -82,6 +82,8 @@ Requires Pi v0.37.3+.
 ```
 pi-harness-runtime/
 ├── index.ts                    # Extension entry point
+├── footer-status.ts            # Footer bar renderer (local vs. mirror mode)
+├── mirror.ts                   # Per-provider quota mirror (mirror.json)
 ├── harness/
 │   ├── job-state-machine.ts   # 14-state lifecycle machine
 │   ├── task-graph.ts           # DAG-based task management
@@ -92,13 +94,15 @@ pi-harness-runtime/
 │   ├── context-window-manager.ts # Context tracking
 │   ├── agent-handoff.ts        # Clean agent transitions
 │   ├── e2e/
-│   │   ├── test-engine.ts     # E2E test runner (coming soon)
-│   │   └── playwright-runner.ts # Browser automation
+│   │   ├── minimax-quota-scraper.ts  # Playwright MiniMax scraper
+│   │   └── playwright-runner.ts       # Browser automation
 │   └── project-detector/
 │       └── detector.ts         # Auto-detect project type
 ├── packages/
-│   ├── providers/adapters.ts   # MiniMax, OpenAI adapters
+│   ├── cookie-sanitizer/       # Live cookie-file sync via chokidar
+│   ├── providers/              # MiniMax, OpenAI, Codex adapters
 │   ├── quota-manager/          # Quota signal collection
+│   ├── auth/                   # MiniMax browser auth
 │   └── worktree/              # Git worktree per task
 └── skills/
     └── harness-runtime/
@@ -124,6 +128,7 @@ cancelled  blocked   waiting_human  repairing  ready_for_client
 - **Auto-repair**: Failure classification + retry with exponential backoff
 - **E2E testing**: Scenario-based Playwright integration (coming soon)
 - **Project detection**: Auto-detects Frappe, Next.js, React, Django, Laravel
+- **Per-provider mirror**: Each LLM provider maintains its own quota record
 
 ## Data Directory
 
@@ -133,7 +138,7 @@ All data stored locally in `~/.pi/`:
 ~/.pi/
 ├── usage-status/         # /usage data
 │   ├── usage.jsonl
-│   └── mirror.json
+│   └── mirror.json        # per-provider quota mirror
 ├── harness/            # /harness data
 │   └── jobs/
 │       └── <job-id>/
@@ -193,59 +198,58 @@ bun test   # 131+ tests passing
 
 Quota data is automatically surfaced per-provider:
 
-| Provider | Source | Cadence |
+| Provider | Source | Notes |
 |---|---|---|
-| MiniMax | Playwright + cookies (continuous scrape) | every ~15 min |
-| OpenAI / OpenAI Codex | TUI message capture (signal on limit) | on first limit hit |
-| GLM (Z.ai / Zhipu) | TUI message capture (signal on limit) | on first limit hit |
-| Anthropic | TUI message capture (signal on limit) | on first limit hit |
-| OpenRouter | TUI message capture (signal on limit) | on first limit hit |
+| MiniMax | Live cookie-file watch + Playwright scrape | Drop folder: `~/.pi-harness-runtime/cookies/` |
+| OpenAI / OpenAI Codex | TUI message capture | Signal on first limit hit |
+| GLM (Z.ai / Zhipu) | TUI message capture | Signal on first limit hit |
+| Anthropic | TUI message capture | Signal on first limit hit |
+| OpenRouter | TUI message capture | Signal on first limit hit |
 | Other / unknown | (no data — footer shows hint) | — |
 
 The footer line carries the provider label, so you always know which LLM the data is from:
 
 ```
-MiniMax:  5h: 92% left · week: 80% left           # continuous (scrape)
-OpenAI:   5h: -- · week: -- (no signal yet)        # pending first limit hit
+MiniMax:  5h: 92% left · week: 80% left            # continuous (cookie scrape)
+OpenAI:   5h: -- · week: -- (no signal yet)          # pending first limit hit
 GLM:      limit hit (tokens), reset 2026-07-23T17:28:00Z   # TUI signal observed
+MiniMax:  cookies not found — drop any cookie file into
+          ~/.pi-harness-runtime/cookies/
 ```
 
-1. **MiniMax setup** (one-time):
+### MiniMax Setup (one-time)
+
+The runtime watches `~/.pi-harness-runtime/cookies/` for cookie files. Drop any cookie export there — it syncs within ~1 second:
+
+1. **Install EditThisCookie** Chrome extension → export from `platform.minimax.io`
+2. **Create the drop folder:**
 
    ```bash
-   # Install EditThisCookie Chrome extension
-   # Go to platform.minimax.io
-   # Export cookies → Netscape format
-   # Save to ~/.config/minimax-cookies.txt
+   mkdir -p ~/.pi-harness-runtime/cookies
    ```
 
-   **Recommended:** drop the file into the dedicated cookie folder. The runtime
-   normalizes any format (Netscape or EditThisCookie JSON, any filename) on its own:
+3. **Drop your cookie file in the folder** — any filename, any format (Netscape `.txt` or EditThisCookie JSON `.json`):
 
    ```bash
-   # Save cookies as any name, any format into:
-   mkdir -p ~/.pi-harness-runtime/cookies
-   cp ~/Downloads/platform.minimax.io_cookies.txt ~/.pi-harness-runtime/cookies/
-   # …or use the EditThisCookie extension export (JSON) — same folder works.
+   cp ~/Downloads/platform.minimax.io_cookies.txt \
+      ~/.pi-harness-runtime/cookies/
+   # …or use the EditThisCookie JSON export — same folder works.
    ```
 
-   The `cookie-sanitizer` package (`@pi-harness/cookie-sanitizer`) runs chokidar v5 on this
+   The `cookie-sanitizer` package (`@pi-harness/cookie-sanitizer`) runs chokidar on this
    folder, normalizes everything to standard Netscape, and writes the canonical cache at
    `~/.config/minimax-cookies.txt`. Live update latency: <1 second after drop.
 
-2. **Other providers**: no setup needed. The runtime reads messages from the active
-   session and captures quota-exhaustion signals from the TUI. Once any limit is hit
-   (e.g. `OpenAI: context length exceeded, reset in 3 hr 27 min`), the footer updates
-   immediately and the data persists across `~/.pi/usage-status/mirror.json`.
+4. **Done!** Quota auto-refreshes every ~15 minutes. Cookie file changes sync immediately.
 
-3. **Environment** (optional override):
+**Override:** set `QUOTA_COOKIE_FILE=/path/to/your/cookies.txt` to bypass the sanitizer
+and read a specific file directly.
 
-   ```bash
-   export QUOTA_COOKIE_FILE=/path/to/your/cookies.txt
-   # When set, the sanitizer is bypassed and the scraper reads this file directly.
-   ```
+### Other Providers
 
-4. **Done!** Quota auto-refreshes every 5 minutes. Cookie file changes sync within ~1 second.
+No setup needed. The runtime reads TUI messages and captures quota-exhaustion signals.
+Once any limit is hit (e.g. `OpenAI: context length exceeded, reset in 3 hr 27 min`), the
+footer updates immediately and the data persists in `mirror.json`.
 
 ## Roadmap
 
@@ -254,9 +258,13 @@ GLM:      limit hit (tokens), reset 2026-07-23T17:28:00Z   # TUI signal observed
 - [x] Repair engine
 - [x] Shared blackboard
 - [x] MiniMax Web automatic quota detection
+- [x] Cookie-file drop folder + live sync (`cookie-sanitizer`)
+- [x] Per-provider quota mirror (`mirror.json` keyed by provider)
+- [x] Multi-provider TUI signal capture (OpenAI, GLM, Anthropic, OpenRouter)
 - [ ] E2E test engine integration
 - [ ] Claude adapter
 - [ ] Production stress testing
+- [ ] RFC-0101: Autonomous Operations Runtime (background execution, task inbox, lease protocol)
 
 ## License
 
@@ -268,17 +276,17 @@ MIT © 2026 MooCoding
 - [context-mode](https://github.com/MiniMax-AI/context-mode) — Context window tracking
 - [pi-web-access](https://github.com/nicobailon/pi-web-access) — Web search for pi
 
-Day 6 adds runtime recovery and remote-observability architecture.
-
 ## RFCs
 
-- RFC-0019 Auto Compact and Continue
-- RFC-0020 Output Token Limit Handler
-- RFC-0021 Partial Response Recovery
-- RFC-0022 Notification Center
-- RFC-0023 Local Browser Agent
+The project tracks 101 design documents:
+
+| RFC | Title | Status |
+|-----|-------|--------|
+| 0001–0034 | Loop Runtime, Provider Adapter, Quota Manager, Playwright, Git Worktree, Checkpoint, Scheduler, Provider Router, Shared Context, Context Window Manager, Shared Blackboard, Agent Handoff, E2E Test Engine, Project Detector, Job State Machine, Task Graph, Master Planner, Repair Engine, Auto Compact & Continue, Output Token Limit, Partial Response Recovery, Notification Center, Local Browser Agent, Local Runtime Agent, Command Executor, Workspace Manager, Runtime API, Policy Engine, DeepAgents Adapter, Agent Worker Interface, Provider Adapter SDK, Checkpoint Engine, Session Manager | Proposed |
+| 0035–0100 | Observability, Roadmap V1, Code Review, Code Generation, Framework Detector, Test Data Generator, Framework Plugin SDK, Prompt Compiler, Context Compiler, Requirement Compiler, Task Compiler, Project Analyzer, Dependency Analyzer, Repo Knowledge Graph, Code Merge Engine, Conflict Resolution, Documentation Generator, Capability Registry, Skill Registry, Model Registry, Cost Optimizer, Performance Optimizer, Evaluation Engine, Learning Engine, Experience Replay, Memory Engine OKF, Frappe/Next.js/React/Django/Laravel/Generic Web Plugins, CLI Plugin SDK, MCP Adapter, A2A Adapter, Codex Adapter, Requirement Intake, Project Bootstrap, Architecture Generator, Sprint Planner, Milestone Manager, Backlog Manager, Human Approval Gate, Release Manager, Version Manager, Deployment Pipeline, Multi-User Runtime, RBAC, Audit Trail, Dashboard, Analytics, Distributed Runtime, Cluster Manager, Runtime Federation, High Availability, Disaster Recovery, + 17 Autonomous Architectures | Proposed |
+| 0101 | [Autonomous Operations Runtime](RFC/0101_AUTONOMOUS_OPERATIONS_RUNTIME.md) — durable Task Inbox, Background Worker, Task Lease protocol, Privilege Broker, Approval Class policy engine, abstract Scheduler, Notification pipeline, Recovery semantics | Proposed |
 
-## Why this matters
+## Why This Matters
 
 These RFCs address real runtime failures:
 
@@ -287,3 +295,4 @@ These RFCs address real runtime failures:
 - Partial responses must be preserved and continued.
 - The human needs mobile/tablet notifications.
 - Headless servers cannot open interactive login windows for MiniMax usage console.
+- The runtime must continue executing after the chat session ends, the SSH session disconnects, or the provider quota exhausts.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-harness-runtime",
-  "version": "0.9.11",
+  "version": "0.9.14",
   "description": "[BETA] Codex-style /usage status + autonomous coding harness for pi. Not production ready — expect breaking changes.",
   "type": "module",
   "scripts": {