Verify typed alias composition in integrations

docs/roadmap/implementation.md

@@ -1,6 +1,6 @@
 # Application-owned aliases implementation plan
 
-Status: in progress; Stages 1–12 completed.
+Status: in progress; Stages 1–13 completed.
 
 ## Authority, baseline, and scope
 
@@ -621,6 +621,17 @@ suite passes with `go test ./... -count=1`.
 local workspace. Do not claim nested modules' pinned core v0.2.0 graph validates
 new alias APIs. See Stage 17 for independent local-source graph verification.
 
+**Completed:** Root binding coverage now verifies every singleton occurrence
+is converted, the last value wins, repeated values retain order, explicit
+false/zero/empty values remain present, required selectors are checked, and
+each invocation receives fresh defaults and input state across canonical and
+alternate spellings. Integration tests exercise scoped selector aliases on
+installed PromptKit collection and prompt-inspection commands, the `smoke`
+shortcut and returned report, failed operand-alias registration with later
+canonical and shortcut calls, and global help aliases for both standard
+families. Verified with the root, ckconfig, and ckprompt suites under the local
+three-module workspace.
+
 ## Stage 14: Update maintained consumer examples
 
 **Work**