v0.3.0
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).
Unreleased
0.3.0 - 2026-08-27
Added
- R2 文件落地(ADR 0005、Entry 術語) (#52):
CONTEXT.md新增Entry Acquisition與Entry Pin正典詞條,並同步更新Marketplace Entry、Acquisition Trust Base與Unavailable Entry描述。- 新增架構決策記錄:
ADR 0005(0005-entry-acquisition-trust-boundary.md),詳述 Entry 級取得之信任邊界(重用既有 Acquisition Trust Base)、零執行安全承諾、command來源永久不合格理由、HTTPS shorthand 正規化、Pin 矩陣映射與漂移更新語意。
- Entry Acquisition 接入雙格式與 Refresh 流程 (#51):
- 接合 Claude marketplace
github/url/git-subdir與 Codex git-kind 條目取得。 - 於 Registration Confirmation 持久化每項 entry 的
entrySnapshots獨立快照。 - 整合 Marketplace Refresh:可動 ref 在上游漂移時產生 Update Candidate,sha-pinned 條目不產生 candidate;Update Plan 與 Apply Update 實施原子處置與快取 pin 保留。
npm、archive與command來源一致披露為 Unavailable Entry。
- 接合 Claude marketplace
- Entry Acquisition 引擎(git 家族 entry) (#50):
- 實作格式中立的 Entry 級取得引擎(
src/registration/entry-acquisition.ts)。 - 支援
github(含 owner/repo shorthand 展開為 canonical HTTPS 定位器)、url、git-subdir(含子目錄 containment 驗證)。 - Selector 映射與 Pin 矩陣:
sha→commit、ref→branch/tag、皆無→可動 default;並存時sha為有效 pin、ref僅作格式檢驗。 - 嚴格 Acquisition Trust Base(
StrictHostKeyChecking=yes、core.hooksPath=/dev/null、GIT_LFS_SKIP_SMUDGE=1)與 Validation Budget fail-closed 約束。 - 批次取得原子性:任一 entry 失敗或超限即整批 fail-closed 並自動清理暫存目錄。
- 實作格式中立的 Entry 級取得引擎(
- R1 文件落地(CONTEXT.md、ADR×2、README) (#49):
CONTEXT.md術語修訂與新增:Marketplace Catalog收編.claude-plugin/marketplace.json、Compatibility Profile改述 v2 雙格式契約、Marketplace與Plugin去除 Codex-format 限定、Unavailable Entry擴充結構化原因分類表、Skill Agent Profile明示 Codex 專屬(Claude 下視為一般 Skill Resource)、新增Marketplace Format正典詞條。- 新增架構決策記錄:
ADR 0003(雙格式偵測與 codex 優先)與ADR 0004(統一 Compatibility Profile v2 取代凍結 v1)。 README.md與package.json描述全面更新反映 Codex 與 Claude 雙格式支援(套件名稱與/codex-marketplace指令維持不變)。
- Claude 外掛完整生命週期與驗收劇本 (#48):
- Claude 安裝生命週期完備:
Install Disabled建立 disabled 狀態(無須 Activation Confirmation);啟用經由preflightPluginEnable重新驗證並要求Activation Confirmation(Default No)。 - Runtime Application 與投影:安裝啟用後
projectEffectiveState及discoverProjectedSkillPaths動態貢獻 Claude plugins 的宣告技能目錄,並遵循Pi → Global優先序。 - Runtime Skill Collision 如實裁決:本地 Pi 原生 skill 優先保留,碰撞之 Bridge 候選標示為
unavailable-collision,未碰撞技能正常投影,外掛分類不受影響保持Compatible。 - Refresh 與 Update Plan:上游變更產生 format-bound
Update Candidate;buildUpdatePlan與applyUpdate遵循全有全無原子提交,要求重新 Registration Confirmation 與 Activation Confirmation。 - Registration Removal 連帶級聯同 registration 下所有 Claude Installations,Global Scope 其餘註冊與安裝不受波及。
- 驗收劇本與測試:以 mattpocock-shaped fixture 完整驗證相容外掛、技能列出、同名碰撞與 TUI transaction-flow。
- Claude 安裝生命週期完備:
- 格式偵測接入登記與瀏覽流程(local + git) (#47):
- 掃描 Marketplace Root 決定性推導 Marketplace Format(codex 優先;兩種 catalog 並存時自動採用 codex,無額外提問)。
- 僅含
.claude-plugin/marketplace.json的 repo 全程可登記:format=claude固化於 Registration;兩者皆無時 CATALOG_MISSING 行為不變。 - 驗證披露、Registration Confirmation 畫面與 Attempt Receipt(Transaction Sheet、Receipt Journal、Attempt Summary 通知)顯示 Marketplace Format。
- 瀏覽(Bridge Ledger / 安裝選單)讀經註冊格式:Compatible entry 顯示外掛與技能清單,不合格 entry 顯示 Unavailable 原因;上游格式翻轉不被靜默採用,僅經 Marketplace Refresh 產生的 Update Candidate 加上明確 Apply Update 變更。
- transaction-flow 測試以 mock Git executor 完整登記仿 mattpocock 夾具成功。
- Claude catalog 結構解析器 (#46):
- 實作
.claude-plugin/marketplace.json結構解析器與 fail-closed 欄位政策。 - 雙格式 Marketplace Entry ID 一致收斂為
/plugins/<zero-based ordinal>。 - 第一天本地相對路徑(
./開頭)分流為 locatable entry,非 git 家族、entry-defined (strict:false)、bare name/pluginRoot 與外部 git 來源產生結構化 Unavailable Entry 原因,command來源永久不合格。
- 實作
- Compatibility Profile v2 (#45):
- 推出單一統一 Compatibility Profile v2 與 Validation Ruleset v2,收斂 Codex 與 Claude 雙格式外掛契約。
- Manifest 欄位三分法:未知欄位 fail-closed Blocking、主動元件 Blocking、已知慣性呈現欄位 Validation Warning;Claude entry
metadata物件視為 Inert Metadata。 SKILL.mdfrontmatter 實施白名單(僅允許name,description,disable-model-invocation)。
Changed
- Bridge State Schema v3 + format 屬性遷移 (#44):
schemaVersion升為3。Registration記錄新增 Marketplace Format 屬性(codex | claude)——本票只鋪持久層地基,格式偵測與 claude 解析由後續票交付。- v2 → v3 WAL migration 為既有 Registration 自動補上
format=codex預設值,內容零損失(已宣告的codex | claude值原樣保留)。 - 新寫入的 Registration 可承載
format=claude並正確回讀。
0.2.0 - 2026-08-26
Removed (Breaking)
- Project Scope 與多範圍架構退休(Global-only simplification) (#58, #61, ADR 0002):
- 徹底移除多範圍維度,Bridge State 轉為單一 Global Scope 管理(
~/.pi/agent/codex-marketplace/state.json)。 - 磁碟上殘留的既有 project state 檔(
{cwd}/.pi/codex-marketplace/state.json)完全無視(不讀、不提示、不刪)。 - 刪除內部 API 之
Scopetype 與'global' | 'project'參數;路徑、store、fence、journal、reconciliation 全部收斂為單一全域實例。 - 移除約 1,800 行專屬 project 模組(
src/projection/overrides.ts、src/projection/project.ts、src/barrier/global-barrier.ts等)。
- 徹底移除多範圍維度,Bridge State 轉為單一 Global Scope 管理(
- Scope Override 功能端到端退休 (#59):
- 移除 overrides 核心模組與 TUI「Scope 與繼承」分區、建立/移除 Scope Override 動作與 inherited/suppresses 標記。
- 繼承自 Global 的 Registration / Installation 一律參與 Effective State,無任何抑制路徑。
- Global Pending Barrier 端到端退休 (#60):
- 刪除 barrier 核心模組(
src/barrier/global-barrier.ts)與全部呼叫點;Attempt Fence 取得前不再檢查 barrier。 BARRIER-01finding code/rule/ui-strings 文案全數清除;Pending Application 復原語意由既有 active recovery chain(如 Retry Application)承擔。
- 刪除 barrier 核心模組(
Changed
- Bridge State Schema v2 + WAL Migration (#63):
schemaVersion升為2。- v1 → v2 WAL migration 剝除
scopeOverrides死欄位;非空 overrides 剝除並產出 non-blockingMIGRATE-01診斷 finding(不 fail-closed)。 - 規範化 Installation ID:自動剝除舊版
global/前綴。
- Runtime Skill Collision 簡化為兩層 (#61):
- 碰撞解析由
Pi → Project Scope → Global Scope三層收斂為Pi → Global Scope兩層。 - 任何已啟用的 Global Plugin skill 只要未與 Pi 原生/本機 skill 碰撞即正常暴露;同層 Bridge 碰撞者皆為 unavailable。
- 碰撞解析由
- TUI Bridge Ledger 單軌收斂 (#62):
- 移除 Project 軌、G/P marker、
g/p瀏覽焦點鍵與 Trust/Barrier 指示區。 - 導航重整為 Observe、Sources、Plugins、Recovery & receipts 四大正典群組。
- 移除 Project 軌、G/P marker、
- 文件與版本定錨 (#64):
- README 全面改寫為單一 Global 行為,釐清
pi install -l屬 Pi host 套件位置,更新 v2 schema 與 TUI 導覽說明。 package.json版本定錨為0.2.0,description 移除多範圍字樣。
- README 全面改寫為單一 Global 行為,釐清
0.1.10 - 2026-08-25
Added
- Runtime Skill Exposure (#54):Bridge Extension 實作 host 資源發現接縫(
pi.on("resources_discover")回傳skillPaths,startup 與 reload 兩種 reason 皆支援),依當下 Effective State(enabled Installation 減去 Scope Override 與 Project Trust 排除)之 Runtime Skill Collision 存活者,動態貢獻 skill 目錄——Git Registration 直接指向 Source Cache 中其 Validation Snapshot fingerprint 對應 entry 內的個別 skill 目錄,Local Registration 指向 live Marketplace Root;路徑解析重用 retained catalog + Contained Path 解析。發現時僅做被動存在性檢查:不重算指紋、不改動 Bridge State、不產生任何 Attempt Receipt;快取 entry 遭外部刪除時逐項略過且 discovery 必定完成(SOURCE_REACQUISITION_REQUIRED/SOURCE_DRIFT仍由 Lifecycle Operations 產生)。新增領域模組src/projection/exposure.ts(ADR 0001)。 - Invocation Policy advisory warning(COMP-W02) (#55):當
agents/openai.yaml宣告allow_implicit_invocation: false且 Skill Descriptor 未宣告disable-model-invocation時,驗證產出非 blocking 的UNENFORCEABLE_INVOCATION_POLICY(COMP-W02)warning finding,outcome 引導作者在 SKILL.md frontmatter 補上disable-model-invocation: true;Effective Invocation Policy 計算與 Compatibility Verdict 不變,Registration 不因此被擋。
0.1.9 - 2026-08-24
Added
- TUI 正體中文化 (#41):新增集中式呈現字串模組
extensions/pi/ui-strings.ts(以穩定訊息 ID 索引的 zh_TW 字典,保留 locale 切換模組縫),/codex-marketplaceTUI 全部使用者可見字串改由字串模組供應——分區名與描述、列標籤、按鍵提示、狀態列、確認與 consent 文案、help 全譯;Attempt Summary/Recovery Action/Verdict 封閉值以正典在前、中文釋義在後並列(如Blocked(受阻));findings 於呈現邊界依 rule code 對應中文文案(rule code/classification/順序不變);glossary 術語(Bridge State、Receipt Journal…)維持英文;CJK 雙寬字元於 120/80/60 欄寬度安全(無溢位、面板框線完整);分派續用結構化 intent,顯示語言不影響任何行為。非 TUI 的list/inspect輸出依議題範圍維持原樣。
0.1.8 - 2026-08-24
Added
- Bridge Ledger TUI (#38): replace the flat
/codex-marketplacemenu with a responsive five-section workspace, simultaneous Global / Project authority rails, persistent Project Trust and Global Pending Barrier status, structured canonical action intents, scope-partitioned browsing focus, Entry-level Plugin rows with directly bound install paths, eligibility-aware State Repair, and 120/80/60-column keyboard navigation. - Shared Transaction Sheet (#38): present every mutation as
Intent → Validation → Consent → Plan → Commit → Receipt, preserve separate Default-No Registration / Activation confirmations, provide expandable complete disclosures, and render Durable / Findings / Runtime outcomes with terminal-safe quoting; preflight cancellation produces a durable Declined Receipt, while active Pending Application chains expose an Attempt Fence-held, exact Revision + Validation Snapshot-bound Retry Application with final pre-reload/post-reload verification (missing snapshots disable unsafe replay, interaction-time drift fails closed without reload, and reload errors remain Pending Application). Repair State also exposes safe atomic Receipt Journal reconstruction forJOURNAL-02degradation while preserving parsed active chains.
0.1.7 - 2026-08-23
Added
- Compatibility Profile v1 Skill Agent Profile (#36/#37):支援
skills/<skill>/agents/openai.yaml與 invocation policy,並以 bounded YAML parsing、Skill ownership 與 Validation Budget 拒絕不安全輸入;新增yamlruntime dependency。
0.1.6 - 2026-08-22
Added
- Git Marketplace Plugin 檢驗與安裝 (#34):接合
SourceCache(Git 定址快取)與buildGitSnapshot指紋驗證,支援 Git Marketplace 的 Plugin 檢驗、TUI 條目呈現(顯示「可安裝」)、Install Disabled/Install and Enable以及啟用(Enable)完整生命週期;快取遺失或指紋漂移時精確產生SOURCE_REACQUISITION_REQUIRED/SOURCE_DRIFTBlocking Finding。
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:
publishjobnpm 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.0withpiextension entryextensions/pi/index.ts(loaded viajiti, no build step). Published to npm withnpm publish --provenance; Git tagv0.1.0mirrors npm. - Bridge State dual-document atomic store: global
{getAgentDir()}/codex-marketplace/state.json+ project{cwd}/.pi/codex-marketplace/state.jsonwithschemaVersion=1, opaque monotonicstateRevision("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 viastate.json.wal(fsynced before commit, replayed on next read after crash, cleaned after commit). Supported forward paths only; unknown/ newerschemaVersion→incompatiblefail-closed; downgrade never writes back. - Source Acquisition: local (canonical real path) and Git (Canonical Git Locator credential-free + Normalized Git Selector
default/branchrefs/heads/*/tagrefs/tags/*/commitlower 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.) sortedclass→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 Disabledwithout Activation Confirmation vsInstall and Enablewith 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-commitref movement alone never produces a candidate), Apply Update (single WAL commit per complete Update Plan with Registration Confirmation + per-Installationupdate/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, onlyenabled,project-over-globalprecedence), 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 Scopeexact-name layering, same-scope Bridge colliders all unavailable, only surviving higher-layer skill reserves the name, lower survives when no higher contender.Availableonly 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-fingerprintflock,p50 <200mson 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/observedrevisions + 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 Stalewhen 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 toprototype/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 Pi0.84.2/ macOS / Linux / Node>=22.19.0; every row is a release gate (v*→ CI full matrix green →npm publish --provenancelatest/nextchannels,0.y/1.0maintenance windows).
What's Changed
- feat: Bridge State——Registration 新增 format 屬性與 v2→v3 遷移(#44) by @SamWang32191 in #71
- feat: Compatibility Profile v2——Claude 格式分類與規則集版本跳升 (#45) by @SamWang32191 in #72
- feat: Claude catalog 結構解析器——雙格式 Entry ID 一致、source 形態分流與 fail-closed 欄位政策(#46) by @SamWang32191 in #73
- feat: 格式偵測接入登記與瀏覽流程——codex 優先、claude 全程可註冊、披露/收據反映 Marketplace Format(#47) by @SamWang32191 in #74
- feat: Claude 外掛完整生命週期與驗收劇本——Install/Enable/Disable/Refresh 語意一致、平坦碰撞裁決與 mattpocock 劇本通過(#48) by @SamWang32191 in #75
- docs: R1 文件落地——CONTEXT.md 術語修訂、ADR 0003/0004、README 與套件描述雙格式更新(#49) by @SamWang32191 in #76
- feat: Entry Acquisition 引擎(git 家族 entry)——github/url/git-subdir 取得、Pin 矩陣、per-entry 快照與預算/信任邊界(#50) by @SamWang32191 in #77
- feat(registration): wire external git entry acquisition to dual formats and refresh by @SamWang32191 in #78
- docs: R2 文件落地——ADR 0005、Entry 術語與 CHANGELOG 記錄(#52) by @SamWang32191 in #79
Full Changelog: v0.2.0...v0.3.0