Tree:
49ec22a928
master
v0.1a
${ noResults }
3 Commits (49ec22a928d134966a5b9bf3329db6d472ba8b21)
| 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 |
5 days ago |
|
Julian Noble
|
687c0113d1 |
G-044 proposed: punk::args-driven repl command completion/hinting; cross-goal weaves
User-approved goal for interactive command completion and hinting in the repl (raw mode primary), driven by the punk::args documentation corpus: - command-word resolution via the same doc-lookup flow as 'i' (ensembles, subcommands, ensemble parameters - characterized in cmdflow.test), argument position via the definitions (options, choices with parse-consistent prefix/deny/reserve matching, literals, multi-form awareness per G-041) - activation preserves the editbuf's literal-tab support (tab is content in this shell - completion cannot exclusively claim plain Tab; trigger scheme decided and recorded at implementation) - per-subshell completion-provider seam: the punk::args completer is the default provider; a subshell can declare an alternative or none - minimum bar is a clean disable for language subshells such as an interactive xtal session (full xtal completion out of scope, not precluded) - introspection must not execute candidate commands (arginfo principle); no per-keystroke terminal queries added when idle (G-013 approach note) Detail-file weaves from the same direction: - G-041: form candidacy should be exposed as an API accepting PARTIAL argument lists (per-form compatibility while typing) for the G-044 hinting consumer - G-043: subshell definitions gain a repl-behaviour composition aspect (completion/syntax provider); xtal-style language subshells recorded as the motivating scenario, an actual xtal session deferred to its own future goal - G-013: raw editor essentials noted as G-044's prerequisite; the editbuf literal-tab constraint recorded as a standing approach note Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com |
1 week ago |
|
Julian Noble
|
9948810b9b |
G-042, G-043 proposed: subshell help topics via punk::config; subshell definition plugins (punk.subshell capability)
Both user-approved after a review of the intended plugin facility (punk::mix::init pluginmgr todos, the punk::pluginmgr 0.5.1 tcllib fork, punk::cap provider/handler system, punk::cap::handlers::templates pathtype resolution, punk::overlay commandset composition and its toml-CLI todo). - G-042: a named subshell declares help topics (name/aliases/summary/text) in punk::config stored configuration, registered into the ::punk::helptopic registry on entry and restored on exit, with an explicit shadowing policy. Text-content only - config is data; code-bearing topics belong to the plugin path where the trust story lives. Detail file records the registry seam (punk 0.2.0), dependencies (hard on G-014; beneficial G-040/G-008/G-009), and the plugin-facility relationship from the review. - G-043: the umbrella for that plugin path - a punk.subshell capability whose providers supply commandset bindings (punk::overlay import), help topics (G-042's registry API) and config defaults per named subshell, with a validating punk::cap handler, an equivalent data-only stored-config declaration path (absorbing punk::overlay's ".toml configuration files for defining CLI configurations" todo), and punk::pluginmgr as the discovery/ safe-interp trust layer for untrusted providers. Also absorbs punk::cap housekeeping found in the review: pkg_unregister api-object cleanup and unhandled-capability discoverability (the deliberate punk.isbogus silence). Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com |
1 week ago |