55 lines
1.5 KiB
Markdown
55 lines
1.5 KiB
Markdown
# G3 Next-Round Expansion Report
|
|
|
|
## Scope
|
|
|
|
This round continues consuming the `95598-ticket-family-candidate` downstream queue instead of stopping at the second-round expansion baselines.
|
|
|
|
Added fixtures:
|
|
|
|
1. `tests/fixtures/generated_scene/paginated_enrichment_expansion_source_distribution`
|
|
2. `tests/fixtures/generated_scene/paginated_enrichment_expansion_service_risk`
|
|
|
|
## Contract Variants Added
|
|
|
|
The next round validates two more `G3` reusable variants:
|
|
|
|
1. `pageNum + ticketNo + aggregate:sourceType`
|
|
2. `pageNo + ticketNo + aggregate:riskLevel`
|
|
|
|
## Delivered
|
|
|
|
Updated:
|
|
|
|
1. `tests/fixtures/generated_scene/p1_family_manifest.json`
|
|
2. `tests/fixtures/generated_scene/p1_family_results.json`
|
|
3. `tests/fixtures/generated_scene/g3_candidate_batch_2026-04-18.json`
|
|
4. `tests/g3_candidate_batch_test.rs`
|
|
5. `tests/scene_generator_test.rs`
|
|
6. `tests/scene_generator_p1_family_test.rs`
|
|
|
|
## Validation
|
|
|
|
Passed:
|
|
|
|
1. deterministic analysis for both new fixtures
|
|
2. package generation for both new fixtures
|
|
3. family-level reusable migration assertions for both new fixtures
|
|
4. batch-asset assertions for the promoted fourth and fifth expansion anchors
|
|
|
|
## Outcome
|
|
|
|
`G3` now has:
|
|
|
|
1. one `P0` anchor
|
|
2. one first expansion fixture
|
|
3. two second-round expansion fixtures
|
|
4. two next-round promoted expansion fixtures
|
|
|
|
The current `paginated_enrichment` family baseline is now validated across:
|
|
|
|
1. `ticketNo`
|
|
2. `workOrderNo`
|
|
3. `orderNo`
|
|
|
|
and across both `riskLevel` and `sourceType` aggregate families with supported pagination-field variants.
|