@narumitw/pi-plan-mode 0.57.0 → 0.57.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +0 -14
- package/dist/chunks/{chunk-YUFPCQVG.js → chunk-57OBPS7P.js} +381 -515
- package/dist/chunks/chunk-57OBPS7P.js.map +7 -0
- package/dist/chunks/{interactive-ui-M3GEZN4M.js → interactive-ui-N2ZKBVNE.js} +84 -183
- package/dist/chunks/interactive-ui-N2ZKBVNE.js.map +7 -0
- package/dist/index.ts +17 -185
- package/dist/index.ts.map +3 -3
- package/docs/command-workflows.md +1 -5
- package/docs/settings.md +1 -23
- package/package.json +1 -1
- package/src/fresh-implementation.ts +3 -46
- package/src/plan-action-controller.ts +10 -26
- package/src/plan-action-menus.ts +104 -65
- package/src/plan-mode.ts +6 -106
- package/src/saved-plan-menu.ts +7 -35
- package/src/settings-menu.ts +1 -35
- package/src/settings.ts +1 -35
- package/dist/chunks/chunk-YUFPCQVG.js.map +0 -7
- package/dist/chunks/interactive-ui-M3GEZN4M.js.map +0 -7
- package/src/fresh-implementation-preferences.ts +0 -102
- package/src/implementation-options.ts +0 -127
- package/src/implementation-preferences.ts +0 -145
package/README.md
CHANGED
|
@@ -11,7 +11,6 @@ Use a Codex-like `/plan` mode to explore a codebase, resolve important questions
|
|
|
11
11
|
- Uses structured questions for important ambiguity and explicit completion for a decision-ready plan.
|
|
12
12
|
- Reviews the complete plan before implementation, export, save, further planning, or discard.
|
|
13
13
|
- Implements in the planning session or a fresh linked session with the approved plan.
|
|
14
|
-
- Selects an implementation model and thinking level through saved defaults or one-menu overrides, without switching back automatically.
|
|
15
14
|
- Restores Plan state and one saved plan across resume and compaction.
|
|
16
15
|
- Configures the Plan tool allowlist, reviewed shell commands, user-trusted subcommands, export path, plan reinjection, shortcut, and thinking level.
|
|
17
16
|
- Publishes statusline state and cooperates anonymously with Workflow Mutex Protocol v1 participants.
|
|
@@ -151,14 +150,6 @@ Empty, malformed, unclosed, or multiple legacy blocks keep Plan mode active and
|
|
|
151
150
|
|
|
152
151
|
After completion, `/plan` opens the ready actions when interactive UI is available.
|
|
153
152
|
The same flat menu shows **Implement here** and **Start fresh and implement**, explains which conversation context each choice uses, and previews the selected **Plan reinjection** policy.
|
|
154
|
-
**Implementation options…** stages model and thinking choices for either action in that menu; `/plan implement` uses saved defaults.
|
|
155
|
-
Choices take effect only when implementation starts and do not change Pi's global defaults.
|
|
156
|
-
After kickoff, run settlement, user abort, and active-plan clearing do not restore the previous model or thinking; subsequent manual choices remain yours.
|
|
157
|
-
Implementation preferences are characterized on Pi 0.85.0; use that release or newer for this feature.
|
|
158
|
-
See [implementation preferences](./docs/settings.md#implementation-model-and-thinking) for inheritance and failure behavior.
|
|
159
|
-
|
|
160
|
-
Selecting another provider with **Implement here** sends the retained planning conversation to that provider.
|
|
161
|
-
Fresh implementation transfers only the approved plan plus the destination's normal resources.
|
|
162
153
|
**Implement here**—and the compatibility route `/plan implement`—appends the Normal contract, lifts the Plan runtime policy, captures the reinjection setting, and starts implementation in the current session with its complete planning conversation and tool calls.
|
|
163
154
|
**Start fresh and implement** waits for the source session to become idle, verifies the selected model and authentication, creates a new session linked to the persisted source as its parent, and transfers the exact approved plan without copying planning messages, tool results, or compaction/branch summaries.
|
|
164
155
|
The destination still loads its normal `AGENTS.md`, skills, project resources, and extensions.
|
|
@@ -251,10 +242,6 @@ Only the latest active Plan contract authorizes the helpers; inactive or stale c
|
|
|
251
242
|
Plan mode does not widen a restrictive active-tool policy; start or restore fails when a required helper is unavailable.
|
|
252
243
|
Stable schemas preserve a cache-eligible prefix but cannot guarantee a hit because provider serialization, cache lifetime, minimum prefix size, implementation details, and session affinity remain external.
|
|
253
244
|
|
|
254
|
-
An explicit implementation model or thinking change is an intentional provider/cache boundary at handoff, not an ordinary-turn context rewrite.
|
|
255
|
-
Preferences and fresh-session acknowledgements are non-model state; they do not add tool schemas or leading prompt instructions.
|
|
256
|
-
Subsequent turns retain the existing append-only context behavior.
|
|
257
|
-
|
|
258
245
|
The default `thinkingLevel: "inherit"` avoids a Plan-specific reasoning-parameter change.
|
|
259
246
|
A fixed Plan thinking level remains supported, but changing reasoning parameters can prevent provider-side state reuse even when prompts and tool schemas stay stable.
|
|
260
247
|
|
|
@@ -307,7 +294,6 @@ The optional file is read at session start and watched for changes; only an expl
|
|
|
307
294
|
```
|
|
308
295
|
|
|
309
296
|
By default, Plan mode inherits thinking, allows active safe built-ins, exports to `PLAN.md`, and relies on ordinary conversation history after implementation starts.
|
|
310
|
-
Implementation model and thinking defaults are optional Settings rows; unset values keep existing behavior, including normal restoration of Plan-specific thinking.
|
|
311
297
|
The shortcut is disabled unless configured.
|
|
312
298
|
Settings saves apply to later workflows; an active implementation keeps its captured reinjection policy.
|
|
313
299
|
The export destination affects the next export immediately.
|