Documentation
¶
Overview ¶
Command testinventorycheck validates the reviewed disposition mapping over the upstream-test inventory. It is the test-level analogue of interfaceinventory / behaviorcheck: the inventory (extract-test-inventory.mjs) is the mechanical denominator of upstream test obligations, and this gate proves every obligation carries a reviewed disposition whose evidence still resolves.
Closure enforced:
- every inventory file has exactly one mapping entry, and every entry names a real inventory file (no orphans, no gaps);
- each entry's upstreamTestHash equals the inventory content hash, so an upstream leap that edits a test invalidates its disposition and forces re-review;
- ported/partial/scenario-covered dispositions name evidence that exists and references the upstream test (path#fragment), a divergence names a D<N> that appears in docs/parity/DIVERGENCES.md, designed-out names a rationale and any evidence it cites resolves too;
- a ported/partial file may list designedOutCases (exact inventory case ids) when only some cases are designed out; the rest stay covered by verified evidence; ids shared by two case sites are rejected, and -release-policy requires the reviewed policy row to list the same approved ids;
- every non-designed-out row citing TestNodeVendoredTuiUpstreamTests is registered in that harness, and no registered file is designed-out or unmapped;
- with -strict, no obligation may remain pending or partial;
- with -release-policy and -write-known-gaps or -check-known-gaps, the marked current-state block of a Markdown file is regenerated or compared;
- with -release-policy, every upstream test has a reviewed production-path tag, hot-path obligations are closed or explicitly recorded as approved 0.3.x known gaps, and the ported total does not decrease from the verified committed baseline.
Click to show internal directories.
Click to hide internal directories.