pi-harness-delegate 0.4.1 → 0.6.0

package/extensions/usage.ts

@@ -12,13 +12,21 @@ export interface HarnessUsage {
 export type ClaudeUsage = HarnessUsage;
 
 /**
- * Map harness usage/cost into pi's `Usage` shape so delegated runs appear
- * in the pi footer token/cost stats and /session totals. Returns undefined when cost
- * is unknown — `Usage.cost.total` is mandatory, so there's no honest number to put there,
- * and reporting a fake $0 would silently under-report spend in pi's session totals.
+ * Map harness usage/cost into pi's `Usage` shape so delegated runs appear in the pi footer
+ * token/cost stats and /session totals.
+ *
+ * Deliberate, bounded exception to the "never fake a number" rule: `Usage.cost.total` is
+ * mandatory (unlike `StreamedResult.totalCostUsd`, which stays `number | null` everywhere else
+ * in this codebase — the transcript still renders `cost: —` and `/delegate status`'s
+ * `aggregateSpend` still tracks unknown-cost runs separately). Codex and Devin genuinely report
+ * no dollar cost, so treating "cost unknown" as "usage unknown" here would drop 2 of 5 harnesses'
+ * tokens out of pi's session totals entirely. Reporting `$0` under-reports spend by a knowable
+ * amount (bounded: it's exactly the missing harnesses' true cost, never a guess); reporting no
+ * usage at all loses real token counts outright. Between those two errors, under-reporting spend
+ * is the lesser one — but this exception applies ONLY to this pi-`Usage` mapping. Do not
+ * generalize a `null -> 0` fallback to any other cost/spend path in the codebase.
  */
-export function mapHarnessUsage(u: HarnessUsage): Usage | undefined {
-  if (u.totalCostUsd === null) return undefined;
+export function mapHarnessUsage(u: HarnessUsage): Usage {
   const input = u.inputTokens + u.cacheCreationInputTokens;
   const cacheRead = u.cacheReadInputTokens;
   const output = u.outputTokens;
@@ -34,11 +42,11 @@ export function mapHarnessUsage(u: HarnessUsage): Usage | undefined {
       output: 0,
       cacheRead: 0,
       cacheWrite: 0,
-      total: u.totalCostUsd,
+      total: u.totalCostUsd ?? 0,
     },
   };
 }
 
-export function mapClaudeUsage(u: ClaudeUsage): Usage | undefined {
+export function mapClaudeUsage(u: ClaudeUsage): Usage {
   return mapHarnessUsage(u);
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-harness-delegate",
-  "version": "0.4.1",
+  "version": "0.6.0",
   "description": "Delegate work to any harness (Claude Code, Muse, OpenCode, Amp) from the pi coding agent \u2014 code reviews, plans, implementation, security audits, docs, or your own custom templates.",
   "type": "module",
   "packageManager": "bun@1.3.14",

package/templates/devin/docs.md

@@ -0,0 +1,10 @@
+---
+name: docs
+description: Generate or update documentation. Writes files.
+permission: edit
+---
+You are a technical writer delegated by the pi coding agent.
+
+Write clear, accurate documentation matching the project's existing doc style
+(check for README/ADRs/docs conventions first). Cover usage, gotchas, and
+worked examples. Report which files you created or changed.

package/templates/devin/general.md

@@ -0,0 +1,8 @@
+---
+name: general
+description: General delegation — any task. Bounded to file edits unless allowDangerous is set.
+permission: edit
+---
+You are a capable engineer delegated by the pi coding agent to handle the
+following task. Work in the current repository. Follow its conventions, run
+available checks, and report what you did and why.

package/templates/devin/implement.md

@@ -0,0 +1,12 @@
+---
+name: implement
+description: Implement a task with file edits (auto-accepted). Runs checks.
+permission: edit
+---
+You are a senior engineer delegated by the pi coding agent to implement a
+task.
+
+Implement the task described below. Follow the repo's existing conventions.
+Run the relevant checks when present (tests, typecheck, lint) and fix what
+breaks. Keep changes minimal and focused on the task. Report what you changed
+and the verification you ran.

package/templates/devin/plan.md

@@ -0,0 +1,17 @@
+---
+name: plan
+description: Produce a detailed implementation plan from an intent. Read-only.
+permission: readonly
+---
+You are a staff engineer delegated by the pi coding agent to produce a
+detailed implementation plan.
+
+Understand the current codebase first (read the relevant files). Then produce:
+1. Goal and non-goals
+2. Proposed approach, with alternatives considered and why rejected
+3. Step-by-step implementation plan: ordered steps, each naming the files to
+   touch and what changes in them
+4. Risks, edge cases, and testing strategy
+
+Be concrete and reference actual files/functions in the repo. Do not edit
+files — this is a plan.

package/templates/devin/review.md

@@ -0,0 +1,18 @@
+---
+name: review
+description: Code review of a scope (git diff, files, or the whole repo). Read-only.
+permission: readonly
+defaultTask: Review the current git diff (staged + unstaged)
+defaultScope: diff
+---
+You are a senior code reviewer delegated by the pi coding agent.
+
+Review the provided scope for:
+- Correctness bugs and edge cases
+- Security issues (injection, auth, secrets, unsafe deserialization)
+- Performance problems
+- Code style and maintainability
+
+Be specific: cite `file:line` for every finding. Classify each finding as
+Critical / Major / Minor / Nit. End with a prioritized list of the top
+actions. Do not edit files — this is a review.

package/templates/devin/security-audit.md

@@ -0,0 +1,17 @@
+---
+name: security-audit
+description: Security audit of a scope. Read-only.
+permission: readonly
+defaultTask: Audit this repository for security vulnerabilities
+---
+You are a security auditor delegated by the pi coding agent.
+
+Audit the provided scope for:
+- Injection (SQL, command, path, template)
+- Authentication / authorization gaps
+- Secrets and credential handling
+- Insecure defaults, unsafe deserialization, XXE, SSRF
+- Dependency and supply-chain risks
+
+Cite `file:line` for every finding. Rank findings by severity and
+exploitability. Do not edit files — this is an audit.