v0.5.0 — 写入更稳，使用记录更完整

v0.5.0 把写入保护、能力检查记录、使用前后记录和可选 Hook 整理到一个正式版本中。三个 README 也重新梳理了用途和操作说明，保留原有框架与视频教程。

This release brings safer writes, identity-bound evidence, use receipts, and optional Hooks, with clearer Chinese and English guides.

主要变化

• 减少误写：旧草稿不能直接覆盖已更新的记录；失败恢复会保留其他人的并发修改，并标记需要人工处理的情况。
• 记清每次使用：新增 use-begin、use-finish，记录使用身份、验收结果和后续事项是否处理完；中断后可用 lifecycle-status 查待办。
• 复核旧证据：record-evidence 保存调用方报告的检查结果；capability-check 核对版本、明确列出的文件、项目位置、有效期、后续失败和未完成使用。
• 补上检查与提醒：可选 Git Hook 检查实际暂存内容；Codex/Grok Build Hook 示例检查未完成使用。Grok 默认只保存本地待办文件，显式启用反馈续接可能增加模型用量。
• 持续验证：Windows 和 Linux CI 运行测试、演示、入门流程、仓库及暂存区检查。

升级说明

1. 获取 v0.5.0 源码，继续使用本机已有 Python 3；核心不需要第三方 Python 包。
2. 已有 schema v3 工作流无须迁移数据。用新版 scripts/workflow.py 运行 rebuild --root <VAULT>，再运行 validate --root <VAULT>，刷新生成指引。
3. 使用 update-project 或 update-capability 的旧脚本，需要先通过 record-hash 记录原文件哈希，再传入 --expected-sha256。原记录变过时，先合并新内容，不能给旧稿直接换一个新哈希。
4. 仍使用 schema v1/v2 的工作流，按迁移说明运行 migrate-v3。新增证据和回执用独立 version 1 格式，启用后请使用新版 CLI。

检查结果由调用方执行并报告；客户端和能力版本由调用方核实，所列文件的哈希由脚本实读计算。记录通过不会自动安装、启用工具或修改等级。Hook 示例不会自动接入客户端，实际发现、信任和事件触发仍需接入后验证。

验证

• 70 项 Python 测试、1 项 Node 测试通过。
• 生成演示：2 个虚构项目、3 个虚构能力，0 错误。
• 仓库检查：155 个 Markdown 文件，包含本地 Git 历史，0 错误。
• 暂存区检查：211 个文件，0 错误。

详见完整更新记录、使用记录说明和 Hook 接入说明。

主分支发布前的 Windows/Linux CI 已通过；发布标签与该次验证的提交一致。

v0.4.0 — B-grade first-use settlement

Focus

Settle B-grade GitHub projects through task-level increment judgment and the current project's first real use, without conflating evidence grade with installation scope.

Highlights

• schema v3 adds the explicit deployment_scope axis: not-installed, project, user, global, or external-service
• migrate-v3 upgrades schema v1/v2 roots transactionally and never infers deployment scope
• capability-deployment records approved deployment facts but never installs or removes files
• method-only B projects remain reference-only; low-risk executable candidates use T0, approved project scope, and the current project's first real task as T1
• T1 success settles to A/retained + active/project; failure or an inconclusive result stays B/reference with an uninstall recommendation
• Grok Build and Codex share the maintained repo-scoped Skill, with Claude Code retained as a compatibility path
• no durable project-trial state is introduced, and grade A never means global installation

Upgrade

Existing schema v1/v2 workflow roots must follow the v0.3 to v0.4 migration guide and supply one explicit deployment scope for every capability.

Validation

• Python unit tests: 23/23 passed
• Node audit tests: 1/1 passed
• generated schema v3 demo: 2 projects, 1 semantic project, 3 capabilities, 0 errors
• repository validation: 141 Markdown files, full Git history scanned, 0 errors
• git diff --check: passed

See the full changelog.

v0.3.0 — Mandatory thin discovery routing

What's Changed

v0.3.0 introduces mandatory thin-discovery routing, separating lightweight capability discovery from deeper repository reading and execution.

Highlights

• Added one distinct capability_summary for every eligible project.
• Added a mandatory Level 0 thin-discovery table before full semantic routing.
• Allowed both high_confidence and gated capabilities to appear during discovery.
• Kept repository reading, installation, enablement, and execution behind their existing gates.
• Added transactional migration from schema v0.2 to v0.3.
• Updated schemas, templates, documentation, repo-scoped skills, and the public demo.
• Improved repository-history privacy validation for normal clones and Git worktrees.

Validation

• 20 Python tests passed.
• Schema v2 demo validation completed with 0 errors.
• 124 Markdown files and Git history validated with 0 errors.
• Node integration tests passed.
• git diff --check passed.

Full Changelog: v0.2.0...v0.3.0

v0.2.0 — Deterministic intake and semantic project routing

v0.2.0 turns the original Markdown starter kit into a deterministic, cross-client workflow for GitHub project intake, capability governance, and semantic project suggestions.

New in v0.2.0

Area	Added in this release
Deterministic intake	Dependency-free CLI, versioned schemas, explicit state machines, transactions, generated indexes, and validation
Semantic project routing	Ordinary-language examples, trigger levels, negative routing, exactly one generated row per eligible S/A/B formal project, and duplicate/staleness detection
Agent bootstrap	One-link bootstrap plus repository-scoped Codex and Claude Code Skills
Safety controls	Read-only project suggestions, explicit no-extra-project, protected write-back, approval gates, health quarantine, and full-history privacy scanning
Cross-client audit	PR #1's optional read-only audit, repaired for native command discovery on Windows, macOS, and Linux
Adoption and maintenance	CLI-generated demo, five Golden Examples, v0.1-to-v0.2 migration guide, bilingual docs, and an optional approval-gated pre-commit hook

Important boundaries

• Semantic routing suggests a project reference; it does not activate an executable capability.
• Installation, login, publication, deletion, and configuration changes remain confirmation-gated.
• The optional pre-commit hook is included but is not enabled automatically.
• No private vault data, personal paths, secrets, or local settings are included.

Validation

• 18 Python unit tests passed.
• 1 Node audit test and the Node syntax check passed.
• Generated demo: 2 projects / 1 semantic project / 3 capabilities / 0 errors.
• Repository audit: 105 Markdown files, generated-file freshness, links/tree/JSON/schema checks, and full Git-history privacy scan / 0 errors.

Upgrade notes

Existing v0.1 records remain usable. To adopt the new deterministic workflow and semantic routing, follow docs/migration-v0.1-to-v0.2.md and rebuild the generated indexes after adding the required semantic fields to eligible formal project cards.

Thanks to @Calvingen3 for the optional read-only capability audit contributed in PR #1 and preserved in this release.

v0.1.0 — First public release

Markdown-first, prompt-triggered workflow for GitHub project intake, capability cold storage, and agent routing (Obsidian + Codex / Claude Code / other coding agents).

What's included

• Mechanism docs ×4: how it works · what your agent actually sees (context & routing) · privacy & sanitization · customization
• Intake screening prompt: prompts/github-intake-prompt.md
• Templates: capability router · capability manifest · GitHub project card
• Bilingual README (EN / 中文) with zero-install Quick Start — just hand the Markdown to your agent

Companion videos (中文)

• Part 1 · Why you shouldn't install every "must-have" AI tool
• Part 2 · The capability cold-vault workflow behind this repo

发命令后由 Agent 自动入库 + 能力冷库与薄路由。零安装：把仓库链接或 Markdown 丢给你的 agent 即可开始。