punkshell

1110 Commits

1 Branch

1 Tag

216 MiB

Commit Graph

Author	SHA1	Message	Date
Julian Noble	6a69cbf85c	goals: xref reconciliation - kit/launcher/modpod cluster (G-019 G-023 G-028 G-029 G-031 G-057 G-077 G-089 G-109 G-111, recorded 2026-07-24) Assisted-by: harness=opencode; primary-model=openrouter/moonshotai/kimi-k3; api-location=openrouter.ai	2 weeks ago
Julian Noble	3a49aa4c48	punk::platform buildsuite axis; record binary-.tm platform-segregation constraints (G-109) - platform records + 'help platforms' gain buildsuite (supported\|planned\|candidate\|none): whether OUR zig buildsuites produce runtimes for a platform. Deliberately a separate axis from tiers - punkbin-structured repos (or third-party equivalents) can host runtimes built by any mechanism, so runtime-tier hosting coexists with buildsuite=none (netbsd/dragonflybsd-class examples, per user review). openbsd/netbsd/dragonflybsd records now carry the runtime tier. Current values: win32-x86_64 supported (suite_tcl90), linux-x86_64 planned (G-105), linux-arm64/linux-arm/macosx/freebsd-* candidate, rest none. - G-109 notes record the binary-.tm platform reality the user's fat-tm experience established (retracting this survey's earlier 'tm-are-cross-platform' shorthand): multi-platform fat .tm are the wrong shape (oversized downloads; same-version shadowing leaves no drop-in path), platform segregation must ride tcl:™️:path via per-platform TM ROOTS selected by boot - and platform dirs cannot nest inside an existing tm root (subdirs are namespace components), so those roots must be sibling trees. Candidate manifest field: declared target platform so libunknown can skip wrong-platform binary .tm. Project 0.18.1. Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com	3 weeks ago
Julian Noble	534bc58dc3	G-109 + G-110 proposed: multi-name .tm discovery; shared-lib extraction cache Two goals split out of the modpod/TIP-741 characterization work, user-approved. G-109 (libunknown manifest-declared multi-name discovery): a zip-based .tm declares case-variant and sub-package require names in a manifest at a well-known internal location, discovered by libunknown at scan time - with real-disk scan performance preserved (worst-case parity with plain tclsh's builtin tm handler; libunknown exists to fix slow-drive/large-tree scan cost). Multi-name .tm are punkshell-only (documented); TIP 590 lowercase single-name stays the plain-tclsh happy path; extensive-tests bar recorded. G-110 (extraction cache investigation): whether per-run fresh-temp-dir copies are necessary or replaceable by a single per-user content-addressed cache (hash-keyed parent dir). Carries the 2026-07-21 sniff evidence: concurrent sharing of one copy works; classic Win32 delete refused while mapped; POSIX- semantics delete succeeds with mappings unharmed (a third option next to TIPs 741/709: unlink-after-load on modern NTFS). Fallback requirement recorded: punkshell wants a win32/old-Windows fallback (industrial systems on isolated VMs/old hardware) - capability-probe, classic-safe GC degradation. Precedents (.NET single-file, critcl cache), sibling-dll sets, AV interplay, and the cheapest-first implementation surfaces (modpod stub -> suite core patch -> upstream) recorded. G-066 note pointed at the new goals. Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com	3 weeks ago

Author

SHA1

Message

Date

Julian Noble

6a69cbf85c

goals: xref reconciliation - kit/launcher/modpod cluster (G-019 G-023 G-028 G-029 G-031 G-057 G-077 G-089 G-109 G-111, recorded 2026-07-24)

Assisted-by: harness=opencode; primary-model=openrouter/moonshotai/kimi-k3; api-location=openrouter.ai

2 weeks ago

Julian Noble

3a49aa4c48

punk::platform buildsuite axis; record binary-.tm platform-segregation constraints (G-109)

- platform records + 'help platforms' gain buildsuite
  (supported|planned|candidate|none): whether OUR zig buildsuites produce
  runtimes for a platform. Deliberately a separate axis from tiers -
  punkbin-structured repos (or third-party equivalents) can host runtimes
  built by any mechanism, so runtime-tier hosting coexists with
  buildsuite=none (netbsd/dragonflybsd-class examples, per user review).
  openbsd/netbsd/dragonflybsd records now carry the runtime tier.
  Current values: win32-x86_64 supported (suite_tcl90), linux-x86_64
  planned (G-105), linux-arm64/linux-arm/macosx/freebsd-* candidate,
  rest none.
- G-109 notes record the binary-.tm platform reality the user's fat-tm
  experience established (retracting this survey's earlier
  'tm-are-cross-platform' shorthand): multi-platform fat .tm are the
  wrong shape (oversized downloads; same-version shadowing leaves no
  drop-in path), platform segregation must ride tcl:™️:path via
  per-platform TM ROOTS selected by boot - and platform dirs cannot nest
  inside an existing tm root (subdirs are namespace components), so those
  roots must be sibling trees. Candidate manifest field: declared target
  platform so libunknown can skip wrong-platform binary .tm.

Project 0.18.1.

Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com

3 weeks ago

Julian Noble

534bc58dc3

G-109 + G-110 proposed: multi-name .tm discovery; shared-lib extraction cache

Two goals split out of the modpod/TIP-741 characterization work, user-approved.

G-109 (libunknown manifest-declared multi-name discovery): a zip-based .tm
declares case-variant and sub-package require names in a manifest at a
well-known internal location, discovered by libunknown at scan time - with
real-disk scan performance preserved (worst-case parity with plain tclsh's
builtin tm handler; libunknown exists to fix slow-drive/large-tree scan cost).
Multi-name .tm are punkshell-only (documented); TIP 590 lowercase single-name
stays the plain-tclsh happy path; extensive-tests bar recorded.

G-110 (extraction cache investigation): whether per-run fresh-temp-dir copies
are necessary or replaceable by a single per-user content-addressed cache
(hash-keyed parent dir). Carries the 2026-07-21 sniff evidence: concurrent
sharing of one copy works; classic Win32 delete refused while mapped; POSIX-
semantics delete succeeds with mappings unharmed (a third option next to TIPs
741/709: unlink-after-load on modern NTFS). Fallback requirement recorded:
punkshell wants a win32/old-Windows fallback (industrial systems on isolated
VMs/old hardware) - capability-probe, classic-safe GC degradation. Precedents
(.NET single-file, critcl cache), sibling-dll sets, AV interplay, and the
cheapest-first implementation surfaces (modpod stub -> suite core patch ->
upstream) recorded.

G-066 note pointed at the new goals.

Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com

3 weeks ago

3 Commits (fe31f094f8aac35f179166f5d0d0460a86166cb2)