State
snapshots/example-counts.json pins example firing counts for Morrison and the NASA aero examples. It contains no entry for packs/vv40/examples/nagaraja/cou1/uofa-nagaraja-cou1.jsonld.
The consequence is narrow but real: the site prebuild drift check that catches a changed count for Morrison will not catch one for Nagaraja. A catalog or shape change that moves Nagaraja's firings passes silently, and the first place anyone notices is a number quoted in a talk that no longer matches the package.
Background for a cold read
This was already noticed and left unactioned — see docs/handouts/SESSION-LOG.md:255-259, from the Nagaraja handout build. It is recorded there as an observation rather than a task, which is why it has not moved.
It matters more now than when it was first noted: Nagaraja is the case study the NAFEMS demo is built around, so its counts are more likely to be quoted and more expensive to get wrong. docs/UofA_Unified_Repair_Spec_v2_1.md §0.3a records a re-measured baseline of 19 findings, 18 vacuous, for nagaraja/cou1 — a starting point for the pin, though it should be re-derived rather than copied.
Suggested next step
Add the Nagaraja entry to snapshots/example-counts.json, re-deriving the counts rather than taking them from the repair spec. If Nagaraja gains a cou2 (filed separately), pin both at the same time so the pair moves together.
Discovered during
PR #85, while auditing what the branch left unguarded.
State
snapshots/example-counts.jsonpins example firing counts for Morrison and the NASA aero examples. It contains no entry forpacks/vv40/examples/nagaraja/cou1/uofa-nagaraja-cou1.jsonld.The consequence is narrow but real: the site prebuild drift check that catches a changed count for Morrison will not catch one for Nagaraja. A catalog or shape change that moves Nagaraja's firings passes silently, and the first place anyone notices is a number quoted in a talk that no longer matches the package.
Background for a cold read
This was already noticed and left unactioned — see
docs/handouts/SESSION-LOG.md:255-259, from the Nagaraja handout build. It is recorded there as an observation rather than a task, which is why it has not moved.It matters more now than when it was first noted: Nagaraja is the case study the NAFEMS demo is built around, so its counts are more likely to be quoted and more expensive to get wrong.
docs/UofA_Unified_Repair_Spec_v2_1.md§0.3a records a re-measured baseline of 19 findings, 18 vacuous, fornagaraja/cou1— a starting point for the pin, though it should be re-derived rather than copied.Suggested next step
Add the Nagaraja entry to
snapshots/example-counts.json, re-deriving the counts rather than taking them from the repair spec. If Nagaraja gains acou2(filed separately), pin both at the same time so the pair moves together.Discovered during
PR #85, while auditing what the branch left unguarded.