base-layer/commandkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Require exact resolved paths for explicit help

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-20 00:23:19 +00:00
parent 7dad20680e
commit fa09edf8cc
3 changed files with 49 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
docs/roadmap/remediation.md
View File

@@ -111,7 +111,7 @@ additional discovery check passed on Go 1.26.8.
## R-3: Preserve exact target lookup for the explicit help command
Status: open. Priority: P2. Category: help grammar regression.
Status: complete. Priority: P2. Category: help grammar regression.
**Evidence:** [renderHelpTargets](../../execute.go#L155) reuses execution lookup
and accepts `routeCanonical` results even when remaining target tokens are
@@ -137,6 +137,13 @@ requires operands.
targets fail with usage status 2; exact aliases, group shortcuts, and discovery
prefixes still render help without application initialization.
**Completed:** Explicit help now requires all resolved target tokens to form
the selected path; execution operands no longer disappear into a help view.
New public-boundary regressions failed before the fix and now reject canonical
and aliased operand-bearing targets while preserving exact command/group aliases,
discovery help, and ordinary execution-form help without input initialization.
The complete offline root suite passed on Go 1.26.8.
## R-4: Resolve discovery-help contexts through group shortcuts
Status: open. Priority: P2. Category: incomplete alias composition.