[cowboyd]

Motivation

Dynamic routing makes CLI binding positional and provisional: an unresolved word may be parameter data or a route selector introduced by a later phase. Binding beyond that boundary can let a parent steal a child's input.

Configuration checkpoints also need a deterministic way to introduce JavaScript values without losing route scope, source precedence, or errors from an invalid selected value.

Approach

Treat bindPhase() as a source scheduler, not a source interpreter. CLI is positional, so it is bound to a fixed point behind the first unresolved-word horizon; value sources are addressable, so they are consulted only after CLI visibility stops advancing. This prevents a parent route from consuming tokens that may belong to a dynamically discovered child while still allowing earlier option values to advance the horizon.

Every source reports the same three states: absent, present and valid, or present and invalid. Absence permits fallback; either present state settles the parameter, so malformed higher-priority input cannot disappear behind a lower-priority value. Immutable source remainders preserve one global claim history across phases, while route-mounted values provide deterministic local-to-ancestor lookup. The resulting schedule is CLI → values → schema absence, with setter syntax available when a route name and option value would otherwise be ambiguous.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/configliere@23

commit: 3580c78