v0.14.10 — .moa_cache/ self-documentation
What's new
moa-bridge as an open-source plugin that writes into the user's workspace now self-documents those writes at the point of impact.
Added
src/cacheReadme.ts(new module): exportsensureCacheReadme()— idempotent, atomic write (tmp+rename), fails silently toconsole.warn- Three-point integration: every code path that creates
.moa_cache/now callsensureCacheReadme()on first creation:l3Summarizer.ts::getCacheDir()moaOrchestrator.ts::getCacheRoot()moaRunner.ts::getReconDumpDir()
- Auto-generated
.moa_cache/README.md(bilingual, Chinese-primary) covers:- Directory layout (
recon//l3_summaries//<task_id>/) - Diagnostics (how to trace a weird @moa output; 1213 Part Diagnostics)
- Cleanup strategies (whole / per-subdir / extract-then-delete)
.gitignorerecommendation- Configuration reference (every
moa.*setting that influences writes) - Privacy notes
- Directory layout (
Changed
- Main README: new "Local cache & workspace artifacts" section
- CHANGELOG: filled in v0.14.7-v0.14.9 history (including v0.14.8 YANKED)
package.json: fixed placeholderrepository.url, addedhomepage/bugs/keywords
Install
code --install-extension moa-bridge-0.14.10.vsixSee CHANGELOG.md for full history.