AGENTS: note build-maintenance task to prune superseded module intermediates before payload wrapping

Built module trees accumulate superseded versions which vfscommonupdate/bootsupport propagate
into _vfscommon.vfs, bootsupport snapshots and shipped binaries. Records the planned prune step
and its punkcheck constraint: deletions must be reflected in (or pruned from) the affected
.punkcheck files so change detection stays sound.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

src/AGENTS.md

@@ -68,6 +68,7 @@ Recovery after a wrong path guess:
 - Use `punk make.tcl project` or `punk902z make.tcl project` inside Punk shell when building binaries through Punk.
 - Binary images are platform-specific; build on each target platform rather than expecting a cross-platform flag.
 - Remove `_build/` artifacts only when a clean/resync is needed, then rerun the relevant `make.tcl` command. Avoid partial cleans that break boot modules.
+- TODO (build maintenance): built module trees accumulate superseded intermediate versions (e.g `modules/punk/console-0.1.2.tm` and `-0.1.3.tm` alongside `-0.1.4.tm`), and `vfscommonupdate`/`bootsupport` propagate them into `_vfscommon.vfs`, bootsupport snapshots and shipped binaries. A prune step for superseded intermediates should run before payloads are wrapped. Constraint: `.punkcheck` state must stay consistent with the pruning — either record the deletions through punkcheck's event mechanism or prune the now-extraneous install records from the affected `.punkcheck` files (root `modules/`, `src/bootsupport`, project-layout bootsupport copies); silent file deletion with dangling punkcheck records would corrupt change detection. Version resolution always selects the highest version, so accumulation is size/cruft hygiene rather than a correctness issue.
 - Use `tcl::tm::path add <dir>` to surface project modules when writing focused tooling.
 - Review VS Code Tcl lint diagnostics before submitting new agent-produced Tcl code, but do not use lint tooling to reformat existing code.
 - When touching VFS payloads, describe regeneration steps in durable docs if the workflow changes.