Skip to content

AID v2.0.3

Choose a tag to compare

@github-actions github-actions released this 05 Jul 02:36
e949bc1

AID v2.0.3 — completes the cross-platform performance hardening begun in v2.0.1 (/aid-discover harvest) and v2.0.2 (project-index). This release extends the same fix across the entire KB / discovery / summarize toolchain: every helper an adopter runs is now fast on Windows Git Bash / MSYS. No methodology or KB-schema changes; drop-in over v2.0.2 (aid update <tool>).

The problem

On Windows Git Bash / MSYS (and cygwin), every fork()/exec costs ~0.5–1.8s — thousands of times slower than on Linux (~microseconds). Any loop that spawns a subprocess per file / per term / per line (echo | grep, $(...), per-item awk/sed/tr/wc/basename) therefore turned multi-second Linux runs into multi-minute — or hung — Windows runs. v2.0.1/v2.0.2 fixed the two hottest offenders; v2.0.3 sweeps the rest.

Fixed

Thirteen more KB/pipeline helpers were re-batched (per-item spawns → a single awk pass or bash builtins). Measured Windows speedups from testing:

  • build-kb-index.sh (RAG routing table, runs last in every discover cycle): ~8m46s → ~36s
  • closure-check.sh (concept-closure oracle): >10 min → ~14s
  • cleanup-classify.sh: ~213s → ~23s
  • kb-actback-task.sh: ~59s → ~8.5s
  • plus lint-frontmatter, build-kb-index, kb-freshness-check, kb-citation-lint, build-metrics, kb-dual-intent-probes, grade-summary, validate-html-output, build-md-export, complexity-score, and parse-recipe.

A follow-up hot-path polish pass removed the remaining incremental forks in the most-invoked scripts: read-setting.sh (lazy path resolution — called on every skill invocation), recon-classify.sh (dropped two /tmp round-trips on the discover triage path), assemble.sh, summarize-preflight.sh, and housekeep-state.sh.

Every change is byte-identical to prior output and cross-OS reproducible — verified by old-vs-new diffs on real inputs plus the full canonical test suite (Windows + Linux). No behavior, format, or contract changed; only the number of subprocesses did.

Unchanged

Methodology phases, KB schema, CLI flags, and all output contracts are identical to v2.0.0–v2.0.2. This is purely a performance patch.

Verify your download

sha256sum -c SHA256SUMS