Tree: 5e9f1c75fc

master

v0.1a

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '5e9f1c75fc'

${ noResults }

Commit Graph

115 Commits (5e9f1c75fc081d80b00aa272a660b9e82880b840)

Author	SHA1	Message	Date
Julian Noble	5e9f1c75fc	G-128: seam selects punkres when built; characterization tests; punkshell 0.30.1 ... src/make.tcl kit icon seam (G-057): mechanism selection is now punkres-first - kiticon::punkres_available (memoized; binary presence at bin/punkres(.exe) is the selection signal) + kit_icon_embed_punkres (exec wrapper; punkres verifies its own output). twapi arm unchanged as fallback; when NEITHER serves the skip notice combines both reasons and names the 'make.tcl tool build punkres' remedy. Sidecar embedding value gains 'punkres' (bin/AGENTS.md format doc, ARCHITECTURE.md kit-icon bullet updated; architecture_lint clean). Live-bake fallback matrix on punkluck86 (win32-ix86 = PE32 arm live): punkres present -> embedded via punkres, kit boots + smoke OK; punkres absent + twapi loadable -> via twapi; both absent -> unavailable with combined notice, embedding none (exact pre-G-128 degradation). Live parity: both arms' baked kits listing-identical (codepage host-ACP noise finding recorded in the goal detail) with byte-identical extracted icons. New src/tests/shell/testsuites/punkexe/punkres.test (7/7 under the tclsh9.0.5-punk runner; self-gates on bin/punkres + store fixture): overlay- unsafe refusal exit 3 with untouched input, consented file-relative shift with convention preserved, payload intact via punk::zip members + crc-verified extraction, icon replaced (extract-ico == punkshell.ico), idempotent re-stamp byte-identical, make.tcl tool info punkres provenance records. Full punkexe suite 83 tests 0 failed (no collateral). Goal detail: Notes findings (codepage noise, root-vendorlib twapi fragility, nested tclsfe payload, metakit move-safety -> G-101 pointer updated) + Progress increment 1 with the two remaining acceptance items (non-windows-host e2e, punkbin publication route) and one acceptance-wording flag for the user (metakit 'kit' shape vs 'zip overlay' clause). punkshell 0.30.1 + CHANGELOG. Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com	4 days ago
Julian Noble	5a8a62547b	G-057: kit icon step - resource sidecar every target, twapi PE embedding ... Every kit a bake builds now gets a <kitname>.resources.toml sidecar (build folder + deployed beside bin/<kit>) recording the build-time icon choice: schema-1 flat TOML in the G-135 tolerant family - kit, target, kit_type, icon_origin default|override, icon_source (repo-relative), icon_hash, provenance source+hash lifted from the icon's assetorigin sidecar (the chain reaches the SVG master), embedding, embedding_status embedded|not-applicable|unavailable|failed, embedding_reason. Byte-stable (no timestamps, write-only-if-changed); named "resources" so the parked RT_VERSION follow-on extends the same file. Format doc: bin/AGENTS.md. win32-target kits get the icon embedded as RT_ICON/RT_GROUP_ICON via the twapi resource-update APIs - the tcl-sfe sfe-0.2.tm mechanism (Ashok P. Nadkarni) generalized: enumerate all existing icon/group entries via extract_resources, delete ALL, write ids 1..N plus one group under the first pre-existing group's name+lang (fallback 1/1033) in a single update transaction - idempotent by construction. Ordering is stub-first: a PER-KIT copy of the extraction phase's payload-free raw runtime prefix is stamped BEFORE payload attach, so the resource rewrite can never corrupt an overlay; all three assemblers (zipfs mkimg, zipcat/concat, sdx wrap) consume the stamped copy; runtime store originals untouched. ::punkboot::kit_icon_process is the single internal entry point with mechanism selection inside (a G-128 portable stamper becomes a substitution). Skip taxonomy: non-PE target / runtimeless .kit = NOT APPLICABLE; cookfs, missing icon, missing raw prefix, cross-host (non-windows process family), twapi-unloadable = UNAVAILABLE with distinct named reasons; embed errors = recapped BUILD-WARNING + status failed. Sidecar written in every case. Default icon joins the kit's punkcheck source set (icon changes rebuild kits); sha256 self-contained (bootsupport has sha1/md5 only), memoized per run. Verified (evidence in the goal detail file Progress): full bake embeds all 10 buildable win32 kits (zip x64+ix86, sdx metakit trio) with resource inspection byte-matching the source ico (punk91, punk86, punk91ix86 inspected; group name SFE preserved); scratch-copy boots for zip, metakit and a stamped concat image (androwish exe-path mount); override round-trip via punk9wintk903.vfs (solid ico embedded + recorded, then reverted); linux cross-target punkshell902 sidecar with not-applicable; mingw tclsh86 bake takes the concat path with the distinct twapi-unloadable notice; vendored twapi 5.0b1 arm proven under tclsh9.0.5-punk; double-restamp converges. punk9_beta embedded+built but deploy still blocked by the known bin file lock (stamped product waits in src/_build). make.tcl workflow text gains the icon step + sidecar output; punkshell 0.29.0 -> 0.30.0 (minor: kits now wear the punkshell icon; new shipped sidecar) with CHANGELOG entry. G-057 detail file: ordering + override + sidecar + seam decisions recorded with tcl-sfe attribution; cross-host known-shortcoming + G-128 remedy recorded per acceptance. Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com	4 days ago
Julian Noble	d76a7907ea	make.tcl tool subcommand: build vendored zig tools into bin/ (G-126); 0.28.3 ... New surface for the vendored first-party build tools under src/tools: make.tcl tool list|info|build|test ?<toolname> ...? ?-test 0|1? - discovery is convention-based (a src/tools directory carrying build.zig is a tool), so the G-128 tool will appear with zero make.tcl edits; per-tool records are read tolerantly from build.zig.zon (version, minimum_zig_version floor) and PROVENANCE.md (upstream, vendored commit) - list/info report installed-binary state (current|stale|absent vs bin/<name><exe-suffix>) and the resolved toolchain - toolchain resolution: PUNK_ZIG=<path> overrides; otherwise bin/tools/zig* is scanned and the LOWEST release satisfying the floor wins - deterministic as newer toolchains get unpacked beside the pinned one; dev builds count only when their base version exceeds the floor - build runs the tree's own 'zig build test' as an EXIT-CODE gate (expected stderr warnings do not fail it), then builds ReleaseSafe and installs to bin/; nothing installs when the gate or build fails; -test 0 skips the gate; build caches are deliberately left in place between runs for rebuild speed (git- and fossil-ignored) - zig stays OPTIONAL: packages/bake never require the step; without a suitable toolchain, list reports the state and build/test exit nonzero with bin/punk-getzig.cmd guidance - full subcommand accompaniments per src/AGENTS.md: punk::args argdoc (SUMMARIES/HELPTEXTS/bespoke passthrough definition), SUBGROUPS ("vendored tools"), known_commands, degraded-mode dispatch, plain help text, bootsupport-staleness exemption, workflow text (new OUT-OF-BAND SUBSYSTEMS section also covering buildsuite), project version 0.28.3 + CHANGELOG entry - piped characterization (zig-independent): src/tests/shell/testsuites/punkexe/maketcltool.test - 4/4 green - verified live: 'tool build punkzip' gated on the vendored tree's 130/130 suite and installed bin/punkzip.exe (ReleaseSafe, v2.3.1, 1.1MB) over the stale Nov-2024 v2.1.0 binary; list state flipped stale -> current; PUNKBOOT_PLAIN degraded dispatch and tabled help verified G-126 Progress updated: the acceptance's build-step clause is satisfied. Remaining: punk::zip fast path, parity suite, benchmark. Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com	5 days ago
Julian Noble	583dd5e0b2	G-133: bake payload/target consistency checks - advisory arch scan + smoke-require probe ... - punkboot::utils 0.5.0: binary_arch_classify (PE Machine field, ELF e_machine, Mach-O thin+universal - honest unknowns), platform_expected_binary, platform_discriminated_segment (canonical <os>-<cpu> tokens + vendor spellings, extensible namespace variables), vfs_binary_arch_report (per-directory exemption, exempt subtrees counted unread) - make.tcl: advisory binary-arch scan at the G-125 gate seam (recapped BUILD-WARNINGs naming file/found-arch/kit-target, capped at 8 per kit with honest total; cross-target kits included); post-build smoke-require probe running the freshly built artifact via its tclsh subcommand with drained stdin (failures recapped naming kit/package/actual error; cross-target skip with stated reason; undeclared kits run nothing new); mapvfs.config entries accept a 5th smoke-require element (mapvfs_parse/mapvfs_kit_outputs carry smokerequire); 'check' reports scan ACTIVE/UNAVAILABLE + declared smoke matrix; workflow K11 - mapvfs.config: smoke-requires declared - punkluck86 {Thread} (the 2026-07-27 incident construction), punk91ix86 {Thread iocp}, punkshell902 {Thread} (cross-target skip demonstrator) - tests: binaryarch.test (generated header fixtures only - no committed binaries; punkluck86 case reproduced; iocp pair + win-x64 exemptions; real-tree sweep with known-real findings filtered), maketclpayloadcheck.test (piped check characterization, ESC-free per G-113) - docs: src/AGENTS.md + bin/AGENTS.md state what the checks do and do NOT guarantee; src/runtime/AGENTS.md entry grammar; ARCHITECTURE.md bake section - REAL FINDING on the scan's first sweep: zint.dll 2.13.0 in punk8win.vfs lib_tcl8/ is 32-bit (PE i386, confirmed with file(1)) and can never load in the x64 tcl8 kits punk86/punkbi/punksys that carry it - those bakes warn until the payload is fixed - punkshell 0.28.2 Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com	6 days ago
Julian Noble	191d8ff490	G-129: kit boot derives its payload mount from the runtime's mount table (punkshell 0.28.0) ... Boot (punk_main.tcl + project_main.tcl, identical copies): - zipfs presence keys on tcl::zipfs::mount - present in every supported zipfs generation - not tcl::zipfs::root (8.7/9-era; absent from the androwish/ undroidwish 8.6 backport, whose ::zipfs ensemble also lacks a root subcommand). - New factored ::punkboot procs (zipfs_mount_pairs, zipfs_kit_mountbase, path_within) derive where this executable's attached archive actually mounted: the mount-table entry whose archive file is [info nameofexecutable] (the backport reports it without the windows drive prefix - handled), fallback the mount containing the boot script. //zipfs:/app stays the expected modern answer, not an assumption. Procs remain defined post-boot for tests. - A mounted archive that cannot be attributed to the executable is reported on stderr instead of silently configuring no internal paths (the old failure shape). - The starkit quick-search line [zipfs root]/app/tcl_library (an error on the backport) uses the derived base; internal_paths gains the derived base when no zipfs volume root covers it; the internal-only simulate-kit branch recognises a script under the derived mount as kit-internal. make.tcl (necessary companion fixes - Scope extension flagged in the goal file): - Runtime capability probe keys has_zipfs on tcl::zipfs::mount (was root, which refused zip assembly for the backport; the block also rode a body-less 'if {![catch ..]}' that only worked because piped-stdin tclsh continues past command errors). - merge_over resolves relative fauxlink targets against the link file's own directory (the fauxlink module's symlink semantics) - identical for the pre-existing root-level links, required for the new nested one. Payload + matrix: - punk8win.vfs gains an app/main.tcl fauxlink beside root main.tcl: the undroidwish family auto-runs app/main.tcl INSIDE the attached archive (embedded /app/main.tcl string in the exe) and ignores a root main.tcl. Inert in the metakit kits sharing the payload (punksys/punk86/punkbi verified). - mapvfs.config: punkluck86 (tclsh8.6.10-luck-zip) + punk91ix86 (tclsh9.1b0-tclsfe), both zip kits targeting win32-ix86. Tests + docs: - New shell/testsuites/punkexe/kitmountpoint.test (4 tests): backport exe-path attribution, modern-32 //zipfs:/app, baked punkexe regression pin, unattributed-mount stderr report + no foreign paths. Self-gates on the untracked verification runtimes. - bin/AGENTS.md "Kit-wrappable runtime requirements (G-129)" + src/AGENTS.md pointer, src/vfs/AGENTS.md boot contract, src/tests/shell/AGENTS.md suite doc, ARCHITECTURE.md boot-chain bullet. - Thin-layout + templates-modpod copies synced (make.tcl modules; _config boot mains refreshed into the project-0.1 store layout per the 17250a8c precedent). Verified: punkluck86 + punk91ix86 boot and resolve punk::args from inside their mounts with externals stripped; punk905/punk902z (zipfs) + punksys/punk86 (starkit) probe byte-identical before/after; both zip offset conventions (mkimg + concat) mount on the backport; full suite 1171 tests with only the documented exec-14.3 baseline failure. Claude-Session: https://claude.ai/code/session_01UEgomWq6kA6c4A8GswqqGW Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com	6 days ago
Julian Noble	df83b21a24	bootsupport: replace mounted modpods by delete-then-place, and explain the windows catch-all (punkshell 0.27.4) ... 'make.tcl bootsupport' failed three times this session replacing the zip-based punk::mix::templates modpod, always with: error copying "<src>" to "<dst>": invalid argument Root cause, demonstrated rather than inferred. A zipfs mount MEMORY-MAPS its archive (tclZipfs.c CreateFileMappingW + MapViewOfFile), and windows refuses to overwrite a file with a user-mapped section open - ERROR_USER_MAPPED_FILE (1224). Any holder blocks it: a running punk shell that loaded the modpod, a src-mode session, or the build itself. Reproduced directly: the same file copies fine unmounted, fails while zipfs-mounted, and copies fine again once unmounted. The message is a dead end BY CONSTRUCTION, which is why two earlier attempts at characterising this (in commit messages and in the archived G-124 detail file - first "a modpod make.tcl has itself mounted", then "a transient lock") were both wrong in different ways. Tcl_WinConvertError maps only Win32 codes 0..267 and sends everything above them to errorTable[1], which is EINVAL - so EVERY high-numbered windows error surfaces as "invalid argument", naming neither cause nor remedy. Byte-identical code in 8.6 and 9.1b1. FIX. ::punkboot::replace_possibly_mapped_file tries the ordinary copy and, on failure, falls back to DELETE-THEN-PLACE, which windows does permit: unlinking a mapped file leaves the holder reading its own mapping while new content lands at the name (measured: delete succeeds while mounted, the mount keeps serving its old content afterwards). Replacement content is staged to a sibling <target>.punkboot-new first, so a mid-sequence failure can never leave the target missing; a 'broken' return - unlinked and unrestorable - is reported as a build failure naming the file to restore by hand. This replaces a narrower prior workaround that only recognised the already-identical case and otherwise recorded FAILED. DIAGNOSIS. ::punkboot::mapped_file_hint fires when a genuine failure carries the catch-all message and explains what it actually means and which process class to look for, instead of leaving "invalid argument" bare. It stays silent for unrelated errors. Verified on the real failure: the bootsupport run that has failed all session now reports "(in-place overwrite refused - replaced by delete-then-place; target was memory-mapped, e.g a mounted modpod)" and completes, with no hand-copy and no rerun. Helper-level checks cover the unmapped path (plain copy, unchanged), the mapped path (recovers, content correct, holder's mapping intact, no temp left behind) and both hint branches. Full suite 1167 tests, 1146 passed, 1 failure - core/tcl exec-14.3, the documented baseline. Documented in src/bootsupport/AGENTS.md, including the general warning that 'invalid argument' from ANY windows file operation in Tcl means "some windows error above 267" and must never be read at face value. Also drafts G-132 (user-approved): the errno catch-all is upstream's defect, not ours, and deserves reporting. The goal is deliberately shaped so an AGENT DRAFTS AND THE DEVELOPER SUBMITS - no account use, no web form, no API - following the G-039 precedent, with the submission-ready text staged in TEMP_REFERENCE and the finding, reproducer, eventual ticket URL and disposition kept in the tracked detail file, because TEMP_REFERENCE is one 'git clean -xdf' from gone. The report's claim is deliberately narrow: the errno conversion is plainly wrong, while the related fact that 'file copy -force' over a mapped file succeeds on unix and fails on windows rides along as context rather than as a second demand. punkshell's workaround is explicitly not removed if upstream fixes it - an upstream fix dates it rather than deletes it. Assisted-by: harness=claude; primary-model=claude-opus-5[1m]; api-location=anthropic.com	6 days ago
Julian Noble	20ee103120	boot-precondition gate learns the exe-path-mount tcl library convention (punkshell 0.27.2) ... The G-125 gate refuses a kit whose merged .vfs supplies no tcl library. It knew two conventions - tcl_library/ for zipfs-attached kits and lib/tcl<major>.<minor>/ for starkit-style ones - which covered all ten kit trees this project builds. A third-party runtime under evaluation (Lean Undroidwish Construction Kit, 32-bit windows, Tcl 8.6.10) uses a third: its attached archive mounts at the EXECUTABLE'S OWN PATH rather than at //zipfs:/app, so [info library] is <exe>/tcl8.6 and the library sits at tcl8.6/ in the root of the tree. The gate reported that runtime unbootable - a false refusal on a directory that is unmistakably a complete Tcl library (auto.tcl, clock.tcl, encoding/, history.tcl, init.tcl, package.tcl ...). Found while investigating whether our bake infrastructure can handle that kit; the androwish/undroidwish zipfs backport for 8.6 mounts this way generally, so it is a family of runtimes, not one artifact. punkboot::utils 0.3.0 -> 0.4.0 adds tcl<M>.<m>/ at the vfs root as a third recognised location; the report's 'checked' list and the not-found reason name all three, as do 'make.tcl check' and the workflow K10 key note. Glob note worth keeping: the root tcl[0-9]* pattern also matches the tcl8/ and tcl9/ MODULE trees this project's own kits carry. They hold no init.tcl, so the existing qualification test rejects them without needing a narrower pattern - now pinned by bootlib_module_tree_not_a_library so a later tightening of the glob has to argue with a test rather than look like an obvious cleanup. Verified: the LUCK runtime's extracted tree now reports ok=1 locations=tcl8.6, and all ten assembled src/_build/*.vfs trees still pass with unchanged detected locations (tcl_library for the six zipfs kits, lib/tcl8.6 for punk86/punkbi/punksys, lib/tcl9.0 for punkshell902). Full suite 1167 tests, 1146 passed, 1 failure - core/tcl exec-14.3, the documented baseline. One of the gate's own punkexe pins failed first time round and was right to: re-wrapping the 'check' report split "...that / cannot initialise" across lines. The pattern now matches across the break rather than the assertion being loosened. Note this does NOT make such a runtime bakeable yet - src/vfs/_config/punk_main.tcl still probes zipfs with 'info commands tcl::zipfs::root' (a 9-era command the 8.6 backport lacks) and assumes the //zipfs:/app mount point, so a kit built on it would not find its own payload. That is separate work; this change only stops the gate refusing a tree that has a perfectly good library. Assisted-by: harness=claude; primary-model=claude-opus-5[1m]; api-location=anthropic.com	6 days ago
Julian Noble	b7c632b670	G-125 achieved: a kit that cannot boot is not deployed (punkshell 0.27.0) ... The kit machinery already knew when it had failed to extract anything from a source runtime, and under G-122 that notice became a recapped BUILD-WARNING - but the build still assembled an artifact, DELETED the deployed kit and copied the new one over it, closing running instances of the kit first. Field-observed 2026-07-26: an msys2-hosted bake of punk91 produced a 49,501,792-byte bin/punk91.exe that failed at startup with "application-specific initialization failed: Cannot find a usable init.tcl", by which point the previously working kit was already gone. G-124 removed the particular cause; this removes the class. A build tool should not make a working executable worse. A bake now refuses any kit whose merged .vfs supplies no tcl library: the kit is listed under FAILED KITS with a reason naming the cause and NOTHING is written - no src/_build/<kit>, no deploy, and the previously deployed bin/<kit> is left byte-identical. The gate sits immediately after the _vfscommon.vfs + <kit>.vfs merges and before the kit-type assembly switch, the last point at which no build product exists; a refusal appends to failed_kits, ends the punkcheck event FAILED and continues, so the punkcheck records stay consistent with what is on disk. The merged src/_build/<kit>.vfs tree is deliberately left behind - it is the evidence for the refusal. It gates on the BOOT PRECONDITION, not on the extraction step having run. Some .vfs folders legitimately supply their own tcl library (src/vfs/punk8_statictwapi.vfs, punk9test.vfs and mkzipfix.vfs do today), and those must keep building - so the check reads the merged tree. It is structural and executes nothing, which also makes it valid for cross-target kits this host could never run, and costs 0.63ms per kit (measured over 200 iterations against the real src/_build/punk905.exe.vfs), so it runs unconditionally. The predicate is punkboot::utils::vfs_boot_library_report (0.2.0 -> 0.3.0), called through a guarded require modelled on the existing get_src_provenance_warnings: a stale or missing bootsupport snapshot degrades the gate to a NOTE rather than failing every kit. Both branches were observed live - before the bootsupport propagation 'make.tcl check' reported UNAVAILABLE, after it ACTIVE. Scope was extended at activation (user-approved) to put the predicate in that module rather than private to the build script, because a gate that cannot be exercised cannot be characterized, and punkboot::utils is already where make.tcl's provenance gate helper lives. What qualifies as a tcl library: tcl_library/init.tcl (zipfs-attached kits) or lib/tcl<major>.<minor>/init.tcl (starkit-style), AND at least one companion file beside it (tm.tcl, package.tcl, auto.tcl, clock.tcl, history.tcl, word.tcl) or an encoding/ directory. The companion test is load-bearing: every punkshell kit carries lib/BWidget1.10.1/init.tcl, so a check that looked for any init.tcl anywhere would pass a kit with no tcl library at all. lib/tcllib2.0 is correctly not matched by the lib/tcl[0-9]* glob. Verified against all 10 assembled trees in src/_build - both conventions are represented (tcl_library for punk902z/punk905/punk91/punk9_beta/punk9bi_beta/punkmagic, lib/tcl8.6 for punk86/punkbi/punksys, lib/tcl9.0 for punkshell902). The no-extraction BUILD-WARNING was reworded from "will not initialise unless src/vfs/<x> supplies one" - a consequence the build then ignored - to "will FAIL the boot-precondition gate unless src/vfs/<x> supplies one". It stays a warning rather than becoming the failure, because a .vfs that supplies its own library needs no extraction. Verified 2026-07-27 end-to-end against a temporary fixture kit (a mapvfs entry pointing a zip kit at a payload-free runtime, plus a vfs with no tcl library), with sentinel files standing in for a previously deployed kit and a previous build product. Across the failing run bin/punkgatefixture.exe (sha1 2a0700eb...) and src/_build/punkgatefixture.exe (sha1 12c50567...) were byte-identical with unchanged mtimes, and the kit was reported under FAILED KITS with the cause named. Adding tcl_library/{init.tcl,tm.tcl} to that same fixture vfs - extraction still yielding nothing - made it build and deploy normally, which is the other half of the criterion. The fixture was removed afterwards and mapvfs.config restored byte-identical to its backup. Real-kit bake through the gate: punk905 builds, deploys and boots. Characterization: 12 tests in modules/punkboot/utils/testsuites/utils/bootlibrary.test (both conventions, the companion-file requirement and its BWidget decoy, near-miss reporting, missing/empty trees, and a sweep asserting every assembled src/_build/*.vfs tree still passes so the gate cannot fail kits that boot today) and 2 in shell/testsuites/punkexe/maketclbootgate.test (the ACTIVE/UNAVAILABLE report, ESC-free per the G-113 piped policy). Existing punkexe suites pass unchanged. Documented in src/AGENTS.md with the remedy when a kit is refused, in ARCHITECTURE.md beside the provenance gates, and in the embedded 'make.tcl workflow' data flow as key note K10 (verified under the default and PUNKBOOT_PLAIN=1 paths, within the 100-column budget). The achieved flip archives the entry and the detail file, and sweeps the live tier: G-127 (its output location inherits the never-written guarantee as long as the gate stays upstream of the artifact write, and its payload/target mismatch reporting should share this vocabulary), G-028 (the sibling "why bin/<kit> was not updated" surface in the same deploy step) and G-101 (a new container type must land its library where the gate looks, or extend the location list). Assisted-by: harness=claude; primary-model=claude-opus-5[1m]; api-location=anthropic.com	6 days ago
Julian Noble	78d9bf238a	G-124 achieved: dependency-free zip reading in punk::zip (punkshell 0.26.0) ... punk::zip could write a zip and split an executable-prefixed one, but nothing in the tree could READ a zip without zipfs, vfs::zip or tcllib's zipfile::decode - a system package punkshell does not vendor, with exactly one consumer: make.tcl's zipfs-less kit extraction. Measured at drafting: msys2's /usr/bin/tclsh8.6 has no tcllib, so a bake driven from that host could not lift the runtime's own zip (its tcl_library) into the kit and the artifact did not boot. punk::zip 0.1.1 -> 0.2.0 adds three commands, stock Tcl only. archive_info reports where the archive begins inside its host file and which offset convention it uses; members walks the central directory and returns one dict per entry without decompressing anything; unzip extracts all or part of it with every member's crc32 verified, directories materialized, and the writer's 2MB whole-member-vs-streaming threshold mirrored. All three accept a plain .zip or a zip attached to an executable or script prefix, so "what is inside this kit / runtime / modpod" is now answerable on a runtime without zipfs. The offset derivation is stated once and shared: offsetbase = cdiroffset - diroffset. Positive means an external preamble with archive-relative offsets, zero means the offsets are file-relative (or there is no preamble); dataoffset is the split point either way. Because every surface reads the ORIGINAL file at that base, the file-relative shape stops being a special case - the broken split-off intermediate is never produced. tclsh90b4_piperepl.exe is the store's one file-relative artifact: the old split-then-tcllib path still fails on it with exactly "Bad zip file. Bad closure.", and it now extracts all 841 members crc-verified in 735ms. extract_preamble consumes that machinery instead of carrying its own scan, and two defects went with the refactor: it read 28 bytes of a 30-byte local file header, and it derived the file-relative base from the FIRST central directory record only (its own '#todo! loop through all cdr file headers'). The shared walk takes the minimum over ALL records and then validates that a PK\3\4 really sits there. Its five puts stdout debug lines are gone. Refusals are decided for every selected member before any file is opened, so an unsupported archive cannot leave a half-populated directory: encrypted entries, zip64 size/offset fields, unknown compression methods, crc mismatch (partial file removed) and member paths that would escape the target are each named. Store and deflate only, mirroring the writer's own primitives. make.tcl's zipfs-less extraction now calls punk::zip::unzip on the original runtime and no longer creates the extracted_<runtime>.zip intermediate. No punkshell code requires zipfile::decode any more. Two categories of hit remain and are deliberate: tcllib's own zip/decode.tcl shipped as a LIBRARY inside some .vfs payloads, and one guarded optional probe inside the vendored third-party ooxml1.10/ooxml.tcl. First tests punk::zip has ever had (src/tests/modules/punk/zip/), covering the three archive shapes from one source tree, the introspection output, the named refusals, and the mkzip -> read round trip - the first coverage that what punkshell WRITES is readable. Verification, all 2026-07-26. Reference host for the dependency-free claim: msys2 tclsh8.6 8.6.12, probed as zipfs / vfs::zip / zipfile::decode all ABSENT - suite driven there harness-free, 28 passed, 2 skipped (the zipfs-gated cross-checks only), 0 failed. 30/30 under Tcl 9.0.3, 28 + 2 skipped under native 8.6. Full source-tree suite after the change: 1142 tests, 1 failure - core/tcl exec-14.3, the documented baseline. Independent cross-check: 868 members of tclsh905.exe extracted byte-identical against the same archive mounted with tcl zipfs. Bake demonstration: 'bake -confirm 0 punk905' driven by the msys2 tclsh8.6 (host=msys-x86_64, target=win32-x86_64) produced extracted_tclsh905.exe/{tcl_library,lib} with no intermediate .zip, and the deployed kit boots with tcl_library at //zipfs:/app/tcl_library, 95 encodings, msgcat 1.7.1, http 2.10.2 - and reads itself with the new reader. Trap worth keeping: zlib stream inflate's 'get' returns only what the stream has already produced, so one get per put silently truncates a large member to the first few chunks (measured 327680 of 5048890 bytes on both 8.6.12 and 9.0.3). The inner drain loop is load-bearing, and the >2MB streaming test exists to catch its removal. Standing question answered and pinned: zipfs does NOT misidentify punk::zip::mkzip directories. It keys on the trailing slash (which punk::zip::walk always emits), not the stored permission bits, exactly as the current cli-999999.0a1.0.tm wording says - the older, less precise wording survives only in frozen module snapshots under src/vfs/mkzipfix.vfs and src/vfs/project.vfs. The real difference from zipfs mkzip is that zipfs writes no directory entries at all. The achieved flip archives the entry and the detail file, and sweeps the live tier: G-034 (the reader is its extract-rather-than-mount alternative, plus the measured finding that make.tcl on 8.6 cannot mount its own templates modpod), G-101 (the read half of a zipfs-less 8.6 container is solved), G-125 (the gate now has a named failure reason to report), G-126 (the member-dict keys and fixture set its parity suite must reproduce, and a back-pointer to G-128 whose only recorded bridge was this goal), G-128 (archive_info answers "is this artifact safe to move the overlay of?" in one call). One acceptance clause is reported for review rather than claimed silently: "NO zipfile::decode requirement remains anywhere in the shipped tree" is satisfied for punkshell's own code, with the vendored-third-party residue named above. The archived detail file's diff is a rename plus the flip's evidence write-up. Assisted-by: harness=claude; primary-model=claude-opus-5[1m]; api-location=anthropic.com	6 days ago
Julian Noble	04d2a51b67	G-122 achieved: make.tcl bakes by target platform, not host personality (punkshell 0.25.0) ... Everything a bake EMITS is now keyed by the artifact's TARGET platform rather than the driving tclsh's personality: the bin/runtime/<tier> store a runtime is read from, .exe suffixing of runtime files and kit outputs, presence checks, and whether the pre-deploy process sweep uses tasklist/taskkill or ps/kill. Host semantics - copy commands, path handling, filesystem case rules, prompts - stay keyed to the host. The default target is the host's platform canon EXCEPT for a cygwin-family host (an msys2/cygwin-runtime tclsh, which reports tcl_platform(platform) unix on windows), which targets win32-x86_64. Such a host now drives the identical kit set, names and store addressing as a native tclsh; before, it reported every kit runtime=missing against a nonexistent mingw64-x86_64 store. mapvfs.config entries take an optional 4th element naming the kit's target platform, so a runtime kept in another platform's tier is a first-class mapping entry. The linux tclkit entry now declares linux-x86_64 and bakes to a suffixless bin/punkshell902. Zip-type kits assemble without zipfs in the driving tcl: when tcl::zipfs::mkimg is absent (any 8.6) the image is built by raw-runtime split + punk::zip::mkzip + concatenation - the same helper the zipcat type uses. Both mount identically (archive-start-relative offsets). Fixes exposed by the above: the runtime capability probe looked for a suffixless filename and so reported find-fail for every runtime on windows; with real capabilities arriving, the extraction try-list was found to test capability presence rather than value, which would send a plain zipfs runtime down the kit path where a failed sdx mksplit replaces raw_runtime with the un-split original; BUILDCOPY names now follow the runtime's own filename; runtime map keys strip only .exe (file rootname would eat the last dotted segment of tclsh9.0.5); and native windows command lines run through a guard suppressing msys2's posix-path argument rewriting - without it taskkill /PID <n> reached taskkill as taskkill C:/<msysroot>/PID <n>, so the sweep could find a running kit but never replace it. punk::platform folds the msys2 family (mingw64/mingw32/ucrt64/clang*) onto one stable 'msys' tag and CYGWIN_NT onto 'cygwin' - msys2's uname renders that token from MSYSTEM, so one binary otherwise canonizes differently per launching shell. New normalize_os; cygwin-x86_64 added to the platform table; 'help platforms' documents the fold. make.tcl check reports the derivation on one line; bakelist rows carry target=<platform> for non-default targets and the detail block names the tier; workflow text gains key note [K9]. New characterization suite maketclplatform.test (5 tests, two self-gating on discovering and probing a real msys/cygwin tclsh). Full suite 1112 tests: 1093 passed, 18 skipped, 1 failed = the documented exec-14.3 baseline. Verified: msys2 tclsh8.6 bakelist output identical to native Tcl 9; a changed punk91 baked and deployed from that host with the sweep killing a running instance msys ps cannot see; a real cross-target linux kit baked from windows to a 24MB ELF; a zipfs-less 8.6 bake producing a bootable zip kit. Assisted-by: harness=claude; primary-model=claude-opus-5[1m]; api-location=anthropic.com	6 days ago
Julian Noble	d9061b90ce	bakelist/bake: loud missing-store-folder diagnosis; punk::platform into bootsupport (punkshell 0.24.1) ... Field-driven follow-ons to G-121 from driving make.tcl with an msys/cygwin-runtime tclsh (scoop msys2 tclsh8.6, tcl_platform(platform)=unix): - bakelist: when the derived per-platform runtime store folder does not exist, a stderr WARNING now shows the platform-canon derivation (tcl_platform os/platform -> canon, observed mingw64-x86_64 under a MINGW64_NT MSYSTEM env) and the header line carries (FOLDER MISSING) - every row reading runtime=missing now self- diagnoses its non-per-entry cause. bake's "No executable runtimes found" exit gains the same note when the folder is absent. Native-host output unchanged (maketclbakelist.test 4 PASS). - make.tcl shell 'help platforms' degraded to "punk::platform package not available" on ALL hosts (not msys-specific): the module was absent from the bootsupport snapshot. Added punk::platform to src/bootsupport/modules/include_modules.config (pure Tcl, deps only Tcl's own platform package); verified the full canon table renders via a piped 'help platforms' under tclsh90 src/make.tcl shell. - G-013 Notes: recorded the msys raw-mode field finding (cursor placed at row 1 after each command under the msys pty class) as a raw-mode-default blocker dimension - console/repl work, deliberately outside the make.tcl host/target catering goal being drafted. Claude-Session: https://claude.ai/code/session_01Jz7wkUsknJzyuJ3tgMaL2t Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com	1 week ago
Julian Noble	0abd07ecd7	G-121: make.tcl bakelist + selective bake (punkshell 0.24.0) ... One parsed-mapping model (::punkboot::lib::mapvfs_parse / mapvfs_kit_outputs / mapvfs_match_outputs) now backs the kit surfaces - the bake machinery, the new bakelist report and the bake/bakelist argdoc kit-name choices all consume the model, never the file format, so the G-024 toml conversion can swap the reader underneath. - bakelist ?kitname ...? (informational SUBGROUP): kit name, type, runtime with presence, vfs folder, deployed state of bin/<kit> vs src/_build/<kit> (current|stale|absent|nobuild; size/mtime fast path, byte-compare when in doubt), anomalies as trailing key=value notes (runtime=missing, vfs=missing, rtrev=r<cur><r<max> via the shared runtime_materialization_check core). Name filtering doubles as per-kit detail (resolved paths/sizes/mtimes). - bake ?kitname ...?: selective kit assembly - unknown names error before any build listing the configured names (flag-order hint included); selected-but- unbuildable kits (missing runtime/vfs) fail fast; runtime BUILDCOPY/caps probe/vfs cksums/vfslibs phase all narrow to the selected kits so other kits' _build/bin artifacts and punkcheck records stay untouched. Bare bake unchanged (verified full-set run). Deprecated alias vfs mirrors the values. - argdocs: SUBVALUES/VALUES_SYNOPSES mechanism, kitname choices enumerated from the mapping at define time (-choicerestricted 0, degrade-safe), block-form help values; SUMMARIES/HELPTEXTS/SUBOPTS/SUBGROUPS/known_commands/plain gethelp/workflow text updated per the update contract; degraded-mode (PUNKBOOT_PLAIN) dispatch collects trailing kit names. - mapvfs.config todo comment retired to point at G-121. - piped characterization: src/tests/shell/testsuites/punkexe/maketclbakelist.test (full-report row/vocabulary + ESC-free, filtered detail, unknown-name errors on both surfaces with the no-build guarantee) - 4 PASS; maketclcolour.test still 3 PASS. - selective-refresh verification (recorded in the goal file): forced punk91 rebuild + deploy via 'bake -confirm 0 punk91'; stat diffs over src/_build and bin show only punk91.exe, punk91.exe.vfs, raw_tclsfe-x64.exe and bin/punk91.exe changed; .punkcheck diffs mention only punk91's records (negative grep for all other kit/vfs names clean). - docs: src/AGENTS.md work-guidance bullet; ARCHITECTURE.md build-entry subcommand list refreshed (bake/bakehouse naming + bakelist, stale in-flux G-112 mention dropped); CHANGELOG 0.24.0 + punkproject.toml minor bump. Claude-Session: https://claude.ai/code/session_01Jz7wkUsknJzyuJ3tgMaL2t Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com	1 week ago
Julian Noble	f5e3ed1ce0	colour policy: unix-class 8.6 terminals detected via the tty channel signature (-mode) ... Second 8.6 tty rung: on unix-class Tcl 8.6 (linux/WSL/mac AND msys2/cygwin- runtime builds, which report tcl_platform unix even on a windows machine - e.g the scoop msys2 usr/bin/tclsh8.6), real ttys are isatty-gated into the tty channel type and expose the serial/tty options (-mode etc) that pipes/ files lack - a zero-exec, dependency-free discriminator exactly parallel to -winsize. Verified: WSL 8.6.14 pty mode=tty colour on ansistrip=0 vs piped tcl86-plain stripped; msys2 8.6.12 piped tcl86-plain (interactive -mode presence per field report); windows batteries + punkexe suites 54/0 unchanged. Together with the 0.23.2 windows console-encoding signature this completes dependency-free 8.6 tty detection - the planned G-122 probe-ladder goal (procfs/test -t/twapi rungs) is superseded before drafting: channel signatures cover every case without exec or optional packages. Also confirmed by byte-diff: 8.6 and 9.x piped help renders are IDENTICAL (modulo native-8.6 zipfs warnings) - no 8.6-specific rendering defect exists; the top-level help's wide Description indent is a cross-version cosmetic of that one constructed definition, present on 9.x too. punkshell 0.23.3 + CHANGELOG; src/AGENTS colour bullet updated. Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com	1 week ago
Julian Noble	ac7dcdb02a	colour policy: never wrap utf-16 console channels; 8.6 windows console auto-detected by encoding signature ... Defect: the G-113 ansistrip transform was pushed onto Tcl 8.6 windows CONSOLE channels, which encode utf-16 ('unicode') - at byte level ESC arrives as 1B 00 so sequences passed through unstripped and the hold-back carry deferred/ dropped real content, seriously mangling interactive punk86/punksys 'src/make.tcl help' layout (user-reported). Chunk-boundary handling itself is sound: a rig proved strip output invariant across chunk sizes 1..4096 over byte-transparent encodings; the failing dimension was encoding, not cutting. (Comparison recorded: shellfilter::chan::ansistrip is the complement - it decodes per the channel encoding and buffers undecodable tails, but assumes line-buffering for sequence splits.) Fix is detection, not utf-16 stripping: only 8.6 windows console channels report -encoding unicode (pipes/files get the system encoding; hidden-console probes confirmed across bawt tclsh86 8.6.13, punk86 8.6.17, punksys 8.6.13; tcl9 consoles report utf-16 but are caught by -winsize first). The policy now treats that signature as tty: mode=tty, colour ON, no transform - interactive 8.6 windows colour with no env var and no twapi. The transform push is now PER CHANNEL and skips utf-16-class channels ('> file' from an 8.6 console wraps stdout only - stderr console keeps its ANSI); ansistrip_pushed is the wrapped-channel list, shell pops exactly those, policy/check lines print ansistrip=stdout+stderr|stdout|0. Verified: hidden-console 8.6 x3 mode=tty ansistrip=0; half-redirected punk86 console run ansistrip=stdout; piped 8.6/9 batteries unchanged (zero ESC, force re-colours); punkexe suites 54/0 (maketclcolour pins updated to the channel-list format). punkshell 0.23.2 + CHANGELOG; src/AGENTS bullet updated. 8.6 unix/WSL stays plain-by-default pending the probe-ladder goal. Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com	1 week ago
Julian Noble	a646f1089f	punk-runtime use accepts suffixless names; make.tcl bake materialization staleness guard ... use wart fixed (both payloads + rewrapped bin/punk-runtime.cmd, checkfile ERROR-free, scriptwrap roundtrip + binscripts freshness suites green 35/0): candidate lookup falls back to <name>.exe when the exact name is absent - exact names (incl. extensionless unix artifacts in foreign -platform staging folders) still match first. Verified live in a throwaway platform folder via the .cmd (ps1 payload) and the bash payload driven directly (msys exe-magic already masked the wart under msys bash; the fallback serves real unix shells). make.tcl: new ::punkboot::runtime_materialization_warning (warn-only, local, no network) - the kit loop compares each wrapped working runtime's beside-toml revision against the highest -r<N> artifact revision in the same folder and emits a recapped BUILD-WARNING naming the repair command. Verified live: toml demoted to revision=1 fires the warning once + recap (and would have caught today's stale-r1 punk9_beta incident at the first bake); current state silent; no spurious rewraps. Pre-family runtimes (no toml) and direct -r<N> references stay silent. Docs: bin/AGENTS.md runtime-manager contract (suffixless use + guard note), src/AGENTS.md Work Guidance bullet; G-121 Notes records the guard as bakelist's acting-path complement; G-031 Notes records the make.tcl-shell punkexe-surface question with the boot-core vehicle recommendation. punkshell 0.23.1 + CHANGELOG. Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com	1 week ago
Julian Noble	889d3cd1c7	G-104: make.tcl buildsuite list/info/build + sources.config self-description contract ... buildsuite group added as a declared passthrough (punk::args + fallback paths): list discovers suites (dirs carrying suite.tcl; _build excluded), info renders the manifest-derived detail, build forwards driver args untouched streaming output and exiting with the driver's status (punk-kit-hosted runs launch the driver via the kit's script subcommand, selected by the G-058 marker). Self-description = manifest option: sources.config gains description/product/ doc/zigpin records parsed by both suite.tcl (strict; pinned-zig default now reads zigpin - one source of truth) and make.tcl (tolerant). suite_tcl90 seeded with its records. Copied trees appear automatically (verified with a throwaway copy). Contract documented in new src/buildsuites/README.md + AGENTS.md, indexed from src/AGENTS.md. CHANGELOG extended under 0.23.0. Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com	1 week ago
Julian Noble	221c2c4fff	G-112 rename core: bake/bakehouse stage-true vocabulary, deprecated aliases, vfslibs fold ... vfs -> bake (kit assembly; vfslibs phase folded in so a bake cannot ship stale binary libs), project retired -> bakehouse (packages + bake, -dirty-abort default ON, refusal names the granular developer flow). project/vfs remain as deprecated aliases: one-line stderr notice + pre-dispatch mapping; alias argdocs mirror their targets so flags parse identically. vfslibs survives as a standalone narrowing (in-session decision recorded in the goal file). SUBOPTS/SUMMARIES/HELPTEXTS/SUBGROUPS/known_commands, end-of-run guidance, plain gethelp and workflow text rewritten to the two-persona model (groups: build & bake / promotion gates / source maintenance / deprecated aliases). Verified: tabled + PUNKBOOT_PLAIN help; dirty-tree refusal via bakehouse and via the project alias; alias help renders. punkshell 0.23.0 + CHANGELOG. Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com	1 week ago
Julian Noble	e03ce1d64a	G-113: make.tcl terminal-aware colour policy (tty probe, force overrides, zero-ESC piped) ... Startup policy: NO_COLOR > PUNK_FORCE_COLOR/FORCE_COLOR > stdout -winsize tty probe (Tcl 8.7+/9); Tcl 8.6 fails OFF. Piped/unknown non-forced runs push an ansistrip transform on stdout+stderr - zero ESC bytes from every emitter incl. module-side (punk::ansi's colour_disabled deliberately keeps non-colour effects; design finding recorded in the goal file). shell pops the transform. sgr_cache cleared for punk-exe-hosted pre-loaded interps per the punk::ansi contract. define_global_ansi fully gated; raw-SGR literals routed through new ::punkboot::sgr gate (fixes a malformed \x1b\31m). check reports the policy. make.tcl converted CRLF->LF. Verified: tclsh90 + punk91 kit piped zero-ESC (check/help/workflow/modules); force overrides re-colour piped output; NO_COLOR always suppresses colour; 8.6 tcl86-plain; real Windows console mode=tty (hidden-console evidence); WSL pty mode=tty vs piped-plain (tclkit-902-Linux64). New suite punkexe/maketclcolour.test 3/3. src/AGENTS.md bullet revised; punkshell 0.22.2. Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com	1 week ago
Julian Noble	cae9f36d3e	Canonical punkshell platform names: punk::platform module, help topic, tree sync (G-105 groundwork) ... Survey outcome (punkbin vs punkshell platform folders): five naming sites had drifted - punkbin folders, bin/runtime, vendorlib_tclX dirs, the punkboot platform_generic snips (an old platform::generic copy), and the Tcl platform package itself whose outputs vary by version (1.1.x renamed modern macOS to 'macos', aarch64/amd64 pass through unmapped). Canon: <os>-<cpu> punkshell platform-dir names, cpu normalized amd64->x86_64 and aarch64->arm64 (arm = 32-bit; on macosx arm folds to arm64 - Apple silicon is 64-bit only), os macos->macosx. The universal 'macosx' name is the runtime-tier convention (punkbin + bin/runtime keep one macOS folder, per make.tcl's existing collapse); per-arch macosx-x86_64/macosx-arm64 serve the lib tier. - new module punk::platform 0.1.0: platforms (canonical records with status supported/dormant/recognized + tiers), normalize, local ?-tier lib|runtime? - full PUNKARGS argdocs. Tcl's platform package stays the raw identifier underneath. - punk 0.2.7: 'help platforms' topic (alias 'platform'; all prefixes mutually ambiguous so they fall through to command lookup, per the env/environment precedent) - canon table with the local interpreter marked and raw platform-package identifiers for comparison. - boot: punkboot platform_punk (inline normalization copy, sync-comment contract with the module) in punk_main.tcl/project_main.tcl/make.tcl; all platform-dir call sites switched to it. make.tcl exercised live; main.tcl copies brace-verified. - vendorlib_tcl8/9 synchronized to canon: freebsd-amd64 -> freebsd-x86_64 (READMEs updated), freebsd-arm64/linux-arm64/macosx-arm64 added, tcl8's untracked-empty linux-arm now tracked + tcl9 gains linux-arm, stray untracked macosx-arm empties removed, msys-x86_64 marked dormant pending a utility decision, top-level READMEs state the canon contract. - punk-runtime bash prongs emit canonical names: aarch64 -> linux-arm64 (no fetch default until punkbin carries that folder), arch-aware freebsd/openbsd/netbsd/dragonflybsd via normalized cpu tokens. Rewrapped; roundtrip pin PASS; layout copy + .ps1 twin refreshed. Flagged for user decisions (recorded in G-105 Notes): punkbin linux-arm holds an arm64-named kit (recommend linux-arm64 folder at next arm publish; artifacts immutable), msys-x86_64 disposition, optional platform-1.1.x re-vendor, src/vfs stays mapvfs-categorized (recommend a mapvfs platform column when cross-wraps land, not a .vfs tree restructure). Project 0.18.0. Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com	2 weeks ago
Julian Noble	e2fc7332fe	G-087 stages 4+5: overlay merge primitive, marker/matrix retirement, version seeding ... Stage 4 - documented overlay semantics implemented (commandset::layout 0.2.0): layout_materialize resolves a layout to its overlay chain (vendor tier then custom tier per store+vendor, <name>@<base> derived-layout folders expanding their base chain first, cycle-guarded) and composes multi-folder chains into a disposable staging dir applying <item>.anti deletion markers (zero-byte marker files recommended - committable, unlike the originally documented empty marker folders, which are also accepted). Single-folder chains with no markers are used in place, so punk.project (store and zipfs modpod) behaviour is unchanged. project.new (commandset::project 0.4.0) copies from the materialized path and the layout listing/scanning commands show the effective merged view. Fixtures: punk.othersample is now a live derived layout (new custom-deck fauxlink ref + .gitignore.anti demo marker); extra.txt/store README rewritten to the implemented semantics. New tcltest suite src/tests/modules/punk/mix/testsuites/layout/materialize.test (20 tests). Anti markers deliberately stay a plain filename convention rather than tag-bearing fauxlinks: a fauxlink is a reference tooling may follow (fcat auto-follows), a marker is a tombstone with no target. Stage 5 - retirements and generated-project version seeding: - The empty unimplemented child-side src/PROJECT_LAYOUTS_CREATE_FROM_... marker folder is deleted along with its project.new and make.tcl sync exclusions. - The vendor/custom x _project matrix collapses for layouts: custom/<vendor> is the one override level; _project folders join no overlay chain (the pseudo-vendor remains for decktemplates module/utility templates only). - project.new seeds generated projects post-materialization (only-if-missing, never from payload): punkproject.toml ([project] name + 0.1.0), a matching CHANGELOG.md ## [0.1.0] header, and punkorigin.toml - an interim generation provenance baseline (utc, layout name + resolved store target, punk::mix::templates version, punkshell version when derivable, origin path) for the G-027 pull design to adopt (noted in G-027). Also: script-mode/programmatic project.new robustness (explicit shellrun require; punk::mix::util askuser/do_in_path/foreach-file fully qualified - the util:: shorthand exists only after cli commandset import). Includes the concurrently-landed (other session, previously uncommitted) 0.3.1 early module-name validation fix in project.new, shipped within the 0.4.0 bump. G-087 flipped achieved 2026-07-19 (verification in the detail file; archive move follows in the next commit). punkshell 0.16.0 -> 0.17.0. Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com	2 weeks ago
Julian Noble	411df7482b	G-087 stage 3: thin layouts + generation-time bootsupport injection (sources) ... 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	2 weeks ago
Julian Noble	c1c7ab3ee7	make.tcl: new 'workflow' subcommand - embedded ASCII build/release data-flow overview ... Prints the release-ready command sequence, source -> built-packages -> bootsupport / kit-vfs / kit-executable folder-flow diagrams, and keyed notes (magic-version stamping, punkcheck provenance, staleness gate, -confirm policy, locked-exe deploys, VCS-tracked output targets). The text is embedded in make.tcl (::punkboot::workflow_text) rather than a data file so it travels with the make.tcl copies seeded into generated-project layouts; content is project-generic accordingly. A MAINTENANCE key in the output states the update contract. punk::args-documented via the existing constructed-definition machinery (SUMMARIES/HELPTEXTS/SUBOPTS + informational SUBGROUPS entry) so tabled help, 'help workflow' and the top-level subcommand table all cover it; also registered in known_commands and the plain punkboot_gethelp fallback, and exempted from the bootsupport staleness gate alongside check/projectversion. Verified in normal and PUNKBOOT_PLAIN dispatch; stray arguments raise a punk::args toomanyarguments usage error; output is pure ASCII, width <= 100. src/AGENTS.md Work Guidance gains the agent update contract: change the workflow text in the same change-set as any build data-flow change, keep the ASCII/width/structure rules, verify with 'make.tcl workflow' (+ one PUNKBOOT_PLAIN run), and the registration-point checklist for subcommand changes. Layout make.tcl copies propagate via 'make.tcl bootsupport' - never hand-synced. punkshell 0.12.42. Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com	2 weeks ago
Julian Noble	596857c407	G-087 hygiene: remove dead layout residue (modpod payload, make.tcl old_layout_update_list) ... - punk::mix::templates modpod (0.1.4): dead templates/layouts/project payload subtree removed - design-generation residue with no reader; layout payloads live in src/project_layouts, located via layout_refs. - src/make.tcl: unused old_layout_update_list (referencing the long-gone src/mixtemplates and modules/punk/mix/templates paths) removed; bootsupport help text now names src/project_layouts/custom/_project/<layoutname> instead of mixtemplates. - src/project_layouts custom/_project make.tcl copies: punkcheck-managed sync outputs refreshed by the verification 'make.tcl modules' run. Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com	2 weeks ago
Julian Noble	a0cd2a982d	make.tcl: warn when a kit .vfs folder has no startup script ... New vfs_startup_script_warning check runs for each .vfs folder about to be built against a runtime: it passes if the folder has a root main.tcl or a root fauxlink resolving to the name main.tcl whose target exists and is a .tcl file. Otherwise a noticeable warning is emitted and the build proceeds (a kit with no startup script is legal). Warnings use a new general-purpose ::punkboot::print_build_warnings channel: column-0 BUILD-WARNING: token for greppability, ANSI highlight for humans, and recap at end of run via the wrapped ::exit (same treatment as PROVENANCE-WARNING). Overlay-only folders with no runtime mapping (e.g _vfscommon.vfs) are not checked. Contract documented in src/vfs/AGENTS.md. Motivated by the punk9win.vfs split initially dropping the main.tcl punk_main fauxlink from punk9wintk90b2.vfs. Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com	3 weeks ago
Julian Noble	378ba8c084	make.tcl shell under punk exes: recompute tcl_interactive, restore accelerator-forgotten packages ... Fixes the two user-reported symptoms of '<punkexe> src/make.tcl shell': Missing prompts: app-punkscript correctly forces ::tcl_interactive 0 for script execution, and punk::repl is already loaded at kit boot - so the shell branch's 'package require punk::repl' re-loads nothing and the repl's load-time interactivity probe (repl line ~44) never re-runs, leaving prompts suppressed on a real console. The shell branch now recomputes ::tcl_interactive via punk::repl::is_interactive against the actual input channel before repl::init/start. Piped behaviour unchanged (probe still reports non-interactive). Raw-mode 'invalid command name struct::set': the accelerator-reload block (package forget + rename of sha1/md5/struct::* so reloads can pick up accelerators from the restored full paths) relied on later package-require chains to restore the forgotten packages. Under a kit, the consumers (punk::lib, punk::du, punk::nav::fs, flagfilter) were pre-loaded at kit boot, their requires never re-fire, and the first repl-thread-side call of a struct::set-backed punk::lib proc (lunique_unordered's self-redefining first invocation, reached via flagfilter/nav::fs in interactive/raw paths) hit the destroyed command. The block now records which of the forgotten packages were actually loaded and re-requires them immediately. Verified by thread-probe: the repl-thread interp now shows struct::set 2.2.5 + sha1 2.0.5 restored identically under tclsh90 and punk91 (previously absent under punk91); the codethread was always unaffected (it re-requires its own package list). src/AGENTS.md: new note - punk-exe-hosted make.tcl runs in a pre-loaded interp, not a virgin one (no-op requires, load-time state like the tcl_interactive probe, kit-vs-bootsupport module provenance mixing); interp surgery in make.tcl must restore deliberately and be tested under both tclsh and a punk exe. Layout make.tcl copies re-synced via the punkcheck channel. Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com	3 weeks ago
Julian Noble	1370484f5e	make.tcl: self-build guard for kit builds under a built punk exe; quieten libunknown double-init ... Self-build guard (user-identified gap): when make.tcl is driven by a built punk executable, the kit whose deployed executable is the running interpreter is now skipped before any build work, with guidance to rerun under tclsh or a different kit. Previously the pre-deploy process sweep matched processes by executable name only and would taskkill the build's own process mid-run with -k (suicide: remaining kits unbuilt, no recap, dangling punkcheck event); without -k only the polite kill's refusal on console processes saved the run, and the deploy delete of the running image would fail with a cryptic message. The sweep additionally excludes the build's own pid unconditionally, covering a same-named copy driving the build from a non-deploy path. Informational and update subcommands were already safe (they exit before the kit machinery); building other kits from a punk exe remains supported. Verified live: 'punk91 src/make.tcl vfs -confirm 0' skips punk91.exe with the warning and processes the other kits normally; plain tclsh runs unaffected. libunknown quietening: 'punkexe src/make.tcl <cmd>' emitted "punk::libunknown::init already done - unnecessary call? info frame -1: ..." because punk_main.tcl had already initialised libunknown (renaming ::package) and make.tcl unconditionally re-sourced the bootsupport copy and called init again, tripping init's load-bearing rename guard. make.tcl now leaves an already-active libunknown in place (no re-source - also avoids silently swapping the running copy for the bootsupport copy when versions diverge); plain tclsh runs source+init exactly as before. Verified: no diagnostic from 'punk91 src/make.tcl projectversion'. src/AGENTS.md build guidance updated (punk-exe-driven builds and the self-kit skip); layout make.tcl copies re-synced via the punkcheck channel. Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com	3 weeks ago
Julian Noble	d0834c1d05	make.tcl argdoc: adopt G-045 @normalize block-form authoring; AGENTS guidance for punk::args doc ergonomics ... Fixes the constructed-definition indent leak user review spotted in 'make.tcl help' output (@cmd -help Description first line rendered less indented than continuations): HELPTEXTS and the inline shell/help/toplevel help values are now block-form (first value line whitespace-only) with a bare @normalize in every constructed definition, per G-045's preferred style. The braced option fragments never leaked (literal block-shaped parts get file-style normalization) and head-form values are contractually untouched by @normalize. Also adds a define-time capability probe (punk::args::get_spec on representative ids inside the guarded block) so a stale punk::args that accepts the raw text but cannot resolve a mechanism (e.g pre-@normalize snapshots) degrades to the plain fallback immediately instead of erroring at first parse. AGENTS infrastructure for future documentation work: src/modules/AGENTS.md "Documentation And Comments" gains a "punk::args definition authoring ergonomics" subsection (G-045 mechanisms: @normalize + block form for constructed defs, -unindentedfields, -& record continuation, container quoting rules; plus the G-030 lessons: explicit @form -synopsis for script-level ids, -optional 0 for pointed choiceviolation errors); src/AGENTS.md cross-references it and names ::punkboot::argdoc as the in-tree constructed-def exemplar. Follow-up recorded in the G-030 archive. Verified: flush Description rendering for toplevel/subcommand/shell/help usage; dispatch, degraded mode (PUNKBOOT_PLAIN) and usage-error paths re-verified; layout make.tcl copies re-synced via 'make.tcl bootsupport -confirm 0' (punkcheck channel); goals_lint unchanged (only the pre-existing G-078/G-081 index-mirror findings). Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com	3 weeks ago
Julian Noble	7ea1deaae5	G-030 achieved: make.tcl dogfoods punk::args - tabled usage, declared subcommands, -confirm prompt policy ... All 15 make.tcl subcommands are punk::args-declared ((script)::punkboot + (script)::punkboot::<sub>, built from single-source summary/help/opt dicts with shared option fragments and explicit @form -synopsis). Bare make.tcl / -help, 'help ?subcommand?' and '<subcommand> -help' render tabled usage; invalid flags/subcommands raise punk::args usage errors (exit 1) with unambiguous prefix resolution; 'shell' is a declared passthrough. Prompt policy: new -confirm 0|1 (default 1) on every confirmation point (bootsupport minor-staleness gate, vfscommonupdate REPLACE, kit-type mismatch). Default prompts only on an interactive terminal and aborts fast with guidance on non-interactive stdin (::punkboot::lib::stdin_is_interactive; Tcl 8.6 lacks the -inputmode probe and is assumed interactive). -confirm 0 proceeds (staleness, REPLACE) or skips the mismatched kit. The piped-y agent workflow is retired; the old vfscommonupdate decline half-abort (printed done, exit 0) now exits 1. Degrade rule: punk::args/punk::ansi/textblock boot requires guarded; definition load caught with fallback to a self-contained scan (-k/-dirty-abort/-confirm supported) + plain punkboot_gethelp (availability NOTE factored into punkboot_availability_note, shared by both paths); rendering degrades independently of parsing (errorstyle minimal / plain help when the ANSI stack is unhealthy); PUNKBOOT_PLAIN=1 forces degraded mode. punk::args joins the bootstrap-tracked _runtime_deps staleness set (parsing contract only - the rendering stack degrades instead; contract docs updated in src/bootsupport/AGENTS.md + src/modules/AGENTS.md, workflow docs in src/AGENTS.md + src/tests/shell/AGENTS.md). Verified: usage/help/error paths, vfscommonupdate fail-fast and -confirm 0 runs with closed stdin, staleness flag route live (args 0.5.0->0.12.0 tripped the gate), degraded-mode help/check/info, full 'project -k -confirm 0' kit build. Dogfooding finding recorded in the goal file: punk::args 0.12.0 reports generic overflow where 0.5.0 reported choiceviolation for optional-choice mismatches (worked around with required leaders; candidate error-selection improvement). Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com	3 weeks ago
Julian Noble	1fa2988a3f	make.tcl: dirty-src provenance gate for build/promotion commands (G-026 direction) ... Build/promotion commands (project packages modules libs vfs vfslibs bin bootsupport vfscommonupdate) now warn when src/ has uncommitted fossil/git changes - artifacts built from dirty src have no committed provenance. Warn-only by default; new -dirty-abort flag makes the check aborting. With '<builtexe> src' available for evaluating uncommitted source directly, building is the promotion step this treats it as. - punkboot::utils 0.2.0: vcs_dirty_warnings gains optional scope arg so only changes under a subpath (src) count; unscoped vendorupdate call unchanged. - Warnings print with a plain column-0 PROVENANCE-WARNING: token (greppable in redirected output) + ANSI colour, shared with vendorupdate's dirty source-project check, and are recapped at end-of-run via a wrapped ::exit so they survive scrolling chatty build output. - Interactive terminal runs (stdin -inputmode probe, tcl 8.7+/9) get a 3s ctrl-c grace countdown before a dirty build proceeds; piped/agent/CI runs pay no delay. - 'make.tcl check' reports src provenance status and what the build commands would do. - Guarded require: stale/missing punkboot::utils snapshot degrades the check to a skip notice, but -dirty-abort then aborts rather than silently losing the requested strictness. Project 0.10.2 -> 0.10.3. Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com	3 weeks ago
Julian Noble	0505397590	G-037 achieved: make.tcl vfslibs propagates vendorlib packages into kit vfs lib_tcl trees; 8.6 kits to tcludp 1.0.13 ... New 'make.tcl vfslibs' step (also run inside 'make.tcl project' before kit vfs assembly): propagates declared vendored platform-library packages into kit vfs lib_tcl<N> trees, ending the hand-copying that let kits ship a known-buggy tcludp through three make invocations (the G-036/G-037 motivating case). - declaration: src/runtime/vendorlib_vfs.toml, parsed with bootsupport tomlish (no ad-hoc parsing; G-024's mapvfs toml conversion NOT required first - this file is recorded as a candidate for absorption into it). [install.<name>] entries: source (relative to src/), targets (kit vfs lib folders relative to src/vfs/), optional supersedes (folder names removed from each target before install - explicit, no silent mixed-version provision per G-035 concerns). - participation is per-package per-kit; authority is the declaration - nothing syncs undeclared, so the known vendorlib/kit twapi drift is deliberately untouched (resolves the direction/authority design question). - punkcheck provenance at src/vfs/.punkcheck (gitignored, outside kit payloads); skip-if-unchanged proven (rerun: 0 copied, 9 skipped per target); malformed/unresolvable entries fail the build naming the entry (exit 3). - 8.6 kits upgraded (the G-036 loose-end decision, recorded): tcludp 1.0.13 is dual-generation (pkgIndex selects tcl9udp1013.dll on 9+, udp1013t.dll on 8.5+) so the single vendorlib_tcl9 source serves punk8win.vfs/lib_tcl8; superseded udp1.0.12 removed. - verified on rebuilt kits: punksys/punkbi (8.6.13) and punk902z (9.0.2) all report package require udp == 1.0.13 loading the generation-appropriate dll from their vfs; no udp1.0.12 remains under src/vfs; punksys piped-shell exit smoke clean. - G-037 flipped proposed -> achieved 2026-07-08 under user direction (no intermediate active stop). - includes project-build byproducts via established channels: bootsupport snapshots refreshed to punk-0.2.1 / punk::lib-0.3.0 (from today's version bumps) and make.tcl synced into layout copies. - project 0.4.8 (CHANGELOG entry) Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com	3 weeks ago
Julian Noble	c98bb5b56e	make.tcl projectversion: escape [X.Y.Z] in warning messages ... The version-mismatch and missing-header warning branches interpolated the literal [X.Y.Z] inside double-quoted puts strings, so Tcl attempted command substitution and the check died with `invalid command name "X.Y.Z"` the first time a warning branch actually fired (surfaced by a manual projectversion check during the 0.4.2 bump, whose CHANGELOG entry was missing at the time). Brackets now backslash-escaped. Layout copies of make.tcl synced by the project build included. Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com	4 weeks ago
Julian Noble	d88e1c1759	punkboot::utils 0.1.1: move vendorupdate dirty-checkout check into module ... Move vendor_source_dirty_warnings out of make.tcl into punkboot::utils as vcs_dirty_warnings (PUNKARGS-documented, caller-label param so the bootsupport update path can share it per G-026). make.tcl now uses a guarded lazy require and degrades to skipped-with-warning if the bootsupport snapshot lacks the proc - a stale/broken snapshot must never brick the make.tcl commands used to repair it. Chicken-and-egg-safe ordering used and now documented in src/bootsupport/AGENTS.md ("Moving make.tcl functionality into punkboot::utils"): edit src module + bump buildversion, make.tcl modules, make.tcl bootsupport, only then repoint make.tcl call sites. Boot-phase code (path setup, punkboot::lib prompts, package-availability checks) stays self-contained in make.tcl. Bootsupport snapshot refresh from the sanctioned pipeline: punkboot::utils 0.1.0->0.1.1, shellrun 0.1.2->0.1.4 (punk::args require fix catch-up), punk::console 0.7.1 content catch-up; layout mirrors via the punkcheck-tracked sync steps. New tests: src/tests/modules/punkboot/utils/testsuites/utils/vcsdirty.test (git fixture: dirty/clean/dedupe/label/unversioned/missing) - 25/25 across punkboot suites; vendorupdate verified end-to-end through the module path. Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com	4 weeks ago
Julian Noble	69d9b8f23a	vendorupdate: warn when pulling from dirty source checkouts; goal G-026 ... make.tcl vendorupdate now walks up from each vendor source path to the nearest fossil and/or git root and warns (non-fatal, once per VCS root) when the checkout is dirty - vendored artifacts built from uncommitted source have no committed provenance. Silent for unversioned or missing locations; dual git+fossil roots report each VCS separately. First real run flagged 8 dirty source projects (the tomlish 1.1.7/1.1.8 incident - vendored content whose source history ended at 1.1.6 - motivated this, remedied upstream by tomlish checkin 37b71e82). Goal G-026 (proposed) carries the enforcement follow-on: abort with explicit override, warn-only as configured mode, shared coverage of bootsupport_localupdate, and a recorded decision on the residual staleness gap. Abort-by-default now would block routine work given the dirty-project count. Project version 0.2.5; vendorupdate doc note in src/AGENTS.md. Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com	4 weeks ago
Julian Noble	c8072d7945	Extract punkboot::utils module + tests, bump project to 0.2.1 ... Move project-version helper procs (parse_punkproject_version, read_punkproject_version, read_changelog_latest_version) out of make.tcl inline definitions into a loadable punkboot::utils module so the parsing logic is unit-testable. - src/modules/punkboot/utils-999999.0a1.0.tm: new module (0.1.0) with the 3 procs in punkboot::utils namespace, PUNKARGS argdoc blocks. - src/modules/punkboot/utils-buildversion.txt: initial 0.1.0. - src/tests/modules/punkboot/utils/testsuites/utils/utils.test: 19 tests covering section tracking, missing fields, wrong sections, whitespace, quote styles, changelog header parsing, pre-release suffixes. All pass. - src/make.tcl: inline procs removed; projectversion block now does package require punkboot::utils and calls punkboot::utils:: procs. - Layout make.tcl files (punk.shell-0.1, punk.project-0.1): same edit; punk.basic keeps inline procs (no bootsupport tree). - include_modules.config: added punkboot::utils entry (main + 2 layouts). - Bootsupport snapshots propagated via make.tcl bootsupport. - AGENTS.md: project version bump 0.2.0 -> 0.2.1 (patch: new make.tcl projectversion subcommand is part of the product surface); added clarifying line that make.tcl command interface warrants at least a patch bump; src/project_layouts/ added to directories agents should not directly modify. - CHANGELOG.md: 0.2.1 entry. Assisted-by: harness=opencode; primary-model=openrouter/z-ai/glm-5.2; api-location=openrouter.ai	4 weeks ago
Julian Noble	78810ba0af	make.tcl: restore 'shell' command guard deleted by projectversion edit ... The projectversion commit accidentally removed the 'if {$::punkboot::command eq "shell"} {' guard line, orphaning the shell command body (package require punk/repl, repl::start) at top-level scope. This broke every command whose if-block lives after line 1942 (vfscommonupdate, vendorupdate, bin, project, modules, libs, packages, vfs) — they would hit the orphaned shell body and attempt to start a REPL instead of running their intended function. No behaviour change beyond restoring the guard; diff vs pre-projectversion make.tcl is now purely additive. Assisted-by: harness=opencode; primary-model=openrouter/z-ai/glm-5.2; api-location=openrouter.ai	4 weeks ago
Julian Noble	717432676f	project versioning: change-driven bump policy + make.tcl projectversion check ... Add a project-level version bumping mechanism for punkshell, tracked in punkproject.toml, independent of individual module versions. - root AGENTS.md: new 'Project Versioning' section with change-driven SEMVER bump policy (patch/minor/major triggers), CHANGELOG.md requirement, advisory enforcement contract, and independence from module versions. - src/AGENTS.md: cross-reference to root Project Versioning section so agents working in src/ discover the rule during their DOX chain walk. - CHANGELOG.md: new repo-root file with initial 0.2.0 entry; latest '## [X.Y.Z]' header must match punkproject.toml version. - src/make.tcl: new 'projectversion' subcommand — read-only, advisory check that warns on CHANGELOG/punkproject.toml version mismatch and on src/ commits since the last punkproject.toml change. Exempt from bootsupport staleness abort (same as 'check'). Self-contained Tcl, no punk deps. Assisted-by: harness=opencode; primary-model=openrouter/z-ai/glm-5.2; api-location=openrouter.ai	4 weeks ago
Julian Noble	ed7ed009b4	superseded-module pruning with punkcheck DELETE events + virtual version sources ... Resolves the build-maintenance TODO: built module trees no longer accumulate superseded intermediate versions, and .punkcheck state stays consistent because every deletion is recorded through punkcheck's event mechanism. punkcheck (0.3.0): - installsource_add_virtual + installevent method targetset_addsource_virtual: 'virtual' named-value SOURCE records (-type virtual -path virtual:<id> -value <v>) compared by stored value, participating in targetset_source_changes. Needed because successive module versions are built from the same physical source files - the recorded virtual module_name/module_version identify which product of the source fileset a target is, at install and delete time. punk::mix::cli (0.5.0): - lib::prune_superseded_target_modules: deletes lower-version .tm siblings only when records prove the same module line (virtual module_name match, or legacy fallback: recorded sources share the keep-version's source folder(s) and name prefix). Unrecorded files are never deleted - reported to stderr instead. - lib::prune_sourcevanished_targets: mirror-prune of recorded targets whose recorded source files no longer exist (layout bootsupport copies, vendormodule copies) - intentional multi-version vendoring is preserved. - build_modules_from_source_to_base prunes after each module install/skip and records virtual module identity sources on installs. make.tcl: - bootsupport: non-glob include_modules.config entries track only the latest version - superseded recorded snapshot versions pruned; project-layout copies mirror-pruned; virtual identity recorded on snapshot installs. Calls guarded (info commands) so a stale bootsupport snapshot degrades to a warning and the two-pass modules+bootsupport bootstrap self-heals. - vendormodule copies in root modules*/ mirror-pruned after install. docs/config: - include_modules.config headers now document the entry format (non-glob = latest-only + prune; glob chars = keep all matches; unrecorded never pruned) - src/AGENTS.md TODO replaced with the durable prune contract; src/bootsupport/AGENTS.md + src/tests/modules/AGENTS.md updated tests: src/tests/modules/punk/mix/testsuites/cli/prune.test (19 tests) covering virtual source recording/comparison and prune identity/safety rules. Suites: punkcheck 64/64, full suite under Tcl 9.0.3 green except pre-existing exec-14.3. payload sync: bootsupport snapshots, project layouts and _vfscommon.vfs pruned of superseded intermediates (~570k lines of stale .tm copies removed). Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com	4 weeks ago
Julian Noble	df78ff9bb5	make.tcl bootstrapping fix, punkcheck refactor and tests	4 weeks ago
Julian Noble	3b261d08b0	update bootsupport	1 month ago
Julian Noble	b69d0e50f3	punk::path and punk::lib fixes	1 month ago
Julian Noble	8f34b311bb	src/make.tcl exclude AGENTS.md from copying to installation folders	2 months ago
Julian Noble	36cb87b0dd	punk::lib - tclscript_info tclscript_showparse, remove line continuations for better cmdtrace support	3 months ago
Julian Noble	0c63b0226b	make.tcl - fix for tclkit runtimes & remove unnecessary copy when zip based runtime	4 months ago
Julian Noble	da11cb6b8f	fix runtime-fallback sdxpath commandline	5 months ago
Julian Noble	bd0a67cb49	fix typo for runtime_buildcopyname	5 months ago
Julian Noble	66d5a767a7	move test for have_sdx til after runtimes examined	5 months ago
Julian Noble	c50fa3171c	attempt to use a runtime with tclkit capability as fallback for tclkit for sdx when tclkit/sdx not available as executables	5 months ago
Julian Noble	c740d29a34	ensure mounted runtime found as possible runtime if it's in the bin/runtime folder	5 months ago
Julian Noble	17b974915e	another _BUILDCOPY fix	5 months ago
Julian Noble	952b88f4e0	fix make.tcl project error with _BUILDCOPY	5 months ago