AID v2.0.5
AID v2.0.5 — a /aid-discover review-scope fix, companion to v2.0.4's scan-scope work: v2.0.4 stopped the scanners from walking non-source trees; v2.0.5 stops the review from grading non-knowledge files. No methodology or KB-schema changes; drop-in over v2.0.4 (aid update <tool>).
Fixed
The /aid-discover review's two keystone gates — M3 (Essence / teach-back) and M4 (Assertiveness / act-back), which force grade ≤ D — read a raw .aid/knowledge/*.md glob with no category filter. So they ingested the KB's meta process/ledger docs (STATE.md, README.md, external-sources.md — kb-category: meta) and the generated INDEX.md as if they were hand-authored project knowledge, poisoning the reconstruction / work-simulation and, through those gates, the grade itself. (The M1/M2 mandates already routed by kb-category, so only the keystone gates leaked.)
v2.0.5 introduces a single, deterministic, tag-driven definition of the reviewed knowledge surface — list_reviewable: the KB .md docs whose frontmatter is kb-category != meta AND source != generated. The review orchestrator computes this once and passes the explicit list to M3/M4 instead of the glob:
- Excludes the meta ledgers (
STATE.md,README.md,external-sources.md) and generated docs (INDEX.md); keeps all hand-authoredprimary/extensionknowledge. - Because it reads each doc's own frontmatter, it needs no hardcoded filename list and adapts if tags are corrected — a doc with no frontmatter defaults to reviewable, so the surface never silently shrinks below the primary docs.
- M2's authoring checks were clarified to apply only to Full Primary docs; M3's blind-reconstruction stage was hardened to disregard ambient host/agent instruction files (
CLAUDE.md,AGENTS.md); andbuild-project-index.sh's stale default output path was realigned to.aid/generated/so a generated index can never sit in the review surface.
Deterministic and robust: one batched awk pass (no per-file spawn), LC_ALL=C ordering, and an empty/absent KB directory returns success with empty output (never aborts the review). Verified by a new regression suite plus the full canonical suite; profiles regenerated and byte-verified against the emission manifests.
Unchanged
Methodology phases, KB schema, CLI flags, and all output contracts are identical to v2.0.0–v2.0.4.
Verify your download
sha256sum -c SHA256SUMS