Skip to content

sairaisaika/project-wiki

v0.2.19MIT

Source-backed Wiki structure, task routing, change review and agent handoffs.

Changelog

Reviewed: 2026-11-03 against c062224

Version history, newest first. Current per-version status (CI, main, package, installation, hooks, use) is one table in docs/wiki/status.md; evidence lives in evals/reports/. The fuller per-version plan narrative stays in docs/PLUGIN_PLAN.md and the session log in PROJECT.md » History; entries below point to them instead of copying them.

The version entries from 0.2.19 down to 0.2.6 were moved from README.md on 2026-11-03 (spacing normalized); the former README section "Historical source and host observations" became these version entries. The following notes describe their own revisions and host scopes, not the current installation state of every reader.

Unreleased (still identified as 0.2.19)

Payload changes after the pinned ee6c065 copies, with no version bump: split-owner handoff guidance (2026-10-30); rule-based routing, invariant tables and five-layer miss classification (2026-10-31); the optional Claude pre-edit gate project-wiki/scripts/edit_gate.py with PreToolUse in hooks/claude.json (2026-11-02, see maintenance.md » Pre-edit gate); consumer matrices and probe validation (2026-11-02); pilot-project references neutralized in the guides (2026-11-01). Session log: PROJECT.md » History (2026-10-30 to 2026-11-02).

0.2.19

0.2.19 is a source candidate for the evolution workflow, exercised in real product and Wiki-maintenance tasks with independent rework retained. Skill-only copies pinned to ee6c065 now match all 19 source files on the selected Mac Codex and Linux Claude hosts; the new Claude invocation advertised and natively loaded the skill. The subsequent Mac catalog also advertises it and Root read the installed entry. Correct adoption and lower rework/context cost remain separate checks. No plugin hooks, trust or access settings changed. See the plan and evaluation.

0.2.18

0.2.18 source candidate adds a private-safe item ordinal to selected-evidence file refusals, preserving their existing prefix and refusal policy. The ordinal follows the current checkpoint list, not always original CLI order; see selected evidence and the bounded evaluation. At its initial checkpoint, installation/publication and independent real-task adoption remained pending. The linked evaluation and this repository's PR #40 record the later scoped mobile adoption and cross-platform CI. That change did not alter skill instructions, hooks or host trust settings.

0.2.17

0.2.17 candidate lets doctor read an explicitly supplied Codex hooks/list snapshot alongside matching installation inventory. It reports one working directory's plugin SessionStart enabled/trust state and lexical source association; it never grants trust or claims execution, context delivery or use. Received paths and commands are not opened or executed. See the bounded design and acceptance plan. The bounded replay separates package/source checks from a supplied real host observation. Source, package, installed host and actual lifecycle acceptance remain separate.

Normal source/main CI and one official Windows installation of 0.2.17 are now verified. The installed doctor consumed a fresh host listing and reported the selected SessionStart as enabled/trusted while leaving execution/delivery/use unverified. Hook definitions and the delivery script were unchanged; no trust settings or running scoped worker were modified. See the bounded host adoption return.

0.2.16

0.2.16 candidate adds an explicit coordinator capture-return command. It derives every actual root/peer diff file through the same collector as final reconciliation, then invokes the reviewed native router with explicit opt-in. Unplanned files, missing peers and selected evidence remain visible to the original gates; source or scope drift during capture refuses the operation without automatic retry. Review, source/main adoption, host installation and product acceptance remain separate. See the bounded actual-return case.

0.2.15

0.2.15 candidate shows the existing unchanged-return predicate at read-only task creation and delegation. A dirty baseline now receives an early advisory; final reconciliation, permissions and snapshot-only reader limits stay intact. Source tests and package checks are separate from installation and host delivery.

0.2.14

0.2.14 makes repeated capture --files groups accumulate instead of silently replacing earlier paths. The native router receives the complete normalized selection; permissions and semantic completion remain separate. See the retained CLI counterexample. Source/main CI and one official Windows installation are verified. The actual installed CLI preserves repeated and later-empty groups; the prior installed copy loses them. At the recorded host cutoff, the new hook is modified and awaits normal user review; installation does not imply trust or automatic context delivery. The same report separates these observations from semantic use.

0.2.13

0.2.13 candidate exposes the saved Wiki path base in every reading view. A normal trusted host delivery exercise succeeded, but its reader initially opened native page keys at the checkout root instead of the Wiki root. The new metadata uses the existing captured base, retains native keys and snapshot-only limits, and does not add a new router. See the bounded case and scope.

0.2.12

0.2.12 candidate adapts the optional hook package container to the observed Codex 0.160 loader: --with-lifecycle-hooks emits legacy host manifests, while plain packages stay portable. One canonical identity/skill/workflow is retained. The version-matched upstream loader explicitly skips portable AgentPlugin hooks; the actual installed old/new-declaration probes both returned no hooks. See the evidence and remaining runtime acceptance. Normal source/main adoption and official Windows installation are now verified. At that 0.2.12 checkpoint, the host discovered SessionStart as untrusted; automatic execution and use are still awaiting normal review and their own evidence. See the bounded adoption return.

0.2.11

0.2.11 candidate declares optional Codex hooks explicitly in the portable root manifest, with a named source-to-package projection and legacy receipt support. This follows an actual 0.2.10 installation whose hook list was empty; source/package checks are not runtime discovery. See the observation and remaining acceptance.

0.2.10

0.2.10 candidate adds an optional internal lifecycle-delivery package profile: python scripts/package_plugin.py --with-lifecycle-hooks --output <new-directory>. Startup/resume/compaction can deliver an explicitly selected saved task through the existing snapshot reader. The default package stays skill-only; no trust, installation, native execution or completion policy is changed by packaging. See scope and host requirements. Source tests, package closure and actual trusted host triggering remain separate.

0.2.9

0.2.9 adds explicit show --snapshot-only for readers forbidden to invoke Git. It renders the saved task records without live input checks and clearly labels currentness as unchecked; default display, dispatch and return guards stay in place. See permission-separated reading and the bounded evaluation. Source/main adoption and one official Windows update to 0.2.9 are now recorded in the bounded adoption return. Installed doctor/helper use and a delivered skill-catalog entry were observed; hooks, trust, automatic lifecycle and business acceptance remain separate. The active scoped Claude worker remains 0.2.4.

The following README overview paragraphs were last revised at the 0.2.9 identity and are kept here as written:

内部协作插件计划:以现有 Skill/工具为唯一内核,补可复现打包、来源自检与宿主接线,再用真实工程验证开工、委派、收尾与接管。内部插件已在一台 Codex 主机通过官方 CLI 安装并核对缓存,Linux Claude 已做临时加载与真实任务试用;桌面自动生命周期、hooks 与完整跨宿主验收仍待,未公开发布到插件目录。根 plugin.json 是身份源,不能单凭它声称运行已验证。0.2.9源码已正常采用,一台 Windows 宿主已更新并实际调用;目录送达、主动读取、hooks 与自动接管分别核验;换行来源机制保留原始输入指纹,区分规范文本来源一致与包文件字节完整;有限宿主采用记录另证历史官方 Windows CLI 安装0.2.5及实际有限使用。既有 scoped 0.2.4 工程任务不由此自动升级。

协作工作流提供原生任务 JSON 的快照、任务包、范围受限的委派和真实 diff 收尾;全部卫星、能力缺口、未展开候选与跨仓版本保留。脚本不派 agent、不自动执行页内检查,也不把结构闭环认证成业务完成。内部插件已有限采用,宿主生命周期与项目试用按计划分别验收。

协同仓库开工时,先核项目实际支持的来源选择参数。原生命令退出成功或印记有效,仍可能读了默认旧仓库;若原生报告提供来源身份,声明 peer 后使用所选来源核对,在派工前比较真实 root / HEAD。C116 使用复盘保留一次协调者误传环境变量的失败与已有核对能力的实际拒收;这是调用方法修正,没有新增插件或修改宿主。

0.2.8

0.2.8 adds optional checkpoint hash observations for explicitly selected historical evidence files, including private files outside Git. The original capture/delegate/return workflow refuses a changed or dropped selection; it does not prevent writes, continuously monitor files or certify business completion. See selected evidence. Source/package/host adoption remain separate. Its later bounded 0.2.8 host receipt is distinguished from the historical 0.2.7 exercise below.

0.2.7

0.2.7 adds an optional comparison between the native router's reported checkout identities and explicitly selected task peers. The C91 exercise preserves the real mismatch and first policy-retention failure, then records the actual CLI/full-suite/package checks, normal source/main adoption and one official Windows update to 0.2.7. A real task started using the installed helper's bytes with strict native-source comparison. Scoped 0.2.4 workers remain pinned; automatic host lifecycle, physical reads and semantic adoption stay separate.

0.2.6

Historical 0.2.6 source was normally adopted and one Windows host was updated through the official CLI, with installed bytes/source and inventory/version observations checked separately. The new doctor only reads caller-captured host evidence; installation/enabling does not establish hook execution or agent adoption. Running scoped workers were not upgraded. See actual host adoption and doctor observations.

0.2.5 and earlier

README carried no separate entry for these versions. Pointers only: