Verify public alias registration flows
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# Application-owned aliases implementation plan
|
||||
|
||||
Status: in progress; Stages 1–11 completed.
|
||||
Status: in progress; Stages 1–12 completed.
|
||||
|
||||
## Authority, baseline, and scope
|
||||
|
||||
@@ -591,6 +591,14 @@ coverage.
|
||||
Fill missing cross-boundary cases rather than duplicating the private algorithm
|
||||
test inventory. No concurrent-dispatch contract is introduced.
|
||||
|
||||
**Completed:** External-package tests now exercise command-only and root-group
|
||||
consumers using only the core import. They cover declaration ordering, alias
|
||||
chains and global flags in one installation batch, canonical operand retention,
|
||||
optional/required/repeated operands without installation-time conversion,
|
||||
declaration reuse, retained construction errors, later registration, failed
|
||||
relationship validation, failed-batch recovery, and refreshed help. The root
|
||||
suite passes with `go test ./... -count=1`.
|
||||
|
||||
## Stage 13: Verify typed bindings and integration composition
|
||||
|
||||
**Work**
|
||||
|
||||
Reference in New Issue
Block a user