punkshell

1 Tag

223 MiB

Author	SHA1	Message	Date
Julian Noble	2aad4d1777	G-053 achieved: punk::args range-valued -multiple occurrence arity (punk::args 0.22.0, project 0.60.0) -multiple now accepts a {min max} range (max -1 = unbounded) alongside the legacy booleans 0/1, so a definition can declare at most once ({0 1}, a second occurrence is a parse error), bounded repetition ({2 4}), or one-or-more ({1 -1}) instead of choosing between silent last-wins (0) and unbounded collection (1). The spec compiler canonicalises once at resolve: the stored -multiple becomes the computed boolean (list-shape collect: true for max>1 or -1, false for legacy 0 and max==1) so every existing collect-vs-replace / scalar-vs-list / leader-value-single-multiple hot-path truth-test stays correct, and the range companions (min/max/maxbounded) live in a separate per-form MULTIPLE_RANGES dict - NOT in ARG_INFO, so they do not ride along when ARG_INFO is round-tripped as a spec via resolved_def copyfrom. Legacy 0/1 and boolean strings (true/false/yes/no) are coerced to the boolean and stay byte-unchanged (no MULTIPLE_RANGES entry for unlimited cases, so {0 -1} is equivalent to legacy 1). Resolve validation: max positive or -1, min <= max, and the -optional/range-min reconciliation (non-zero min forces presence, contradicts -optional -> reject with a clear message; declare -optional 0). The value-shape rule: max==1 forms stay scalar, max>1 or -1 yield the occurrence list. Parse enforcement: a new PUNKARGS VALIDATION occurrencecount failure class (payload <argname> count <n> min <m> \| max <m>) fires in a single post-loop pass per section (opts/leaders/values) via a private::multiple_range_enforce helper. Over-max is a hard contradiction (fires in both normal and viability-probe modes; parse_status_classify maps it to invalid); under-min is pure end-of-input exhaustion (SUPPRESSED in the G-152 viability probe via the viabilitycheck arg, classified incomplete so a viable form reports incomplete not invalid). Legacy -multiple 1 required with 0 occurrences still reports trailingvaluecount (byte-unchanged, not occurrencecount). Rendering: the usage-table Multi column reflects the range (0-1 / 2-4 / 1+ for unbounded-with-floor; the greencheck stays for legacy 1), the string renderer emits MULTI:0-1 etc., and the synopsis distinguishes at-most-once (?arg?, no ellipsis) from repeating (arg...). -multipleunique/-multipleuniqueset compose with max>1 ranges unchanged. define -help documents the range form and the -optional/range-min rule. New testsuite multipleranges.test (28 tests: 13 define-time canonicalisation+validation, 12 parse-time enforcement incl parse_status verdicts and a legacy-required-still-trailingvaluecount guard, 3 rendering). Legacy untouched by default confirmed: full punk/args suite 399/0 (3 skipped), punk/ns 125/125. All G-053 acceptance criteria met; goal flipped to achieved 2026-08-08 and archived (detail -> goals/archive/, index -> GOALS-archive.md, reference sweep applied to G-072/G-084, deferred G-084 cross-member -multiple collection decision recorded as a Follow-on => goal G-084). Project version 0.59.0 -> 0.60.0 (minor: backward-compatible behaviour addition). punk::args module 0.21.0 -> 0.22.0. Assisted-by: harness=pi; primary-model=huggingface/zai-org/GLM-5.2; api-location=huggingface.co	3 days ago
Julian Noble	d3dcc31dc4	goals system v2: semicolon Scope delimiters, version marker, lint delimiter check - GOALS.md: "Goals-system: v2" front matter; canonical "Goals system versions" section; Scope structure rule (elements separated by '; ' at top level, commas only inside parens/braces); Child DOX Index note in root AGENTS.md - goals_lint.tcl: new finding for top-level commas in Scope lines (paren/brace depth-aware) - goals_xref.tcl: repo-local configuration via goals/xref.conf (path roots, stop words, file extensions, reference containers, module dirs, bare_path_roots, prefix_anchors); defaults byte-identical to previous behaviour (verified on this tree) - goals/AGENTS.md: cross-repo goal references drop the G- prefix; xref.conf documented in Verification - Scope delimiter normalisation across GOALS.md, GOALS-archive.md and all detail files, live and archived: 224 lines, top-level commas only; conservation verified (goals_xref report byte-identical pre/post, diff hunks are Scope lines only). Archived tier converted under explicit user approval; sanctioned exception recorded in GOALS-archive.md. Assisted-by: harness=opencode; primary-model=openrouter/moonshotai/kimi-k3; api-location=openrouter.ai	2 weeks ago
Julian Noble	7e7d515cd0	G-041 achieved: multi-form matching - automated form selection for parsing and documentation Acceptance reviewed clause-by-clause in the detail file: auto-selection on a unique clean match (forms.test GAPs flipped), candidate-naming noformmatch/multipleformmatches errors, -form list restriction across get_dict/parse/parse_status/arg_error, doc surface presenting the best-matching form(s) ('i after cancel <id>' presents the cancel form; 's after cancel someid' underlines the matching synopsis lines), explicit single -form unchanged, full punk::args/punk::ns suites pass (full tree 822/836 with only the exec-14.3 baseline failure). Flip edits: index entry to GOALS-archive.md (achieved 2026-07-13), detail Status flipped with acceptance review and live-verification record, reference sweep updates G-044 (candidacy API now available - parse_status formstatus), G-055 backlink, G-072 backlink. Detail-file move to goals/archive/ follows as a pure rename; goals_lint transiently unclean between the two commits. Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com	4 weeks ago
Julian Noble	d4519f41d3	G-071 achieved: punk::args 0.9.0 allocation choice screen - lseq-class optional-element arglists parse in-form (project 0.12.11) Root cause: get_dict_can_assign_value blanket-satisfied the member check for any argument carrying choices, so an optional restricted-choice value (the lseq '..'/'to' noise word) consumed any word whenever arity permitted, starving later elements/clauses and failing validation with a confusing trailing-choices error ('lseq 0 10 2' shape). Fix: an allocation choice screen using choiceword_match (the shared G-040 implementation - exact/alias/prefix/nocase semantics; -choicemultiple words screened per list member within min/max), applied only where allocation has an alternative: -optional arguments and further occurrences of -multiple arguments. Required arguments are deliberately not screened - the word must fill them and validation's choiceviolation reporting stays informative (the existing parsestatus/cmdhelp/choices pins forced and now document both refinements). -choicerestricted 0 behaviour unchanged. Results: the allocation.test GAPs flipped ('1 2 3' and '1 2 by 3' parse with correct clause shapes {{} 3}/{by 3}; '1 2 3 4' gets the plain excess-values rejection instead of blaming the unrelated optional); prefix normalization survives the screen; all noise-word variants and if-shape guards unchanged. lseq moduledoc matrix parses per lseq.n under -form range, and 'i lseq 0 10 2' works end-to-end. Remaining lseq divergences trace to G-041 form selection or the -type expr laxity recorded in G-055 - not allocation. Also corrected an increment-1 mis-premise: parse_status ALREADY accepts -form before the withid/withdef tail per its documented synopsis - the probe had passed it trailing. GAP replaced by parsestatus_form_option_order (correct-order acceptance incl. the form key, trailing rejection). No code change was needed for that acceptance clause. Verification: punk::args suite 193 pass / 1 pre-existing skip / 0 fail; punk::ns 53/53; full source-tree suite 813 pass / 13 skip / 1 fail = exec-14.3 only (known baseline) - zero regressions (tclsh 9.0.3; lseq verification in punk902z src, Tcl 9.0.2). Flip edits: G-071 index entry moved to GOALS-archive.md (achieved 2026-07-12), detail Status flipped with the acceptance review and before/after record; reference sweep updates G-041 (prerequisite fixed, parse_status correction) and G-072 Notes. The detail-file move to goals/archive/ follows as a pure rename; goals_lint transiently unclean between the two commits. Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com	4 weeks ago
Julian Noble	803b44bd6c	goals: add G-071 (optional-element allocation correctness) and G-072 (compound clause types) Both user-approved drafts from the G-041 prework probe findings: - G-071: value-allocation correctness for optional standalone values + trailing optional-member clauses (the lseq "0 10 2" in-form failure), error-blame quality, and parse_status -form support. A G-041 prerequisite: no lseq form accepts those arglists under the current allocator, so form auto-selection alone cannot fix them. - G-072: named compound clause types with per-alternate element typing and arity for heterogeneous repeating clauses (try on/trap handlers), building on the design sketches embedded in the ::try moduledoc notes. Includes a recorded examination of Elixir gradual set-theoretic types (user direction): punk::args -type \| and literal() are already a fragment of the set algebra; negation would subsume reserved-word deny-lists; per-alternate arity falls out of union-of-shapes. Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com	4 weeks ago

5 Commits (3abfe674fa23fcaae7ec8a71e9c1e6ddcd99775c)