# Changelog All notable changes to pi-67 are documented here. The format is based on Keep a Changelog, and this project uses semantic versioning for the pi-67 distribution itself. Pi package dependency versions are managed separately in `package.json`. ## [Unreleased] ## [0.15.8] - 2026-07-30 ### Added - Added workspace-scoped operation locks, pre-mutation snapshots, atomic file transactions, and structured operation reports for install, update, migration, rollback, extension restore, and theme changes. Interrupted or failed mutations now preserve a deterministic recovery point instead of leaving partially updated workspace state. - Added executable Draft 2020-12 JSON Schema contracts for distro manifests, update plans, and publish reports, together with release-contract, content, workflow, transaction, and dependency-closure tests in every CI platform lane. - Added backup provenance and workspace identity checks, explicit opt-ins for cross-workspace or unverifiable legacy restores, and deterministic archive and prune result schemas. ### Changed - Reduced `install.sh` to the immutable manager bootstrap and compatibility boundary. Existing matching release pointers resume through the manager, while workspace mutation policy is now implemented once in the CLI rather than duplicated across the shell installer and manager commands. - Declared a single repository-local Pi `0.80.6` package as a development-only TypeScript host, pinned Ajv and TypeScript as direct development tools, and added a dependency-closure gate that rejects duplicate or nested Pi runtimes without inspecting or changing the global Pi installation. - Upgraded `pi-simplify` to `0.2.3`, refreshed the lockfile, and made runtime dependency installation use the supported peer-omission policy on macOS, Linux, and Windows. - Reworked the bundled scraping templates to expose checkpoint corruption, page-change timeouts, empty-page retries, persistence failures, and bounded batch completion instead of silently continuing with ambiguous state. - Corrected bundled Lark reference and slide-template contracts and removed the obsolete MCP optimization proposal whose implementation guidance no longer matched the distributed runtime. ### Fixed - Allowed CLI error paths to drain pending HTTP, stream, and libuv handles before exiting, preventing Windows native aborts after Hy-Memory requests while preserving the documented non-zero exit codes. - Made Hy-Memory HTTP saturation return a complete bounded 503 response after consuming the request body, instead of resetting Windows clients when a handler slot is unavailable. - Made clean release-artifact validation rebuild its repository development dependency closure from the committed lockfile, so schema checks no longer depend on host-global Ajv availability. - Made real upstream Pi integration probes invoke the locked CLI module directly, so npm 10 installations using `--omit=peer` remain testable even when npm omits the package's `.bin/pi` link. - Normalized generated-workflow contract fixtures before matching multiline behavior, keeping the same assertions valid in Windows CRLF checkouts. - Made Hy-Memory service ownership single-writer and observable across the manager and Python service, bounded active/dead-letter outbox count and bytes, retained deterministic retry ordering, pruned expired dead letters, propagated request deadlines, capped streamed HTTP responses, and returned non-zero CLI status when flush or digest reports `success=false`. - Hardened `vision_read` so local files are realpath-confined to the active workspace, symlink escapes are rejected, declared MIME is checked against image magic, file/data/provider response sizes are bounded, and host cancellation aborts I/O without starting a hidden fallback request. - Made release publication require the exact clean `main` commit, a successful push CI run for that SHA, valid schemas and artifacts, and an unpublished npm version. Git branch, tracking-ref, live-remote, and registry failures now remain distinct and machine-readable. - Fixed managed-extension install/restore, immutable release activation, and settings migration so concurrent writers, command failures, or partial filesystem changes cannot be reported as successful. ### Security - Narrowed npm publish workflow permissions, bounded release jobs, prevented republishing immutable versions, and added input/content boundary tests for filesystem paths, provider responses, generated JSON, and vendored assets. ## [0.15.7] - 2026-07-29 ### Fixed - Declared and installed `iconv-lite@0.7.3` as a manager-owned runtime dependency of the `pi-smart-fetch@0.3.12` charset compatibility patch, so a fresh Pi workspace no longer depends on a source-checkout npm tree and the patched extension can resolve its decoder on macOS and Windows. - Added a packed-manager fresh-install gate that creates an isolated HOME, installs the real npm extension dependency closure, applies the compatibility patch, verifies local module resolution, and loads the resulting extension. ## [0.15.6] - 2026-07-29 ### Changed - Updated the bundled first-party Consumer Brand Commerce and Marketing Skill Pack from `2.0.0` to `2.2.0` at upstream commit `1c28f48ef002ce7dea18bbf5746eb9b4c2876971`, refreshing all eight Commerce and Marketing Skills, their self-contained references, and the deterministic unit-economics calculator. ### Fixed - Preserved `owner=pi67-first-party` and `distribution=bundled-release-only` when the Commerce Skill Pack sync helper refreshes `shared-skill-packs.json`, and added regression coverage for the ownership, distribution, and upstream provenance contract. ## [0.15.5] - 2026-07-26 ### Fixed - Recognized upstream Pi object entries in `settings.json.packages` by their `source`, so resource-filtered packages remain configured, participate in identity deduplication, and are not re-added as unfiltered string entries by update or repair. - Distinguished `pi list` resource-filtered entries from genuine package load failures. Deep extension diagnostics now report filtered packages without changing their baseline status, scheduling automatic actions, or emitting `[object Object]` for invalid package configuration. - Normalized object package sources across distro manifests, xtalpi smoke and coverage planning, doctor, report, and smoke checks. ### Changed - Documented explicit routing between `pi-smart-fetch` for known URL and batch retrieval and `pi-web-access` for search, repository, PDF/video, and fallback retrieval, with browser67 and `js-reverse` escalation boundaries. ## [0.15.4] - 2026-07-23 ### Changed - Changed image-understanding routing to prefer the active model's native multimodal input through Pi attachments or `read`. `vision_read` remains an explicit, observable fallback for text-only providers such as `xtalpi-pi-tools`, while `image_review` remains human review rather than OCR. - Removed the always-loaded `vision_read` prompt bias that told native multimodal models to hand every image to a second model, preserving the original pixels, model choice, latency, and context whenever native image transport is available. - Added the bundled `pi-vision-bridge` source to the strict xtalpi TypeScript project so fallback metadata and execution changes are covered by the same compile gate as the text-only provider route that consumes it. - Added runtime registration and real upstream Pi prompt probes that fail if `pi-vision-bridge` reintroduces a global `promptSnippet`, stops advertising `vision_read` as a text-only fallback, or injects the legacy image-routing bias before a provider request. ## [0.15.3] - 2026-07-23 ### Fixed - Fixed the Windows doctor package probe when Scoop, npm, or another shim resolves `pi` to `pi.ps1`. The bounded external-command runner now launches PowerShell scripts through the current PowerShell host while preserving the original argument vector, timeout, output capture, and exit code. - Made non-timeout `pi list --no-approve` failures observable by reporting the exit code and a bounded first error line instead of the generic `pi list failed` warning. - Extended the immutable Windows doctor regression with a real temporary `pi.ps1` shim, successful package-list execution, argument verification, and a controlled non-zero exit that proves the failure summary remains non-blocking and diagnostic. ## [0.15.2] - 2026-07-23 ### Fixed - Fixed the Windows PowerShell doctor JSON boundary so MCP runtime and active provider helper results are parsed from the structured external-command result's `text` field instead of stringifying its OrderedDictionary wrapper. This removes the false `Unexpected character encountered while parsing value: S` warning/failure on valid helper JSON. - Stopped immutable releases from comparing the distro root manifests with `npm/package.json` and `npm/package-lock.json` byte-for-byte. Immutable doctor runs now rely on installed dependency and extension compatibility checks, while legacy/source layouts direct manifest drift through `pi-67 update` instead of the deprecated `pi67-update.ps1` updater. - Added a Windows regression that builds a real immutable distro, executes the PowerShell doctor through both helper call sites, parses its final JSON, and requires zero failures without legacy updater guidance. ## [0.15.1] - 2026-07-23 ### Fixed - Excluded `.gitignore` from immutable distro contents because npm strips that file from packed artifacts, which previously left the published bundle manifest referencing a missing file and blocked fresh install or legacy migration with `pi-67 distro bundle integrity mismatch: .gitignore`. - Extended packed-artifact self-tests to stage and verify the installed immutable distro through the same integrity gate used by real install, update, and migration flows instead of relying only on a dry-run preview. ## [0.15.0] - 2026-07-22 ### Added - Added manager-bundled immutable distro releases under `~/.pi/pi67/releases/` with an atomic current pointer, activation journals, interrupted-activation recovery, same-version content collision rejection, no-op repeated activation, previous-release rollback, and an explicit reversible migration from legacy Git workspaces. - Added a canonical 21-entry default extension minimum-baseline registry and machine-local ownership ledger. Missing and safely-behind pristine defaults can update independently; newer, modified, forked, diverged, and unknown extensions are preserved rather than downgraded or overwritten. - Added extension `inspect`, `plan`, `status`, `diff`, and single-extension backup/restore flows, plus a deep real-`pi list --no-approve` resolution probe that exposes configured packages as `load-failed` without auto-replacing their local content. - Added the missing `lark-apps` and `lark-note` bundles so all 27 Lark Skills remain in the default distribution. ### Changed - Embedded the complete distro and per-file SHA-256 manifest in the npm manager artifact. Standard install/update no longer clones or pulls mutable GitHub `main`; legacy shell updaters no longer copy the release lock into the runtime or run a whole-extension-tree `npm ci`. - Fully decoupled Pi version management from pi-67. Status, version, manifest, update plan, doctor, and report no longer compare installed/tested/latest Pi, recommend a Pi upgrade, or mutate the Pi runtime; diagnostics are limited to command availability and real configuration/package loading probes. - Defined the public memory stack as two distinct layers: `pi-observational-memory` for in-session compression and `pi-hy-memory` for cross-session long-term memory. Existing personal `agent_memory` MCP state is preserved during migration/rollback but is not publicly distributed. - Marked the eight Commerce/Marketing and 21 AI Berkshire Skills as `pi67-first-party` and `bundled-release-only`. User updates preserve newer or modified active Skills and receive first-party changes only through a tested pi-67 release. - Reworked installation, update, Windows, troubleshooting, schema, Skill governance, and release documentation around immutable artifacts and non-downgrading ownership boundaries. - Isolated release pointers, extension ledgers, locks, journals, migrations, backups, reports, and runtime state for custom `--agent-dir` workspaces under a stable hashed `~/.pi/pi67/workspaces/` root. The canonical `~/.pi/agent` workspace keeps the existing `~/.pi/pi67` path. ### Fixed - Prevented installed npm package self-tests from rebuilding or deleting their own immutable `distro/`, and kept distro runtime-script dependencies self-contained inside the release artifact. - Normalized bundled-extension text hashes across LF and CRLF checkouts so the same extension baseline validates consistently on Windows, macOS, and Linux. - Prevented a pi-67 release from overwriting a user-upgraded third-party extension merely because the release baseline is older. - Prevented repair from treating all npm extension versions as one lockstep runtime and from changing unrelated extensions when only one baseline needs installation or repair. - Prevented custom workspaces from reading or overwriting the canonical workspace release pointer, ownership ledger, locks, backups, or migration state. ## [0.14.3] - 2026-07-21 ### Changed - Stopped distributing the user-specific `agent_memory` MCP through the default template, configure helper, and installation guidance. `pi-hy-memory` is the only long-term memory mechanism distributed by pi-67; updates continue to preserve existing user-managed MCP entries without deleting or replacing their data. ## [0.14.2] - 2026-07-21 ### Fixed - Hardened `xtalpi-pi-tools` against malformed Windows `bash` JSON actions by preserving valid nested quote escapes, routing raw `C:\\...` command paths through a targeted bounded repair, and teaching the protocol to prefer `$HOME` or forward-slash paths. Added a version-aware `pi-smart-fetch@0.3.12` compatibility patch so declared GBK/GB2312 response charsets are decoded from original bytes instead of being forced through UTF-8 `response.text()`. ## [0.14.1] - 2026-07-21 ### Fixed - Made `pi-rules-loader` parse rule frontmatter `triggers`, inject at most three directly matched rules in full, persist the active route across contextual follow-ups, clear it on topic changes, and expose matched-rule read failures. Added deterministic investment triggers plus unit and real upstream-Pi prompt capture coverage so a generic Web search can no longer silently replace the required AI Berkshire Skill route for non-trivial stock opinions. ## [0.14.0] - 2026-07-21 ### Added - Added `ai-berkshire-investment-suite@1.0.0`, a shared Pi/Codex Pack containing 21 AI Berkshire value-investing Skills, referenced Python tools, MIT license, per-Skill provenance, and reproducible registry/lock SHA-256 metadata. - Added `rules/investment.md` and upgraded the Pi kernel to `v1.8-pi` so stock, earnings, industry, portfolio, thesis, income-investing, management, private company, and publishing requests route to the appropriate AI Berkshire Skill with date, dual-source, exact-calculation, report-audit, Markdown-source, and delegation-truthfulness gates. - Added a daily PR-only AI Berkshire upstream refresh workflow. It uses a stable automation branch, generated-path allowlisting, credential-scoped push/PR steps, and draft review for Skill-set or validation changes; it never auto-merges, publishes npm, tags, or releases. ### Changed - Extended shared Skill Pack governance, CLI help, installation/release docs, integrity gates, and temporary-HOME active deployment tests to cover both the eight-Skill Commerce Pack and the 21-Skill AI Berkshire Pack. ### Fixed - Made AI Berkshire generation adapt bundled Python help examples to Skill- relative `scripts/` paths and transactionally remove upstream-deleted Skills only when their current directory still matches the previous provenance lock. ## [0.13.2] - 2026-07-21 ### Fixed - Stopped a clean, release-current `update --check` from unconditionally recommending a no-op `pi-67 update`. The distro update recommendation now appears only when the checked remote branch actually differs; explicit local repair and release-lock synchronization actions remain visible separately. ## [0.13.1] - 2026-07-21 ### Fixed - Made the tracked root `package-lock.json` the authoritative release-tested baseline for managed Pi packages. `update --check` now treats newer registry versions, including semver-compatible patches, as maintainer-owned baseline drift instead of repeatedly asking employees to run an `npm ci` update that can only reinstall the existing lock. Local versions ahead of or behind the lock are resynchronized deterministically, including with remote checks disabled. ## [0.13.0] - 2026-07-20 ### Added - Added the first-party `pi-hy-memory` extension for private, per-system-user long-term memory shared across that user's Pi projects. Upstream `pi` remains the only chat runtime; the extension recalls before an agent turn and queues only settled user/final-assistant text for background capture. - Added `pi-67 memory` lifecycle commands for initialization, status, doctor, service control, pause/resume, upgrade, outbox flush, confirmed deletion, explicit System 2 digest, and reset-with-backup. - Added authenticated loopback service and outbox boundaries around the pinned official `hy-memory==1.2.20` SDK, including atomic writes, idempotent request IDs, retry backoff, dead-letter handling, bounded payloads, host/bearer validation, credential redaction, and generic internal errors. - Added Linux, macOS, Windows, CLI, packed-artifact, TypeScript, Python wrapper, security, configuration, and retry regression gates for the memory extension. ### Security - Keeps Hy-Memory config, SiliconFlow credentials, local Chroma/SQLite data, runtime files, outbox, and logs outside the Git checkout under `~/.hy-memory/pi67`. The DeepSeek credential is read dynamically from the upstream Pi `auth.json` entry instead of being copied into repository state. - Treats recalled text as untrusted context, excludes system/thinking/tool and failed/aborted output from automatic capture, redacts common credential shapes, and requires explicit confirmation for deletion, digest, and reset. ### Fixed - Canonicalized existing filesystem paths when checking loopback service identity, so macOS aliases such as `/tmp` and `/private/tmp` cannot make a valid isolated service look foreign or leave initialization waiting until timeout. ### Changed - Bumped the pi-67 distribution and public manager to `0.13.0`. The canonical memory model contract uses `deepseek-v4-flash` for Hy-Memory extraction and reasoning plus SiliconFlow `BAAI/bge-m3` for embeddings. BGE-M3 omits the unsupported request `dimensions` field while the local vector store remains fixed at 1024 dimensions. ## [0.12.1] - 2026-07-16 ### Added - Added a cross-platform prompt-governance check for AGENTS kernel size, upstream system-prompt ownership, rule/prompt metadata, stale capability names, and duplicated rules-loader content. Release and Bash/PowerShell smoke gates now run the same check. ### Changed - Reduced the always-loaded Pi `AGENTS.md` kernel from 216 to 125 lines and moved detailed pi-67 runtime/provider/install/release ownership into the on-demand `rules/pi67-product-boundary.md` rule. - Simplified `pi-rules-loader` to inject one compact absolute-path rule index instead of repeating the AGENTS routing matrix and duplicate display paths. ### Fixed - Replaced stale `agent_memory_briefing` / `agent_memory_recall` guidance with the current short direct-tool names, and made extension/MCP routing explicitly conditional on the live tool list and runtime configuration. ## [0.12.0] - 2026-07-15 ### Added - Added a tracked root `package-lock.json` and made install, update, CI, and release preparation use deterministic `npm ci` installs. Release tooling can now prepare its ignored `npm/` runtime directly from the tracked lock in a clean checkout and removes task-created runtime state on exit. - Added fail-closed updater branch discovery for Bash and PowerShell. An explicit branch wins; otherwise the updater uses a compatible configured upstream, a matching remote branch, or a remote-default branch only when its commit exactly matches local `HEAD`. Divergent and detached checkouts require an explicit branch. - Added aggregate update phase timings for Git, configuration, Skills, npm, verification, and total duration, plus a native macOS smoke job alongside the existing Ubuntu and Windows CI matrix. - Added focused integration coverage for branch resolution and the `v0.11.7` tracked-to-ignored settings migration. Packed-artifact and settings ownership tests now live in focused, package-contained modules under `packages/pi67-cli/scripts/checks/`, while the existing CLI check remains the single lifecycle entrypoint. ### Changed - Moved `settings.json` from version-controlled distribution content to ignored per-machine runtime state. `settings.example.json` is now the tracked default template; fresh installs copy it only when local settings are missing, while updates preserve existing provider, model, theme, packages, and runtime markers. - Removed the legacy repository-local settings clean filter for current installs. Updates from older releases still migrate `lastChangelogVersion` into `~/.pi/pi67/state.json`, remove the obsolete Git filter, and preserve both clean and locally modified legacy settings. - Reduced default shared-Skill drift output to one compact summary. Use `pi-67 install --verbose`, `pi-67 update --verbose`, or PowerShell `-SkillDriftDetails` for per-Skill paths and hashes; strict mode remains detailed and fail-closed. ### Fixed - Prevented feature or maintenance checkouts from accidentally pulling a guessed branch such as `main` when branch ownership is ambiguous. - Removed the clean-checkout release dependency on an already-populated, ignored `npm/node_modules` directory or a pre-existing local `settings.json`. - Made the xtalpi smoke planner read machine-owned settings from the configured agent directory and fall back to tracked `settings.example.json` in a clean checkout, while still failing closed when neither source exists. ## [0.11.7] - 2026-07-15 ### Changed - Unified the external companion lifecycle around user-facing intent. `pi-67 external install browser67` now owns both the first checkout and full runtime preparation; `external update browser67` pulls an existing clean checkout and reruns preparation only after a real revision change or when deterministic readiness is incomplete. `external setup browser67` is now an explicit rebuild for an already installed checkout, while update no longer silently installs missing external repositories. Automated update setup preserves an existing valid alternate MCP checkout; dirty repos continue to fail closed without reset, clean, or overwrite. - Simplified the normal pi-67 maintenance path to `pi-67 update`. The updater now automatically forces managed npm dependency synchronization when its read-only plan detects missing or stale pi-67-managed packages. `--repair` is reserved for explicitly forcing npm reinstall when the plan appears current but the installation is damaged, and the ineffective command-level `pi-67 update --yes` option has been removed. Fresh-install recovery keeps `pi-67 install --repair --yes` because moving an existing non-Git workspace still requires explicit consent. - Removed `pi-67 update --include-pi`, `pi-67 update --all`, and the underlying `pi update --all` execution path. Upstream Pi is now a strict separate lifecycle: pi-67 may report installed/tested/latest compatibility and the standalone npm update command, but install/update/repair never mutates the Pi runtime. pi-67 update remains responsible for its manager-adjacent distribution, managed extensions, Skills, rules, prompts, templates, configuration repair, and workspace dependencies. - Reduced the Windows `pi67-bootstrap.ps1` release asset to a focused pi-67 manager/workspace installer and updater. Windows Terminal, PowerShell 7, Git, fnm, Node.js/npm, and upstream Pi are now explicit manual prerequisites; the script no longer requests UAC or mutates workstation, shell, registry, provider, or npm-registry configuration. - Reworked the Windows fresh-install guide into a complete zero-to-ready sequence beginning with Administrator Windows PowerShell and a WinGet command-line installation of Windows Terminal, followed by manual runtime preparation and the lightweight pi-67 bootstrap. - Corrected the true fresh-machine prerequisite chain so a missing WinGet is recovered before Windows Terminal installation: App Installer registration first, Microsoft Store installation/update when absent, and the official Microsoft.WinGet.Client repair flow as a command-line fallback. - Documented the required Windows Terminal post-install contract: use the newly installed PowerShell 7 profile as the default, enable profile-level administrator startup, and use a fixed highest-privilege scheduled task plus pinned shortcut for daily launches without repeated UAC prompts. The guide retains system UAC for the original Terminal icon and other elevation paths, and includes verification and rollback steps. Windows workstation acceptance schema v5 validates PowerShell 7, its elevated default profile, and the fixed highest-privilege launcher. - Added Notepad4 as the manual prerequisite immediately after PowerShell 7. The fresh-install and acceptance contracts require the Windows Explorer context-menu integration and registry-based replacement of Windows Notepad; the taskbar jump-list option remains optional. The lightweight pi-67 bootstrap still does not install or configure Notepad4. - Moved Git for Windows into the manual sequence immediately after Notepad4. The guide now reloads User/Machine PATH, verifies `where.exe git` and `git --version`, proves the resolved Git `cmd` directory is persistent, and provides a deduplicating User PATH repair only when WinGet did not persist the directory. Windows acceptance retains the same persistent-PATH gate. - Made the fnm/Node stage reproducible from a missing PowerShell 7 profile: close all Terminal windows after installing `Schniz.fnm`, create `$PROFILE`, edit it through Notepad4, load the canonical `fnm env --use-on-cd` line into the current shell, and select `lts/krypton`. The manual contract now persists `https://registry.npmmirror.com/` as the final npm registry; workstation acceptance validates that value without modifying user configuration. - Added an optional Oh My Posh workstation-polish step with the user-scoped WinGet package, profile initialization, theme gallery, and reversible removal. `Maple Mono NF CN` is the primary team font because it combines Nerd Font icons with CJK coverage and 2:1 terminal alignment; the guide downloads the official latest archive and checksum, verifies SHA-256, and retains Meslo only as a compatibility fallback. The faster standard PowerShell initializer is the default; `--eval` is documented only as the slower ExecutionPolicy fallback. Bootstrap and workstation acceptance remain independent of this appearance layer. ### Fixed - Made Windows bootstrap dry-run output render the exact workspace command for the selected mode, so update previews show `pi-67 update` instead of the install-only `--repair --yes` consent flags. ## [0.11.6] - 2026-07-14 ### Fixed - Detect the observed selected-tool direct-kind drift shape, such as `{"kind":"bash","command":"..."}`, and grant it one additional targeted, bounded repair within the existing total recovery budget. The flattened object is never executed; only a subsequent canonical `tool_call` envelope can reach the existing whitelist, schema, repeat, and shell guards. - Isolated the packed-artifact self-test from an outer `npm publish --dry-run` lifecycle so inherited `npm_config_dry_run=true` cannot suppress the nested tarball that `prepublishOnly` must install and execute before publication. ## [0.11.5] - 2026-07-14 ### Added - Split the `xtalpi-pi-tools` runtime into explicit configuration, transport, protocol, tool, and turn-state boundaries. `provider-turn.ts` is now a thin orchestrator, while preparation, final policy, recovery prompts, request budgets, and execution-ledger behavior have dedicated owners. - Added strict TypeScript compilation, acyclic module-graph and orchestration size gates, plus Node unit, integration, replay, state-machine, and transport suites with enforced line, branch, and function coverage on Node 22/24 CI. ### Changed - Made the `v2` reliability engine the deterministic default with an explicit runtime profile: bounded request attempts, per-attempt timeout, total request deadline, Retry-After clamp, jittered backoff, response-byte limits, and caller-abort ownership are now resolved and validated in one policy layer. - Unified continuation detection across serialization, vision routing, provider preparation, and final-answer validation. Action continuations such as `继续优化`, `继续修复`, `继续测试`, and `继续收口` now recover recent user context instead of losing the previous task and tool-selection intent. - Applied explicit user tool constraints before browser and vision preferences. Forbidden tools are removed from the eligible set and `only use ...` constraints cannot be overridden by recovery boosts or bridge routing. ### Fixed - Reduced browser-routing false positives for generic MCP, knowledge-base uploads, document downloads, component/source inspection, tests, schemas, databases, and queues while preserving explicit browser67, Chrome/Edge, current-page, login-state, URL-open, and URL-screenshot tasks. - Hardened response normalization, final-answer boundaries, provider error telemetry, body-read timeout classification, malformed native tool calls, and bounded recovery so protocol drift cannot become a fake success or an unvalidated local tool execution. ## [0.11.4] - 2026-07-14 ### Added - Added a state-scoped `pi67.skill-deploy-lock.v1` guard so concurrent writers cannot mutate the same Active Skill root. Dry-runs remain lock-free; dead-process locks recover automatically and release verifies an owner token. - Changed managed Skill deployment to treat the Git-tracked Pack as the only content source of truth. Sync uses transient staged/previous transaction directories, removes stale transaction residue, and creates no persistent Skill content backups; rollback is Git commit/tag selection followed by sync. - Added versioned shared Skill Pack governance for the eight-Skill Consumer Brand Commerce and Marketing suite, including `pi-67 skills packs` and explicit transactional `pi-67 skills sync-pack --yes` deployments. - Added a shared `pi67-shared-skill-packs-status/v1` diagnostic contract across status, update plans, Bash/PowerShell Doctor, and Report, with non-writing remediation previews and strict-mode Pack parity gates. - Added `shared-skill-packs.lock.json` provenance governance with a clean-source Git requirement, locked upstream Commit, Manifest and Pack SHA-256 values, per-Skill fingerprints, and blocking vendored-integrity diagnostics. ### Fixed - Fixed release artifact smoke checkout detection so linked Git Worktrees are accepted instead of being rejected because their `.git` marker is a file. - Isolated the updater smoke fixture behind its own temporary branch and bare remote so release checks remain deterministic from detached Worktrees. - Materialized linked runtime state before the DeepSeek smoke mutation so test writes cannot follow symlinks back into the source checkout. ## [0.11.3] - 2026-07-13 ### Fixed - Made the published npm manager artifact self-contained by removing the browser67 runtime dependency on a repository-root script that is not shipped inside `@bigking67/pi-67`. - Added a packed-artifact regression gate that installs the generated tarball in an isolated directory and executes `pi-67 external --help`, preventing source-worktree checks from masking missing npm package files. ## [0.11.2] - 2026-07-13 ### Added - Added a release-tested upstream Pi runtime baseline to the distro manifest. `pi-67 version`, `pi-67 status`, and both doctor implementations now report installed, tested, and available runtime version state instead of treating any successful `pi --version` response as fully current. - Added `pi-67 external setup browser67`, which turns the optional browser67 companion checkout into a runnable integration by installing dependencies, preparing the unpacked extension, synchronizing active skills, and safely merging MCP paths. `--start-hub` remains explicit. - Added `pi-67 external doctor browser67 --deep` with separate deterministic checkout/config checks and a live Hub/extension readiness probe. ### Fixed - Doctor now warns when the installed upstream Pi runtime is older than the version exercised by the current pi-67 release, preventing a stale runtime from producing an otherwise false-green readiness result. - Replaced the obsolete `pi skill list` doctor probe with the non-interactive `pi list --no-approve` package registry command required by upstream Pi 0.80.6, preventing doctor from accidentally starting an interactive model request. - Isolated smoke logs per process and moved filename extensions before the trailing `mktemp` template, so concurrent macOS smoke/release checks no longer race on shared files or fail with spurious `ENOENT` errors. ## [0.11.1] - 2026-07-12 ### Changed - Restored upstream Pi ownership of `/login`, `/model`, authentication persistence, selected-model persistence, and next-launch restoration. - Windows acceptance now reports Pi startup readiness separately from optional model-request readiness. Provider-specific live checks run only when the currently selected provider already has usable credentials. - Windows Node 22/24 CI now verifies `xtalpi-pi-tools` model registration with a non-secret discovery-only fixture, then independently proves that real Pi reaches `session_start` with no provider credentials. This matches upstream Pi 0.80.6, which hides credential-gated models from `--list-models`. - `pi-67 xtalpi configure --verify` remains an optional company-provider convenience. Blank input or `--no-prompt` without a key succeeds without writing provider/model state. - Install and update flows no longer auto-select, reconcile, or rewrite the upstream Pi provider/model selection based on available keys. ### Fixed - Fixed `xtalpi-pi-tools` provider registration so upstream Pi can enter its interactive interface without any configured API key. - Missing credentials now affect only the corresponding model request; they no longer fail bootstrap, doctor, smoke, or Windows startup acceptance gates. ## [0.11.0] - 2026-07-12 ### Added - Added `scripts/pi67-bootstrap.ps1`, a Windows PowerShell 5.1+-compatible fresh-machine bootstrap that repairs missing WinGet, installs/configures Windows Terminal, PowerShell 7 and Notepad4, persists Git PATH, provisions fnm + Node.js 24 LTS, and only then installs the real upstream Pi runtime, the pi-67 manager, the managed workspace, the company provider, and the complete Windows acceptance flow from one downloaded file. - Added `pi-67 xtalpi configure` with hidden key input, environment-secret injection, dry-run/JSON modes, canonical provider repair, Windows JSON encoding normalization, idempotent writes, and optional live provider-health verification. - Added `docs/windows-fresh-install.md` with the supported beginner flow, checksum verification, Node-manager policy, result semantics, logs, and separated npm/GitHub/xtalpi/proxy troubleshooting. - GitHub Releases now upload `pi67-bootstrap.ps1` and `pi67-bootstrap.ps1.sha256` so the documented `releases/latest/download/...` URL remains stable and auditable. ### Changed - New Windows installations use `Schniz.fnm` with `lts/krypton`, persist the official PowerShell initialization block, set the fnm default, and enforce both Node.js major 24 and the complete upstream runtime minimum of `>=22.19.0`. - Full-mode Windows bootstrap now treats Windows Terminal, PowerShell 7 and Notepad4 as explicit workstation stages: Terminal defaults to PowerShell 7, both PowerShell profiles use `elevate=true` by default, and Notepad4 receives verified Explorer/notepad.exe registry integration. `-Minimal` remains the explicit opt-out for these desktop stages. - A normal bootstrap now performs one UAC Administrator relaunch, while `-SelfTest` and `-DryRun` remain non-elevating and offline/read-only. - Windows Node 22/24 CI, PowerShell smoke, release-check, and release artifact smoke now cover the bootstrap self-test and a fresh isolated `xtalpi configure --dry-run --no-prompt --json` contract. - Fresh-install documentation now leads with the one-file bootstrap while keeping `pi` as the only standard daily runtime entrypoint. - Windows download snippets use `Invoke-WebRequest -UseBasicParsing` for Windows PowerShell 5.1 compatibility, and the GitHub Release command now requires the exact npm manager version and the npm `latest` dist-tag to agree before exposing the bootstrap asset. Actual release notes and bootstrap assets are sourced from committed `HEAD`, even when unrelated dirty runtime state is explicitly allowed. ### Fixed - Provider configuration now preserves unrelated providers and extra local models while repairing drifted public `xtalpi-pi-tools` fields from the canonical template instead of directing users to a repair path that might leave the drift unchanged. - Safe `models.json` replacement now handles Windows rename-over-existing behavior with a rollback file, restores the previous target on failure, and never deletes the old config before the replacement is ready. - Bootstrap completion no longer claims a full pass when the personal xtalpi key was intentionally skipped; it reports `READY_WITHOUT_XTALPI` until the provider is configured and verified. - `xtalpi configure` now rejects valid JSON with a non-object root or a non-string existing API key without rewriting the file, and hidden prompts use stderr so interactive `--json` keeps stdout machine-readable. - Common `xtalpi configure` failures now return concise CLI errors instead of a Node stack trace, and secret-bearing atomic temp/rollback files are ignored if a process is interrupted before cleanup. - Fresh-machine setup no longer installs standalone `OpenJS.NodeJS.LTS`, no longer treats missing WinGet as a manual-only blocker, and no longer reports Terminal/PowerShell installation failures as optional warnings in full mode. ## [0.10.29] - 2026-07-10 ### Changed - Restored the product boundary between upstream Pi and pi-67: `pi` is the standard runtime and daily entrypoint, while `pi-67` installs, configures, updates, diagnoses, and validates the surrounding team workspace. - Windows one-command acceptance now uses the real `pi --version` command as its runtime hard gate. The optional `pi-67 launch` compatibility helper is no longer treated as proof that upstream Pi is installed or usable. - Repositioned `pi-67 launch` in CLI help and installation/troubleshooting documentation as a temporary PATH helper for an already-open Windows terminal, not as the normal startup path. - Documented why the project is named pi-67, how it grew from 67's long-term Pi usage and company Agent tooling responsibilities, and why it remains a curated Windows/macOS team distribution rather than a generic starter. ### Fixed - Windows Node 22/24 CI now installs the real upstream Pi npm package and runs bare `pi --version`. The separate launch-helper compatibility check also targets that installed runtime instead of a temporary fake `pi.cmd`. - Release gates now reject a Windows acceptance contract that substitutes `pi-67 launch` for the real Pi runtime check. ## [0.10.28] - 2026-07-10 ### Fixed - Fixed Windows guarded launch when upstream Pi is installed through npm or Scoop and PowerShell resolves `pi.ps1`, but Node must execute `pi.cmd`. `npm`, `npx`, and `pi` now continue through the `cmd.exe /d /s /c *.cmd` fallback after Windows `EINVAL` / `ENOEXEC` spawn failures. - `pi-67 launch` now checks whether upstream Pi exists before launching it and no longer converts every child-process spawn failure into the misleading `upstream pi command was not found` error. ### Changed - Windows one-command acceptance now explains that update stages were skipped because `-SkipUpdate` was requested, prints a bounded failed-stage output tail alongside the full log path, and gives launch recovery guidance that distinguishes a working bare `pi` from a manager-launch defect. - Windows CI now executes `pi-67 launch` against a real temporary `pi.cmd` shim instead of checking only the fallback candidate list. ## [0.10.27] - 2026-07-10 ### Added - Added `scripts/pi67-windows-acceptance.ps1`, a single Windows update-and- acceptance entrypoint that updates the npm manager and local distribution, then validates version/configuration, doctor, repository smoke, guarded launch, xtalpi health/capability, and the targeted `read-package` / `read-enoent-recovery` live tool chain. - Added `-SkipUpdate` for validating the current installation without network updates and `-SelfTest` for deterministic offline Windows/CI contract validation. ### Changed - Added the Windows acceptance self-test to GitHub Actions and the release gates so the one-command path cannot drift without detection. - Updated installation, release, and troubleshooting documentation to distinguish npm manager self-update, local distribution update, upstream Pi package update, and guarded launch. ## [0.10.26] - 2026-07-10 ### Added - Added `pi-67 launch`, a guarded upstream Pi launcher that checks Git before starting `pi`, patches a discovered Git for Windows directory into the child process PATH, and can persist that directory into Windows User PATH with `--persist-git-path` / global `--yes`. - Added the `xtalpi-pi-tools` compatibility protocol v2 runtime with explicit `legacy` / `shadow` / `v2` engines, reliability-oriented policy profiles, canonical SHA-256 tool-call fingerprints, strictly paired call/result receipts, and bounded recovery budgets. - Added focused `config/`, `protocol/`, `tools/`, `transport/`, and `turn/` modules plus unit, transport, state-machine, integration, and replay tests so the provider no longer concentrates protocol behavior in one parser file. - Added Windows PowerShell `read-enoent-recovery` live coverage and capability CLI forwarding for `--json-action-runs`, `--skip-native-probes`, and `--output-file`. ### Fixed - Windows first-run docs now avoid launching bare `pi` before `pi-67 install --repair --yes`; upstream Pi installs git-based packages such as `git:github.com/justhil/pi-image-gen`, so a stale PowerShell PATH could otherwise crash with `spawn git ENOENT`. - The pi-67 command runner now has Windows `.cmd` fallbacks for `pi` and `npx`, matching the existing npm fallback behavior. - A deterministic tool failure such as `read` returning `ENOENT` no longer permits the same fingerprint to execute again. The local runtime emits one bounded `recovery.repeated_tool`, promotes path-discovery tools such as `fffind`, and continues to a final answer instead of abandoning the task. - HTTP attempts, response-body reads, retry delays, and recovery loops now share explicit per-attempt and total request deadlines, preventing the previous `attempts x full timeout` worst-case latency path. - Tool selection now incorporates recent failure context while keeping transient replay limited to explicitly read-only idempotent tools; shell, edit, write, and unknown-side-effect calls are never automatically replayed. ## [0.10.25] - 2026-07-09 ### Changed - `pi-67 update` / `pi-67 update --repair` now block when the active npm manager is older than npm latest or older than the local distro version, so users update the manager before running stale update/repair logic. - `pi-67 update --check --no-remote` now reports registry-skipped managed packages explicitly instead of showing an ambiguous zero-current summary. - `pi-67 doctor` now emits a human-readable manager preflight warning when the active npm manager is stale, without changing JSON doctor output. ### Fixed - Hardened `xtalpi-pi-tools` browser67 routing for Chinese prompts such as "打开浏览器～browser67" and "用 Chrome 打开..." where the browser marker may use Chinese punctuation or appear before the action verb, so the `mcp` gateway is selected instead of `bash` / `web_fetch`. - Browser67 / `tmwd_browser` tasks now fail closed or repair when the model tries to use `bash` with macOS `open`, `open -a "Google Chrome"`, `xdg-open`, `start`, `python -m webbrowser`, normal browser-app launches, or local `browser67` CLI probes as a substitute for Pi's MCP gateway. - Retry-style follow-ups such as "再试一下" now reuse recent user context for tool selection, preventing a second browser attempt from losing the original Chrome/browser67 intent. ## [0.10.24] - 2026-07-09 ### Changed - Updated the managed `pi-subagents` baseline to `^0.34.0`, matching the current npm release so Pi no longer keeps asking users to run the upstream `pi update --extensions` path after a normal `pi-67 update --repair`. ### Added - Added managed npm package baseline auditing to `pi-67 update --check` and `pi-67 extensions doctor`, distinguishing local install drift from pi-67-release baseline drift before users see a generic Pi package-update prompt. ## [0.10.23] - 2026-07-09 ### Changed - `pi67-configure.sh` and the MCP config normalizer now write browser67 custom checkout paths as machine-local `cwd` plus relative `args` instead of copying the full browser67 path into each MCP entrypoint argument. - Clarified MCP path documentation so public templates stay portable while local ignored `mcp.json` files may contain machine-specific paths. ## [0.10.22] - 2026-07-09 ### Added - Added `scripts/pi67-mcp-config-utils.cjs` to normalize and inspect Pi `mcp.json` runtime paths using the same no-shell-expansion rules as `pi-mcp-adapter`. - Added a targeted `mcp-connect-tmwd-browser` smoke case for verifying that Pi can start the browser67 `tmwd_browser` MCP server, not just inspect gateway status. ### Fixed - Fixed browser67 / `tmwd_browser` MCP startup failures when Pi `mcp.json` used shell-only `$HOME` / home placeholders inside stdio `command` or `args`; install, configure, update, doctor, smoke, and release gates now normalize or report adapter-incompatible paths. - `pi67-doctor.sh --deep-mcp` now matches `pi-mcp-adapter` runtime behavior instead of expanding `$HOME` itself, so bad MCP args fail the diagnostic instead of producing a false pass. - Fresh installs and Windows PowerShell updates now run MCP path normalization for local config, while preserving user-owned runtime files. ## [0.10.21] - 2026-07-09 ### Added - Added `xtalpi-pi-tools` browser/MCP selected-tool routing so browser67, Chrome, Edge, current-tab, login-state, click/type, upload/download, screenshot, DevTools, DOM, and network-inspection tasks select the `mcp` gateway when available, even with a low `XTALPI_PI_TOOLS_MAX_TOOLS`. - Added documentation and release/smoke tracked-file gates for the new browser bridge. ### Fixed - Browser tasks no longer fail with `xtalpi-pi-tools 请求了不可用工具：mcp` when `mcp` exists in the runtime tool list but was previously omitted from the selected-tool allowlist. - Ordinary public-URL summarization remains routed to `web_fetch` / `web_search`, avoiding unnecessary browser67 activation. ## [0.10.20] - 2026-07-09 ### Added - Added the bundled `pi-vision-bridge` local extension and `vision_read` tool so screenshot, image, and OCR tasks are routed through a local multimodal bridge before `xtalpi-pi-tools` hands ordinary text evidence to xtalpi. - Added xtalpi vision-task detection, image-path `read` de-prioritization, vision bridge readiness fail-closed behavior, model-output repair prompts, doctor checks, smoke-plan metadata, coverage audit rules, and release gates for `vision_read`. ### Fixed - `xtalpi-pi-tools` no longer treats Pi's accepted Plan mode continuation wrapper (`Plan mode is now disabled... Implement this proposed plan now`) as active Plan mode, and smoke gates now cover that continuation path. ## [0.10.19] - 2026-07-09 ### Fixed - Windows Git PATH repair now broadcasts the Windows environment change after `pi-67 install --repair --yes` writes the discovered Git directory into User PATH, improving the "new terminal can run git" behavior while preserving the safe User-PATH-only boundary. ## [0.10.18] - 2026-07-09 ### Fixed - `pi-67 install --repair --yes` now persists a discovered Git for Windows directory into Windows User PATH when Git is installed but the current PowerShell session cannot find `git`. The installer still patches the current process PATH first, writes only User PATH under explicit `--yes`, and does not silently modify Machine PATH or install Git. ## [0.10.17] - 2026-07-09 ### Fixed - Windows Git discovery is now self-healing for common Git for Windows installs. If `git.exe` exists in standard install locations but PowerShell has not picked it up in `PATH`, `pi-67` prepends that Git directory for the current process before clone/update/doctor/smoke commands run. - PowerShell helper scripts now use the same Git discovery path, so direct `.\scripts\pi67-update.ps1`, `doctor`, `smoke`, and report flows no longer fail just because Git is installed but missing from the current shell PATH. ## [0.10.16] - 2026-07-09 ### Fixed - `pi-67 install --repair --yes` now checks that `git` is available before moving an existing non-Git `~/.pi/agent` directory into the repair backup. Missing Git now fails early with actionable install guidance instead of doing a backup/restore round trip and surfacing `spawnSync git ENOENT`. ## [0.10.15] - 2026-07-09 ### Fixed - `pi-67 install --repair --yes` now safely handles an existing non-Git `~/.pi/agent` directory by moving it to `~/.pi/pi67/backups/-non-git-agent-dir/agent` before cloning the managed pi-67 checkout. The default `pi-67 install` path still blocks instead of silently overwriting a plain folder, but now prints the exact dry-run and repair commands. - Empty pre-created agent directories are now accepted as clone targets instead of being rejected as non-Git folders. ## [0.10.14] - 2026-07-08 ### Fixed - `pi-67 update --repair` now refreshes the Git index stat cache for `settings.json` when Git reports `M settings.json` but `git diff` has no real content changes. This clears the Windows false-dirty state that can remain after line-ending/runtime-state cleanup. ## [0.10.13] - 2026-07-08 ### Fixed - `pi-67 update --repair` now normalizes `settings.json` BOM/CRLF line endings even when `lastChangelogVersion` is already absent. This clears Windows Git false-dirty states where `git diff -- settings.json` only reports the `LF will be replaced by CRLF` warning and has no real content diff. ## [0.10.12] - 2026-07-08 ### Fixed - `settings.json` is now explicitly tracked as `text eol=lf` alongside the runtime clean filter. This removes the Windows Git `LF will be replaced by CRLF` false-dirty warning after updates when there is no real settings content diff. ## [0.10.11] - 2026-07-08 ### Fixed - Bash and PowerShell distro updaters now run settings runtime-marker normalization again as the final update step, after smoke/report side effects. This keeps `settings.json.lastChangelogVersion` out of Git status even when an older global manager invokes a newer local updater script. ## [0.10.10] - 2026-07-08 ### Fixed - The update preflight runtime-marker regression test now covers both Bash and PowerShell distro updater entrypoints, matching the real cross-platform manager dispatch path. ## [0.10.9] - 2026-07-08 ### Fixed - `pi-67 update --repair` now migrates and normalizes the `settings.json.lastChangelogVersion` runtime marker before invoking the local distro updater script. This lets a freshly installed latest npm manager clean the common `M settings.json` state even when the checked-out distro is still older than the runtime-marker migration scripts. ## [0.10.8] - 2026-07-08 ### Changed - `pi-67 version` now prints a clear next-step recommendation when the global npm manager is newer than the local `~/.pi/agent` distro checkout, or when `settings.json` is dirty from the migrated Pi runtime changelog marker. This makes the supported flow explicit: `npm install -g` updates only the manager, then `pi-67 update --repair` updates and normalizes the local distro. ## [0.10.7] - 2026-07-08 ### Changed - `settings.json` no longer carries the Pi runtime-only `lastChangelogVersion` marker in the tracked baseline. Install/update now migrates that marker into ignored manager state at `~/.pi/pi67/state.json`, normalizes the runtime field out of `settings.json`, and installs a local Git clean filter so future Pi changelog marker writes cannot be carried into normal diffs or commits. - Shared-skill drift wording now describes existing different global skills as "preserved user-modified" skills instead of user-facing "conflicts", while keeping the existing non-destructive policy and JSON compatibility fields. ### Fixed - `pi-67 update --check`, `pi-67 status`, `pi-67 skills inventory`, doctor, and updater logs now use preserved-user-modified wording so beginners do not mistake safe user-owned global skills for broken pi-67 state. ## [0.10.6] - 2026-07-08 ### Changed - `xtalpi-pi-tools` now retries retryable runtime chat-completion transport failures by default, with bounded backoff and debug telemetry for request attempts, retry delays, and retry suppression reasons. This moves the provider-health retry behavior into the normal live provider path. - Bash and PowerShell targeted xtalpi smoke now treat final-answer compliance as a local repairable condition: when tool choice, arguments, debug telemetry, and execution are already valid but the final answer misses required smoke text, the runner performs one no-tool final-answer repair instead of rerunning tools or reporting a protocol failure. - Doctor skill-list probes now default to a 60 second timeout, and the npm manager accepts `pi-67 doctor --no-skill-list` for the POSIX doctor path. - `pi-67 report --json` now works as a command-level JSON option. Dry runs emit a machine-readable dry-run object; real runs emit the generated report JSON to stdout after writing the report file. - The npm publish workflow now installs extension dependencies and runs the full `scripts/pi67-smoke.sh --ci` gate before packing or publishing. ### Fixed - Bash xtalpi smoke self-tests now simulate real tool-selection telemetry, so continuation/final-repair regressions fail the local gate instead of being hidden by simplified fake-Pi fixtures. - PowerShell targeted smoke retries `missing_final_text:*` final-answer-only failures and self-tests the final compliance repair eligibility path. ## [0.10.5] - 2026-07-08 ### Changed - Bash and PowerShell updaters now use `git fetch` followed by `git merge --ff-only FETCH_HEAD` so they can inspect incoming changed paths before deciding whether dirty preserved runtime files need temporary cleanup. - Dirty user runtime config now stays in place without creating a backup when the remote is already current or the incoming update does not touch those runtime files. Runtime backups are created only when incoming changed paths overlap dirty preserved runtime config, and equivalent snapshots are still reused. - `pi-67 update --check` now reports benign/current dirty runtime config as `preserve-in-place-no-backup` when the remote already matches local HEAD, instead of presenting every dirty runtime marker as a planned backup. - Release/smoke gates now check the README version badge against `VERSION`, reject obvious simulated placeholder final answers in xtalpi smoke, and require package metadata smoke cases to report the actual package version. - Added `pi-67 xtalpi run` plus a Windows PowerShell launcher for the stable xtalpi-pi-tools runtime path. The launchers default `PI_OBSERVATIONAL_MEMORY_PASSIVE=true` so post-final observational-memory writes cannot hold the main task lifecycle open. - Doctor now bounds `pi skill list` with `--skill-list-timeout-seconds` / `-SkillListTimeoutSeconds` and reports a warning instead of hanging when the Pi skill registry is slow. ### Fixed - Documentation now consistently distinguishes current first-class runtime backups under `~/.pi/pi67/backups/` from legacy read-only `~/.pi/agent-backups/` conflict snapshots. - Bootstrap snippets no longer recommend preserving the removed `extensions/xtalpi-compat/index.ts` runtime path; they focus on current local runtime config files instead. ## [0.10.4] - 2026-07-08 ### Fixed - Command-level `--help` is now side-effect free across the npm manager CLI: `pi-67 update --help` and other command help paths print usage without entering update/repair logic, acquiring update backups, or writing runtime state. - Real `pi-67 update` now checks the update plan before starting the update lifecycle, so blocked non-runtime dirty worktrees fail closed without first creating a runtime backup. - `pi-67 xtalpi drift` now defaults to full-suite artifacts, preventing targeted one-off smoke runs from creating expected case-set or runtime fingerprint drift noise. - Bash and PowerShell runtime preservation dedupe now recognize both `manifest.json` and manager-style `backup-manifest.json` snapshots under `~/.pi/pi67/backups/`, reducing duplicate backup directories across older and newer backup formats. ### Added - `pi-67 backups prune` and `pi-67 backups archive` for dry-run-first runtime backup retention, with `--keep-last` applied per backup kind and legacy snapshots included only when explicitly requested. - `pi-67 skills plan` and `pi-67 skills diff ` for read-only shared-skill drift review before choosing whether to preserve, sync, or manually merge global skills. - `pi-67 xtalpi trend`, `pi-67 xtalpi drift`, and `pi-67 xtalpi stress --until-done` as user-facing wrappers around the local xtalpi smoke artifact quality gates. - CLI contract self-tests covering command-level help parsing and the guarantee that help commands do not create runtime backups. - Windows CI now exercises Node 22 and Node 24 and runs npm manager CLI contract smoke commands in addition to the PowerShell repository smoke. ### Changed - Runtime config backup ownership is now documented as script-level updater behavior: the npm manager owns planning, locking, blocked-plan classification, and orchestration, while Bash/PowerShell updaters create `pre-update-runtime-*` snapshots only when dirty preserved runtime files must be temporarily cleared for `git pull --ff-only`. - Unknown shared-skill names now fail with concise CLI errors instead of stack traces. ## [0.10.3] - 2026-07-08 ### Changed - Real `pi-67 update` / `pi-67 update --repair` lifecycle backups are now deduplicated: if the preserved runtime files are byte-for-byte identical to the latest backup for the same operation, the manager reuses the existing snapshot instead of creating another timestamped directory. - Direct PowerShell `scripts/pi67-update.ps1` runs also deduplicate identical dirty runtime-config preservation snapshots under `~/.pi/pi67/backups/`. - The Windows PowerShell updater no longer contains the legacy `~/.pi/agent-backups/pre-update-*` writer. Runtime config preservation is handled only through the first-class `~/.pi/pi67/backups/` path. - `pi-67 themes set ` now exits without writing a backup when the requested theme is already selected. ## [0.10.2] - 2026-07-08 ### Fixed - `pi-67 update --check` now reads the latest `@bigking67/pi-67` manager version directly from the npm registry HTTP API instead of spawning local `npm` / `npm.cmd`, eliminating the Windows PowerShell `spawnSync npm.cmd EINVAL` failure class for `Manager latest`. - Windows npm execution now has a final `cmd.exe /d /s /c npm.cmd ...` fallback for explicit npm operations such as `pi-67 self-update` or maintainer publish checks, covering environments where direct `npm.cmd` spawning fails even though PowerShell `npm install -g ...` works. ### Added - `pi-67 backups list --include-legacy` and `pi-67 backups inspect --legacy ` now expose the older PowerShell `~/.pi/agent-backups/pre-update-*` conflict snapshots as read-only diagnostics, so users can distinguish them from first-class runtime backups under `~/.pi/pi67/backups/`. ## [0.10.1] - 2026-07-07 ### Fixed - Windows npm manager commands now fall back to `npm.cmd` when plain `npm` cannot be spawned directly, so `pi-67 update --check` can report `Manager latest` instead of `unknown (spawnSync npm ENOENT)`. ### Changed - Clarified the public install/update path: `npm install -g @bigking67/pi-67` is the recommended daily manager install, while `npx -y @bigking67/pi-67@latest ...` remains the always-fresh one-shot recovery and verification path. ### Added - `packages/pi67-cli/` as the publishable `@bigking67/pi-67` npm manager package, exposing `pi-67` / `pi67` for install, update, doctor, smoke, status, report, xtalpi, themes, skills, extensions, external, backups, and version workflows. - `pi-67 self-update` plus npm latest-version hints in `pi-67 update --check`, so stale global managers are visible and users can run a single explicit manager update without changing Pi's upstream `pi` command. - `pi-67 publish-check` as a maintainer readiness gate for version consistency, Trusted Publishing workflow drift, npm registry state, local npm auth visibility, and `npm pack --dry-run`. - `pi-67 manifest` as a read-only ownership contract for pi-67 managed packages, runtime packages, local extensions, themes, shared skills, external repos, and preserved runtime config files. - `pi-67 manifest --validate` as a standalone extension-registry policy gate, sharing the same validator with `publish-check` and release checks. - `pi-67 extensions list`, `pi-67 extensions doctor`, `pi-67 extensions inspect `, and `pi-67 extensions plan` as the user-facing extension ownership and policy diagnostics. - `pi-67 backups list`, `pi-67 backups inspect`, and `pi-67 backups restore` as the supported recovery path for repo-external update/repair/theme-set runtime snapshots. - `shared-skills/commerce-growth-os/` as the vendored Pi distribution copy of `https://github.com/bigKING67/commerce-growth-os`, so Pi/Codex can share the commerce growth skill through `~/.agents/skills`. - `rules/commerce-growth.md` plus Pi rules-loader routing for commerce growth, marketplace operation, assortment, pricing, channel control, ROI/profit, and platform-currentness tasks. - `scripts/pi67-sync-commerce-growth-os.sh` as a dry-run-first maintainer helper for refreshing the vendored `shared-skills/commerce-growth-os` copy from the standalone upstream checkout. - `scripts/pi67-shared-skills-inventory.sh` as a read-only inventory for explaining `shared-skills/` versus `~/.agents/skills` drift without overwriting global skills. - `scripts/pi67-fuzz-xtalpi-parser.mjs` as an offline parser matrix gate for xtalpi tool-call alias/wrapper compatibility and fail-closed cases. - `scripts/pi67-patch-pi-until-done-runtime-queue.{mjs,sh,ps1}` to check and patch `pi-until-done@0.2.2` for the newer Pi runtime queue contract that requires `streamingBehavior` on `pi.sendUserMessage(...)`. - `scripts/pi67-xtalpi-provider-capability-probe.mjs` to live-probe xtalpi support for plain chat, `json_object`, `json_schema strict`, native tools, strict tools, `role=tool` continuation, and local JSON action envelopes without printing API keys. ### Changed - User-facing update docs now make `pi-67 update` the recommended pi-67 distribution update path, while keeping `pi update --extensions` scoped to upstream Pi extension updates. - `pi-67 update` documentation now explicitly preserves existing local config files, user packages, global skills, external repos, and `settings.json.theme`; theme changes require `pi-67 themes set `. - `pi-67 update --check --json` now emits explicit `actions`, `blocked`, and `warnings` arrays so users can see planned writes, preserved paths, strict shared-skill blockers, and dirty external-repo blockers before running an update. - `pi-67 update` / `pi-67 update --repair` now acquire a repo-external update lock and snapshot preserved runtime files under `~/.pi/pi67/backups/` before dispatching Bash or PowerShell update scripts. - Bash and PowerShell updaters now preserve dirty user runtime config in in-place checkouts by backing it up, temporarily clearing it for `git pull --ff-only`, and restoring it after the pull; unrelated tracked edits still block by default. - Backup restore is preserve-scoped: it only writes known runtime config files and creates a pre-restore backup before replacing the current local runtime state. - Backup manifests now record both present and missing preserved runtime slots, so restore can also remove a preserved config file that did not exist when the backup was created. - `pi-67 themes set ` now writes a runtime backup before explicitly changing the selected theme, while normal update remains forbidden from changing theme selection. - Update-plan self-tests now cover clean repo, runtime-config dirty preservation, unsafe dirty blockers, missing managed extension repair, missing theme assets, shared-skill default/strict behavior, dirty external repos, and manager self-update actions. - `pi-67 update --strict-shared-skills` now forwards strict shared-skill parity checks through both Bash and Windows PowerShell update paths, while the default still preserves existing different global skills. - `pi-67 publish-check` now gates the distro ownership manifest, including preserved runtime config policy, required local extensions, user-managed baseline packages, theme preservation, shared-skill preservation, and dirty external-repo blocking policy. - Extension-registry policy checks are now centralized in `packages/pi67-cli/src/lib/extension-registry.mjs`, with self-tests for duplicate ids, missing smoke gates, forbidden update behavior, unsafe config patches, theme drift, shared-skill drift, dirty external-repo drift, and unregistered managed extensions. - `pi-67 publish-check` now checks npm scope visibility during remote publish readiness, so missing npm namespaces fail before the final publish step with an actionable message. - Pi AGENTS/rules documentation now routes commerce growth work to `commerce-growth-os` without adding local absolute paths or duplicate active package roots. - External skill sync now supports both root-level `repo/SKILL.md` skill repositories and legacy `repo/skills/*/SKILL.md` layouts, with fixture coverage for root-level discovery, apply, and read-only checks. - `scripts/pi67-status.sh` now classifies benign `settings.json` runtime-marker dirty state separately and reports recent xtalpi provider-health retry/failure trend from local smoke artifacts. - `scripts/pi67-doctor.sh` now points shared-skill drift warnings to the new inventory helper instead of leaving operators with only a long skill-name list. - `docs/xtalpi-pi-tools.md` now documents the root-cause boundary for xtalpi empty replies, missing replies, and missed tool calls: the company proxy is treated as plain Chat Completions only, while Pi owns tool selection, protocol parsing, validation, repair, diagnostics, and smoke gates locally. - `xtalpi-pi-tools` now guards premature final answers: Plan mode instruction echoes, missing `` blocks, continuation no-progress replies, intent-to-tool promises without tool calls, and weak acknowledgements trigger a bounded local repair turn instead of silently ending the agent turn. - `xtalpi-pi-tools` now fails closed for stubborn Plan mode contract misses by synthesizing a local `` fallback after the bounded repair budget is exhausted, so users do not get stranded on a raw provider-format error. - `xtalpi-pi-tools` now blocks obvious shell mismatches before execution when the model sends raw PowerShell cmdlets or unquoted Windows backslash script paths to the `bash` tool, then asks the model to repair with bash-compatible commands or an explicit `powershell.exe` / `pwsh` invocation. - `xtalpi-pi-tools` now accepts legacy Pi-style tool envelopes that use `id=...`, `name="..."`, and `arguments_json: {...}` inside ``, preventing that provider drift from surfacing as an invalid JSON stop. - `xtalpi-pi-tools` now normalizes broader high-probability text tool-call drift locally, including `tool` / `tool_name` / `function_name` name aliases, `args` / `input` / `parameters` / `arguments_json` argument aliases, JSON-string arguments, text-native `function_call` / `tool_calls[0].function` shapes, generic `` tags, uppercase tool tags, and nested attributed envelopes, while still failing closed on multiple calls, unknown fields, empty argument strings, and mismatched attributed names. - `xtalpi-pi-tools` now strips mixed `previous_pi_tool_call` history blocks from otherwise valid final answers or tool envelopes before final-answer guards run, so model responses such as "收到，重新发起搜索。" plus copied history are repaired as no-progress continuations instead of surfacing raw internal protocol text to users. - `xtalpi-pi-tools` no longer serializes prior assistant `toolCall` blocks into model-visible `previous_pi_tool_call` history records; the model sees the subsequent tool-result wrapper as evidence, while legacy history markers remain supported only as cleanup/repair inputs. - `xtalpi-pi-tools` final-answer guards now reject echoed protocol/tool-result wrapper instructions such as `Tool protocol rules:` or `content_is_untrusted: true` as internal context leaks. - `xtalpi-pi-tools` fallback error summaries now sanitize raw-response excerpts before displaying them, avoiding a second leak of internal Pi protocol markers when repair is exhausted. - `xtalpi-pi-tools` parser now accepts local JSON action envelopes (`{"kind":"tool_call",...}` and `{"kind":"final",...}`) for providers where targeted JSON action works but native JSON schema / OpenAI tools do not; unknown fields and invalid action kinds still fail closed. - `xtalpi-pi-tools` now uses local JSON action as the only runtime protocol through `json-action-protocol.ts`: it sends only plain Chat Completions plus `response_format={"type":"json_object"}` as a syntax hint, while keeping action schema validation, selected-tool allowlist, argument validation, shell guard, repair prompts, execution, and debug/smoke gates local to Pi. - `xtalpi-pi-tools` now hard-pins runtime tool coordination to local JSON action only. Old `` markup is treated as provider drift or historical artifact leakage, then repaired back to JSON action instead of being available as a fallback protocol. - `xtalpi-pi-tools` final-answer protocol boundary is now centralized in `protocol-boundary.ts`, covering JSON object/array pseudo tool calls, OpenAI `tool_calls`, `function_call`, reserved `until_done_*` calls, and dynamically selected extension tools without relying on a fixed tool-name allowlist. - Bash and PowerShell xtalpi smoke summarizers now reuse the same protocol-boundary semantics and fail final-answer quality when tool-call-like JSON/protocol content appears in final text, while preserving ordinary business JSON as valid answer text. - `xtalpi-pi-tools` now safely recovers malformed JSON-action `final` envelopes whose text contains unescaped quotes, then routes the recovered text through the normal final-answer guard instead of exhausting invalid-JSON repair; malformed `tool_call` envelopes still fail closed. - `xtalpi-pi-tools` JSON action parsing now strips Markdown code fences before protocol validation, so fenced local JSON actions remain on the normal parser path while fenced legacy protocol markup is still rejected. - `full-suite-strict` smoke trend gates now treat bounded local repair as an operationally acceptable provider success path while continuing to gate empty finals, raw tool markup, process failures, provider errors, case-set drift, and excessive repair rates. - PowerShell `pi67-xtalpi-pi-tools-smoke.ps1` now includes the two-turn `until-done-continuation` targeted case, matching the documented Windows command and preventing it from failing as an unknown case. - Install, update, doctor, smoke, and release-check flows now include the `pi-until-done` runtime queue compatibility check/patch so `/until-done` no longer regresses after a normal pi-67 update. - Pi extension dependency baselines now track the current `pi-subagents`, `@narumitw/pi-plan-mode`, and `@narumitw/pi-btw` releases so `pi67-update.ps1` no longer reverts those packages behind Pi's own extension-update check. ## [0.10.0] - 2026-07-02 ### Added - `extensions/xtalpi-pi-tools/` as the new xtalpi provider that keeps tool calling local to Pi and sends only plain chat messages to the company proxy. - `scripts/pi67-xtalpi-pi-tools.sh` stable launcher for `xtalpi-pi-tools/deepseek-v4-pro`. - `scripts/pi67-test-xtalpi-pi-tools.sh` protocol/unit coverage for parser, serializer, and no-native-tools payload invariants. - `scripts/pi67-xtalpi-pi-tools-smoke.sh` live smoke coverage for no-tool, bash, read, and web/read tasks. - `scripts/pi67-smoke.ps1` as a PowerShell-native Windows smoke entrypoint for repo metadata, JSON, Node helper, xtalpi endpoint-contract, documentation, and portability checks. - `scripts/pi67-update.ps1` as a PowerShell-native Windows updater that preserves local config, syncs npm/shared skills, runs PowerShell smoke, writes `pi67-report.json`, and auto-backs up narrow known xtalpi migration conflicts before pulling. - `scripts/pi67-doctor.ps1` as a PowerShell-native Windows readiness doctor for local config, npm sync, shared skills, Node engine warnings, and the xtalpi `/chat/completions` endpoint contract. - `scripts/pi67-report.ps1` as a PowerShell-native report writer that emits `pi67-report/v2` and embeds the PowerShell doctor by default. - `scripts/pi67-json-utils.cjs` and `scripts/pi67-json-utils.ps1` as shared JSON compatibility helpers for UTF-8 BOM, UTF-16, and leading NUL byte recovery. - `scripts/pi67-xtalpi-pi-tools-debug-summary.sh` for summarizing live smoke debug telemetry and recovery events. - `scripts/pi67-validate-xtalpi-provider-error-contract.mjs` for standalone provider error contract validation. - `extensions/xtalpi-pi-tools/fixtures/replay-cases.json` for parser/provider replay regression cases. - `extensions/xtalpi-pi-tools/provider-error-contract.json` as the shared provider error classification and health-retry contract. - `docs/xtalpi-pi-tools.md` documenting the local tool protocol, runtime knobs, migration, and validation flow. ### Changed - Default provider is now `xtalpi-pi-tools` with `deepseek-v4-pro` and thinking off. - Update helpers now run npm sync with `--no-audit --no-fund --prefer-offline` and continue skipping npm entirely when `npm/package.json` already matches the repo `package.json`. - PowerShell update `-CheckOnly` now reports `pi67-report.json` freshness, and `-NoReport` / `-NoDoctor` allow faster or lower-risk Windows update runs. - Windows documentation now treats PowerShell as the primary path and stops presenting an extra Unix-like shell as the default Windows entrypoint. - `models.example.json` now keeps only one xtalpi provider template: `xtalpi-pi-tools`. - `scripts/pi67-configure.sh` migrates old `xtalpi` / `xtalpi-tools` keys and baseUrl into `xtalpi-pi-tools`, then removes old xtalpi provider entries by default. - `scripts/pi67-update.sh` now runs a no-prompt config migration step after updates, so existing installs converge to `xtalpi-pi-tools` without a separate manual command. - Release and smoke checks now validate `xtalpi-pi-tools` artifacts and no-native-tools payload invariants. - `xtalpi-pi-tools` now executes only the selected tools shown to the model and marks tool results as untrusted data to reduce prompt-injection and protocol-boundary confusion. - `xtalpi-pi-tools` now repairs function-style pseudo tool calls such as `fetch_content({...})`, and live smoke checks require expected tool execution events instead of accepting any final text. - `xtalpi-pi-tools` now validates tool arguments against a lightweight JSON Schema subset before execution and repairs obvious schema mismatches locally. - `xtalpi-pi-tools` debug output now emits a stable redacted JSONL schema, and the live smoke checks validate debug telemetry plus recovery-event summaries. - Tool metadata, tool-call history, and repair prompts now neutralize local protocol markers before sending text to xtalpi, reducing injection risk from malformed tool descriptions or bad model output. - `scripts/pi67-test-xtalpi-pi-tools.sh` now replays fixture-backed bad-output cases, so real parser/provider regressions are easier to extend without bloating test code. - `scripts/pi67-xtalpi-pi-tools-smoke.sh` now includes a local bash/read multi-tool case and finishes with thresholded debug-summary gating for the latest smoke run. - `xtalpi-pi-tools` now accepts the common `{"arg":...}` variant as a local tool call, repairs raw Pi protocol markup leaked into final answers, and the live smoke rejects any remaining raw markup. - `scripts/pi67-test-xtalpi-pi-tools.sh` now runs smoke/debug-summary self-tests, so tool-boundary and artifact-threshold gates have offline regression coverage. - `xtalpi-pi-tools` now neutralizes attributed Pi protocol tags inside untrusted tool output, closing a prompt-injection gap around `` variants. - `xtalpi-pi-tools` now treats incomplete Pi protocol tag fragments as raw markup, so malformed `