@difflab/pi 0.6.0 → 0.7.0-rc.202609271854.6af8600

package/dist/tools/plan.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"plan.d.ts","sourceRoot":"","sources":["../../src/tools/plan.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,YAAY,EAAE,cAAc,EAAE,MAAM,iCAAiC,CAAC;AAQpF,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,UAAU,CAAC;AAM/C,OAAO,EAAmB,KAAK,SAAS,EAAE,MAAM,eAAe,CAAC;AAmBhE,MAAM,MAAM,eAAe,GAAG,IAAI,CAAC,YAAY,EAAE,QAAQ,GAAG,iBAAiB,CAAC,GAC5E,OAAO,CAAC,IAAI,CAAC,YAAY,EAAE,aAAa,CAAC,CAAC,CAAC;AAE7C,wBAAgB,eAAe,CAC7B,GAAG,EAAE,eAAe,EACpB,MAAM,EAAE,cAAc,EACtB,KAAK,GAAE,SAA6B,GACnC,SAAS,cAAc,EAAE,CA6W3B"}
+{"version":3,"file":"plan.d.ts","sourceRoot":"","sources":["../../src/tools/plan.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,YAAY,EAAE,cAAc,EAAE,MAAM,iCAAiC,CAAC;AAQpF,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,UAAU,CAAC;AAM/C,OAAO,EAAmB,KAAK,SAAS,EAAE,MAAM,eAAe,CAAC;AAchE,MAAM,MAAM,eAAe,GAAG,IAAI,CAAC,YAAY,EAAE,QAAQ,GAAG,iBAAiB,CAAC,GAC5E,OAAO,CAAC,IAAI,CAAC,YAAY,EAAE,aAAa,CAAC,CAAC,CAAC;AAE7C,wBAAgB,eAAe,CAC7B,GAAG,EAAE,eAAe,EACpB,MAAM,EAAE,cAAc,EACtB,KAAK,GAAE,SAA6B,GACnC,SAAS,cAAc,EAAE,CAkR3B"}

package/dist/tools/review.d.ts

@@ -1,4 +1,42 @@
 import { type ToolDefinition } from '@earendil-works/pi-coding-agent';
+import { run } from '../extensions/processx';
+import { type ReviewComment, type ReviewDraft, type ReviewThreadRecord } from '../review';
+export declare function hasReviewDraft(comments: readonly ReviewComment[], body: string): boolean;
+export declare function reviewBrowserCommand(url: string, platform?: NodeJS.Platform): {
+    command: string;
+    args: string[];
+};
+export declare function openReviewUrl(url: string, execute?: typeof run, platform?: NodeJS.Platform): Promise<boolean>;
+export declare function partitionReviewComments(comments: readonly ReviewComment[], knownFingerprints: ReadonlySet<string>, model: string): {
+    checkpointed: {
+        source: ReviewComment;
+        published: {
+            body: string;
+            file: string;
+            line?: number;
+            side?: import("..").ReviewSide;
+            author?: string;
+            sourceCommentId?: string;
+        };
+        fingerprint: string;
+    }[];
+    candidates: {
+        source: ReviewComment;
+        published: {
+            body: string;
+            file: string;
+            line?: number;
+            side?: import("..").ReviewSide;
+            author?: string;
+            sourceCommentId?: string;
+        };
+        fingerprint: string;
+    }[];
+};
+export declare function reviewResponseResolution(question: boolean, requested?: boolean): boolean;
+export declare function workingTreeReplyDraft(thread: ReviewThreadRecord, body: string): ReviewDraft;
+export declare function resolveReviewThread(comment: ReviewComment, threads: readonly ReviewThreadRecord[]): ReviewThreadRecord | undefined;
 export declare function workingTreeDiff(cwd: string): Promise<string>;
 export declare function createReviewTools(): readonly ToolDefinition[];
+export declare function syncLocalThreadArtifact(path: string, title: string, sessionSlug: string, threads: readonly ReviewThreadRecord[]): Promise<ReviewThreadRecord[]>;
 //# sourceMappingURL=review.d.ts.map

package/dist/tools/review.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"review.d.ts","sourceRoot":"","sources":["../../src/tools/review.ts"],"names":[],"mappings":"AAGA,OAAO,EAAqC,KAAK,cAAc,EAAE,MAAM,iCAAiC,CAAC;AA2EzG,wBAAsB,eAAe,CAAC,GAAG,EAAE,MAAM,GAAG,OAAO,CAAC,MAAM,CAAC,CAalE;AAID,wBAAgB,iBAAiB,IAAI,SAAS,cAAc,EAAE,CAma7D"}
+{"version":3,"file":"review.d.ts","sourceRoot":"","sources":["../../src/tools/review.ts"],"names":[],"mappings":"AAGA,OAAO,EAAqC,KAAK,cAAc,EAAE,MAAM,iCAAiC,CAAC;AAKzG,OAAO,EAAE,GAAG,EAAc,MAAM,wBAAwB,CAAC;AACzD,OAAO,EAwBL,KAAK,aAAa,EAClB,KAAK,WAAW,EAChB,KAAK,kBAAkB,EACxB,MAAM,WAAW,CAAC;AAwEnB,wBAAgB,cAAc,CAAC,QAAQ,EAAE,SAAS,aAAa,EAAE,EAAE,IAAI,EAAE,MAAM,GAAG,OAAO,CAExF;AAED,wBAAgB,oBAAoB,CAAC,GAAG,EAAE,MAAM,EAAE,QAAQ,GAAE,MAAM,CAAC,QAA2B;;;EAM7F;AAED,wBAAsB,aAAa,CACjC,GAAG,EAAE,MAAM,EACX,OAAO,GAAE,OAAO,GAAS,EACzB,QAAQ,GAAE,MAAM,CAAC,QAA2B,GAC3C,OAAO,CAAC,OAAO,CAAC,CAOlB;AAED,wBAAgB,uBAAuB,CACrC,QAAQ,EAAE,SAAS,aAAa,EAAE,EAClC,iBAAiB,EAAE,WAAW,CAAC,MAAM,CAAC,EACtC,KAAK,EAAE,MAAM;;;;;;;;;;;;;;;;;;;;;;;;;EAUd;AAED,wBAAgB,wBAAwB,CAAC,QAAQ,EAAE,OAAO,EAAE,SAAS,CAAC,EAAE,OAAO,GAAG,OAAO,CAExF;AAED,wBAAgB,qBAAqB,CAAC,MAAM,EAAE,kBAAkB,EAAE,IAAI,EAAE,MAAM,GAAG,WAAW,CAY3F;AAED,wBAAgB,mBAAmB,CACjC,OAAO,EAAE,aAAa,EACtB,OAAO,EAAE,SAAS,kBAAkB,EAAE,GACrC,kBAAkB,GAAG,SAAS,CAmBhC;AAED,wBAAsB,eAAe,CAAC,GAAG,EAAE,MAAM,GAAG,OAAO,CAAC,MAAM,CAAC,CAalE;AAID,wBAAgB,iBAAiB,IAAI,SAAS,cAAc,EAAE,CAof7D;AAID,wBAAsB,uBAAuB,CAC3C,IAAI,EAAE,MAAM,EACZ,KAAK,EAAE,MAAM,EACb,WAAW,EAAE,MAAM,EACnB,OAAO,EAAE,SAAS,kBAAkB,EAAE,GACrC,OAAO,CAAC,kBAAkB,EAAE,CAAC,CAwB/B"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@difflab/pi",
-  "version": "0.6.0",
+  "version": "0.7.0-rc.202609271854.6af8600",
   "description": "Tools and skills for the pi coding agent",
   "repository": {
     "type": "git",
@@ -34,8 +34,7 @@
     "agents/",
     "dist/",
     "skills/",
-    "templates/",
-    "workflows/"
+    "templates/"
   ],
   "pi": {
     "extensions": [
@@ -58,7 +57,6 @@
   },
   "dependencies": {
     "@juicesharp/rpiv-ask-user-question": "^2.10.1",
-    "cmd-ts": "^0.15.0",
     "commander": "^14.0.0",
     "mdast-builder": "1.1.1",
     "pi-mcp-adapter": "^2.33.0",

package/skills/plan/SKILL.md

@@ -1,23 +1,17 @@
 ---
 name: plan
-description: Route natural-language planning requests to Diffpi's /plan commands. Use when a user wants to create, revise, annotate, finalize, or execute a durable plan, or asks which /plan command to run.
-allowed-tools: ask_user_question
+description: Create, revise, annotate, finalize, and execute durable Diffpi plans. Use for /skill:plan, /plan, or natural-language planning requests.
+allowed-tools: read grep find write edit symbol_search module_report read_symbol ask_user_question Agent get_subagent_result steer_subagent plan_context plan_annotate plan_start_execution plan_update_status plan_log_progress plan_run_gates plan_record_ci watch_ci
 ---
 
-# Plan Command Guide
+# Plan
 
-Use `/plan` commands as the execution boundary. Do not reproduce their workflows, call `plan_*` tools directly, or edit managed plan files.
+This skill owns the workflow. `/plan` only forwards its raw arguments to `/skill:plan`. Do not emit another command to paste or rely on a command handler to select an agent, parse flags, or inject a workflow. For NEW and UPDATE, use ordinary file tools to edit the authoritative live PLAN.md and implementation brief files. Never use file tools to alter immutable legacy snapshots, revisions, reviews, or logs; remaining references to those managed artifacts are transitional guidance pending phase 4.
 
-## Natural-language routing
+Identify the first explicit verb (`init`, `new`, `update`, `annotate`, `finalize`, `go`, `help`) or infer one from the user's request. For NEW and UPDATE, select one unique repository-root plan by path and its plan files, and read it before acting; ask only for a material decision if the plan remains ambiguous. Read exactly the corresponding [workflow reference](references/workflows/) before acting. Preserve the user's request and intent, including visible completed task information; this is authoring input, not a managed revision transaction.
 
-Map the user's intent to one command:
+`new` creates a complete plan without launching an editor; `init` creates a phase-less draft and opens it. For NEW and UPDATE content changes, write the authoritative live PLAN.md and numbered briefs directly through successive normal read/write/edit calls, then read back each file. Invoke exactly one independently verified frontier/high-thinking `diffpi-plan-reviewer` per iteration; repair actionable findings and rerun it within bounded attempts. If effective model/thinking selection cannot be verified, fail preflight with the exact observed selection and required correction; do not silently promise runtime verification. Phase/task status and execution gates remain managed-tool concerns. The remaining init/annotate/finalize/go references retain old managed-tool calls only as transitional guidance until phase 4 replaces them; they must not be presented as Planner capabilities. `go` calls `plan_start_execution` before any code change; if the plan is draft or on the wrong branch, stop.
 
-- Create an empty plan shell: `/plan init <short-slug> [--branch <name>]`
-- Research and author a complete plan: `/plan new <short-slug> [--branch <name>] [--bg] [prompt...]`
-- Revise a plan from chat instructions or its current plan review: `/plan update [short-slug] [--branch <name>] [--bg] [instructions...]`
-- Review a plan in tuicr and save the result: `/plan annotate [short-slug]`
-- Validate and mark a plan ready: `/plan finalize [short-slug]`
-- Execute a plan: `/plan go <short-slug> [--mode <no-commit|commit|push>] [--bg]`
-- Show command help: `/plan help`
+`--bg` requests one named background agent through `Agent` (Planner for authoring, Orchestrator for execution); pass the verb, exact arguments, cwd, and a `background: true` instruction. Remove `--bg` from the child's request and explicitly forbid redispatch. Return after launching it. A background child must not ask user questions. If `Agent` is unavailable, stop and report that background execution cannot be started; never silently execute inline. Without `--bg`, execute in the current turn: author as Planner, coordinate go as Orchestrator and delegate bounded Worker tasks; do not assume an inline mode switch occurred. Do not launch a multi-agent workflow unless the user explicitly opts into one.
 
-Infer the command, slug, branch, and free-text arguments from recent conversation when they are clear. If a required value cannot be inferred, use `ask_user_question`; do not ask in plain chat. Then give the user one exact, copyable `/plan` command. Explain defaults only when relevant: `go` uses `--mode no-commit` when `--mode` is omitted.
+Operational references: [init](references/workflows/init.md), [new](references/workflows/new.md), [update](references/workflows/update.md), [annotate](references/workflows/annotate.md), [finalize](references/workflows/finalize.md), [go](references/workflows/go.md), [help](references/workflows/help.md). NEW and UPDATE use direct authoritative file writes. The init/annotate/finalize/go references are transitional managed-tool guidance until phase 4 replaces them.

package/skills/plan/references/design-quality.md

@@ -0,0 +1,30 @@
+# Plan authoring quality
+
+Build from repository evidence. Keep the result compact and useful to a Worker.
+
+## PLAN.md
+
+- Keep intent, requirements, design, references, and numbered phases in `PLAN.md`.
+- Give each phase a stable ID, title, objective, and prerequisites. Prerequisites belong to phases only.
+- Put each discrete implementation action in a flat task checkbox with a stable task ID and title. Do not put dependency metadata, steps, file scopes, or acceptance criteria under the checkbox.
+- Preserve phase/task ID and order parity in every implementation brief.
+
+## Implementation brief
+
+- Give tasks ordered implementation steps. Add nested `Verify` bullets under the relevant task; verification is part of the task, not a separate task.
+- List exact file scopes and acceptance criteria for every task.
+- Put libraries and algorithms under **Implementation Constraints**.
+- Include exactly one fenced `text` phase-level directory tree. Label every file leaf with one of `[ADD]`, `[MODIFY]`, `[REMOVE]`, `[MOVE from: path]`, or `[VERIFY]`.
+- Read back each file after writing it. Normal successive write/edit calls are intentional: incomplete drafts remain visible until the plan is ready.
+
+## Review and repair
+
+Template metadata such as revision snapshots and managed markers is not an authoring requirement. Treat their removal as a legacy compatibility change: the existing managed parser will stop recognizing these templates until the follow-on source migration adds a replacement contract. Report that break explicitly; do not preserve metadata in the templates solely to hide it.
+
+After writing the current `PLAN.md` and all numbered briefs, independently invoke exactly one VERIFIED frontier/high-thinking `diffpi-plan-reviewer` in read-only mode. The reviewer checks structure and parity, action labels, whole-plan quality, consistency and risk, and whether every task is executable by a lightweight Worker without guessing, in one pass. Do not replace this with cheap separate reviewers or tiered checks.
+
+The Planner repairs actionable findings and reruns the same reviewer within bounded attempts. A passing review does not prove that source code implements the plan. `annotate` is optional human review; it does not replace the automated reviewer.
+
+## Contracts and consequences
+
+Describe real API or data-flow changes. If there is no public API change, say so and show the relevant internal contract. Explain before/after invocation, what readers or Workers consume, validation and failure visibility, and at least one concrete trade-off. Do not use scaffold placeholders in a plan marked ready.

package/skills/plan/references/workflows/annotate.md

@@ -0,0 +1,11 @@
+# `/plan annotate`
+
+## PLAN.md task
+
+Review the selected plan in tuicr and save one immutable review.
+
+## Brief
+
+1. Call `plan_context` and resolve the exact plan ID from the slug or conversation; ask the user only if candidates remain ambiguous.
+2. Call `plan_annotate` using the plan file; it owns the tuicr session and review artifact.
+3. Report the selected plan, launch result, and copyable fallback command. Tell the user to run `/plan update <plan-id>` after closing tuicr.

package/skills/plan/references/workflows/finalize.md

@@ -0,0 +1,7 @@
+# Finalize
+
+1. Call `plan_context` to resolve exactly one persisted plan. Call `plan_review` once for that plan and revision. If a current annotation exists, incorporate its exact feedback as one content request through `plan_apply_revision` before finalizing; do not mutate the plan per individual comment. A stale review must not be applied.
+2. Call `plan_validate` with `strict: true` on the resulting revision. Stop if any error remains; this validates plan structure, detailed briefs, and revision snapshots, **not implementation correctness**. Do not mark a plan with empty briefs ready.
+3. Call `plan_update_status` to mark the draft `ready`. Do not call `plan_start_execution` until the user chooses execution.
+4. In foreground mode, use one `ask_user_question` for next action (execute now in foreground/background, later, or keep planning); if executing, also obtain commit mode (`no-commit`, `commit`, or `push`; default `no-commit` if already specified). If they choose execution, follow the [go workflow](go.md) directly in the selected mode; background execution launches one child, not another slash command. If they choose later or planning, return the ready state. Background finalization cannot ask and must leave execution for an explicit request.
+5. No inline mode was selected by a command, so do not unset one as a side effect of finalization.

package/skills/plan/references/workflows/go.md

@@ -0,0 +1,8 @@
+# Go
+
+1. Call `plan_context` with the supplied slug. Accept only `no-commit`, `commit`, or `push`; omitted `--mode` means `no-commit`. Do not ask for a mode if the user already chose it.
+2. If the resolved plan is `draft`, finalize it inline before execution: call `plan_review` for the current revision and consume only a current review (apply its exact feedback as one `plan_apply_revision` amend when present; ignore stale reviews), then call `plan_validate` with `strict: true`. If validation passes, call `plan_update_status` for the plan from `draft` to `ready`. Do not invoke the finalize workflow or ask its next-action question. An already `ready` or `blocked` plan needs no review or readiness transition; pass it to `plan_start_execution`, which owns restart and blocker eligibility checks.
+3. Call `plan_start_execution` **before** modifying source, delegating work, or running gates. This enforces ready/blocked status, correct branch, clean worktree when committing, and durable execution ownership. On failure, stop and report the exact blocker; never implement a draft plan speculatively.
+4. Use the returned execution ID and packet. Read the complete phase briefs, assign bounded tasks in dependency order to Workers, and track progress and status through plan tools. Workers do not commit or restructure the plan. Run `plan_run_gates` when a phase's tasks are complete. Failed gates block that phase until repaired and rerun.
+5. In `no-commit`, make no commits or pushes. In `commit`, commit once per phase **after** gates pass; do not push or watch CI. In `push`, push each gated phase commit and monitor CI for its exact SHA, collecting the monitor before the next push and all monitors before completion. Persist the observed commit/CI metadata through plan tools.
+6. Complete the plan only after every task, phase, gate, and required CI settles. Report execution ID, mode, and evidence. Background execution must not affect foreground mode; foreground execution does not require a mode reset because this skill did not select one.

package/skills/plan/references/workflows/help.md

@@ -0,0 +1,10 @@
+# `/plan help`
+
+## PLAN.md task
+
+Show the available plan commands and their concise purposes.
+
+## Brief
+
+1. List `init` (phase-less draft), `new` (research and author), `update` (apply review/instructions), `annotate` (tuicr review), `finalize` (validate and mark ready), `go` (start execution), and `help`.
+2. State that `--branch` records or filters metadata, `go` defaults to `--mode no-commit`, and background workflows do not ask questions.

package/skills/plan/references/workflows/init.md

@@ -0,0 +1,5 @@
+# Init
+
+1. Resolve the supplied short slug and optional branch, title, intent, issue ID, and URL. `--branch` records metadata; it does not switch branches. Call `plan_context` first and stop if the selected plan already exists.
+2. Call `plan_init` with `open: true` and `request: {kind: "user", text: <exact incoming request>}`. The tool creates one phase-less draft and its initial request-scoped revision snapshot, then opens `PLAN.md` in a supported adjacent editor tab. Do not perform additional content mutations for this request.
+3. Return the plan ID, clickable path, and actual launch outcome or fallback path. Explain that `annotate` stores a plan review, `update` applies review or further instructions, and `finalize` checks completeness before execution.

package/skills/plan/references/workflows/new.md

@@ -0,0 +1,7 @@
+# New
+
+1. Resolve the initiating nested Git root and the requested slug/branch, then inspect for a plan collision. If a matching plan already exists, stop. Only after confirming no matching plan exists, research and create the plan; do not read a nonexistent plan. If the goal is unspecified in foreground mode, ask one material question; background work must report a blocker instead.
+2. Research repository files, APIs, tests, and constraints. Follow [plan authoring quality](../design-quality.md). Draft the complete PLAN.md and one numbered brief per phase. Preserve the user's request and intent in the visible plan content, including any visible completed task information; this is authoring input, not a revision transaction.
+3. Write the plan directory directly with normal `write`/`edit` calls. Write PLAN.md and briefs incrementally so incomplete files remain visible. Do not call `plan_apply_revision`, `plan_validate`, or edit managed snapshots. Include exact scopes, ordered steps, constraints, acceptance criteria, task parity, one action-labeled tree per brief, and nested verification.
+4. Read back every written file. Invoke exactly one `diffpi-plan-reviewer` over PLAN.md and all numbered briefs in a single pass. Before relying on its result, verify the effective model is the explicit frontier model (prefer `openai-codex/gpt-5.6-sol`, or an available equivalent), thinking is high, and tools are read/search-only. If selection cannot be verified, fail preflight with the exact observed model/thinking/tools and required correction; do not silently promise runtime verification or use a cheap fallback.
+5. Repair actionable findings directly, then rerun the same reviewer within bounded attempts. A pass checks plan quality only; it does not prove source implementation. Report plan and brief paths, review evidence, and any compatibility caveat. Policy governs the plan-file source scope; this is not a Pi sandbox guarantee.

package/skills/plan/references/workflows/update.md

@@ -0,0 +1,7 @@
+# Update
+
+1. Select exactly one unique repository-root plan by its path and plan files. Read the current PLAN.md, all numbered briefs, and the incoming request. Preserve the user's intent and all visible completed task information, including IDs, ownership, evidence, and dependencies.
+2. Research affected repository files and follow [plan authoring quality](../design-quality.md). Build the entire resulting PLAN.md and numbered briefs in memory, preserving exact phase/task order parity. Do not guess among plans or rewrite historical records.
+3. Apply the update through successive direct `write`/`edit` calls to the authoritative plan files. Do not call `plan_apply_revision`, `plan_validate`, or edit managed snapshots. Read back each file after writing. New files remain visible while incomplete.
+4. Invoke exactly one `diffpi-plan-reviewer` over the current PLAN.md and every numbered brief in one pass. Verify its effective model is the explicit frontier model (prefer `openai-codex/gpt-5.6-sol`, or an available equivalent), thinking is high, and capabilities are read/search-only. If effective selection cannot be verified, fail preflight with the exact observed model/thinking/tools and required correction; never silently promise runtime verification or accept a cheap fallback.
+5. Repair actionable findings directly and rerun the same reviewer within bounded attempts. Report changed files, review evidence, remaining blocker, and compatibility caveat. A passing review is structural/semantic plan evidence only, not proof source code implements the plan. Policy governs the plan-file source scope; this is not a Pi sandbox guarantee.

package/skills/review/SKILL.md

@@ -1,15 +1,15 @@
 ---
 name: review
-description: Code review workflows over GitHub, GitLab, or local tuicr revision dumps. Use for auto reviews, review opening and editing, addressing, publishing, completing, merging, or local review requests.
-allowed-tools: ask_user_question review_context review_new review_edit review_diff review_gates review_submit review_add_comment review_comments review_dump review_respond review_publish review_complete review_merge review_launch_ui
+description: Create, edit, review, address, publish, complete, and merge GitHub/GitLab or local tuicr reviews. Use for /skill:review, /review, or natural-language review requests.
+allowed-tools: read ask_user_question Agent get_subagent_result steer_subagent review_context review_status review_new review_open review_edit review_diff review_gates review_submit review_add_comment review_comments review_respond review_publish review_complete review_merge review_launch_ui diffpi_template
 ---
 
-# review
+# Review
 
-Use the exact package workflow supplied by the `/review` command. Do not look for workflow files inside this skill.
+This skill owns the workflow. `/review` only forwards raw arguments to `/skill:review`; never rely on command-side flag parsing or mode activation. Parse the first non-flag argument as the verb and preserve remaining arguments and their order. Normalize `create`, `draft` → `new`; `launch` → `auto`; `ready` → `publish`; `close` → `complete`; `land` → `merge`. `open` and `status` are first-class lifecycle workflows. Empty/unknown verb shows [help](references/workflows/help.md).
 
-Call `review_context` first. Treat `--local` as a working-tree tuicr flow. A completed local session becomes one immutable review dump; applying feedback starts a new revision. Local reviews have no thread ledger, replies, resolution state, or remote promotion.
+`--local` selects the working-tree tuicr backend and **must be preserved** for the selected workflow; without it, use the forge. `--bg` is an execution flag: remove it from the child request and launch exactly one named background Orchestrator through `Agent`, passing verb, arguments, cwd, and an explicit `background: true` instruction. The child executes the workflow once without redispatch or interactive questions; the current foreground role remains unchanged. Without `--bg`, execute directly in this turn. Do not change inline modes or emit a command for the user to paste. Do not launch a multi-agent workflow unless the user explicitly opts into one.
 
-Without `--local`, use the detected GitHub or GitLab target directly. Stage findings, read forge threads, post replies, publish status, and perform lifecycle actions through the remote review tools.
+Read [the selected reference](references/workflows/) before acting. Every operational workflow calls `review_context` first with the same target and `local` setting. Use `ask_user_question` only for material decisions not derivable from the request; never ask as plain chat text. `auto` and `address` require reviewer judgment and thread classification; if a background Orchestrator is running, delegate that bounded judgment to a Reviewer via `Agent`, then collect the result. Delegate non-overlapping implementation only where useful. Lifecycle verbs retain the coordinator role. Tools own target selection, templates, comment staging, replies, publication, and forge calls; do not reimplement them with shell commands.
 
-Use `ask_user_question` only for decisions that cannot be derived. Inline `auto` and `address` run under Reviewer; lifecycle workflows run under Orchestrator. Background execution is already routed by the command and must not change the foreground mode.
+References: [auto](references/workflows/auto.md), [new](references/workflows/new.md), [open](references/workflows/open.md), [status](references/workflows/status.md), [edit](references/workflows/edit.md), [address](references/workflows/address.md), [publish](references/workflows/publish.md), [complete](references/workflows/complete.md), [merge](references/workflows/merge.md), [help](references/workflows/help.md). Keep publication separate from completion and merge; `review_merge` remains GitHub-only.

package/skills/review/references/review-standards.md

@@ -2,6 +2,13 @@
 
 Use these rules for review and address workflows.
 
+## Operational workflow rules
+
+- Each workflow parses its own arguments. Do not assume a parent `/review` command stripped `--bg` or selected a backend.
+- Call `review_context` first, with `local: true` for `--local` and `local: false` for forge-backed work. Pass the same target and backend to every later lifecycle tool.
+- Skill-owned aliases (`open`, `create`, `draft`, `launch`, and `close`) follow their named workflow; they do not bypass argument parsing or safety checks.
+- `--bg` runs the complete workflow in a tracked background Orchestrator. Lifecycle ownership and publication/completion/merge safety remain unchanged.
+
 ## Intent
 
 Check that the change serves the stated PR intent. Treat a missing required behavior as blocking.
@@ -20,4 +27,4 @@ Prefer existing package APIs and small public surfaces. Add a dependency when it
 
 ## Responses
 
-Respond to every addressed thread. State what changed and include verification evidence. Keep every thread open for the user to resolve. Address workflows must never resolve or delete threads.
+Respond to every thread with an explicit outcome and verification evidence. Apply every relevant requested change now; “deferred”, “later”, and “follow-up” are not acceptable unless the user explicitly requested deferral. Mark a thread unresolved only for a concrete external blocker or material user decision, and include attempted fixes and evidence. Keep every thread open for the user to resolve. Address workflows must never resolve or delete threads.

package/skills/review/references/workflows/address.md

@@ -0,0 +1,11 @@
+# address
+
+1. Parse an optional PR/MR id or URL and `--local`. The skill owns `--bg` dispatch before this reference is followed; a background child executes these steps directly and must not redispatch.
+2. Run this workflow as the reviewer coordinator. Call `review_context` first with the same target and `local: true` when `--local` is present, otherwise `local: false`.
+3. Call `review_comments` with the same target and backend. With `--local`, it synchronizes every comment in the selected tuicr session to `.diffpi/review/<session-slug>.md`. Existing replies and statuses remain; source comments removed by the user become resolved ledger entries.
+4. Classify every thread, group justified code changes into bounded non-overlapping tasks, and delegate those tasks to lightweight worker agents. Keep questions, outcome decisions, integration, and response text in the reviewer coordinator. With `--local`, workers modify the current working tree without committing. Without `--local`, apply a fix only when the comment requests a change.
+5. Apply every relevant requested change in this workflow. Do not label a relevant request deferred, later, or follow-up unless the user explicitly requested deferral. Use unresolved only for a concrete external blocker or material user decision, and state the attempted fixes and evidence. Respond to every thread with an explicit outcome and verification evidence. Answer questions and leave them open. For substantive requests, state what changed and whether it is resolved, but leave every thread open for the user to resolve. Do not resolve remote threads or delete local source comments in this workflow, including for trivial requests.
+6. When a remote address flow changes code, invoke the upstream `/git commit --no-push` workflow after checks pass and before drafting responses. Use `--atomic` when the fixes form separate logical commits.
+7. Call `review_respond` for each thread with `resolve: false`. With `--local`, every response is posted to tuicr and recorded in the session ledger. Without `--local`, replies post to the forge immediately. The user owns thread resolution.
+8. With `--local`, call `review_launch_ui` with `local: true` after replies are recorded so the user can inspect the working-tree review in tuicr.
+9. Report fixed, committed, answered, addressed, unresolved, and skipped counts. Resolved must always be zero in this workflow. Do not publish, complete, or merge.

package/skills/review/references/workflows/auto.md

@@ -0,0 +1,18 @@
+# auto
+
+1. Parse an optional PR/MR id or URL and `--local`. The skill owns `--bg` dispatch before this reference is followed; a background child executes the remaining steps directly and must not redispatch. `launch` aliases this workflow.
+2. Call `review_context` first with the same target and `local: true` when `--local` is present, otherwise `local: false`.
+3. Call `review_new` with the same target and backend selection to create the local tuicr review or remote draft PR/MR and open its tuicr UI. A remote branch must be clean and pushed. If the review already exists, use `review_edit` with the same backend instead.
+4. Before reviewing, run `review_gates` so the project's discovered format-check and lint tasks run first, followed by its other gates. Preserve and report failures; do not substitute visual inspection for failed or skipped checks.
+5. Run review judgment as the reviewer agent. Inline, the reviewer performs the workflow tool calls directly. In background execution, the orchestrator delegates judgment to the reviewer and retains lifecycle calls. The reviewer fetches the diff with `review_diff` and may launch parallel lightweight subagents for independent areas when useful.
+6. Review the change for:
+   - whether it accomplishes the stated intent;
+   - whether the technical approach is the best practical way to accomplish that intent;
+   - correctness, including failure paths and edge cases;
+   - code quality, readability, and maintainability;
+   - minimality and conciseness, including unnecessary agent-generated changes;
+   - documentation accuracy and completeness; and
+   - reviewer coordination, including keeping lifecycle ownership clear and avoiding duplicate or conflicting findings.
+     Use parallel lightweight workers for independent review areas when useful, then reconcile their results before submission.
+7. Produce only grounded findings, then call `review_submit` with the same target and backend (`local: true` for `--local`, otherwise `local: false`). Remote findings remain pending for `publish` or `complete`.
+8. Report the artifact or pending-review state, finding count, gate results, backend, and any launch instruction. Do not complete or merge the review.

package/skills/review/references/workflows/complete.md

@@ -0,0 +1,7 @@
+# complete
+
+1. Parse an optional PR/MR id or URL, `--local`, and exactly one remote action: `--approve`, `--reject`, or `--abandon`. The skill-owned `close` alias follows this workflow. Skill-owned `--bg` dispatch has already occurred; a background child must not redispatch or ask questions. If a remote action is missing in foreground mode, ask the user with `header: "Action"`; all question headers must be 16 characters or fewer. In background mode, stop with a blocker instead of guessing.
+2. Call `review_context` first with the same target and `local: true` when `--local` is present, otherwise `local: false`.
+3. With `--local`, call `review_complete` with `local: true`. It archives the reply overlay to `.diffpi/reviews/<session-slug>.md`, then deletes the exact persisted tuicr session. This is destructive and prevents its comments from appearing in future tuicr sessions.
+4. Without `--local`, map `--approve`, `--reject`, or `--abandon` to the `review_complete` action `approve`, `reject`, or `abandon`. The tool applies the remote lifecycle action but does not merge.
+5. Report the archive path or remote result. Do not call `review_merge`.

package/skills/review/references/workflows/edit.md

@@ -0,0 +1,7 @@
+# edit
+
+1. Parse an optional PR/MR number, URL, or branch target and `--local`. Skill-owned background dispatch has already occurred; a background child follows these steps without redispatch.
+2. Call `review_context` first with the same target and `local: true` when `--local` is present, otherwise `local: false`.
+3. Call `review_edit` with the same target and backend. With `--local`, it opens an existing local tuicr session. Without `--local`, it opens an existing PR/MR in tuicr, including a non-draft PR/MR for continued work on its comments.
+4. If no matching local session or remote PR/MR exists, report the error and direct the user to `new`. Do not create a review, generate findings, publish, complete, or merge.
+5. Report whether tuicr opened in a mux, prepared a Zed task, or returned a command.

package/skills/review/references/workflows/help.md

@@ -0,0 +1,36 @@
+# help
+
+Print the following help text:
+
+```text
+Workflows for PRs and local review. Use:
+
+Create a review and generate findings:
+  /review auto [pr-or-branch] [--local] [--bg]
+
+Create a local review or remote draft PR/MR:
+  /review new [title] [--intent text] [--base branch] [--local] [--bg]
+
+Open an existing remote PR/MR in the system browser (never creates one):
+  /review open [pr-number|pr-url|branch] [--local]
+
+Show review and worktree lifecycle status:
+  /review status [pr-number|pr-url|branch] [--local]
+
+Open an existing review in tuicr without generating findings:
+  /review edit [pr-number|pr-url|branch] [--local] [--bg]
+
+Address review comments:
+  /review address [pr-number|pr-url|branch] [--local] [--bg]
+
+Publish comments and a review status:
+  /review publish [pr-number|pr-url|branch] [--local] [--comment|--approve|--request-changes|--close] [--bg]
+
+Complete a review without merging:
+  /review complete [pr-number|pr-url|branch] [--local|--approve|--reject|--abandon] [--bg]
+
+Merge an approved remote review:
+  /review merge [pr-number|pr-url|branch] [--bg]
+```
+
+`--local` selects the working-tree tuicr backend. Otherwise, a target is a PR/MR number, URL, or branch; no target means the current branch. `--bg` launches a tracked background Orchestrator and leaves the current chat mode unchanged. `new` creates a review. `open` opens an existing remote URL in the system browser, or directs to `new`; with `--local` it creates/opens the local working-tree review. `status` reports local and remote state without requiring a forge or tuicr binary. `edit` only opens an existing local session or remote PR/MR in tuicr. `auto` creates a review, then delegates findings to the reviewer agent. `create` and `draft` alias `new`; `launch` aliases `auto`; `close` aliases `complete`. `publish` publishes remote draft PR/MR review comments and status or promotes local comments. `complete` makes a lifecycle decision without merging, or archives the local overlay and deletes its tuicr session.

package/skills/review/references/workflows/merge.md

@@ -0,0 +1,6 @@
+# merge
+
+1. Parse an optional PR number, URL, or branch. This workflow is remote-only; reject `--local`. The skill has already handled `--bg`; a background child must not redispatch. Call `review_context` first with the target and `local: false`. Do not query the forge through MCP or duplicate merge-readiness checks: `review_merge` uses the GitHub CLI to confirm the PR is open, non-draft, clean, and its checks are settled before merging. Do not require approval from the current user; authors cannot approve their own PRs. GitHub branch protection remains authoritative.
+2. If a conventional squash subject is required and the subject is unclear, use `ask_user_question`.
+3. Call `review_merge` with the chosen subject. Treat its CLI-backed readiness result as authoritative.
+4. Report the merge result.

package/skills/review/references/workflows/new.md

@@ -0,0 +1,19 @@
+# new
+
+## Arguments
+
+```text
+/review new [title] [--intent text] [--base branch] [--local] [--bg]
+```
+
+- `title` is the optional first positional argument; quote a title containing spaces.
+- `--intent` and `--base` each consume the following value. `--local` is a boolean backend flag; the skill handles `--bg` before this workflow.
+- Flags may appear in any order. Reject unknown or duplicate flags, missing flag values, and extra positional arguments. Stating this grammar before the procedure is intentional: an explicit argument contract is the best practice for making workflow behavior predictable and preventing ambiguous execution.
+
+## Workflow
+
+1. Parse the arguments using the grammar above after skill-owned background dispatch. A background child follows these steps directly and must not redispatch. A remote target is the current branch; `new` creates a new review rather than opening an existing one.
+2. Call `review_context` first with `local: true` when `--local` is present, otherwise `local: false`.
+3. Call `review_new` with the parsed title, intent, base branch, and the same explicit backend selection (`local: true` for `--local`, otherwise `local: false`). With `--local`, it creates and opens a local tuicr working-tree review. Without `--local`, it requires a clean, pushed branch, creates a draft PR/MR, and opens that PR/MR in tuicr.
+4. If a local session or remote PR/MR already exists, direct the user to `edit` instead.
+5. Report the PR/MR URL and whether tuicr opened in a mux, prepared a Zed task, or returned a command. Do not generate findings, publish, complete, or merge.

package/skills/review/references/workflows/open.md

@@ -0,0 +1,3 @@
+# open
+
+Call `review_context` first. Without `--local`, call `review_open` to resolve an existing PR/MR and open its URL in the system browser. It must never create a PR/MR; if none exists, direct the user to `/review new`. If browser launch fails, show the plain URL. With `--local`, call `review_new` with `local=true` to preserve local working-tree behavior.

package/skills/review/references/workflows/publish.md

@@ -0,0 +1,8 @@
+# publish
+
+1. Parse an optional PR/MR id or URL, `--local`, and one status: `--comment`, `--approve`, `--request-changes`, or `--close`. The default is comment. The skill has already handled `--bg`; a background child follows these steps without redispatch.
+2. Call `review_context` first with the target and `local: true` so the exact tuicr PR session can be inspected. If no matching local session exists, continue with `local: false` only for forge-native pending review work. If that session exists and has drafts, publish through the local promotion path even when the user omitted `--local`. Use `local: false` only when no matching tuicr session exists or when the target has forge-native pending review work.
+3. The local promotion path reads the exact tuicr session. A local line comment on the same file and line as an existing remote thread is treated as a response, not a new comment. A leading `[REOPEN]`, `[RESOLVE]`, or `[DELETE]` changes the thread state; the marker is removed from the response body. `[DELETE]` deletes the matched remote thread when the forge supports it. Other unpublished line comments become new review comments. The tool follows the stored local overlay path, posts unpublished replies to their remote threads, and then publishes the selected status. Question replies remain open. The tool does not post an overall review comment.
+4. For a forge-native review without a matching tuicr session, call `review_publish` without `local`. Existing pending forge comments already contain provenance, so the tool only publishes them with the selected status and no overall comment.
+5. Comment, approve, and request-changes mark a draft PR/MR ready before publication. Close publishes pending work as comment status and then closes the PR/MR. GitLab rejects request-changes because it has no equivalent review state.
+6. Report promoted comment and reply counts, the public status, and the final PR/MR state. Publishing never merges. If a response cannot be matched by file and line, report it as a new comment rather than silently attaching it to the wrong thread.

package/skills/review/references/workflows/status.md

@@ -0,0 +1,3 @@
+# status
+
+Call `review_context` first, then `review_status` with the same target and local setting. Report branch, worktree counts, local and remote review state, URLs, and remote tuicr state. Status must remain useful when no forge or tuicr binary is installed.

package/templates/plan/PLAN.md

@@ -1,13 +1,10 @@
-<!-- diffpi-plan: {"schemaVersion":1,"id":"{{id}}","revision":0,"branch":"{{branch}}","status":"draft","createdAt":"{{created_at}}","updatedAt":"{{updated_at}}"} -->
-
 # {{title}}
 
 - **Plan ID:** {{id}}
 - **Branch:** {{branch}}
+- **Status:** draft
 - **Issue:** {{issue_id}}
 - **Issue URL:** {{issue_url}}
-- **Status:** draft
-- **Revision:** 0
 
 ## Intent
 
@@ -15,26 +12,35 @@
 
 ## Requirements
 
-<!-- Add requirements. -->
+<!-- Add concrete requirements. -->
 
 ## Design
 
 ### Big Ideas
 
-<!-- Describe the main approach. -->
+<!-- Describe the outcome-oriented design. -->
 
 ### Key API Addition/Updates
 
-<!-- Describe public API changes. -->
+<!-- Describe public or internal contract changes. -->
 
 ### Consequences
 
-<!-- Describe trade-offs and limitations. -->
+<!-- Describe before/after behavior, risks, and trade-offs. -->
+
+## Phases
+
+<!-- Use numbered phases. State prerequisites on the phase only; do not add task dependencies here. -->
+
+### Phase 1: <!-- phase title -->
 
-## Implementation
+- **Phase ID:** <!-- assign a stable phase ID -->
+- **Prerequisites:** <!-- list phase IDs, or “None” -->
+- **Objective:** <!-- state the outcome -->
 
-<!-- Add phases with plan_add_phase. -->
+- [ ] <!-- assign a stable task ID --> Task title
+- [ ] <!-- assign a stable task ID --> Another task title
 
 ## References
 
-<!-- Add references. -->
+<!-- Add repository or external references. -->

package/templates/plan/implementation.md

@@ -1,24 +1,46 @@
-# Phase {{phase_id}}: {{phase_title}}
+# Phase {{phase_ordinal}}: {{phase_title}}
 
-## Summary
+- **Phase ID:** {{phase_id}}
+- **Prerequisites:** {{phase_prerequisites}}
 
-<!-- State the change delivered by this phase in one short paragraph or up to three bullets. -->
+## Objective
 
-## Scope
+{{phase_objective}}
 
-**Objective:** {{phase_objective}}
+## Tasks
+
+<!-- Keep tasks flat and in phase order. Repeat this shape for each task. -->
+
+### 1. <!-- task title -->
+
+- **Task ID:** <!-- stable task ID -->
+- **Steps:**
+  1. <!-- ordered implementation action -->
+  2. <!-- ordered implementation action -->
+- **Verify:**
+  - <!-- command or inspection that proves this task -->
+- **File scopes:** `<!-- exact/path/to/file -->`
+- **Acceptance:** <!-- observable result -->
 
-**Tasks:**
 {{phase_tasks}}
 
-## Files Changed
+## Implementation Constraints
 
-<!-- Show the directory tree. Annotate files added, removed, and updated. -->
+### Libraries and Algorithms
 
-## API Changes
+{{phase_libraries}}
 
-<!-- Document each public app, library, module, class, or function. Include behavior, data contracts, and imperative or declarative APIs. -->
+### Constraints
 
-## Implementation Constraints
+{{phase_constraints}}
+
+## Phase File Tree
+
+<!-- Include exactly one tree. Label every file leaf with [ADD], [MODIFY], [REMOVE], [MOVE from: path], or [VERIFY]. -->
 
-<!-- State required libraries, algorithms, patterns, restrictions, and important implementation details. -->
+```text
+Phase {{phase_ordinal}}/
+├── [MODIFY] <!-- exact/path/to/implementation-file -->
+└── [VERIFY] <!-- exact/path/to/test-or-check -->
+{{phase_file_tree}}
+```

package/dist/commands.d.ts

@@ -1,22 +0,0 @@
-import type { ExtensionAPI, ExtensionContext } from '@earendil-works/pi-coding-agent';
-import { type Runner } from './extensions/cmdtsx';
-import type { ModeController } from './modes';
-import { type PlanWorkflowArguments, type PlanWorkflowName } from './workflow';
-export type WorkflowAgent = 'planner' | 'orchestrator' | 'reviewer' | 'worker';
-export type WorkflowRuntime = {
-    pi: ExtensionAPI;
-    ctx: ExtensionContext;
-    modes: ModeController;
-};
-export type WorkflowInvocation = {
-    [Name in PlanWorkflowName]: {
-        workflow: Name;
-        arguments: PlanWorkflowArguments[Name];
-        agent?: WorkflowAgent;
-        isBackground?: boolean;
-    };
-}[PlanWorkflowName];
-export declare function tokenizeCommandArgs(raw: string): string[];
-export declare function generateCommandHelp<Args, Result>(command: Runner<Args, Result>): Promise<string>;
-export declare function createWorkflowInvoker(runtime: WorkflowRuntime): (invocation: WorkflowInvocation) => Promise<void>;
-//# sourceMappingURL=commands.d.ts.map

package/dist/commands.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"commands.d.ts","sourceRoot":"","sources":["../src/commands.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,YAAY,EAAE,gBAAgB,EAAE,MAAM,iCAAiC,CAAC;AACtF,OAAO,EAAU,KAAK,MAAM,EAAE,MAAM,qBAAqB,CAAC;AAE1D,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,SAAS,CAAC;AAC9C,OAAO,EAAoB,KAAK,qBAAqB,EAAE,KAAK,gBAAgB,EAAE,MAAM,YAAY,CAAC;AAIjG,MAAM,MAAM,aAAa,GAAG,SAAS,GAAG,cAAc,GAAG,UAAU,GAAG,QAAQ,CAAC;AAE/E,MAAM,MAAM,eAAe,GAAG;IAC5B,EAAE,EAAE,YAAY,CAAC;IACjB,GAAG,EAAE,gBAAgB,CAAC;IACtB,KAAK,EAAE,cAAc,CAAC;CACvB,CAAC;AAEF,MAAM,MAAM,kBAAkB,GAAG;KAC9B,IAAI,IAAI,gBAAgB,GAAG;QAC1B,QAAQ,EAAE,IAAI,CAAC;QACf,SAAS,EAAE,qBAAqB,CAAC,IAAI,CAAC,CAAC;QACvC,KAAK,CAAC,EAAE,aAAa,CAAC;QACtB,YAAY,CAAC,EAAE,OAAO,CAAC;KACxB;CACF,CAAC,gBAAgB,CAAC,CAAC;AAIpB,wBAAgB,mBAAmB,CAAC,GAAG,EAAE,MAAM,GAAG,MAAM,EAAE,CAwBzD;AAED,wBAAsB,mBAAmB,CAAC,IAAI,EAAE,MAAM,EAAE,OAAO,EAAE,MAAM,CAAC,IAAI,EAAE,MAAM,CAAC,GAAG,OAAO,CAAC,MAAM,CAAC,CAItG;AAED,wBAAgB,qBAAqB,CAAC,OAAO,EAAE,eAAe,IACvB,YAAY,kBAAkB,KAAG,OAAO,CAAC,IAAI,CAAC,CAwBpF"}

package/dist/extensions/cmdtsx.d.ts

@@ -1,2 +0,0 @@
-export { command, dryRun, flag, oneOf, option, optional, positional, restPositionals, string, subcommands, type Runner, } from 'cmd-ts/dist/esm/index.js';
-//# sourceMappingURL=cmdtsx.d.ts.map

package/dist/extensions/cmdtsx.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"cmdtsx.d.ts","sourceRoot":"","sources":["../../src/extensions/cmdtsx.ts"],"names":[],"mappings":"AAEA,OAAO,EACL,OAAO,EACP,MAAM,EACN,IAAI,EACJ,KAAK,EACL,MAAM,EACN,QAAQ,EACR,UAAU,EACV,eAAe,EACf,MAAM,EACN,WAAW,EACX,KAAK,MAAM,GACZ,MAAM,0BAA0B,CAAC"}

package/dist/tools/plan-schema.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"plan-schema.d.ts","sourceRoot":"","sources":["../../src/tools/plan-schema.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AAMxB,QAAA,MAAM,mBAAmB;;;;;;;kBASd,CAAC;AAEZ,QAAA,MAAM,oBAAoB;;;;;;;;;;;;;kBAQf,CAAC;AAYZ,eAAO,MAAM,2BAA2B;;;;;;;;;;;kBAO7B,CAAC;AAEZ,eAAO,MAAM,wBAAwB;;;;;;;;;kBAW1B,CAAC;AAEZ,eAAO,MAAM,kCAAkC;;;;;;;;;;;;;;;kBAa3C,CAAC;AAEL,eAAO,MAAM,4BAA4B;;;;;;;;;;;;;;;;;;;kBAQ9B,CAAC;AAEZ,eAAO,MAAM,+BAA+B;;;;;;kBAQjC,CAAC;AAEZ,eAAO,MAAM,+BAA+B;;;;;;;;;;;;;;;;;;kBAejC,CAAC;AAEZ,eAAO,MAAM,4BAA4B;;;;kBAE9B,CAAC;AAEZ,eAAO,MAAM,+BAA+B;;;;;;;;;;kBAYjC,CAAC;AAEZ,eAAO,MAAM,4BAA4B;;;;;;;kBAS9B,CAAC;AAEZ,eAAO,MAAM,4BAA4B;;;;;;;;;;;;;;kBAY9B,CAAC;AAEZ,eAAO,MAAM,0BAA0B;;;kBAAkE,CAAC;AAE1G,eAAO,MAAM,kCAAkC;;;;;;;;;kBAOpC,CAAC;AAEZ,eAAO,MAAM,gCAAgC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;kBA+BlC,CAAC;AAEZ,MAAM,MAAM,aAAa,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,mBAAmB,CAAC,CAAC;AAChE,MAAM,MAAM,cAAc,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,oBAAoB,CAAC,CAAC"}