v0.2.0

37 commits since v0.1.0. Headline: How-L1 shipped, cross-file citation resolution (R9/Phase B) closed the single-hop/same-file limitation, an installer exists, and the protocol's evidence base grew from four synthetic demos to three real-world dogfood case studies with tool-measured token-reduction and fallback-relevance numbers.

Added
install.sh / install.ps1: the installer promised by several SKILL.md files and ROADMAP.md's former top-priority item. Copies .github/skills/, .github/prompts/, .cursor/rules/, and AGENTS.md (merged into a marked block, not overwritten wholesale) into a target project directory; with --init-project/-InitProject, also scaffolds context-config.yaml from the template and starter_kit/project_guidelines/.pointer.md, each only if not already present. Supports --dry-run/-DryRun and requires an explicit, existing --target/-TargetPath. Re-running is idempotent and never clobbers project-owned files. --only/-Only (ROADMAP item 2) narrows a run to specific skills instead of installing all of them.
How-L1 (piloting): deterministic, zero-LLM structural indexing of external org-wide process-standard .md references (CMMI/ISO 9001/IEEE, etc. — reuses md_index.py, the same mechanism as What-L1), gap-triggered off Step 2's existing How-L2 org-convention check and scoped once per package/task-type rather than per aspect, with no web-search fallback chain of its own — Step 2's existing best-practice-template prompt substitutes for one. Gated for human review at Step 9 like every other fallback layer.
Cross-file citation resolution (ROADMAP item 1 / R9, Phase B): a cross-ref naming a document designator (e.g. IEEE 802.11-2020 §9.3.2) now resolves across files, joined via each target file's doc_id front matter — closing 0.1.0's disclosed "single-hop/same-file only" limitation. Same-file refs are unaffected; a designator with no matching doc_id stays resolved: false with resolution_status: "unresolved-doc-not-found". See examples/cross-file-resolution-demo/ for the worked resolved/doc-not-found/doc-ambiguous/clause-not-found cases.
MCP-backed What-L1/How-L1 sourcing (ROADMAP items 9/11): scripts/mcp_mirror.py mirrors MCP-fetched content into local .md files gated by content-hash comparison instead of mtime, so md_index.py's existing --stale-check picks up upstream changes with zero changes to md_index.py itself. Wired in as a new Step 0 in both references/what-l1-fallback-query.md and references/how-l1-fallback-query.md, gated on what_l1.mcp_source/how_l1.mcp_source (default []) — a project that never configures an MCP source sees zero behavior change. See examples/mcp-what-l1-demo/WALKTHROUGH.md for a validated, real-command round trip.
Project memory feedback loop (ROADMAP item 6) and context-package usage aggregation report (ROADMAP item 7) for ult-context-generate — scripts/usage_report.py scans real contexts/.yaml/.addenda.yaml files to report whether assembled context items are actually cited downstream or sit unused.
ult-repo-layout: layer-path discovery engine and confirm-layers human-approval step with drift tracking (D23 S17.2–S17.8), plus per-candidate include_roots validation and further drift tracking (S40).
Three real-world dogfood case studies (CEP-DP-001D) replacing/augmenting the four synthetic demos as the project's evidence base: Open5GS + RFC 6733 (S6a Error-Message AVP gap), FastAPI + OpenAPI (callbacks/links parity gap), and Textual (ordinary run + a deliberate negative-control run) — plus a shared case-study methodology template.
Real token-efficiency and fallback-relevance evidence: graphify benchmark run for real for the first time against all three case studies' graphs (36.8x / 5.6x / 39.6x fewer tokens/query), and a new naive-keyword-search baseline (EVIDENCE-METHODOLOGY.md §4) measuring whether the naive search a developer would try first actually finds what CEP found — closing both evidence gaps §1 previously named as open. See case-studies/SYNTHESIS.md for the cross-case synthesis and the README's new "Measured impact" table.
CONFORMANCE.md: a CEP Conformance Specification — how to check whether an implementation actually conforms to PROTOCOL.md.
GLOSSARY.md, RFC 2119 (MUST/SHOULD/MAY) markup on the protocol's state machine, and new PROTOCOL.md sections on lifecycle, roles, and open questions.
EVIDENCE-METHODOLOGY.md, a reproducibility guide, and an evidence-record template (references/) defining what "measured" vs. "self-reported" vs. "inference" means in this project's documentation, and how to reproduce every measurement named in it.
README hero banner and "Measured impact" table summarizing the three case studies' real, tool-measured numbers up front.
Fixed
graphify merge-graphs multi-root crash: was a stale local install, not an unfixed upstream bug — graphify >= 0.9.11 persists the directed/multigraph keys the merge needs and composes correctly. ult-codegraph/SKILL.md now documents multi-root indexing + merge as a supported path and requires >= 0.9.11. See ROADMAP.md item 4.
md_index.py query ranking: fixed a ranking bug and added a warning on low heading density; a later fix boosts title matches so a heading whose own title contains the query terms ranks ahead of a same-count body match. Also documents a graphify ID-collision fix.
Same-file clause-id ambiguity is now surfaced rather than silently resolved to whichever heading came first — a cross-ref matching two headings in the same file is kept with resolved: false / resolution_status: unresolved-ambiguous.
install.ps1's directory copy made cross-platform.
Doc-audit pass: a full one-by-one review of every .md file in the repo for currency ahead of this release — reconciled stale node/edge counts and citations to files that don't exist, re-ran and recaptured every examples/*/WALKTHROUGH.md's tool output against the current md_index.py/mcp_mirror.py behavior, fixed several docs that described R4/R9 as future work after they had already shipped, and added missing cross-references (CONFORMANCE.md, the 4th CI check, ROADMAP.md item 14) across PROTOCOL.md, EVIDENCE-METHODOLOGY.md, CONTRIBUTING.md, and several skill references.
Known limitations (disclosed, not regressions)
How-L1 is piloting, not yet field-validated against a real corpus (ROADMAP.md item 13).
Cross-file citation resolution requires a doc_id join key on the target file's front matter; a target indexed without one can never be matched even if the clause exists.
No capability-profile / tool-restriction frontmatter field exists yet on any skill (ROADMAP.md item 14).
Cursor's adapter is generated and doc-verified but not field-tested against a live install.
No real 3GPP corpus exists yet for a domain-specific ult-codegraph example (ROADMAP.md item 8); the Open5GS case study is real telecom code but general-purpose graph structure.