A REQUIRED typed value or leader whose present word fails the basic-type
allocation screen (int/double/bool/number/dict) now reports the pointed
typemismatch naming the word and argument (-badarg/-badval, same shape
as the G-082 overflow-site selection) instead of the generic
missingrequiredvalue/missingrequiredleader shortfall. The in-loop
required-arg raise sites consult the rejection record returned by
get_dict_can_assign_value; the leaders-loop edit mirrors the values
loop per the MAINTENANCE contract. Unchanged by design: end-of-input
shortages (valuemissing/count classes), literal-typed members,
multi-member clause partials (no rejection record - conservatism
preserved), and required-arg choice words (never screened - G-071
asymmetry, choiceviolation already pointed).
parse_status: the shape now classifies invalid/typemismatch (the
formstatus viability verdict was already invalid; one probe re-parse
saved); argdoc status-key note updated. Pins deliberately flipped:
parsestatus.test (renamed parsestatus_typed_value_screen_typemismatch),
formviability.test (single-form top-status/formstatus split demo
re-anchored on a required-option shape), punk/ns cmdhelp.test message
match. New errorselection.test coverage: required value + leader
typemismatch pins plus unchanged-shape guards.
Verified tcl 9.0.3: punk/args subtree 280 total / 277 passed / 3
intended skips / 0 failed; punk/ns only the pre-existing nslist(1)
box-baseline failure (stash-verified unrelated). tcl 8.7: touched args
suites 38/38, cmdhelp 45/45.
Follow-on disposition flipped => landed in
goals/archive/G-082-punkargs-error-selection.md (goals_lint clean;
ledger 23 open / 20 goal / 15 landed / 2 declined). punkshell 0.53.1 +
CHANGELOG entry. Bootsupport/vfscommon args copies stay 0.15.1 until
the next promotion + bake.
Claude-Session: https://claude.ai/code/session_01QgaxV27VZkmEec7oNbEVFc
Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com
Follow-on: a REQUIRED typed value failing the basic-type screen reports missingrequiredvalue rather than a typemismatch naming the word (the rejection-record seam would cover it) => open
Follow-on: a REQUIRED typed value failing the basic-type screen reports missingrequiredvalue rather than a typemismatch naming the word (the rejection-record seam would cover it) => landed 2026-08-05 (punk::args 0.15.2 - the required-arg raise sites in the values AND leaders loops consult the rejection record and report the pointed typemismatch; end-of-input/literal/clause-partial shortfalls unchanged; pins flipped in parsestatus.test/formviability.test/cmdhelp.test, new errorselection.test required-position coverage)
#0.15.2 - G-082 follow-on: a REQUIRED typed value or leader whose present word fails the basic-type allocation screen (int/double/bool/number/dict) now reports the pointed typemismatch (message + errorcode with -badarg/-badval, same shape as the G-082 overflow-site selection) instead of the generic missingrequiredvalue/missingrequiredleader shortfall - the in-loop required-arg raise sites consult the rejection record returned by get_dict_can_assign_value for the current word. Unchanged by design: end-of-input shortages (valuemissing/count classes), a word failing a required literal-typed member, and multi-member clause partials (no rejection record - conservatism preserved); required-arg choice words were never screened (G-071 asymmetry) so choiceviolation reporting is untouched. parse_status consequences: this shape's top-level status flips incomplete->invalid with failureclass typemismatch (the formstatus verdict was already 'invalid' - the G-152 probe confirmed each such 'incomplete' away before reporting; one probe re-parse saved); multiform noformmatch classes unchanged (already invalid), per-form failureclass/message now the pointed typemismatch. parse_status argdoc status-key note updated. Pins flipped deliberately: parsestatus.test typed-value allocation failure, formviability.test single-form record (top-status/formstatus divergence demonstration re-anchored on a required-option shape), punk/ns cmdhelp.test badarg message match; new errorselection.test required-position coverage (value + leader) with unchanged-shape guards (end-of-input, literal-typed, clause partial).
#0.15.1 - G-164 viability-probe alternative-allocation re-probe: when the valmin reservation seats a word that literally names a declared required option into a required value slot at end-of-input, and the resulting optionmissing stands in the G-152 viability probe (a value word consumed, defeating the position guard), the probe now re-parses with the stolen word(s) consumed as the options they name (private::get_dict_form's viabilitycheck argument carries {1 reseat_words} on the re-probe pass) and grants 'incomplete' (viable) on pure end-of-input exhaustion after that re-seating. Cures the 'i hash -t' false negative: the test form classes viable since {-t foo} parses; sibling forms stay invalid. Options still missing after the re-seating are ordinary exhaustion in the re-probe. Runtime seating is unchanged - the re-probe runs only inside the probe, only via reservation-seated words (the trailing-flag-as-value rule is load-bearing; flagvalues_plain_then_dash and the runtime optionmissing path pinned unchanged). A stolen word naming a value-TAKING required option stays conservative (invalid) - re-seated, it seats as a value again at end-of-input. Verdict contract documentation updated in the parse/parse_status argdoc. formviability.test gains 7 pins (re-probe, delete-form, other-missing-options exhaustion, unnamed stolen word, value-taking conservatism, runtime-unchanged, single-form formstatus); the cmdhelp.test GAP pin cmdhelp_GAP_multiform_flagled_testform_false_notviable flips to cmdhelp_multiform_flagled_testform_viable.
#0.15.1 - G-164 viability-probe alternative-allocation re-probe: when the valmin reservation seats a word that literally names a declared required option into a required value slot at end-of-input, and the resulting optionmissing stands in the G-152 viability probe (a value word consumed, defeating the position guard), the probe now re-parses with the stolen word(s) consumed as the options they name (private::get_dict_form's viabilitycheck argument carries {1 reseat_words} on the re-probe pass) and grants 'incomplete' (viable) on pure end-of-input exhaustion after that re-seating. Cures the 'i hash -t' false negative: the test form classes viable since {-t foo} parses; sibling forms stay invalid. Options still missing after the re-seating are ordinary exhaustion in the re-probe. Runtime seating is unchanged - the re-probe runs only inside the probe, only via reservation-seated words (the trailing-flag-as-value rule is load-bearing; flagvalues_plain_then_dash and the runtime optionmissing path pinned unchanged). A stolen word naming a value-TAKING required option stays conservative (invalid) - re-seated, it seats as a value again at end-of-input. Verdict contract documentation updated in the parse/parse_status argdoc. formviability.test gains 7 pins (re-probe, delete-form, other-missing-options exhaustion, unnamed stolen word, value-taking conservatism, runtime-unchanged, single-form formstatus); the cmdhelp.test GAP pin cmdhelp_GAP_multiform_flagled_testform_false_notviable flips to cmdhelp_multiform_flagled_testform_viable.
#0.15.0 - @values -flagvalues (G-150 follow-on, user-directed): a @values section may declare -flagvalues 1 - an unmatched dash-led word in option position is then consumed as a trailing value instead of raising invalidoption (declared options still match first; the '--' end-of-options marker is unaffected; off by default). Motivation: '--help'-style forms robustly swallowing ignored trailing words of any shape - previously such a word seated as a value only positionally (at end-of-input via the valmin reservation, or within a bounded valmax) and errored 'Unexpected option' otherwise ('{--help -t foo}' on the unconstrained shape). Mechanism: VAL_FLAGVALUES on the form dict (template default false; @values compiler key, boolean-validated at resolve time) short-circuits the unmatched-dash-word fallback in the parse engine. In-tree consumer: punk::auto_exec::hash's help form. New testsuite flagvalues.test (9 tests: seating matrix, declared-option precedence, off-by-default contrast, optionmissing after value seating, key validation). Documented in the module header notes.
#0.15.0 - @values -flagvalues (G-150 follow-on, user-directed): a @values section may declare -flagvalues 1 - an unmatched dash-led word in option position is then consumed as a trailing value instead of raising invalidoption (declared options still match first; the '--' end-of-options marker is unaffected; off by default). Motivation: '--help'-style forms robustly swallowing ignored trailing words of any shape - previously such a word seated as a value only positionally (at end-of-input via the valmin reservation, or within a bounded valmax) and errored 'Unexpected option' otherwise ('{--help -t foo}' on the unconstrained shape). Mechanism: VAL_FLAGVALUES on the form dict (template default false; @values compiler key, boolean-validated at resolve time) short-circuits the unmatched-dash-word fallback in the parse engine. In-tree consumer: punk::auto_exec::hash's help form. New testsuite flagvalues.test (9 tests: seating matrix, declared-option precedence, off-by-default contrast, optionmissing after value seating, key validation). Documented in the module header notes.
#0.14.0 - G-152 suffix-viability verdict: multiform per-form failure statuses (the 'formstatus' records, the noformmatch errorcode's 'classes' list and its -formerrors records) are now SOUND suffix-viability verdicts - a form reports 'incomplete' (viable) if and only if every supplied word was validly consumed as a prefix of that form and the failure is pure exhaustion at end-of-input; anything already supplied contradicting the form reports 'invalid'. Previously the count/missing-required failure classes granted 'incomplete' before final validation ever saw the consumed words, so a wrong action word landed 'incomplete' on a value-carrying sibling form identically to a genuinely-viable prefix ({frobnicate} vs {info} were indistinguishable), and a word rejected by an allocation type screen (missingrequiredvalue) also classed 'incomplete'. Mechanism: private::get_dict_form gains a viability-probe mode (optional 4th arg) suppressing exactly the pure-exhaustion raises - below-minimum leading/trailing count shortfalls and missing-required leader/option/value checks, each position-guarded so appended words could actually reach the missing element (leaders only with no option/value words consumed; options only before value words and any eopts --; values always), plus an adhoc option's value lying beyond the supplied words - while every contradiction raise stands, including final validation of the consumed words (the soundness backstop). Multiform candidacy and parse_status's single-form formstatus record confirm each classify-'incomplete' failure with one probe re-parse before reporting it. Documented conservatism: input ending INSIDE a multi-member type clause reports invalid (clause allocation cannot affirm the partial words). Rendered noformmatch messages mark each form line '(viable - needs more arguments)' or '(not viable)' after the stable "form '<fid>':" anchor; the existing incomplete-first ranking thereby puts still-satisfiable forms first. Contract documented in the parse ('Multiform failure contract' help section) and parse_status (formstatus/status key) argdocs; parse_status's top-level 'status' for single-form parses keeps the engine classification (display-scheme driver) - only formstatus carries the verdict. New testsuite formviability.test (acceptance scenarios, option-position guards, single-form record soundness, clause conservatism, message marking); forms.test verdict pins deliberately updated (ms/idle 'incomplete'->'invalid' for words failing their type screens).
#0.14.0 - G-152 suffix-viability verdict: multiform per-form failure statuses (the 'formstatus' records, the noformmatch errorcode's 'classes' list and its -formerrors records) are now SOUND suffix-viability verdicts - a form reports 'incomplete' (viable) if and only if every supplied word was validly consumed as a prefix of that form and the failure is pure exhaustion at end-of-input; anything already supplied contradicting the form reports 'invalid'. Previously the count/missing-required failure classes granted 'incomplete' before final validation ever saw the consumed words, so a wrong action word landed 'incomplete' on a value-carrying sibling form identically to a genuinely-viable prefix ({frobnicate} vs {info} were indistinguishable), and a word rejected by an allocation type screen (missingrequiredvalue) also classed 'incomplete'. Mechanism: private::get_dict_form gains a viability-probe mode (optional 4th arg) suppressing exactly the pure-exhaustion raises - below-minimum leading/trailing count shortfalls and missing-required leader/option/value checks, each position-guarded so appended words could actually reach the missing element (leaders only with no option/value words consumed; options only before value words and any eopts --; values always), plus an adhoc option's value lying beyond the supplied words - while every contradiction raise stands, including final validation of the consumed words (the soundness backstop). Multiform candidacy and parse_status's single-form formstatus record confirm each classify-'incomplete' failure with one probe re-parse before reporting it. Documented conservatism: input ending INSIDE a multi-member type clause reports invalid (clause allocation cannot affirm the partial words). Rendered noformmatch messages mark each form line '(viable - needs more arguments)' or '(not viable)' after the stable "form '<fid>':" anchor; the existing incomplete-first ranking thereby puts still-satisfiable forms first. Contract documented in the parse ('Multiform failure contract' help section) and parse_status (formstatus/status key) argdocs; parse_status's top-level 'status' for single-form parses keeps the engine classification (display-scheme driver) - only formstatus carries the verdict. New testsuite formviability.test (acceptance scenarios, option-position guards, single-form record soundness, clause conservatism, message marking); forms.test verdict pins deliberately updated (ms/idle 'incomplete'->'invalid' for words failing their type screens).
#typemismatch from the same rejection-record seam the optional-overflow selection uses.
test errsel_required_type_reject {Required typed (int) value and leader rejecting a present word report pointed typemismatch (punk::args 0.15.2 - was missingrequiredvalue/missingrequiredleader)}\
-setup $common -body {
set docid1 ::testspace::errsel_required_type_value
set docid2 ::testspace::errsel_required_type_leader
#2026-08-05 (agent, G-082 follow-on): the type-screen probe formerly demonstrated the
#documented top-status/formstatus split (engine 'incomplete' via missingrequiredvalue
#vs verdict 'invalid') - punk::args 0.15.2 reports that shape as the pointed
#typemismatch (engine 'invalid', agreeing with the verdict), so the split
#demonstration moved to the required-option probe (optionmissing classifies
#'incomplete' while the consumed value word defeats the probe's position guard).
test formviability_singleform_formstatus_sound {single-form parse_status: the formstatus record carries the viability verdict while the top-level status keeps the engine classification}\
test formviability_singleform_formstatus_sound {single-form parse_status: the formstatus record carries the viability verdict while the top-level status keeps the engine classification}\
test formviability_clause_partial_conservative {input ending inside a multi-member type clause reports invalid - documented conservatism of the verdict}\
test formviability_clause_partial_conservative {input ending inside a multi-member type clause reports invalid - documented conservatism of the verdict}\
test parsestatus_typed_value_allocation_failure {a supplied word failing its -type check surfaces as an allocation shortfall WITH the unfillable argument as badarg}\
#flipped 2026-08-05 (agent, G-082 follow-on) - was parsestatus_typed_value_allocation_failure
#pinning failureclass missingrequiredvalue: punk::args 0.15.2 reports a required typed
#value's basic-type screen rejection as the pointed typemismatch (badarg unchanged)
test parsestatus_typed_value_screen_typemismatch {a supplied word failing a required value's -type screen reports typemismatch WITH the unfillable argument as badarg}\
-setup $common -body {
-setup $common -body {
set ps [punk::args::parse_status {v1 x x} withid ::testspace::psfix]
set ps [punk::args::parse_status {v1 x x} withid ::testspace::psfix]
lappend result [dict get $ps ok] [dict get $ps failureclass] [dict get $ps badarg]
lappend result [dict get $ps ok] [dict get $ps failureclass] [dict get $ps badarg]
@ -112,7 +115,7 @@ namespace eval ::testspace {
}\
}\
-cleanup {
-cleanup {
}\
}\
-result [list 0 missingrequiredvalue firstval bad unparsed]
-result [list 0 typemismatch firstval bad unparsed]
test parsestatus_count_shortfall_incomplete {too few values reports incomplete with no offending argument}\
test parsestatus_count_shortfall_incomplete {too few values reports incomplete with no offending argument}\
#the failure message names the queried command via parse -caller instead of whatever
#the failure message names the queried command via parse -caller instead of whatever
#the call-frame walk found.
#the call-frame walk found.
test cmdhelp_badarg_marking_failed_typed_value {a value failing its -type check (surfacing as an allocation shortfall) badarg-marks the unfillable argument's row}\
#required typed value's screen rejection as the pointed typemismatch ("Trailing argument
#'firstval' ... requires type 'int'") instead of the missingrequiredvalue shortfall
#("fail on firstval"); the badarg marking derivation is unchanged
test cmdhelp_badarg_marking_failed_typed_value {a value failing its -type check (typemismatch since punk::args 0.15.2) badarg-marks the failing argument's row}\
-setup $common -body {
-setup $common -body {
variable BAD
variable BAD
set out [punk::ns::cmdhelp ::testspace::helpfix v1 x x]
set out [punk::ns::cmdhelp ::testspace::helpfix v1 x x]
#the message names the failing argument and its row is badarg-marked
#the message names the failing argument and its row is badarg-marked
#punk::args 0.12.6: the message renders once BELOW the usage display - sample the last line
#punk::args 0.12.6: the message renders once BELOW the usage display - sample the last line
lappend result [string match "*fail on firstval*" [punk::ansi::ansistrip [lindex [split $out \n] end]]]
lappend result [string match "*Trailing argument 'firstval'*requires type 'int'. Received: 'x'*" [punk::ansi::ansistrip [lindex [split $out \n] end]]]
lappend result [any_line_has_sgr $out firstval $BAD]
lappend result [any_line_has_sgr $out firstval $BAD]
lappend result [any_line_has_sgr $out lastval $BAD]
lappend result [any_line_has_sgr $out lastval $BAD]
