v0.5.0

Changelog

Unreleased

0.5.0 (2026-10-30)

• Use target in controlled apply documents and accept JSON nesting up to the shared 128-level evidence budget. Host adapters must use schema 4 plans.

0.4.0 (2026-10-29)

• Add an injected Apply entry point for checksummed plans, explicit item selection, interactive confirmation and safe failure reporting, without domain, runner or connector dependencies.

0.3.0 (2026-10-24)

• Use JSON Pointer keys in configuration field provenance, separating literal dots, slashes, tildes, empty keys and nested mappings.
• Remove only actual descendant sources when a mapping is replaced; preserve array replacement and empty-mapping merge behavior.
• Breaking change: sources.fields and host --show-config output no longer expose dotted-path aliases; migrate field lookups to JSON Pointer.

0.2.1 (2026-10-23)

• Use English command help, prompts and collection/review diagnostics.
• Allow compatible dotenv versions without an upper version bound.

0.2.0 (2026-10-23)

• Rename Initialization to Initializer and Application to Router; remove the old constants and require paths in the 0.2.0 candidate.
• Preserve caller argument strings during routing and publish configuration applicability only after every layer succeeds.
• Remove quadratic field-source scans for leaf configuration values.
• Bound offline review source counts and cumulative bytes, and treat batch directory names literally.
• Redact adapter argument and dependency errors at the collection boundary.
• Share offline review preflight/publication ordering and redacted diagnostics without depending on Runner or domain schemas.
• Bound input bytes and configuration nesting/nodes before deserialization; merge owned layers without recursive copies.
• Synchronize newly created parent directories before publishing configuration templates.

0.1.0 (2026-10-22)

• Extract reusable configuration discovery, private initialization, command dispatch, option groups, terminal interaction, input/output and collection entrypoint orchestration.
• Integrate existing VXLAN, Wireless and net-connector backup/topology entrypoints; keep baseline integration limited to the existing coverage script.
• Preserve Ruby 3.4 compatibility and verify standalone package installation without application or device dependencies.