# @signalridge/pi-goal ## 1.4.2 ### Patch Changes - d9219d4: Correct shipped documentation that contradicted the code or the manifest. - `pi-subagents`: the summary line still advertised protocol-v3 spawning while the feature list and the managed-spawn section described v4. - `pi-worktree`: the workspace-switching section named `/tree`; the registered command is `/worktree`. - `pi-workflows`: removed an orphaned sentence fragment left behind by an edit to the saved-workflow paragraph. - `pi-plan-mode`, `pi-goal`, `pi-usage-extension`: the stated Pi floor (`0.80.6`, `0.42.4+`) contradicted the declared `^0.84.0` peer range, which resolves to `0.84.x`. `pi-usage-extension` also carried a "Last updated" stamp from a version that predates the workspace baseline. - `pi-welcome`: the example card was a real session capture. It is now a generic sample, and Install moved above the configuration sections instead of sitting below them. - 1f586f8: Expand Pi peer support to `^0.84.0 || ^0.85.0`, retaining 0.84 compatibility while admitting 0.85 releases. The previous zero-major caret range excluded Pi 0.85.1. Update existing Pi development dependency pins to 0.85.1. - d9219d4: Converge every README on one house style: plain sentence-case headings, no decorative emoji. Ten packages carried an emoji heading scheme inherited from their upstream forks while the other nineteen used plain headings, so the same monorepo rendered as two unrelated projects on npmjs.com. Headings are now emoji-free and titles are sentence case. Also removes the `Keywords` section from those ten. It duplicated each package's `package.json` `keywords` field, which is what npm actually indexes, and no plain-style README carried one. `Installation` is now `Install` everywhere. Headings that were Title Case are sentence case too, so one convention now covers the whole monorepo. Existing in-page anchor links are unaffected: GitHub lowercases heading slugs already. Documentation only — no runtime change. - 1f586f8: Keep goal iteration and continuation numbering correct when Pi compacts between tool results and the next response within one run. Preserve existing response limits and manual/post-run compaction handling. Capture subagent invocation results from finalized assistant events with bounded message retention so compaction cannot hide a final error or mix in historical output. Recognize explicitly selected PowerShell when the host provides it, without requiring its export on older Pi versions or expanding default wildcard tools. Use real session contexts for workflow replay and live TUI progress, release widget bindings on shutdown, and allow foreground checkpoint dialogs in RPC mode while retaining print-mode defaults. Cancel unanswered dialogs with their owning execution on tool abort, pause, stop, disposal, or fatal failure without journaling cancelled answers. - Updated dependencies [1f586f8] - Updated dependencies [1f586f8] - Updated dependencies [1f586f8] - Updated dependencies [1f586f8] - @signalridge/pi-ui@1.3.1 ## 1.4.1 ### Patch Changes - c1b1741: Durability and containment fixes found in a repository-wide scan. `pi-gpt-fast` rewrote pi's own global `settings.json` with a plain `writeFileSync`. That file is shared with pi and every other extension, and this one is the only writer of it; a torn write would have left the user with no pi configuration at all rather than just no gpt-fast setting. It now writes a temp file and renames, matching every other settings writer in the repository. `pi-goal` gets the same treatment for its cross-project goal state file, which its own settings module already did. `pi-ralph-wiggum` resolved `/ralph start ` straight against the session cwd, so `../../notes.md` would create directories and a file outside the project the user opened — silently, before the loop started. This extension drives long unattended loops, so that command is as likely to come from a model as from a person. Task-file paths are now required to stay inside the workspace, on the command, on the `ralph_start` tool, and on the paths read back out of persisted state, so a state file written earlier or edited by hand cannot pull a file in from outside either. The containment test canonicalizes both sides before comparing, because a purely lexical one is defeated by a symlink: every segment of `linked/plan.md` reads as inside the workspace when `linked` is a door out of it. `realpathSync` throws on a path that does not exist yet — the ordinary case, since `start` is usually creating the file — so it resolves the deepest existing ancestor and re-attaches the not-yet-created suffix, which cannot itself be a link. The traversal test matches a `..` segment rather than a `..` prefix; the prefix form also rejected `..notes.md`, an ordinary filename sitting in the workspace. Every remaining bare `catch {}` now says why the error is safe to drop, matching the convention the rest of the repository already follows. ## 1.4.0 ### Minor Changes - 07350d4: Standardize extension-owned popup surfaces with an idempotent Pi-style border adapter. Native Pi dialogs retain their built-in framing and RPC behavior; custom menus and overlays gain consistent border rules. ### Patch Changes - Updated dependencies [07350d4] - @signalridge/pi-ui@1.3.0 ## 1.3.1 ### Patch Changes - f714ea0: Publish the package versions already prepared by the previous release transition after its first publish attempt was blocked before npm publication. ## 1.3.0 ### Minor Changes - b6cf242: New `goal_wait` tool: a goal that depends on something outside the session — CI finishing, a review landing, a reply arriving — can now say so. Without it the model either burns continuation turns re-checking or reports a blocker that is not one; `goal_wait` records *why* it is waiting, pauses the goal, and either waits for the next real message or wakes itself on a deadline. It reuses the existing `paused` state rather than adding a fourth one, so every resume path, restore path, and status surface already handles it, and the deadline resumes through the same code as `/goal resume` (tool-policy preparation, recovery clearing, prompt delivery) rather than a second, lesser resume. Requests below 10s are clamped rather than refused — the model's intent ("wait, then check") is right even when its number makes a polling loop — and the reply says when a number was raised. The wake-up re-checks at fire time that the goal is still the paused, active one, and a generation counter keeps an already-in-flight callback from waking a goal that was cleared microseconds earlier. `toolVisibility` now defaults to `"after-first-goal"` instead of `"always"`. `goal_complete` and `goal_blocked` are meaningless without an active goal, so in a session that never runs `/goal` — the overwhelming majority — their definitions and prompt guidelines were pure context cost paid on every request. They are now withheld until the first accepted `/goal` activation, and a session that restores an unfinished goal reveals them at startup as before. Nothing else changes: the `"after-first-goal"` machinery is unchanged, missing and invalid settings both land on the new default (an unreadable settings file must not be a way to get the always-on behaviour), and `"always"` remains available for anyone who wants a tool schema that is identical from session startup. Reload Pi after changing the setting, as before. ### Patch Changes - b6cf242: Peer dependency ranges now name the versions actually validated against, so an untested host combination fails at install time instead of silently at runtime: `@earendil-works/pi-coding-agent`, `pi-ai`, `pi-tui`, and `pi-agent-core` move from `"*"` to `^0.84.0`, and `typebox` from `"*"` to `^1.3.11`. Shared dependencies now carry ONE declared range across every package that uses them, and `bun run check:shared-deps` keeps it that way. `@narumitw/pi-tui-kit` was declared at three disjoint floors — `^0.54.0`, `^0.51.0`, and `^0.49.1` across nine packages — and the lockfile duly resolved three copies (0.54.0, 0.51.0, 0.49.3) installed side by side. For a shared rendering surface drawing into one terminal inside one host process, that means a theme rendering one way in one extension and another way in the next, with nothing failing at install to say so. All nine now declare `^0.54.0` and the install resolves a single copy. `@sinclair/typebox` likewise converges on `^0.34.50`. The new check covers `dependencies` and `peerDependencies` and compares range strings rather than their semantics: two ranges that merely overlap are still a finding, because the goal is one intentional answer per dependency rather than an accidental intersection. `devDependencies` are deliberately out of scope — a build tool is not a shared surface, and `pi-subagents` intentionally carries its own toolchain. `docs/package-boundaries.md` documents the Kit as a shared surface for the first time. ## 1.0.0 ### Major Changes - Adopt a unified 1.0.0 across every published package. The version numbers no longer track their upstream forks individually; from this release each package is versioned on its own merit against the Signalridge line, and 1.0.0 is the shared starting point. Packages whose behavior changed in this release document that change in their own changeset entries; the remainder are re-released unchanged so the whole set shares one baseline. ## 0.49.7 ### Patch Changes - fa9c938: Reduce idle startup imports by loading Goal presentation, Chat networking and UI, and Sync operation-specific modules only when their routes require them. ## 0.49.6 ### Patch Changes - 6f98395: Sanitize terminal-rendered Goal text, bound terminal-tool inputs and outputs, report malformed commands in headless modes, and keep runtime smoke coverage on public Pi APIs.