Resolve entered command routes to canonical paths
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# Application-owned aliases implementation plan
|
||||
|
||||
Status: in progress; Stages 1–6 completed.
|
||||
Status: in progress; Stages 1–7 completed.
|
||||
|
||||
## Authority, baseline, and scope
|
||||
|
||||
@@ -439,6 +439,13 @@ local workspace.
|
||||
an explicit longer route while canonical `run full` remains unchanged;
|
||||
flags/values/space-containing argv tokens never becoming command components.
|
||||
|
||||
**Completed:** Routing snapshots now retain canonical path metadata and the
|
||||
separate command-alias resolver. Execution resolves command prefixes before
|
||||
parsing, tracks the original input-token origins through alias chains, and
|
||||
preserves the remaining argv. Canonical operands, flags, terminators, unknown
|
||||
paths, and alias-only discovery prefixes receive distinct route results.
|
||||
Verified with root and both integration module suites using the local workspace.
|
||||
|
||||
## Stage 8: Integrate parser-aware flag aliasing and short grammar
|
||||
|
||||
**Work**
|
||||
|
||||
Reference in New Issue
Block a user