v0.1.5

Changelog

All notable changes to pi-codex-marketplace are documented here. Format follows Keep a Changelog and SemVer (starting at 0.1.0; Git tags v* mirror npm versions).

0.1.5 - 2026-08-22

Fixed

• README 安裝語意：對齊 pi --help 與 docs/packages.md — pi install 需 npm: 前綴、本地路徑用 pi install ./path、臨時試用用 pi -e <source>（非 pi install -e）、update/remove/list/config 語意修正。

0.1.4 - 2026-08-22

Fixed

• publish Node 22 → 24：publish job npm 10.9.3 不支援 OIDC Trusted Publishing（需 npm 11.5.1+），改為 node 24（opencode 同款），移除臨時調試步驟。

0.1.3 - 2026-08-22

Fixed

• 調試 OIDC：新增暫時性 debug OIDC token 步驟與 verbose 日誌以定位 ENEEDAUTH。

0.1.2 - 2026-08-22

Fixed

• Trusted Publisher OIDC：對齊 opencode-roast-tone-plugin 可發版樣式 — repository.url 去除 git+ 前綴 (https://github.com/SamWang32191/pi-codex-marketplace)，publish.yml 移除 environment: npm（OIDC token 不帶 environment claim），升級 actions/checkout@v5/setup-node@v5 以匹配可發版 repo 的 proven 流程。

0.1.1 - 2026-08-22

Added

• Release skill .agents/skills/release — project skill 將發版流程固化為 v* tag → CI gate → npm provenance → GitHub Release 五步，涵蓋首發 OTP 與 OIDC Trusted Publisher 分支、常見失敗與完成條件。

0.1.0 - 2026-08-22

Initial Bridge Package release — single pi extension, Pi 0.84.2 baseline.

Added

• Bridge Package pi-codex-marketplace@0.1.0 with pi extension entry extensions/pi/index.ts (loaded via jiti, no build step). Published to npm with npm publish --provenance; Git tag v0.1.0 mirrors npm.
• Bridge State dual-document atomic store: global {getAgentDir()}/codex-marketplace/state.json + project {cwd}/.pi/codex-marketplace/state.json with schemaVersion=1, opaque monotonic stateRevision ("0"→"1"→"2"…), file lock (.lock), WAL (state.json.wal), temp→fsync→rename + dir fsync + read-after-verify. Only authoritative fields persisted; Effective State, catalogs, diagnostics derived at read time.
• WAL migration (src/bridge-state/migrate.ts): forward migrations via state.json.wal (fsynced before commit, replayed on next read after crash, cleaned after commit). Supported forward paths only; unknown/ newer schemaVersion → incompatible fail-closed; downgrade never writes back.
• Source Acquisition: local (canonical real path) and Git (Canonical Git Locator credential-free + Normalized Git Selector default/branch refs/heads/*/tag refs/tags/*/commit lower 40/64 hex) with Resolved Revision, non-executing retrieval (no hooks/filters/submodules/dependencies/Plugin components), Acquisition Trust Base validation (selected Git/SSH, system CAs, existing known-hosts, approved credential helper/agent; rejects unknown/changed host keys and locator-changing redirects).
• Validation: Validation Snapshot (ordered paths/types/modes/symlink targets/content hashes + Source Key + Canonical Locator + Resolved Revision + Compatibility Profile v1 + Ruleset + Budget fingerprints), Contained Path/Contained Symlink strict containment, Validation Budget fail-closed at boundary, ordered Findings with stable rule codes (CONT-01, COMP-02, FENCE-01, BARRIER-01, etc.) sorted class→phase→target→pointer→rule.
• Compatibility Profile v1: atomic Compatible/Incompatible/Invalid classification; closed manifest + Skill Descriptor/Body contract, Pi-native skill semantics, Inert Metadata tolerates as Warning, unknown/unsupported Active Component → Incompatible/Incompatible, no partial projection. Collision never changes Plugin classification.
• Lifecycle: Scope-local atomic Lifecycle Operations — Registration (local/Git), Installation (Install Disabled without Activation Confirmation vs Install and Enable with Activation Confirmation, re-enable re-validates), Removal (Registration cascades same-scope Installations), Rebind (fresh validation + Registration Confirmation + complete Update Plan), Marketplace Refresh (non-mutating, Update Candidate only when snapshot differs; full-commit ref movement alone never produces a candidate), Apply Update (single WAL commit per complete Update Plan with Registration Confirmation + per-Installation update/disable/remove + per-enabled Activation Confirmation), Scope Overrides (project-only sparse suppression by Registration ID / Installation ID, removal reveals inherited Global without mutating it), Read-time Effective State (global-baseline + project additions – overrides, only enabled, project-over-global precedence), Projected Skills via Pi resource-discovery seam (raw snapshot paths, Bridge-held provenance, host-verifiable reload = Applied).
• Runtime Skill Collision: skill-granular Pi → Project Scope → Global Scope exact-name layering, same-scope Bridge colliders all unavailable, only surviving higher-layer skill reserves the name, lower survives when no higher contender. Available only by independent host evidence.
• Source Cache (src/cache/): Git-only, fingerprint-addressed at {getAgentDir()}/codex-marketplace/cache, pinned set = committed Bridge State + pending Update Candidate + in-flight, total 2 GiB LRU on unpinned only, synchronous evict/prune, no background/TTL, offline reuse only on exact fingerprint hit, Stale Snapshot never becomes success. Per-fingerprint flock, p50 <200ms on hit.
• Source Drift: external local-source mutation detected as Blocking Finding, Bridge State unchanged, affected Installations not Projected until explicit Refresh produces an Update Candidate.
• Receipt Journal + Attempt Fence + Global Pending Barrier (src/journal/, src/barrier/, src/reconciliation/): immutable redacted Attempt Receipts (expected/target/observed revisions + Validation Snapshots + findings + earlier receipt recovery link), bounded durable journal with active recovery chains preserved across restarts (reconstructible from authority, prunable only outside active chain, degraded diagnosis separate from persistence outcome), per-scope Attempt Fence exclusivity and exact-state binding (Rejected as Stale when State Revision or snapshot moves, no queue), Persistence Failed (previous still verified) vs Persistence Indeterminate (neither previous nor target verifiable — blocks further Lifecycle/Runtime until readable and exact, no auto-rollback), Global Pending Barrier (global pending/indeterminate/journal-degraded blocks every project mutation/application, including Lifecycle/Repair/project startup reconciliation; inspection/Refresh remain, global-first recovery), 8 closed Attempt Summaries, closed Recovery Actions (only currently safe next step, no auto-retry), startup reconciliation (produces a new receipt for pending, no retry/rollback).
• TUI management flow (/codex-marketplace): single aggregated command faithful to prototype/tui-management-flow@c9107d2 — hybrid discovery/guided, explicit scope choice per operation, Registration/Activation separated snapshot+revision bound Default No confirmations, Update Plan Checklist, partitioned Global/Project lists, skill-granular diagnostics, synchronized Findings, closed Recovery Actions, immediate-reload three-orthogonal Receipt report, Pending/Global Barrier blocking hints.
• Verification matrix: synthetic / pinned SamWang32191/codex-plugins@98e78ca / adversarial three-tier fixtures × (unit + integration + E2E at the TUI seam) on Pi 0.84.2 / macOS / Linux / Node >=22.19.0; every row is a release gate (v* → CI full matrix green → npm publish --provenance latest/next channels, 0.y/1.0 maintenance windows).

Full Changelog: v0.1.4...v0.1.5