[docs] (P7): package D3's note, and the census row its fix falsified

P3b/P4b wave 2-D package D3, slice 3.

docs/Disaggregated/notes/p34b/espryt-d3.md, in espryt-d1.md's shape: the mechanism end to end,
the decision between resolving the predicate and indexing the reverse edge with the argument
that decided it (deletion ordering), the red-once evidence with the exact ctest invocations and
the red and green lines per arm, the gate numbers, and six things that remain.

The decision, stated once here because the note argues it at length: the gate resolves through
Desc.ViewOf to the storage record; the reverse index was rejected because it needs pruning on
VIEW death or an owner upload bumps a recycled slot's Serial, because it makes
ApplyTextureUpload write a record other than the one the call names, and because
VkTextureManager::ResolveWireTextureStorage already resolves the same way on the Magma side -
an index would have given the two backends two answers to one question.

notes/p34b/split-scenario-census.md is updated where the fix falsified it - the summary row,
the texture-family row and the exclusion section - and NOT rewritten anywhere else. D2's text
stands and D3's resolution sits above it in a quoted block, because a package note is a record
of what that package did rather than a live statement of the tree. Two citation corrections
taken while reading the device-window baseline: the CTS block is KHR-GL46 and not KHR-GL43, and
texture_view is 1/7 fail there with the failing case view_sampling, NOT coherency - coherency
reads Pass, which is what D2 claimed and is now checked per case against report-texture.json
rather than against a summary line.

espryt-d2.md itself is left alone and the note says why it is left alone.

Gates on this head, all measured rather than carried over: G1 .text 0xa52203, nm --defined-only
30570 symbols 0 added / 0 removed, -D 0/0, ninja -C build-linux rc 0. fatal_census rc 0 (79
abort sites, 0 unmarked - unchanged, rule I). link_ratchet --assert-monotone rc 0 (unchanged at
186). spawn_lane_parity rc 0. Lanes: unit 2418/2418, integration-split 264/264,
integration-spawn 180/180, integration-tcp 183/183, integration-magma-split 75/75, all 100%.
Name sets against a real ctest -N at a7c06f4f: +1 on each of split/spawn/tcp (the un-excluded
case), 0 elsewhere, 0 removed anywhere.
This commit is contained in:
2026-09-22 18:10:56 -04:00
parent 1c36987e84
commit 00d0239696
2 changed files with 405 additions and 5 deletions
@@ -15,12 +15,16 @@ Package D1 owns `PixelStoreSweep`, `DepthStencilReadbackMatrix`, `PackedWordRead
| | registered | excluded by name | blocked, not registered |
|---|---|---|---|
| texture family | 7 scenarios | 1 case | 0 |
| texture family | 7 scenarios | ~~1 case~~ **0** (package D3 fixed the defect) | 0 |
| program family | 5 scenarios | 9 cases (one scenario's remainder) | 0 |
**12 scenarios newly carry `integration-split` / `-spawn` / `-tcp` entries**, 71 cases per arm.
Plus `TextureViewAliasScenario` (this package's own, 3 of 4 cases). The split-arm registration
count recorded for the tier-2 Magma replay went from 33 to 46.
Plus `TextureViewAliasScenario` (this package's own, ~~3 of 4 cases~~ **all 4 since D3**). The
split-arm registration count recorded for the tier-2 Magma replay went from 33 to 46.
**Updated by package D3** (`notes/p34b/espryt-d3.md`): the one excluded case is the only row of
this census that has moved, and it moved because the defect behind it was fixed rather than
because the exclusion was widened or narrowed. Everything else below is as D2 measured it.
## Texture family
@@ -33,7 +37,7 @@ count recorded for the tier-2 Magma replay went from 33 to 46.
| `ImageTargetKindScenario` | 29 | pass (24 run, 5 skip) | pass | pass | — the 5 skips are `*Texture2DMultisample*` capability skips that also skip under monolith |
| `IntegerBorderColorScenario` | 6 | pass | pass | pass | — |
| `SwizzleAccessRoutineScenario` | 4 | pass | pass | pass | — |
| `TextureViewAliasScenario` (this package) | 4 | 3 pass, 1 red | 3 pass, 1 red | 3 pass, 1 red | **`TheOwnerUploadDrainRunsAgainAfterADrawBoundary`**, excluded by name — see below |
| `TextureViewAliasScenario` (this package) | 4 | 4 pass | 4 pass | 4 pass | ~~`TheOwnerUploadDrainRunsAgainAfterADrawBoundary`, excluded by name~~ — **fixed by package D3**, see below |
### The debt-table 待核 row: is the P6 inspection forwarder debt closed?
@@ -45,7 +49,18 @@ white-box half (`PipeApplyPeek`) agrees with Espryt's applied value in every arm
now registered in the three arms, so the answer is re-taken on every CI run rather than by
inspection.
### `TextureViewAliasScenario.TheOwnerUploadDrainRunsAgainAfterADrawBoundary` — excluded by name
### `TextureViewAliasScenario.TheOwnerUploadDrainRunsAgainAfterADrawBoundary` — ~~excluded by name~~ FIXED (package D3)
> **D3's resolution, at the head of D2's own diagnosis because the diagnosis was right.** The
> fix is at the GATE: `IsDrawSyncCleanByRecord`'s two STORAGE clauses resolve through
> `Desc.ViewOf` to the storage record (`PipeTextureStorageRecordForRecord`), and
> `SyncTextureViewToBackendByRecord` stamps the same storage serial, so the stamp and the gate
> name one quantity. The three PARAMETER clauses stay the view's own record's. The publisher-side
> reverse index was rejected: it needs pruning on VIEW death or an owner upload bumps a recycled
> slot's `Serial`, and `VkTextureManager::ResolveWireTextureStorage` already resolves the same way
> on the Magma side, so the index would have given the two backends two answers to one question.
> The case is un-excluded and green on all three arms; `CONTRACT-P5E.md` §5.2 now states the rule
> the code implements. Everything from here to the end of this section is D2's finding as written.
Red on inproc, spawn AND tcp; green under monolith. **Not a lane problem — a product defect this
package found.** After a view has been SAMPLED once, a later `glTexSubImage` through the OWNER's
@@ -69,6 +84,11 @@ footprint), and the publisher form needs an O(#texture records) scan or a revers
`MGPipeResourceRecord`, plus a `CONTRACT-P5E` amendment. `KHR-GL43.texture_view.coherency` is
exactly this test and reads Pass in the CTS baseline, which is a **monolith** reading.
> **D3**: taken at the gate. `KHR-GL43.texture_view.coherency` still has no SPLIT reading on this
> tree — the CTS baselines are monolith and the split comparison is the device window's (門 5) —
> so the integration case is the only thing standing behind the fix on host hardware. Listed in
> `espryt-d3.md`'s "what remains".
### `SampledSetStalenessScenario` on tcp
`AQueuedClearIsMaterialisedWhenAFilterChangeCompletesTheTexture` aborted once in a full