Repository navigation
Correct PR 664 component-count history after connector pruning #702
Description
From PR #664 adversarial review 5136972896.
Seven records still carry CONNECT_CAUSAL_GRAPH_COMPONENTS provenance that says issue #183 graph fragmentation was resolved from N components to 1. Later PR #664 repair passes removed the unsupported connectors, so those shipped records intentionally remain fragmented and need corrective provenance instead of the stale claim.
Affected records:
- data/traits/environment/ph_delta_mid2.yaml
- data/traits/environment/ph_delta_mid3.yaml
- data/traits/environment/ph_delta_very_low.yaml
- data/traits/environment/temperature_range_mid4.yaml
- data/traits/environment/temperature_range_mid3.yaml
- data/traits/environment/temperature_optimum_high.yaml
- data/traits/environment/temperature_optimum_very_low.yaml
Resolution target:
Append curation_history events and history sidecars that state the actual shipped component counts after evidence-weak connectors were pruned.
Activity