refactor(runtime): retain complete reconciliation outputs
This commit is contained in:
@@ -156,16 +156,18 @@ silently equated with the generated bytes observed by CDP.
|
||||
|
||||
## Bounds and determinism
|
||||
|
||||
Inputs allow up to eight static layers and 32 passive captures. Runtime entity,
|
||||
reconciliation item, and static load-state projections have caller-visible
|
||||
limits and report omitted counts when reached. The merged application graph
|
||||
retains all selected roots, nodes, edges, and observations from those inputs;
|
||||
it adds no second aggregate prefix cap. Reaching an input projection limit
|
||||
reports exact omitted counts and `coverage.status: truncated`.
|
||||
The workflow does not impose aggregate count caps on static layers, passive
|
||||
captures, runtime entities, reconciliation items, static load states, runtime
|
||||
mapping declarations, or candidate references. These collections remain
|
||||
subject to the structural validation applied to each Evidence record and
|
||||
application graph; passive capture collection limits are committed by the
|
||||
observation operation that produced that Evidence. Reconciliation reports zero
|
||||
omitted items when it projects the complete supplied inputs. Static JavaScript
|
||||
analysis can still report its own bounded AST coverage as partial or truncated.
|
||||
|
||||
Layers, captures, nodes, edges, matches, and evidence links are canonically
|
||||
ordered. Repeating the same verified Evidence, mappings, and limits produces
|
||||
the same reconciliation, graph, and Evidence identifiers.
|
||||
ordered. Repeating the same verified Evidence and mappings produces the same
|
||||
reconciliation, graph, and Evidence identifiers.
|
||||
|
||||
## Non-goals
|
||||
|
||||
|
||||
Reference in New Issue
Block a user