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

package/dist/workflow.d.ts

@@ -1,80 +0,0 @@
-export type PlanWorkflowName = 'init' | 'new' | 'update' | 'annotate' | 'finalize' | 'go' | 'help';
-export type ReviewWorkflowName = 'auto' | 'new' | 'edit' | 'address' | 'publish' | 'complete' | 'merge' | 'help';
-export type PlanWorkflowArguments = {
-    init: {
-        plan: string;
-        branch?: string;
-    };
-    new: {
-        plan: string;
-        branch?: string;
-        background: boolean;
-        prompt?: string;
-    };
-    update: {
-        plan?: string;
-        branch?: string;
-        background: boolean;
-        instructions?: string;
-    };
-    annotate: {
-        plan?: string;
-    };
-    finalize: {
-        plan?: string;
-    };
-    go: {
-        plan: string;
-        commitMode: 'no-commit' | 'commit' | 'push';
-        background: boolean;
-    };
-    help: Record<string, never>;
-};
-export type ReviewWorkflowArguments = {
-    auto: {
-        target?: string;
-        local: boolean;
-        background: boolean;
-    };
-    new: {
-        title?: string;
-        intent?: string;
-        base?: string;
-        local: boolean;
-        background: boolean;
-    };
-    edit: {
-        target?: string;
-        local: boolean;
-        background: boolean;
-    };
-    address: {
-        target?: string;
-        local: boolean;
-        background: boolean;
-    };
-    publish: {
-        target?: string;
-        comment: boolean;
-        approve: boolean;
-        requestChanges: boolean;
-        close: boolean;
-        background: boolean;
-    };
-    complete: {
-        target?: string;
-        local: boolean;
-        approve: boolean;
-        reject: boolean;
-        abandon: boolean;
-        background: boolean;
-    };
-    merge: {
-        target?: string;
-        background: boolean;
-    };
-    help: Record<string, never>;
-};
-export declare function loadPlanWorkflow<Name extends PlanWorkflowName>(name: Name, args: PlanWorkflowArguments[Name]): Promise<string>;
-export declare function loadReviewWorkflow<Name extends ReviewWorkflowName>(name: Name, args: ReviewWorkflowArguments[Name]): Promise<string>;
-//# sourceMappingURL=workflow.d.ts.map

package/dist/workflow.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"workflow.d.ts","sourceRoot":"","sources":["../src/workflow.ts"],"names":[],"mappings":"AAMA,MAAM,MAAM,gBAAgB,GAAG,MAAM,GAAG,KAAK,GAAG,QAAQ,GAAG,UAAU,GAAG,UAAU,GAAG,IAAI,GAAG,MAAM,CAAC;AACnG,MAAM,MAAM,kBAAkB,GAAG,MAAM,GAAG,KAAK,GAAG,MAAM,GAAG,SAAS,GAAG,SAAS,GAAG,UAAU,GAAG,OAAO,GAAG,MAAM,CAAC;AAEjH,MAAM,MAAM,qBAAqB,GAAG;IAClC,IAAI,EAAE;QAAE,IAAI,EAAE,MAAM,CAAC;QAAC,MAAM,CAAC,EAAE,MAAM,CAAA;KAAE,CAAC;IACxC,GAAG,EAAE;QAAE,IAAI,EAAE,MAAM,CAAC;QAAC,MAAM,CAAC,EAAE,MAAM,CAAC;QAAC,UAAU,EAAE,OAAO,CAAC;QAAC,MAAM,CAAC,EAAE,MAAM,CAAA;KAAE,CAAC;IAC7E,MAAM,EAAE;QAAE,IAAI,CAAC,EAAE,MAAM,CAAC;QAAC,MAAM,CAAC,EAAE,MAAM,CAAC;QAAC,UAAU,EAAE,OAAO,CAAC;QAAC,YAAY,CAAC,EAAE,MAAM,CAAA;KAAE,CAAC;IACvF,QAAQ,EAAE;QAAE,IAAI,CAAC,EAAE,MAAM,CAAA;KAAE,CAAC;IAC5B,QAAQ,EAAE;QAAE,IAAI,CAAC,EAAE,MAAM,CAAA;KAAE,CAAC;IAC5B,EAAE,EAAE;QAAE,IAAI,EAAE,MAAM,CAAC;QAAC,UAAU,EAAE,WAAW,GAAG,QAAQ,GAAG,MAAM,CAAC;QAAC,UAAU,EAAE,OAAO,CAAA;KAAE,CAAC;IACvF,IAAI,EAAE,MAAM,CAAC,MAAM,EAAE,KAAK,CAAC,CAAC;CAC7B,CAAC;AAEF,MAAM,MAAM,uBAAuB,GAAG;IACpC,IAAI,EAAE;QAAE,MAAM,CAAC,EAAE,MAAM,CAAC;QAAC,KAAK,EAAE,OAAO,CAAC;QAAC,UAAU,EAAE,OAAO,CAAA;KAAE,CAAC;IAC/D,GAAG,EAAE;QAAE,KAAK,CAAC,EAAE,MAAM,CAAC;QAAC,MAAM,CAAC,EAAE,MAAM,CAAC;QAAC,IAAI,CAAC,EAAE,MAAM,CAAC;QAAC,KAAK,EAAE,OAAO,CAAC;QAAC,UAAU,EAAE,OAAO,CAAA;KAAE,CAAC;IAC7F,IAAI,EAAE;QAAE,MAAM,CAAC,EAAE,MAAM,CAAC;QAAC,KAAK,EAAE,OAAO,CAAC;QAAC,UAAU,EAAE,OAAO,CAAA;KAAE,CAAC;IAC/D,OAAO,EAAE;QAAE,MAAM,CAAC,EAAE,MAAM,CAAC;QAAC,KAAK,EAAE,OAAO,CAAC;QAAC,UAAU,EAAE,OAAO,CAAA;KAAE,CAAC;IAClE,OAAO,EAAE;QACP,MAAM,CAAC,EAAE,MAAM,CAAC;QAChB,OAAO,EAAE,OAAO,CAAC;QACjB,OAAO,EAAE,OAAO,CAAC;QACjB,cAAc,EAAE,OAAO,CAAC;QACxB,KAAK,EAAE,OAAO,CAAC;QACf,UAAU,EAAE,OAAO,CAAC;KACrB,CAAC;IACF,QAAQ,EAAE;QACR,MAAM,CAAC,EAAE,MAAM,CAAC;QAChB,KAAK,EAAE,OAAO,CAAC;QACf,OAAO,EAAE,OAAO,CAAC;QACjB,MAAM,EAAE,OAAO,CAAC;QAChB,OAAO,EAAE,OAAO,CAAC;QACjB,UAAU,EAAE,OAAO,CAAC;KACrB,CAAC;IACF,KAAK,EAAE;QAAE,MAAM,CAAC,EAAE,MAAM,CAAC;QAAC,UAAU,EAAE,OAAO,CAAA;KAAE,CAAC;IAChD,IAAI,EAAE,MAAM,CAAC,MAAM,EAAE,KAAK,CAAC,CAAC;CAC7B,CAAC;AAIF,wBAAgB,gBAAgB,CAAC,IAAI,SAAS,gBAAgB,EAC5D,IAAI,EAAE,IAAI,EACV,IAAI,EAAE,qBAAqB,CAAC,IAAI,CAAC,GAChC,OAAO,CAAC,MAAM,CAAC,CAEjB;AAED,wBAAgB,kBAAkB,CAAC,IAAI,SAAS,kBAAkB,EAChE,IAAI,EAAE,IAAI,EACV,IAAI,EAAE,uBAAuB,CAAC,IAAI,CAAC,GAClC,OAAO,CAAC,MAAM,CAAC,CAEjB"}

package/workflows/plan/annotate.md

@@ -1,13 +0,0 @@
-# annotate
-
-## Arguments
-
-- **Invocation:** `/plan annotate [short-slug]`
-- `[short-slug]` (optional): Plan to annotate. Omit it only when context resolves exactly one plan.
-
-## Instructions
-
-1. Call `plan_context` and infer planId from the provided short slug/conversation context. Fall back to looking at available active plan candidates, and ask user which to annotate listing available options.
-2. Call `plan_annotate`; it uses `tuicr --file .diffpi/plan/{planId}`, never `-p` or `--path`.
-3. Report the selected plan, launch result, and copyable fallback command. Closing tuicr saves one immutable plan review for the current plan revision.
-4. Tell the user to run `/plan update <plan-id>` after closing tuicr.

package/workflows/plan/finalize.md

@@ -1,15 +0,0 @@
-# finalize
-
-## Arguments
-
-- **Invocation:** `/plan finalize [short-slug]`
-- `[short-slug]` (optional): Plan to validate and mark ready. Omit it only when context resolves exactly one plan.
-
-## Instructions
-
-1. Call `plan_context` and use the current persisted plan, including changes authored through chat.
-2. Call `plan_review` once. If a review exists for the current plan revision, apply its feedback using the update workflow's mutation rules. If no review exists, continue directly.
-3. Call `plan_validate` with `strict: true`. Address validation issues and stop on unresolved errors or Design above 800 words.
-4. Mark the draft ready with `plan_update_status`.
-5. Use one `ask_user_question` call to choose the next action. Choices are foreground execution, background execution, execute later, or continue planning. When execution is selected, also ask for `no-commit`, `commit`, or `push` mode.
-6. Call `diffpi_modes_unset` before returning so finalization exits to the default inline mode. For execution, return the exact `/plan go <short-slug> --mode <mode>` command, adding `--bg` for background execution. Do not call `plan_start_execution`; `/plan go` routes execution to Orchestrator.

package/workflows/plan/go.md

@@ -1,20 +0,0 @@
-# go
-
-## Arguments
-
-- **Invocation:** `/plan go <short-slug> [--mode <no-commit|commit|push>] [--bg]`
-- `<short-slug>` (required): Plan to execute.
-- `--mode no-commit` (optional, default): Execute without creating commits.
-- `--mode commit` (optional): Create one local commit after each completed phase. Do not push or monitor remote CI.
-- `--mode push` (optional): Create and push one commit after each completed phase, then monitor remote CI before completion.
-- `--bg` (optional): Launch the execution Orchestrator in the background and preserve the current foreground mode.
-
-## Instructions
-
-1. Call `plan_context` with the supplied slug.
-2. Read the requested commit mode from `--mode`. Use `no-commit` when the flag is omitted. Do not ask the user to select a commit mode.
-3. Reject values other than `no-commit`, `commit`, or `push`. The command parser normally performs this validation before invoking the workflow.
-4. The command has already selected the foreground Orchestrator or launched the background Orchestrator. Continue as the current Orchestrator and launch implementation Workers as needed.
-5. Call `plan_start_execution` with the selected commit mode. This tool initializes durable execution state and returns the execution packet. It does not select a mode, send another turn, or launch an agent.
-6. In `no-commit` mode, do not create or push commits. In `commit` mode, create one local commit after each phase passes its gates, but do not push or monitor remote CI. In `push` mode, commit and push each phase, record pending CI, and launch a bounded background Worker to call `watch_ci` for the exact commit and then `plan_record_ci` for the phase while the next phase executes. Collect that monitor before the next push and collect all monitors before completion; failed or timed-out CI blocks execution.
-7. For foreground execution, call `diffpi_modes_unset` after the plan is completed. Background execution must not change the foreground mode. Report the execution ID and selected commit mode.

package/workflows/plan/help.md

@@ -1,20 +0,0 @@
-# help
-
-## Arguments
-
-- **Invocation:** `/plan help`
-- This workflow accepts no arguments.
-
-## Instructions
-
-Show these commands:
-
-- `/plan init <short-slug> [--branch <name>]` creates a phase-less draft.
-- `/plan new <short-slug> [--branch <name>] [--bg] [prompt...]` creates and populates a plan.
-- `/plan update [short-slug] [--branch <name>] [--bg] [instructions...]` applies the current plan review before other instructions.
-- `/plan annotate [short-slug]` reviews the plan with tuicr and saves an immutable review dump when tuicr closes.
-- `/plan finalize [short-slug]` validates and marks a plan ready.
-- `/plan go <short-slug> [--mode <no-commit|commit|push>] [--bg]` starts execution.
-- `/plan help` shows this reference.
-
-`--branch` records or filters a branch. It does not create or switch branches. Background workflows do not ask questions.

package/workflows/plan/init.md

@@ -1,13 +0,0 @@
-# init
-
-## Arguments
-
-- **Invocation:** `/plan init <short-slug> [--branch <name>]`
-- `<short-slug>` (required): Short, stable name used to identify the plan.
-- `--branch <name>` (optional): Branch metadata to record on the plan. It does not create or switch branches.
-
-## Instructions
-
-1. Call `plan_init` with the supplied slug and branch metadata. Include explicit intent, title and issue tracker id/url when available. The tool creates only `PLAN.md`.
-2. Open `PLAN.md` in supported IDEs/terminals/multiplexers in a new or available chat-adjacent tab. Skip to next step if IDE/terminal/mux is unsupported.
-3. Report the plan ID and path (clickable link so users can click to open in their environment). Explain that `/plan annotate` records a plan review and `/plan update` applies that plan review or direct chat instructions until `/plan finalize` is called.

package/workflows/plan/new.md

@@ -1,20 +0,0 @@
-# new
-
-## Arguments
-
-- **Invocation:** `/plan new <short-slug> [--branch <name>] [--bg] [prompt...]`
-- `<short-slug>` (required): Short, stable name used to identify the plan.
-- `--branch <name>` (optional): Branch metadata to record on the plan. It does not create or switch branches.
-- `--bg` (optional): Whether this is a background agent, or running in chat thread
-- `[prompt...]` (optional): Natural-language scope, requirements, or constraints for the plan.
-
-## Instructions
-
-1. Call `plan_context`, then `plan_init` if the supplied plan does not exist.
-2. In foreground mode, if `prompt` is not provided, ask the user "What would you like to plan?". If its clear from recent chat or branch name what is going to be worked on, provide options for the user to choose from along with a free text entry option. Use `ask_user_question` only for decisions that materially change scope.
-3. In background mode, never ask; record safe assumptions and stop with a blocker if ambiguity cannot be resolved.
-4. Once goal is understood, ground the plan in repository files and the supplied prompt if chat has not established this context..
-5. Use `plan_update_overview`, `plan_add_phase`, and `plan_update_phase` to create the plan. Use the planning tools to enforce the declared requirements, references, phase dependencies, file scopes, steps, and acceptance criteria; do not write PLAN.md by hand when a tool can make the change.
-6. Create one implementation file per phase at `.diffpi/plan/<plan-id>/implementation/phase-<phase-id>.md`. Fill in the implementation template with the phase summary, file tree, public APIs and data contracts, required libraries or algorithms, and implementation constraints. Keep each phase focused on one or two modules or libraries, preferably one. The only exception is when scaffolding structures for new projects/modules/libraries/etc.
-7. Keep Design near 300 words and call `plan_validate` in the background.
-8. After validation, if in foreground mode, notify the user that you will continue updating the plan with continued conversation. In background mode, finish planning and notify the user that they can explicitly call `/plan update` if they want to make updates and re-enter plan mode. Also notify them to use `/plan finalize` when ready for implementation.

package/workflows/plan/update.md

@@ -1,18 +0,0 @@
-# update
-
-## Arguments
-
-- **Invocation:** `/plan update [short-slug] [--branch <name>] [--bg] [instructions...]`
-- `[short-slug]` (optional): Plan to update. Omit it only when exactly one plan candidate is selected.
-- `--branch <name>` (optional): Branch metadata used to select or update the plan. It does not create or switch branches.
-- `--bg` (optional): Whether workflow is running in a bacground agent or main chat thread.
-- `[instructions...]` (optional): Natural-language changes to apply after the current plan review.
-
-## Instructions
-
-1. Call `plan_context` with the supplied slug and branch metadata. Infer slug based on recency/chat if not provided.
-2. Call `plan_review` before interpreting the supplied instructions. It returns the latest immutable tuicr review dump for the current plan revision. If no review exists, continue with the supplied instructions alone.
-3. Apply the review feedback and then the explicit instructions through `plan_update_overview`, `plan_add_phase`, `plan_remove_phase`, or `plan_update_phase`. Updating the plan advances its revision, so the review dump will not be applied again.
-4. In foreground mode, use `ask_user_question` for requests which need further discussion. In background mode, do not ask; address with best effort.
-5. Call `plan_validate` and address any issues.
-6. Tell the user they can continue updating the plan through chat, run `/plan annotate` for another review, finalize with `/plan finalize`, or proceed to implementation.

package/workflows/review/address.md

@@ -1,8 +0,0 @@
-# address
-
-1. Read `Arguments.target` and `Arguments.local`.
-2. Call `review_context`.
-3. In local mode, call `review_dump`. This saves one immutable review revision and removes the completed tuicr session. Apply its feedback to the working tree, run relevant checks, then call `review_launch_ui` with `local: true` to begin the next revision. Local reviews have no replies or resolution state.
-4. In remote mode, call `review_comments`. Classify every thread and apply only justified changes. Run relevant checks and commit fixes through `/git commit --no-push` when code changes.
-5. For remote threads, call `review_respond` with a concise outcome. Leave the thread open unless the user explicitly requested resolution.
-6. Report changed, answered, skipped, and remaining items. Do not publish, complete, or merge.

package/workflows/review/auto.md

@@ -1,8 +0,0 @@
-# auto
-
-1. Read `Arguments.target` and `Arguments.local`.
-2. Call `review_context` with the selected target and backend.
-3. Create or open the review with `review_new` or `review_edit`.
-4. Run `review_gates`, then call `review_diff` and review only that change.
-5. Produce grounded findings and call `review_submit`. Local findings stay in tuicr. Remote findings stay pending until `/review publish`.
-6. Report the backend, findings, gate results, artifact, and launch instruction. Do not publish, complete, or merge.

package/workflows/review/complete.md

@@ -1,7 +0,0 @@
-# complete
-
-1. Read the typed target, local mode, and lifecycle action from `Arguments`.
-2. Call `review_context`.
-3. In local mode, call `review_dump` to save the final immutable revision and remove the completed tuicr session.
-4. In remote mode, ask for a missing action, then call `review_complete` with `approve`, `reject`, or `abandon`.
-5. Report the dump path or remote result. Do not merge.

package/workflows/review/edit.md

@@ -1,7 +0,0 @@
-# edit
-
-1. Read `Arguments.target` and `Arguments.local`.
-2. Call `review_context`, then `review_edit`.
-3. Local mode opens the current working-tree review revision. Remote mode opens the existing PR/MR in tuicr.
-4. If no review exists, direct the user to `/review new`.
-5. Report the launch result. Do not create findings or change lifecycle state.

package/workflows/review/help.md

@@ -1,14 +0,0 @@
-# help
-
-Show these commands:
-
-- `/review auto [target] [--local] [--bg]` generates findings.
-- `/review new [title] [--intent text] [--base branch] [--local] [--bg]` starts a review.
-- `/review edit [target] [--local] [--bg]` opens an existing review.
-- `/review address [target] [--local] [--bg]` applies feedback. Local mode dumps one revision and starts the next.
-- `/review publish [target] [--comment|--approve|--request-changes|--close] [--bg]` publishes remote review work.
-- `/review complete [target] [--local|--approve|--reject|--abandon] [--bg]` finishes without merging.
-- `/review merge [target] [--bg]` merges a green remote review.
-- `/review help` shows this reference.
-
-`--local` selects the working-tree tuicr flow. Local reviews are immutable revision dumps with no replies, resolution state, or remote promotion. Remote reviews use GitHub or GitLab comments and lifecycle operations directly. `--bg` launches an Orchestrator without changing the foreground mode.

package/workflows/review/merge.md

@@ -1,6 +0,0 @@
-# merge
-
-1. Local mode is not accepted; only remote reviews can merge.
-2. Call `review_context` and confirm the PR is open, non-draft, mergeable, and green.
-3. Ask for a conventional squash subject only when it cannot be derived.
-4. Call `review_merge` and report the resulting merge.

package/workflows/review/new.md

@@ -1,7 +0,0 @@
-# new
-
-1. Read `Arguments.title`, `Arguments.intent`, `Arguments.base`, and `Arguments.local`.
-2. Call `review_context` with the selected backend.
-3. Call `review_new`. Local mode opens a working-tree review in tuicr. Remote mode creates a draft PR/MR from a clean pushed branch and opens it in tuicr.
-4. If the target exists, direct the user to `/review edit` instead.
-5. Report the created target and launch instruction. Do not generate findings or publish it.

package/workflows/review/publish.md

@@ -1,6 +0,0 @@
-# publish
-
-1. Read the typed target and status flags from `Arguments`. The default is comment.
-2. Local mode is not accepted; local reviews use immutable revision dumps and have no publish step.
-3. Call `review_context`, then `review_publish` with the selected status.
-4. Report the public review status and final PR/MR state. Publishing never merges.