Tree:
ab75a78b06
master
v0.1a
${ noResults }
3 Commits (ab75a78b06d9ce682dc036e6d0ac5dba4c9e41f1)
| 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 |
1 week 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 |
2 weeks ago |
|
Julian Noble
|
0540c3c19b |
add goals G-033 (proj cwd-project mode) and G-034 (8.6 shell modpod mount)
G-033: an explicit `proj` package-mode token lets an installed (visitor) punkshell binary detect the punk project containing the cwd - walking up to the nearest VCS repo root, the marker punk::repo::is_project_root already uses - and set up source/dev library resolution against THAT project, so `punkshell proj shell` explores a project interactively even when the project builds no shell-capable binary (or no binary at all). History check recorded: cwd project-structure detection was never active in the boot modes (src/dev are exe-relative; os is shallow cwd-only), but the runtime detector find_project already exists and dev commands use it - so the marker question (VCS repo root, not punkproject.toml which tomlish lacks) is already answered; this aligns boot modes with it. Explicit token gates it per user decision (no silent rebind on cd); boot chicken-and-egg (find_project is in punk::repo, not loadable at the package-mode phase) handled by a lean inline VCS-root walk-up or post-boot deferral. Reuses the existing src-mode path machinery, parameterised on the detected root. Not gated on the module.templates/punk::cap plugin machinery. G-034: zip-based #modpod modules (e.g. punk::mix::templates) fail to mount in the shell subcommand's code interp on Tcl 8.6 - `dev module.templates` errors with `invalid command name vfs::RegisterMount` / no template providers - while the same call works via the script subcommand / main interp (reproduced 2026-07-07). The code interp lacks the vfs::zip library that supplies zip mounting for pre-zipfs Tcl. Tcl 9 (zipfs) unaffected. Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com |
2 weeks ago |