Unify typed binding preparation
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# Implement the optional integration modules and captured registration API
|
||||
|
||||
Status: implementation in progress. Stages 1 and 2 are complete; subsequent work follows the ordered roadmap.
|
||||
Status: implementation in progress. Stages 1 through 3 are complete; subsequent work follows the ordered roadmap.
|
||||
Execute the stages in order. Each stage is sized as a separate Luna coding-agent
|
||||
assignment. This document authorizes no publication or changes to sibling
|
||||
repositories.
|
||||
@@ -222,9 +222,14 @@ object deep copies.
|
||||
combined names, short names, duplicate bindings, and help conflicts. Avoid
|
||||
integration-specific reserved-flag lists.
|
||||
|
||||
**Completion evidence:** existing presence/repetition/help tests, adjusted to the
|
||||
selected constructors, plus focused converter call counts and repeated-slice
|
||||
independence. Do not add a new grammar restriction.
|
||||
**Completion evidence — complete:** flags and operands now prepare the same
|
||||
identity-bearing typed application value. Binding constructors retain invalid
|
||||
wiring/cardinality for installation; copies preserve identity and independent
|
||||
lookalikes do not. Conversion remains before input creation, every singleton
|
||||
occurrence is parsed once, and repeated core slices are copied per application.
|
||||
Existing presence, repetition, help, and operand tests pass with the captured
|
||||
constructors, along with focused identity, converter-count, and independence
|
||||
checks. No new grammar restriction was added.
|
||||
|
||||
## Stage 4: Implement captured flag application
|
||||
|
||||
|
||||
Reference in New Issue
Block a user