Each site read in context, not grep-replaced; bakehouse vs bake chosen per
meaning, and missing invocation arguments supplied where the reference
describes an unattended flow:
- G-005 Approach + Notes, G-006 Acceptance + body: 'make.tcl project' ->
'make.tcl bakehouse' (the full consumer build these goals integrate with;
no flags - conceptual references on a clean checkout, not recipes).
- G-057 Acceptance: 'make.tcl project' -> 'make.tcl bake' (icon embedding
lives in the kit-wrap stage and must hold for a bare bake; bakehouse
inherits).
- G-028 Context DELIBERATELY UNCHANGED: dated 2026-07-07 incident narrative -
the command actually run; history stays verbatim (alias keeps it readable).
- src/runtime/mapvfs.config todo: 'vfs' -> 'bake' wish, re-annotated - G-104
achieved WITHOUT the single-kit-by-name/list-kits item (still open).
- src/runtime/vendorlib_vfs.toml header: vfslibs now runs as a phase of bake
(G-112 fold), not 'as part of project'.
- shellexit.test + staticruntime.test rebuild comments: 'project' -> 'bake'
AND stale '(interactive y confirmation)' / bare vfscommonupdate corrected to
'-confirm 0' (piped y retired since G-030) - the missing-arguments class.
- punk.project layout store vfs READMEs (lib + modules): 'make.tcl vfs' ->
'make.tcl bake'; modpod template twins propagated via the punkcheck
layout->modpod sync (make.tcl modules run), never hand-edited.
Variant-phrasing sweep confirmed non-hits: G-115 '(vfs assembly)' names the
src/vfs payload tier (name retained), G-047 'make.tcl/project.new' is the dev
project.new command. Archive tier + CHANGELOG history untouched.
goals_lint + goals_xref refs clean.
Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com
Use mapvfs.config to configure building of a kit (metakit or zipfs) executable from customized .vfs folders
within src/vfs
A runtime must be installed in the appropriate bin/runtime/ folder to build the executable.
These can be installed by running: bin/runtime.cmd fetch
or alternatively by downloading from an artifact source such as : https://www.gitea1.intx.com.au/jn/punkbin
Appropriate runtimes should be self-contained Tcl executables that are either metakit or zipfs aware,
and have an attached vfs with 'info library' support files.
A plain tclsh, even if it has zipfs support, is unlikely to work unless it has the tcl_library folder (with init.tcl and others) and possibly some
other required modules such as msgcat placed within the .vfs folder being used to build the executable.
A plain tclsh may commonly depend on shared libraries elsewhere on the system, and so the resulting executable may not be as portable.
Julian Noble
232f2f6096