Parent, status and trigger
Parent: #919, Phase 2 / B1.5. Deferred catalog feasibility spike.
Requires A2's gcdump evidence-quality decisions (#927/#928) and B1.2's rubric (#921), plus explicit prioritization. Does not depend on Phase 4 experimental capture modes.
Evidence and question
tests/DotnetDiagnostics.ScenarioEvaluation.Tests/Scenarios/gc-storm.scenario.json uses windowed LOH/Gen2/GC signals; ScenarioReplayTests.cs includes churn with zero final retained LOH. Related validation exists in Core HeapGrowthDiffTests.cs and HeapSnapshotQueryDispatcherTests.cs. This does not yet demonstrate that agent evaluation distinguishes retained growth from transient allocation pressure.
Can one bounded retained-growth workload be distinguished from an allocation-churn control using existing temporal/heap evidence?
Bounded scope and acceptance
No general leak catalog, NativeAOT changes, universal heap-completeness detector, new capture mechanism or MCP tool.
Validation and closure evidence
Reuse existing heap/scenario tests and isolated execution. Preserve workload shape, expected/observed retention, capture timing and quality, competing explanations and the limitations of the decision.
Parent, status and trigger
Parent: #919, Phase 2 / B1.5. Deferred catalog feasibility spike.
Requires A2's gcdump evidence-quality decisions (#927/#928) and B1.2's rubric (#921), plus explicit prioritization. Does not depend on Phase 4 experimental capture modes.
Evidence and question
tests/DotnetDiagnostics.ScenarioEvaluation.Tests/Scenarios/gc-storm.scenario.jsonuses windowed LOH/Gen2/GC signals;ScenarioReplayTests.csincludes churn with zero final retained LOH. Related validation exists in CoreHeapGrowthDiffTests.csandHeapSnapshotQueryDispatcherTests.cs. This does not yet demonstrate that agent evaluation distinguishes retained growth from transient allocation pressure.Can one bounded retained-growth workload be distinguished from an allocation-churn control using existing temporal/heap evidence?
Bounded scope and acceptance
No general leak catalog, NativeAOT changes, universal heap-completeness detector, new capture mechanism or MCP tool.
Validation and closure evidence
Reuse existing heap/scenario tests and isolated execution. Preserve workload shape, expected/observed retention, capture timing and quality, competing explanations and the limitations of the decision.