Tree: a7bc62c3fb

master

v0.1a

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from 'a7bc62c3fb'

${ noResults }

Commit Graph

5 Commits (a7bc62c3fb1ae2ec7b438444196a241c9c18d18e)

Author	SHA1	Message	Date
Julian Noble	a7bc62c3fb	punk::libunknown 0.3.0: ::package override installs via commandstack (G-176 increment 2; project 0.63.0) ... The ::package override (the 'epoch' subcommand and controlled 'forget') now installs via commandstack::rename_command -renamer punk::libunknown instead of the former 'rename ::package :📦:' + namespace-import mechanism. Both live ::package overrides (this and punk::packagepreference's) now share one managed stack whatever the install order - stack removals and third-party renames re-link correctly instead of operating on the wrong command (previously commandstack's ::package stack believed the packagepreference wrapper was live while libunknown's unmanaged import actually was; restore_original would have stranded :📦:). Migration deltas (exactly the set enumerated in the goal Context): - the override body runs at :: - the four bare epoch_incr_pkg/epoch_incr_tm calls are fully qualified (the old namespace-import execution context is gone) - the dead 'variable has_package_files' declaration dropped (its only use was already commented out; the module-load probe stays) - the two :📦: delegation sites (forget arm, default arm) now delegate via COMMANDSTACKNEXT; :📦: no longer exists (nothing in the tree called it) - init does 'package require commandstack' (a no-op when already provided - e.g whenever punk::packagepreference::install ran first, as in punkshell boot; resolvable via tm paths in every other real init context - bootsupport and the common vfs both carry commandstack-0.7.1) - re-entry guard is now a stack query for the punk::libunknown record (same 'already done' notice; the old ::punk::libunknown::package proc-existence check tested a proc that no longer exists) - init argdoc reworded; file renamed libunknown-0.2.4.tm -> libunknown-0.3.0.tm (git mv + fossil mv) with Meta/manpage/provide-block version updates and a changelog entry per the in-file bump procedure. Behaviour of every subcommand arm is unchanged: all increment-1 BEHAVIOUR pins in packageoverride.test passed byte-identically; only its four MARKED-TO-FLIP install-shape pins flipped as fenced (origin ::package, no :📦: residue, managed stack records - 1 solo, 2 in both packagepreference interop orders). discovery.test and packageoverride.test child interps now pre-source the source-tree commandstack by path (their tm paths are cleared); libsearch/shadowing children resolve commandstack via inherited parent paths and needed no changes. Two out-of-scope items recorded as open Follow-ons in the goal (Scope amendment needed if pursued): boot-site commandstack pre-sourcing (punkboot core.tcl / make.tcl / punk::repl / punk::lib child-seeding - to preserve the minimal-untracked epoch intent exactly) and make.tcl's 'info commands ::punk::libunknown::package' skip-guard modernization (old kits still satisfy it; switch to a package-provide check before or with the 0.3.0 bootsupport/kit promotion). Goal Scope mirrors updated to the new filename (rename anticipated in the Scope text). Project 0.62.2 -> 0.63.0 + CHANGELOG. Suites: libunknown tree + loadedlib 42/42; full modules tree 1346 total / 1335 pass / 11 constraint-skipped / 0 fail (zig-built tclsh90s 9.0.5); testbody_lint 1699 clean; goals_lint clean (80 active-index / 96 archived); make.tcl projectversion consistency OK (and that run itself exercised the bootsupport-0.2.4 transition path live). Claude-Session: https://claude.ai/code/session_01QgaxV27VZkmEec7oNbEVFc Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com	2 weeks ago
Julian Noble	ec781d7019	punk::libunknown 0.2.3: pkgIndex.tcl scripts run in the global namespace again (punkshell 0.27.1) ... A third-party 8.6 kit under evaluation (Lean Undroidwish Construction Kit, 32-bit windows) could not load its own bundled twapi 4.7.2 inside punkshell: P% package require twapi invalid command name "twapi::set_scriptdir" ("package ifneeded twapi 4.7.2" script) twapi's pkgIndex.tcl defines 'namespace eval twapi { proc set_scriptdir ... }' when the INDEX is sourced, and its ifneeded script calls that command at require time. The command existed - as ::punk::libunknown::twapi::set_scriptdir. punk::libunknown 0.2.0 moved index sourcing out of 'namespace eval ::' into source_pkgindex, a proc of the punk::libunknown namespace, to stop each index's helper variables leaking into the global namespace and to stop a user global named 'dir' being clobbered. That fixed the frame, but a proc body executes in ITS OWN namespace, so an index's RELATIVE 'namespace eval foo' started creating ::punk::libunknown::foo instead of ::foo. Stock tclPkgUnknown is a proc in ::, so indexes have always had global resolution; the ifneeded script, evaluated later at global scope, then looked for a command that was never there. The body now runs via apply with :: as its namespace argument, which gives both properties at once: a local frame (index helper variables still discarded, user 'dir' still safe) and the global resolution context indexes are written against. Not twapi-specific: any index that defines commands or namespaces at source time for its own ifneeded scripts to use hits this, and the pattern is common in third-party indexes. punkshell's own vendored twapi 5.0b1 happens to avoid it (self-contained 'apply' ifneeded scripts), which is why the tree never surfaced it. Verified on the LUCK 8.6.10 runtime end-to-end - 'package require twapi' at the punkshell prompt now returns 4.7.2 with ::twapi::scriptdir correctly set - and pinned generically by pkgindex_relative_namespace_is_global in the discovery suite, whose new fixture copies twapi's pattern so no third-party kit is needed. The pin was proven to bite: driven against the pre-fix body the same fixture fails with 'invalid command name' and leaves ::punk::libunknown::pklu_nsindex behind; against 0.2.3 it resolves and leaves nothing. Full suite 1165 tests, 1144 passed, 1 failure - core/tcl exec-14.3, the documented baseline. Manual-version bump per src/modules/AGENTS.md: file renamed, Meta line, manpage_begin and provide-block updated, version-history line appended. The rename sweep converted the two goal Scope references (G-035, G-109) from the exact filename to the glob form src/modules/punk/libunknown-*.tm that GOALS.md's own Scope-authoring guidance recommends, so the reference stops drifting at every bump. Also records in G-035 the mechanism behind its "avoid mixing .tm and pkgIndex.tcl provision" folklore, which this investigation identified (non-contract Notes). Stock ::tcl:™️:UnknownHandler returns early when $satisfied is set and therefore never falls through to ::tclPkgUnknown, so a require satisfied from a .tm suppresses the whole library scan. Measured with a synthetic fixture on both 8.6.10 and 9.0.3: with mixpkg 1.0 as a .tm and mixpkg 2.0 in an auto_path library under 'package prefer latest', stock returns 1.0 and reports only 1.0 from 'package versions', runs no index side effect and registers no sibling package; the libunknown chain returns 2.0 and does all three. libunknown already neutralises it - its handler still computes $satisfied but the early return is commented out - and that unconditional fallthrough is exactly what the epoch cache pays for. The folklore is therefore substantiated for stock Tcl with a named failure mode (silent older-version selection) and neutralised under the punkshell chain, with stock behaviour still reachable in any interp that has not run punk::libunknown::init. Assisted-by: harness=claude; primary-model=claude-opus-5[1m]; api-location=anthropic.com	4 weeks ago
Julian Noble	3970b8e695	punk::libunknown 0.1 -> 0.2.0: adopt major.minor.patch + manual-versioning guidance ... Verified nothing depends on the old version or filename before renaming: all 'package require punk::libunknown' sites are unversioned; punk_main.tcl and punk::repl locate the module by globbing libunknown-*.tm and picking the highest by vcompare (so the renamed dev copy now also outversions the stale bootsupport and project.vfs 0.1 copies deterministically, instead of relying on tm path order for a same-version tie); bootsupport's include_modules.config lists it by name only. The 0.2.0 number retroactively versions the two changes shipped against the 0.1 filename earlier today (register_all_tm deep discovery - a minor API addition - and the source_pkgindex sourcing-scope fix). A version-history comment block in the module header now substitutes for the buildversion.txt changelog other modules carry. src/modules/AGENTS.md: the punk::libunknown exception bullets now spell out the manual-versioning mechanics for agents - same Patch/Minor/Major bump rules as buildversion-tracked modules, executed as a file rename plus Meta line, manpage_begin, provide-block and version-history updates, with a check for exact-version/filename dependents before any first bump. discovery.test/libsearch.test: the source-tree libunknown locator now picks the highest libunknown-*.tm by vcompare instead of plain lsort (robust to future version bumps). Verified live in punk902z src: package provide reports 0.2.0, register_all_tm present, lib.search deep discovery intact. Suites green under tclsh90 and tclsh87. Build artifacts synced (root modules/ and _vfscommon.vfs carry only libunknown-0.2.0.tm). punkshell 0.10.2. Stale 0.1 copies remain in src/bootsupport/modules (pending 'make.tcl bootsupport') and src/vfs/project.vfs (pending layout maintenance) - both now cleanly outversioned at runtime. Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com	1 month ago
Julian Noble	d35e055efc	punk::libunknown: isolate pkgIndex.tcl sourcing - stop clobbering global 'dir' ... zipfs_tclPkgUnknown previously declared 'global dir' and executed pkgIndex.tcl scripts via 'namespace eval ::' - the pkgIndex $dir contract was met by writing the global namespace's dir variable, silently overwriting any user global named 'dir' whenever a package require fell through to the pkg unknown handler (observed misdirecting a file write into the user's Tcl installation during test development), and each index's stray unqualified variables (ver, pkg, script, _CawtSubDirs, ...) leaked into ::. Index scripts now execute in a source_pkgindex proc frame: $dir is a formal parameter and auto_path/env are global links - exactly the environment stock tclPkgUnknown documents (its indexes see dir as the handler's proc-local plus 'global auto_path env'), without stock's incidental exposure of all its other proc locals. tcl::Pkg::source uplevels into the caller's frame, so the scheme works unchanged for the 8.6 pre-tip459 fallback. The legacy non-epoch branch already sourced in the handler frame and simply gains stock parity from the 'global dir' removal. Reviewed against tcllib 2.0's vendored index behaviours (all compatible): qualified '$dir ni $::auto_path'/'lappend ::auto_path' extension in the top-level index, its own apply-scoped subindex sweep (the same isolation idiom), vsatisfies guards with early return, 'package provide' during index sourcing (try/pkgIndex.tcl on 9+), and critcl-generated ifneeded strings (md5c, tcllibc) whose proc definitions run at require time, not source time. One deliberate divergence from stock: each index file gets its own frame, so unqualified variables no longer persist between index files within one sweep (stock shares its handler frame across the sweep) - nothing in tcllib relies on that. discovery.test: the GAP pin flips to libunknown_pkgunknown_preserves_global_dir, plus new pins for the index contract - $dir-based ifneeded/source works, unqualified 'lappend auto_path' extension reaches the real ::auto_path, and stray index-script sets don't leak to ::. Verified live in punk902z src: ::dir no longer set at startup, user dir global survives package activity, tcllib md5/struct::set/json load through the new frame, lib.search deep discovery unaffected. Remaining startup globals def/pkg/ver come from punkshell's own boot code (punk_main.tcl foreach loops), not the handler. punkshell 0.10.1. punk::libunknown remains manually versioned at 0.1; vfs artifact synced, bootsupport copy untouched as before. Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com	1 month ago
Julian Noble	0c243a9ba9	dev lib.search: deep module discovery by default; -refresh = genuine re-scan ... punk::libunknown gains register_all_tm: walks every tcl:™️:list path recursively and registers ifneeded scripts for .tm modules at every namespace depth (the tm unknown handler only registers siblings at the requested depth, leaving never-requested subfolders like test::* invisible to 'package names'). First registration wins - parity with the handler and the shadowing pins. Reuses/populates the per-epoch directory index cache (zipfs whole-tree listing; per-dir globs for filesystem paths; #modpod-*, #tarjar-* and _build skipped) and runs at most once per tm epoch per interp - the guard is the interp-local tm_fullscan variable, deliberately not in the shareable epoch dict since ifneeded registrations are interp-local. punk::mix::commandset::loadedlib 0.2.0: search runs register_all_tm plus the auto_path pkgIndex sweep by default when punk::libunknown is active, so 'dev lib.search test' now shows deep modules without -refresh. -refresh is repurposed to mean a genuine filesystem re-scan: package epoch incr (invalidating the scan caches) then rediscovery - picking up .tm files added/removed on disk. Without punk::libunknown (or with an older copy lacking register_all_tm) -refresh falls back to the previous dummy-require deep walk. Dependency fixes: highlight ansi computed only when -highlight 1 via qualified punk::ansi with inline require (previously relied on the shell-global a+ alias unconditionally and errored in bare interps), inline requires for punk::path (fallback walk) and textblock (table output). New test suites (green under tclsh90 and tclsh87): - modules/punk/libunknown/testsuites/discovery/discovery.test: lazy-depth sibling registration, register_all_tm all-depths/cached-per-epoch/ head-wins-parity, package epoch shape and trace-driven increments, epoch-cache short-circuit + incr recipe, and a GAP pin of zipfs_tclPkgUnknown clobbering a user global 'dir' variable (stock tclPkgUnknown keeps dir proc-local; fix candidate). - modules/punk/mix/testsuites/loadedlib/libsearch.test: search match semantics, default deep discovery, -refresh re-scan contract, highlight without shell-global ansi aliases. Both suites source the source-tree punk::libunknown directly by path: 'package require' would tie-break the same-version bootsupport copy by tm path order (testinterp order favours bootsupport; child-interp 'tm::add {*}list' reverses precedence). Verified live in 'punk902z src'. Build artifacts synced via make.tcl packages + vfscommonupdate (loadedlib-0.2.0.tm, libunknown-0.1.tm). Note: src/bootsupport copy of punk::libunknown intentionally untouched - becomes stale until the next 'make.tcl bootsupport' sync; loadedlib degrades gracefully against it. punk::libunknown remains manually versioned at 0.1. punkshell 0.10.0 (see CHANGELOG.md; also records the 0.9.1 doc-only -refresh help rewrite). Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com	1 month ago