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

Record alias invocation metadata decision

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-19 01:18:13 +00:00
parent 4b53c96cf3
commit f526198059
1 changed files with 14 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
docs/roadmap/aliases.md
View File

@@ -213,9 +213,17 @@ defaults, typed bindings, input preparation, providers, diagnostics, and
outcomes. Execute the ordinary lifecycle once. Alias registration, resolution,
and help do not invoke application input/state factories or acquisition callbacks.
Retain the entered alias path and resolved canonical path for routing and
presentation. Whether this identity is exposed through the public invocation
API remains open.
Expose the original entered command path and final resolved canonical command
path as read-only invocation metadata. Both paths exclude the executable name,
flags, and operands. For a direct canonical invocation the paths are equal;
for `app pk test full`, they can be `pk test full` and `promptkit test all`.
Retain the endpoints through a chain; intermediate rewrites are not part of
the selected public metadata.
Consumers can use the canonical path to identify the operation consistently
and the entered path for logging and diagnostics. CommandKit dispatch and
bindings continue to use the canonical target. Exact accessor names and path
representation remain API design details under OD-1.
Support both help forms:
@@ -364,13 +372,9 @@ duplicate handling, and core-only availability are selected above. What public
declaration type lets `New` and `App.Register` accept commands and aliases
together? How do collections of reusable declarations and group composition
interact with application-root alias paths? What exact whitespace parsing and
path validation rules accompany the selected string representation?
### OD-5: Invocation identity
Does the public invocation API expose entered and canonical command paths?
What identity is retained through a chain, and how is it represented in that
API? Help and diagnostic presentation are selected above.
path validation rules accompany the selected string representation? What
accessor names and representation expose the selected read-only entered and
canonical invocation paths?
### OD-6: Flag alias scope and composition