Project Tom Hagen: document dynamic parsing

[cowboyd]

Motivation

The README introduced Configliere as an entry-point router, but did not clearly explain how dynamic parsing changes ordinary help and version assumptions. Inspecting raw argv and bypassing configuration loading for --help or --version can resolve the wrong route when configuration or plugins introduce routes at runtime.

The two primary reasons to pause parsing—loading configuration values and loading plugins that add options or routes—also need to be explicit.

Approach

Explain Configliere through its governing abstraction: parsing progressively binds phases, expands the available route graph, and only then resolves a method at the deepest selected route. Configuration files and plugins are presented as the two canonical reasons to suspend that process—one contributes later value sources, while the other can contribute parameters and routes.

Help and version follow the same routing process as execution because they are methods on a resolved route, not shortcuts inferred from raw argv. A driver must therefore advance each successful increment until it reaches an intent or failure. This deliberately means that help for a dynamically introduced route may require loading configuration or plugins; in exchange, Configliere never prints authoritative help for an incomplete route graph. Increment work should remain side-effect-safe, report requirement failures through Result, and defer application behavior until an EXECUTE intent.

[pkg-pr-new]

Open in StackBlitz

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

commit: d56e132