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.