Compile effective flag aliases during installation

docs/roadmap/implementation.md

@@ -1,6 +1,6 @@
 # Application-owned aliases implementation plan
 
-Status: in progress; Stages 1–5 completed.
+Status: in progress; Stages 1–6 completed.
 
 ## Authority, baseline, and scope
 
@@ -408,6 +408,15 @@ unknown scopes; inactive globals; scoped overrides inside a chain; cycles;
 global `--color → --missing`; collision after `--missing` becomes available;
 root/group help targets and failed-batch preservation.
 
+**Completed:** Installation candidates now compile effective global and
+canonical-command-scoped flag aliases from captured canonical metadata and
+built-in help spellings. Chain resolution applies scope precedence, tracks
+inactive global destinations, detects cycles, and rejects newly active
+canonical-source collisions without publishing failed candidates. Root, group,
+command, and alias-prefix discovery contexts retain only their applicable
+spellings. Verified with root and both integration module suites using the
+local workspace.
+
 ## Stage 7: Resolve entered routes to canonical commands
 
 **Work**