Record inspection comparison across application types

This commit is contained in:
2026-11-21 03:37:15 +00:00
parent 86a9060418
commit afe83a6fd2
3 changed files with 60 additions and 4 deletions

View File

@@ -30,6 +30,9 @@ API remain outside this roadmap.
Add two complementary capabilities: trusted access to current typed settings,
and a lightweight reporting view over existing frozen inspection state.
The inspection comparison extension is recorded in
[ADR 0024](../adr/0024-compare-inspection-views-across-application-types.md), which
extends [ADR 0010](../adr/0010-effective-configuration-diff.md).
### Typed value access
@@ -263,9 +266,8 @@ presence-state handling, resource capture, and settings ownership refactoring.
repository checks. This is an additive API; existing loading, inspection,
comparison, and shared source-version behavior remain as documented.
Clarify the distinction between same-type `Diff[T]` and structural view
comparison in the architecture policy and comparison documentation. Record
the extension to [ADR 0010](../adr/0010-effective-configuration-diff.md) through
the ADR process, preserving its accepted decision content.
comparison in the architecture policy and comparison documentation, following
[ADR 0024](../adr/0024-compare-inspection-views-across-application-types.md).
Completion means both representative library consumers can obtain their typed
settings and existing provenance from one application result without application