@evoclock/pi-agentic-driver 0.9.3 → 0.10.0

package/PROVENANCE.md

@@ -72,3 +72,12 @@ This repository is the public package source for `@evoclock/pi-agentic-driver`.
   change it, the switch is not persisted, and each microVM run still requires
   native confirmation. Headless sessions fail closed. The existing trusted
   facts, fixed argv, receipt validation, and cleanup checks remain unchanged.
+- The unified tasks skill (session task tools + owner-initiated TaskPromote)
+  reimplements the documented behavior of @ladbabynpm/picc-tasks v0.2.0 (MIT,
+  Copyright (c) 2026 Ladbaby) as prior art: the same tool names, the same
+  storage model (session JSONL snapshot entries plus a disk mirror at
+  ~/.pi/tasks/{taskListId}/tasks.json), and the same result text. No code is
+  copied; this is a clean AGPL-3.0-only reimplementation to the same behavior
+  spec, so no MIT license text is vendored. picc-tasks is an independent
+  project by its author, used as reference; it is not affiliated with, nor
+  does it endorse, pi-agentic-driver.

package/README.md

@@ -43,6 +43,7 @@ proofs for agentic workflows.
 | Tool | What it does | Status |
 |------|--------------|--------|
 | `code_phage` | Reviews a plan against a stated goal before code is written and advises your agent. | shipped |
+| `tasks` | Keeps a session plan close to the work, then lets the owner make selected items durable in `TASKS.md`. | shipped |
 | `agentic_herdr_communication` | Exchanges marked reports with worker agents; never grants authority. | shipped |
 | `agentic_herdr_spawn_worker` | Starts one Pi worker in a pane or tab, with native confirmation. | shipped |
 | `agentic_aidr` | A remedy for AI;DR. Reviews writing for clarity, simplicity, brevity, and humanity. | shipped |
@@ -95,14 +96,43 @@ only, not a runtime dependency).
 
 </details>
 
+<details>
+<summary><strong>tasks, from session plan to durable work</strong> <em>(shipped)</em></summary>
+
+Plans stay close to the work. They do not become board work by accident. The tasks skill gives Pi a familiar session list. It adds an owner-approved way to keep selected tasks in the durable `TASKS.md` board.
+
+- **Keep the working list simple.** Use `TaskCreate`, `TaskGet`, `TaskList`, and `TaskUpdate` as usual; the above-editor widget and footer pill stay live as tasks change.
+- **Keep the Claude-like view.** `/tasks` provides descriptions, active forms, and internal-task markers without mutating the plan.
+- **Make durable work deliberate.** `TaskPromote` never runs automatically. It previews the exact cards and destination before the owner confirms.
+- **Keep authority clear.** The trusted board writer creates and updates `TASKS.md`. The skill does not bypass it.
+- **Make migration gentle.** Existing task files remain readable. Moving to the driver-owned skill does not strand current plans.
+
+The result is a clean handoff from a session plan to durable work. Selected tasks can survive the session, appear on the shared board, and become available for controlled dispatch when ready.
 
-- **prompted planning lifecycle.** Natural-language goals become complete
-  semantic proposals with parent and scope choices at native boundaries. No
-  retry loops, no model-supplied identifiers.
-- **native assignment selection.** Planned assignments are chosen through a
-  native UI over derived candidates, never by model-supplied targets.
-- **inventory refresh.** Git-aware codebase inventory regeneration with
-  verification receipts, so prior-art matching stays honest.
+</details>
+
+**Available now:**
+
+- **task-ledger integration.** Agents can read and act within board card
+  states while the trusted writer retains authority over admission,
+  completion, reconciliation, and migration. The Tasks skill also bridges
+  session planning to the durable `TASKS.md` board.
+- **role and phase routing.** The router separates planning, implementation,
+  review, and escalation phases. It reports endpoint warm state when
+  configured. Warm-session preference remains future work; route affinity
+  never overrides authority.
+
+**Planned in this theme:**
+
+- **prompted planning lifecycle.** Turn natural-language goals into complete
+  proposals with parent and scope choices at native boundaries. No retry
+  loops or model-supplied identifiers.
+- **native assignment selection.** Choose planned assignments through a
+  native UI over derived candidates, never through model-supplied targets.
+- **inventory refresh.** Regenerate the Git-aware codebase inventory with
+  verification receipts so prior-art matching stays honest.
+- **project status and state review.** Add read-only views of workspace Git
+  state, formal records, and task-state health.
 
 <details>
 <summary><strong>router, capacity/policy routing with a binding dispatch gate</strong> <em>(released, 0.9.2)</em></summary>
@@ -180,6 +210,57 @@ is for. The dispatch gate reads them when judging whether a task fits.
 
 </details>
 
+<details>
+<summary><strong>Janus, local Jev evaluation service</strong> <em>(shipped)</em></summary>
+
+Janus is the local evaluation service bundled in this repository under
+`janus/`. It is the only component allowed to talk to the TypeSafe Jev
+model. It wraps the official TypeSafe SDK. It exposes one evaluation endpoint
+and health probes on loopback. The router's semantic ranking and binding
+dispatch gate call it. Nothing else in the harness talks to Jev directly.
+
+**Guarantees:**
+
+- **Loopback only.** Janus binds `127.0.0.1:8787` and nothing else. There is
+  deliberately no bind-address option: it is a local tool.
+- **Key stays in the macOS Keychain.** Janus reads the TypeSafe API key at
+  runtime with a guarded `security` lookup. It never passes the key to
+  subprocesses. It never writes the key to logs or transcripts.
+- **Redaction before every external call.** A secrets/PII pass runs over the
+  state before anything leaves the machine. No disable knob exists.
+- **Single-flight.** Janus coalesces identical requests. It caps distinct
+  in-flight evaluations. It rejects overflow with `busy` instead of queuing
+  silently.
+- **Controlled requests.** Janus enforces a 30k-token request budget. It
+  rejects oversized requests instead of truncating them.
+
+**Running it:**
+
+```sh
+cd janus
+```
+
+```sh
+npm install
+```
+
+```sh
+npx tsx janus/server.ts
+```
+
+For a persistent setup, use the launchd template at
+`janus/user.janus.plist`. Provision the TypeSafe Direct key once in the
+Keychain. The command is in `janus/README.md`.
+
+**When Janus is down:** semantic ranking falls back to preference order. The
+binding dispatch gate blocks dispatch and fails closed. Janus never becomes a
+silent dependency: its absence is loud.
+
+See `janus/README.md` for the full endpoint contract, the error taxonomy, and
+configuration.
+
+</details>
+
 ## Multi-agent communication
 
 *Extensions for controlled coordination between agents.*
@@ -582,20 +663,21 @@ silently allowed.
 
 *Extensions that keep routine Git low-friction and consequential Git guarded.*
 
-**In development:**
+**Planned:**
 
-- **git workflow safeguards.** Design only; the package contains no Git
-  extension yet. The planned capability covers exact-file staging, native
-  confirmation, post-confirmation drift checks, and protected-operation
-  boundaries.
-- **assignment-aware Git journeys.** Merge and protected-push flows bound to
-  a verified assignment, so consequential Git operations carry their own
-  recorded provenance.
+- **git workflow safeguards.** Not packaged yet. The planned capability covers
+  exact-file staging, native confirmation, post-confirmation drift checks,
+  and protected-operation boundaries.
+- **assignment-aware Git journeys.** Planned merge and protected-push flows
+  bound to a verified assignment, so consequential Git operations carry their
+  own recorded provenance.
 
 ## Package integrity
 
 *Extensions that keep the installed set honest and the record controlled.*
 
+**Planned:**
+
 - **security and integrity scanning.** Static scanning of MCP configs, agent
   skills, and extension packages for hardcoded secrets, prompt and shell
   injection, data-exfiltration endpoints, untrusted integrations, PII
@@ -653,10 +735,10 @@ extensions you want with the object form in your Pi settings:
 }
 ```
 
-The package includes the `herdr-communication.ts`, `herdr-lifecycle.ts`, and
-`herdr-dispatch.ts` extensions. It also includes `linux-microvm.ts`. Use `pi config` to enable or
-disable individual resources from an installed package. You are not required
-to use every extension.
+The package includes the Herdr communication, lifecycle, and dispatch
+extensions, the board and Tasks extensions, and `linux-microvm.ts`. Use
+`pi config` to enable or disable individual resources from an installed
+package. You are not required to use every extension.
 
 ## License