Tree: 0c243a9ba9

master

v0.1a

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '0c243a9ba9'

${ noResults }

Commit Graph

3 Commits (0c243a9ba961ebf4b86ff610bf703e1a5f05a2c7)

Author	SHA1	Message	Date
Julian Noble	ae04b3f8c9	GOALS: two-tier index restructure - summary-only GOALS.md, canonical Goal/Acceptance in detail files, archive-on-flip ... - GOALS.md collapsed to summary entries (ID/status/title/Scope/detail pointer): 104.6KB -> 23KB so a full read stays cheap; Scope lines kept verbatim so path-grep goal discovery still works - canonicality split: index canonical for ID/status/title/Scope, detail file canonical for Goal:/Acceptance:; all 61 detail-file headers reconciled from the index (fixes stale copies, e.g. G-036 detail acceptance predated the achieved rework), bodies preserved untouched - detail files created for the three index-only goals G-017, G-034, G-054; every goal now has one - 10 achieved goals (G-007 G-015 G-036 G-037 G-040 G-046 G-049 G-054 G-058 G-059) archived: summary records appended to GOALS-archive.md, detail files moved to goals/archive/; archive-on-flip replaces the ~30-achieved-entries trigger - GOALS.md preamble/rules reworked: read workflow (read index in full, then detail files of scope-intersecting goals before editing), contract spans both tiers with proposal-first unchanged, next-free-ID counts the archive, achieved flip judged against the detail-file Acceptance and includes archiving - progress convention codified from G-001 increment-1 practice: index entries carry status only, never progress; incremental progress lives in the detail file's ## Progress section (landed/remaining); achieved flip requires the remaining-work list resolved - a partial increment never flips a goal - goals/AGENTS.md rewritten for the split (required 4-field header, one detail file per goal, orphan rules covering archive/); root AGENTS.md Child DOX Index + Repo-wide Notes updated; GOALS-archive.md preamble updated - stale detail-file paths updated to goals/archive/ in src/lib/app-punkscript/punkscript.tcl (comment), runtimebash_wsl.test, wslprobe.tcl and the G-042 detail file; propagated copies (root lib/, src/vfs/_vfscommon.vfs, src/_build) left to refresh via normal build steps - no project version bump: governance docs and source comments only, no user-visible shell behaviour Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com	3 weeks ago
Julian Noble	062ec6fe93	G-033 revised: proj: scope prefix, kit-first canonical, help text persisted ... Design review outcomes (2026-07-07): - Syntax: proj is not a fifth ordered token (category error - the dash list is an ordered sequence of path blocks whose order IS the same-version tie-break dial, per the verified tm rules and punk_main''s own comment). Decided form: [proj:]<block>[-<block>...] - the prefix scopes WHICH project root dev/src resolve against (cwd walk-up to the nearest VCS repo root vs exe-relative), staying outside the ordered list whose semantics are untouched. Explicit prefix = no silent rebind on cd. Rejected: auto-detection, an explicit flag (less convenient), token-attached qualifiers. - Shadowing: visitor mode makes cross-lineage same-version-different-code ties structurally expected (binary and visited project snapshots are different vintages by definition). Order only arbitrates exact ties - dev-versioned, higher-versioned and kit-absent modules come from the project in either order. Canonical documented invocation is proj:internal-src (kit-first: the visiting shell''s infrastructure survives ties; for a standalone downloaded binary the kit is its only trustworthy lineage and internal is location-independent); proj:src documented as the faithful-vintage variant. Trimmed kits (G-019) compose gracefully - kit-first only arbitrates ties. - Required boot notice: detected root + effective precedence. - packagemode help text drafted and persisted in the detail file as the designated G-032 source (live only when the prefix ships); G-032 detail cross-references it. Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com	3 weeks ago
Julian Noble	c662ed1ed5	add goals G-031/G-032: componentized kit boot + punk::args launcher ... G-031: split the monolithic vfs main (punk_main.tcl: 1190-line apply block - ~1060 lines boot machinery, ~100 lines dispatch tail) into a layout-owned boot core (shipped via _vfscommon.vfs, sourced by vfs-relative path since no package paths exist at boot; pull-updatable per the G-027 ownership model) and a thin project-owned main declaring app subcommands at commented customization points. Fork cost measured: tomlish_main.tcl carries ~20 custom lines on a stale 500-line 2025 vintage copy; project_main.tcl (901 lines) same at template vintage - boot improvements never reach derived projects. Acceptance: behaviour parity across dispatch cases and vfs types, project subcommand added by editing only the thin main (tomlish the proving ground), boot core versioned/reportable (G-025). G-032: the default dispatch defines subcommands via punk::args - tabled -help enumerating built-in and project-registered subcommands, parsed options with tabled usage errors (script/G-015 or version-report/G-025 as first candidates), G-030 degradation rules (guarded require; parsing falls back to switch semantics, help to a plain list; rendering degrades independently). Parked decision: the silent unknown-arg->script reclassification should stop swallowing typos (candidate rule: reclassify only when the argument names an existing file). Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com	3 weeks ago