punk::cap::handlers::templates 0.3.0: module-pathtype layout refs resolve
against the providing module's own templates/project_layouts store (sibling of
its layout_refs folder) instead of the never-existing <modulebase>/src tree -
module-carried thin layouts become usable.
punk::mix::templates 0.2.0: ships the thin punk.project layout payload inside
the modpod (payload synced from src/project_layouts by make.tcl - see below);
shellproject_multivendor declaration fixed decktemplates -> src/decktemplates
(shell-project layouts/templates were invisible when cwd was outside any
project).
punk::mix::commandset::project 0.3.0: project.new injects bootsupport into the
generated project at generation time via new lib::bootsupport_inject - manifest
(include_modules.config) driven module resolution from the generating shell's
project bootsupport tree, or a standalone kit's tcl:™️:list paths (999999.*
dev versions never injected; latest-version non-glob semantics matching
make.tcl bootsupport; adjacent non-.tm support files such as struct sets_*.tcl
and textutil .tex data carried along; bootsupport lib* trees copied from a
shell project, notice emitted for manifest-less standalone kits); punkcheck-
recorded with plain-copy degradation. -layout now prefix-matches the live
layout set instead of the package-load-time snapshot.
punkcheck 0.4.0: start_installer_event no longer writes literal '$eventid'/
'$rel_source'/'$rel_target'/'$config' into event headers (braced-literal
expansion bug, latent since inception - collided as duplicate ids when install
and installtrack writers shared one db); sources with no common root vs the
punkcheck folder (e.g //zipfs:/ module-mounted layouts) are recorded as
independent absolute paths instead of erroring.
punk::mix::base 0.1.1 -> 0.1.2 (manually versioned rename): cksum_path no
longer hangs forever on vfs-mounted files - tcllib -file digest modes read via
fileevent+vwait and zipfs channels never deliver fileevents (empty
ZipChannelWatchChannel in core); non-native files are slurped and digested in
data mode (new cksum_data_command per algorithm + cksum_crc_data/
cksum_adler32_data helpers; exec-based sha3 errors cleanly for vfs paths).
make.tcl: custom/_project layout bootsupport-sync retired (project layouts
store no snapshots); sync_layouts retargeted to thin vendor layouts (make.tcl,
build.tcl + bootsupport manifest copies; punkcheck db at
src/project_layouts/.punkcheck) plus store->modpod punk.project payload sync
(excludes bin/sdx.kit and src/PROJECT_LAYOUTS_* marker; fossil settings kept
via core-exclude override); bootsupport copy onto a modpod the running
make.tcl has mounted records OK when target content is already identical
(FAILED-record churn fix); workflow text updated (DIAGRAM 1b) and help/argdoc
texts adjusted.
bootsupport include_modules.config: added previously-recordless-but-required
entries cmdline (fileutil dep), struct::set (make.tcl accelerators), textutil,
textutil::expander, textutil::patch - generated projects' make.tcl now boots
under a plain tclsh.
Docs: root/src/bootsupport/punk AGENTS.md updated for the retired sync and
build-managed modpod payload; goal detail G-087 stage-3 progress record;
CHANGELOG 0.16.0 + punkproject.toml bump.
Claude-Session: https://claude.ai/code/session_01WS3VakZo4sgbFzcQFW3twZ
Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com
- `src/project_layouts/` — Project layout templates; partly updated by `make.tcl bootsupport` but full synchronisation requires manual work or future `make.tcl` improvements. Agents must not directly edit files under `src/project_layouts/` unless the user explicitly names a path there or specifically requests layout changes. When a `src/make.tcl` change affects layout make.tcl files, note it in the completion report for the user to handle — do not attempt manual synchronisation.
- `src/project_layouts/` — Thin project layout payloads (structure, scripts, docs, manifests - no stored bootsupport/vfs module snapshots; G-087). The build's thin-layout sync step (`make.tcl modules`/`libs`/`packages`/`project`) keeps each layout's `src/make.tcl`, `src/build.tcl` and bootsupport `include_modules.config` copies current, and syncs the punk.project payload into the `punk::mix::templates` modpod source tree; `dev project.new` injects bootsupport modules/libs into generated projects from the generating shell at generation time. Agents must not directly edit files under `src/project_layouts/` unless the user explicitly names a path there or specifically requests layout changes; never hand-edit the synced copies (they are punkcheck-managed build outputs).
@ -5,6 +5,14 @@ The latest `## [X.Y.Z]` header must match the `version` field in `punkproject.to
Entries are newest-first; one bullet per notable change. See the root `AGENTS.md`
"Project Versioning" section for the bump policy.
## [0.16.0] - 2026-07-19
- G-087 stage 3 - thin project layouts with generation-time injection: `dev project.new` now injects bootsupport into the generated project from the generating shell's current trees (modules per the layout's `include_modules.config` manifests plus adjacent support files; bootsupport lib trees from a shell project; standalone kits resolve modules from their own module paths and emit a notice for the manifest-less lib set). The ~40MB of stored bootsupport/vfs module snapshots left `src/project_layouts` (fat `custom/_project` fragments and their `_overrides` refs retired; vendor layouts thinned to structure/scripts/docs/manifests).
- A bare punk kit outside any project can now list and generate the `punk.project` layout: `punk::mix::templates` 0.2.0 ships the thin payload inside the modpod (build-synced from the store), `punk::cap::handlers::templates` 0.3.0 resolves module-pathtype layout refs against the module's own store, and the `shellproject_multivendor` declaration was fixed to `src/decktemplates` (shell-project layouts/templates were invisible when cwd was outside any project). `project.new -layout` is now prefix-matched against the live layout set instead of a load-time snapshot.
- make.tcl: former custom/_project layout bootsupport-sync retired; new thin-layout sync keeps layout `make.tcl`/`build.tcl`/manifest copies and the modpod payload current (workflow DIAGRAM 1b); bootsupport copy onto a self-mounted modpod now converges when content is already identical.
- punkcheck 0.4.0: `punkcheck::install` event headers no longer record literal `$eventid`/`$rel_source`/`$rel_target`/`$config` strings (latent since inception; collided when mixing install + installtrack writers in one db), and sources sharing no common root with the punkcheck folder (e.g `//zipfs:/` module-mounted layouts) are recorded as independent absolute paths instead of erroring. punk::mix::base 0.1.2: `cksum_path` no longer hangs forever on vfs-mounted files (tcllib `-file` digest modes rely on fileevents, which zipfs channels never deliver - data-mode digests are used for non-native filesystems).
- bootsupport `include_modules.config` completed with previously-recordless-but-required entries: `cmdline`, `struct::set`, `textutil`, `textutil::expander`, `textutil::patch` (generated projects' make.tcl now boots under a plain tclsh).
## [0.15.1] - 2026-07-19
- punk::ns 0.9.1: `get_ns_dicts` per-namespace `packagetails`/`packageprefixes` fix - the two lists were initialized once before the matched-namespaces loop, so with multiple matched namespaces (path globs, trailing `**`) every dict after the first carried the union of all earlier namespaces' entries, mis-marking non-package children in `nslist`/`n//` underline styling and in the returned data; a child with several deeper packages below it was also recorded once per matching package (now once). Single-namespace queries (the nslist.test tier A pins) were unaffected; the multi-namespace reset is now pinned in nslist.test. Documentation-only PUNKARGS added for `get_ns_dicts` (documents the returned per-namespace dict keys and `-allbelow`/`-nspathcommands`) and `nslist_dict`.
@ -69,14 +69,14 @@ Recovery after a wrong path guess:
- Use `tclsh src/make.tcl vfscommonupdate` to rebuild `_vfscommon.vfs`. The REPLACE confirmation prompts on an interactive terminal; unattended/agent runs must pass `-confirm 0` (with the default `-confirm 1` and a piped/closed stdin, make.tcl aborts fast with guidance instead of reading stdin - do not pipe `y`).
- `tclsh src/make.tcl workflow` prints an embedded ASCII data-flow overview of the build/release workflow (release-ready command sequence, source→outputs folder flow, kit assembly, keyed notes). The text lives in `::punkboot::workflow_text` in `src/make.tcl` - embedded rather than a data file so it travels with the make.tcl copies seeded into generated projects. **Update contract (agents):** whenever build data flow changes - a make.tcl subcommand added/removed/repurposed, a source or output folder added or rerouted, a propagation target added, a gate (staleness/provenance/confirm) or deploy behaviour changed - update the workflow text in the same change-set. Keep it plain ASCII, max line width 100, and preserve the RELEASE SEQUENCE / DIAGRAM / KEY-NOTES / MAINTENANCE structure; verify by running `tclsh src/make.tcl workflow` (and once under `PUNKBOOT_PLAIN=1`). Adding/changing a subcommand also means: SUMMARIES + HELPTEXTS + SUBOPTS (+ SUBGROUPS) in `::punkboot::argdoc`, `known_commands`, the plain `punkboot_gethelp` text, and a project-version bump (make.tcl interface is product surface per root AGENTS.md). Layout make.tcl copies pick the change up via `make.tcl bootsupport` - do not hand-sync them.
- make.tcl subcommands and flags are punk::args-declared (G-030): `tclsh src/make.tcl help ?subcommand?` or `<subcommand> -help` shows tabled usage; invalid arguments produce punk::args usage errors. The dispatch degrades to plain scan/help when the bootsupport punk::args (or its rendering stack) is stale or unavailable; `PUNKBOOT_PLAIN=1` forces the degraded mode for troubleshooting. The `::punkboot::argdoc` definitions are constructed (string-built) and use the G-045 authoring mechanisms — block-form help values + `@normalize`, explicit `@form -synopsis` — see src/modules/AGENTS.md "punk::args definition authoring ergonomics" before editing them or authoring similar definitions.
- Uncommitted `make.tcl`-generated outputs may be batched into one commit, regardless of how many `make.tcl` invocations produced them. This covers punkcheck-managed build outputs that are VCS-tracked: `src/bootsupport/`, `_vfscommon.vfs/modules` + `/lib`, and declared per-kit `*.vfs/lib_tcl<N>/<pkg>` subfolders. (Root `modules/`, `lib/`, `modules_tcl<N>/`, `lib_tcl<N>/` are gitignored and never committed.) Each module's old→new version rename is atomic; a regeneration reflects one build-output refresh, not independent hand-edits. This is a carve-out from generic "split aggressively" commit guidance for punkcheck-managed build outputs only — it does not cover user-curated VFS content (`_config/`, per-kit `*.vfs/` outside declared `lib_tcl<N>` subfolders, `_aside/`, `mkzipfix.vfs`, `_vfscommon.vfs/doc`), which commits separately per its own concerns.
- Uncommitted `make.tcl`-generated outputs may be batched into one commit, regardless of how many `make.tcl` invocations produced them. This covers punkcheck-managed build outputs that are VCS-tracked: `src/bootsupport/`, `_vfscommon.vfs/modules` + `/lib`, declared per-kit `*.vfs/lib_tcl<N>/<pkg>` subfolders, the thin-layout sync copies (`src/project_layouts/vendor/punk/<layout>/src/{make.tcl,build.tcl}` + bootsupport manifest copies), and the module-shipped layout payload under `src/modules/punk/mix/#modpod-templates-*/templates/project_layouts/` (G-087: synced from `src/project_layouts` - never hand-edit the modpod copy). (Root `modules/`, `lib/`, `modules_tcl<N>/`, `lib_tcl<N>/` are gitignored and never committed.) Each module's old→new version rename is atomic; a regeneration reflects one build-output refresh, not independent hand-edits. This is a carve-out from generic "split aggressively" commit guidance for punkcheck-managed build outputs only — it does not cover user-curated VFS content (`_config/`, per-kit `*.vfs/` outside declared `lib_tcl<N>` subfolders, `_aside/`, `mkzipfix.vfs`, `_vfscommon.vfs/doc`), which commits separately per its own concerns.
- Use `punk make.tcl project` or `punk902z make.tcl project` inside Punk shell when building binaries through Punk. Driving make.tcl from a built punk executable is supported for informational/update subcommands and for kit builds of *other* kits — the kit whose deployed executable is running the build is skipped with a warning (it cannot be replaced while running, and the pre-deploy process sweep must not kill the build itself; the sweep also excludes the build's own pid in all cases). Rebuild that kit from tclsh or a different kit.
- **Punk-exe-hosted make.tcl runs in a pre-loaded interp, not a virgin one** — the kit's script-mode boot has already loaded much of the punk stack (punk, punk::lib, punk::repl, punk::console, punk::du, flagfilter, struct::set ...) and set process state (app-punkscript forces `::tcl_interactive 0` for script semantics; libunknown/packagepreference are active). Consequences make.tcl must (and now does) handle explicitly: `package require` of an already-provided package is a no-op, so anything make.tcl breaks in the interp (the accelerator-reload block forgets+destroys sha1/md5/struct::* — it re-requires what was loaded), and anything computed at package-load time (punk::repl's `::tcl_interactive` probe — the shell branch recomputes it before `repl::start`), must be restored deliberately rather than relying on later loads to re-fire. Also note the copies that run in this mode are the *kit's* pre-loaded modules, not the bootsupport snapshots make.tcl's paths would otherwise prefer — silent provenance mixing when versions diverge. When adding interp-surgery or load-time-state assumptions to make.tcl, test under both `tclsh src/make.tcl ...` and `<punkexe> src/make.tcl ...`.
- 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.
- Superseded module intermediates are pruned automatically so payload wrapping inherits clean trees:
- `punk::mix::cli::lib::prune_superseded_target_modules` runs inside `build_modules_from_source_to_base` after each module install/skip (covers root `modules/`, `modules_tcl8/`, `modules_tcl9/`), and from `make.tcl bootsupport` for non-glob `include_modules.config` entries (glob entries may intentionally track multiple versions and are never pruned).
- `punk::mix::cli::lib::prune_sourcevanished_targets` mirror-prunes recorded `.tm`targets whose recorded source files no longer exist: project-layout bootsupport copies (installer `punkboot-bootsupport`) and root `modules*/` vendormodule copies (installer `make.tcl`).
- `punk::mix::cli::lib::prune_sourcevanished_targets` mirror-prunes recorded targets whose recorded source files no longer exist: root `modules*/` vendormodule copies (installer `make.tcl`) and the thin-layout/modpod sync copies recorded in `src/project_layouts/.punkcheck` (installer `make.tcl`, all file types).
- Every deletion is recorded as a punkcheck DELETE event in the owning `.punkcheck`, so change detection stays consistent. Files without a qualifying punkcheck install record (e.g placed manually) are never deleted — they are reported to stderr and must be removed by hand if unwanted.
- Install records carry virtual `module_name`/`module_version` SOURCE entries (punkcheck `targetset_addsource_virtual`, punkcheck >= 0.3.0) identifying which product of a source fileset a target is — needed because successive versions are typically built from the same physical source files. Prune trusts this identity; for legacy records it falls back to requiring the candidate's recorded sources to share the keep-version's source folder(s) and module-name prefix.
- The make.tcl call sites are guarded with `info commands` checks: after changing this tooling itself, the first `make.tcl modules` + `make.tcl bootsupport` pass builds/propagates the new tooling (prune skipped with a stderr note) and the next pass prunes.
@ -8,8 +8,9 @@ Modules and libraries required during the build/bootstrap/make process before th
- Agents should not directly modify files in this tree unless the task specifically targets boot behaviour.
- Bootsupport modules are snapshots that may lag behind or diverge from the corresponding `src/modules/` versions intentionally.
- The systematic update workflow is `modules/include_modules.config` (entries are `<base> <module>` pairs; base `src/vendormodules` for vendored modules, base `modules` for the project's *built* root modules - build with `make.tcl modules` first) followed by `tclsh src/make.tcl bootsupport`, which also propagates snapshots into the project-layout bootsupport trees.
- For non-glob config entries only the latest version is tracked: `make.tcl bootsupport` prunes punkcheck-recorded superseded older `.tm` versions from the bootsupport folders (recorded as DELETE events in `src/bootsupport/.punkcheck`), and mirror-prunes project-layout copies whose recorded sources vanished. Use a glob entry to intentionally keep multiple versions. Files without punkcheck install records are never pruned automatically.
- The systematic update workflow is `modules/include_modules.config` (entries are `<base> <module>` pairs; base `src/vendormodules` for vendored modules, base `modules` for the project's *built* root modules - build with `make.tcl modules` first) followed by `tclsh src/make.tcl bootsupport`. Project layouts store no bootsupport snapshots (G-087): `dev project.new` injects bootsupport into generated projects from the generating shell at generation time, and the layouts carry only manifest copies of `include_modules.config` (synced by the thin-layout sync step of `make.tcl modules`/`libs`/`packages`/`project` runs - a manifest edit reaches layouts and the templates modpod on the next such build).
- For non-glob config entries only the latest version is tracked: `make.tcl bootsupport` prunes punkcheck-recorded superseded older `.tm` versions from the bootsupport folders (recorded as DELETE events in `src/bootsupport/.punkcheck`). Use a glob entry to intentionally keep multiple versions. Files without punkcheck install records are never pruned automatically.
- The manifest is expected to be complete: a module physically present in bootsupport but missing from `include_modules.config` (a recordless legacy file) works for this checkout but is invisible to generation-time injection - generated projects then lack it. cmdline and struct::set were re-added to the manifest this way (2026-07-19). `make.tcl bootsupport` itself copies only manifest-listed `.tm` files; injection additionally carries adjacent non-.tm support files (e.g struct's `sets_*.tcl`, textutil's `.tex` data) that some modules load from their own directory.
- `dev lib.copyasmodule` is a manual convenience for copying a module (or a single-file pkgIndex.tcl library, converting it to .tm form) from a running punk shell - see `modules/README.md`; it is not the primary update mechanism.
@ -39,6 +39,7 @@ Source of truth for all modules under the `punk::*` namespace. This is the prima
- Private helpers go in `namespace eval private { ... }` blocks.
- Keep `namespace export` lists alphabetized.
- The `#modpod-*` folders contain files that get packed into `.tm` module archives during build — do not flatten them.
- `mix/#modpod-templates-*/templates/project_layouts/` is a build-managed copy of the thin punk.project layout, synced from `src/project_layouts/vendor/punk/project-0.1` by make.tcl's thin-layout sync step (G-087) - edit the store layout, never this copy. It ships inside the built `punk::mix::templates` module so a bare kit can list and generate the punk.project layout (resolution via punk::cap::handlers::templates >= 0.3.0).
- Follow the parent `src/modules/AGENTS.md` "Versioning And Releases" rules: bump `<modulename>-buildversion.txt` on any API or behavior change and append a changelog comment line documenting the change.
#0.3.0 - G-087 stage 3: module-pathtype layout refs now resolve - the layout root for a module-provided ref is the project_layouts folder within the providing module's own templates tree (sibling of its layout_refs folder), instead of the never-existing <modulebase>/src/project_layouts. Enables module-carried thin layout payloads (bare kit can list and generate the module-shipped punk.project layout).
#0.2.0 - G-087 stage 2: layout refs are now fauxlink files (<alias>#<encodedtarget>.fauxlink|.fxlnk, resolved via the fauxlink module; target relative to <projectroot>/src/project_layouts). Bespoke <alias>@<target>.ref grammar removed - .ref files are no longer recognised. Alias-less (leading-#) refs and unresolvable refs are skipped with a warning (punkcheck excludes leading-# filenames). New dependency: fauxlink. Also fixes the ignore* skip (previously matched against the full glob path, so it never applied).
#0.1.1 - fix: pkg_register 'absolute' pathtype branch had a non-braced expr 'if {!file exists $normpath}' which raised an expr syntax error on any absolute-pathtype provider registration; now correctly tests ![file exists $normpath]
#0.1.1 - fix: pkg_register duplicate-registration guard did 'dict get $provider_info $pkg' without a dict exists check, erroring for any second provider package registering the same capability
package provide punk::mix::base [namespace eval punk::mix::base {
variable version
set version 0.1.1
set version 0.1.2
}]
#version history (manually versioned module - real version is the filename/provide value)
#0.1.2 - fix: cksum_path hung forever on files on non-native (vfs-mounted e.g //zipfs:/) filesystems - the tcllib -file digest modes read via fileevent+vwait and vfs channels never deliver fileevents. Files on non-native filesystems are now slurped and digested in data mode (new cksum_data_command per algorithm incl new cksum_adler32_data/cksum_crc_data helpers; exec-based sha3 returns an unsupported_algorithm_for_vfs_path error for vfs paths). Needed for punkcheck::install from module-carried //zipfs:/ layout payloads (G-087 stage 3).
#0.1.1 - fix: get_template_basefolders no-handler warning used 'put' instead of 'puts'; missing-handler path now warns and returns an empty dict instead of erroring on an unset variable
puts stderr "commandset::project::new WARNING - no handler available for the 'punk.templates' capability - template providers will be unable to provide layout locations"
return
}
#validate -layout against the live layout names with prefix matching (exact name wins, unique prefix accepted)
#consider using punk::cap to enable multiple template-substitution providers with their own set of tagnames and/or tag wrappers, where substitution providers are all run
puts stderr "bootsupport_inject NOTICE - $bm manifest has entries but no shell project bootsupport tree is available and the running shell is $running_tclx - skipping (populate $bm manually or regenerate from a matching shell)"
continue
}
foreach tmdir [tcl::tm::list] {
if {[file isdirectory $tmdir]} {
lappend sourceroots $tmdir
}
}
puts stdout "bootsupport_inject: $bm resolving manifest entries from the running shell's module paths ([llength $sourceroots] paths)"
}
if {![llength $sourceroots]} {
puts stderr "bootsupport_inject WARNING - no usable module source paths for $bm"
puts stderr "bootsupport_inject WARNING - lib tree copy failed for $lf: $errM"
}
}
} else {
if {[file isdirectory [file join $bootbase lib]]} {
puts stderr "bootsupport_inject NOTICE - bootsupport lib packages (pkgIndex.tcl-based, e.g fileutil) were not injected: no shell project bootsupport lib tree is available from this shell (standalone kit; the lib set has no manifest). The generated project's make.tcl requires them under a plain tclsh - run it via this shell's executable instead (<punkexe> src/make.tcl ...), or populate src/bootsupport/lib manually."
#0.3.0 - G-087 stage 3: new lib::bootsupport_inject (+ lib::_tm_version_sort) - project.new now injects bootsupport modules into the generated project from the generating shell's current trees, driven by the thin layout's include_modules.config manifests (shell-project bootsupport tree preferred; standalone kits resolve via tcl::tm::list; 999999.* dev versions never injected; punkcheck-recorded with plain-copy degradation)
#0.3.0 - bootsupport_inject also tree-copies the shell project's src/bootsupport/lib* pkgIndex-based lib trees (e.g fileutil - required by the generated make.tcl under plain tclsh); standalone kits emit a notice (lib set has no manifest) - generated make.tcl remains runnable via the kit executable
#0.3.0 - bootsupport_inject carries adjacent non-.tm support files beside matched modules (struct sets_*.tcl loader companions, textutil .tex hyphenation data) via new private helper _bootsupport_inject_copyfile; bootsupport include_modules.config gained the previously-missing cmdline and struct::set entries (files existed recordless in bootsupport; fileutil requires cmdline, make.tcl uses struct::set)
#0.3.0 - new: -layout now prefix-matched against the live layout set at call time instead of the package-load-time LAYOUTNAMES snapshot (stale snapshot could reject layouts that appeared after load, e.g when cwd moved into a project)
#0.2.2 - fix: new's no-handler warning path used 'put' instead of 'puts' (raised invalid command name error instead of warning)
#0.2.1 - fix: -layout now validated and normalized via tcl::prefix::match against documented layout choices, matching the PUNKARGS -choiceprefix default (true); previously the manual parser accepted arbitrary values with no validation
#0.2.0 - updated punkcheck::install call sites to use -exclude-paths / -exclude-paths-core (replaced -antiglob-paths + -exclude-dirsegments) — call-site API change warrants minor bump
#0.2.0 - G-087 stage 3: ships the thin punk.project layout payload at templates/project_layouts/vendor/punk/project-0.1 (synced from src/project_layouts by make.tcl - do not hand-edit the modpod copy) so the module-shipped ref resolves via punk::cap::handlers::templates 0.3.0 and a bare kit can generate projects. shellproject_multivendor declaration fixed to src/decktemplates (was decktemplates, which never existed at a project root - layouts/templates from the shell's own project were invisible when cwd was outside any project).
#0.1.4 - removed dead templates/layouts/project payload subtree (design-generation residue: no reader; layout payloads live in src/project_layouts, located via layout_refs - G-087 hygiene)
#0.4.0 - cross-root sources: installfile_add_source_and_fetch_metadata now records sources that share no common root with the punkcheck folder (e.g //zipfs:/ module-mounted sources installing to the filesystem) as independent absolute paths via the cksum helpers' empty-base mode, instead of erroring 'don't share a common root'. Enables punkcheck::install from module-carried (vfs-mounted) layout payloads - G-087 stage 3 bare-kit project generation.
#0.3.2 - fix: start_installer_event built its EVENT header record from a braced literal, writing the literal strings '$eventid' '$rel_source' '$rel_target' '$config' into every punkcheck::install event header instead of the values. Readers matching on the returned eventid masked it, but any two such events in one file collide on the duplicate literal id when punkcheck::installtrack loads the file (first hit: G-087 stage 3 sharing src/project_layouts/.punkcheck between install and installtrack writers), and event -source/-targets/-config provenance metadata was unrecorded.
#0.3.1 - PUNKARGS fix: install -overwrite, -source-checksum and -punkcheck-folder now declare -choiceprefix 0 so documented behaviour matches the manual parser (exact match required, no prefix matching)
#0.3.0 - added installsource_add_virtual proc + installevent targetset_addsource_virtual method: 'virtual' named-value SOURCE records (-type virtual -path virtual:<id> -value <v>) compared by value, for e.g recording resolved module build versions on install/delete records
