CNA-BUG-254: docs/directx9-renderer.md says the DIRECTX9 custom ShaderEffect phase (D9-11) has not been started; plans/plan_dx9.md records it fully closed on 2026-07-15

CNA snapshot 009d40f5  ·  Known Issues › Current bugs  ·  source links pinned to 009d40f5

The DIRECTX9 renderer document lists custom ShaderEffect (D9-11) as not started, while the plan it points to records D9-110, D9-111 and D9-112 all closed on 2026-07-15.

Identifier

CNA-BUG-254

Category

Bug

Subsystem

Documentation & release tooling

Status

Open

Verified against

CNA 009d40f5 (009d40f5dd085c4e674d3479675fac84b12b3e0a)

Severity

Low (a triage suggestion, not a project priority)

Evidence basis

Source-verified: read at TARGET, not executed

Tests touching this area

None

Affected contract

docs/directx9-renderer.md, the gap list of the DIRECTX9 renderer document

Expected behaviour

A status statement in a renderer document should match the plan record the document itself sends the reader to for task-by-task status.

Actual behaviour at TARGET

docs/directx9-renderer.md says: “D9-11 (custom ShaderEffect) is explicitly ask-first in plans/plan_dx9.md's own execution order and has not been started.” plans/plan_dx9.md, section “Phase D9-11 — Custom ShaderEffect”, says: “Authorized 2026-07-15 by the project owner. FULLY CLOSED the same day — D9-110/D9-111/D9-112 all ✓”, and records the CTAB parser, D3D9EffectBackend and the SpriteBatch::Begin(effect) wiring as closed. The document's own last line points the reader to that plan for status.

Source locations

• docs/directx9-renderer.md — the gap list that calls D9-11 not started
• plans/plan_dx9.md — Phase D9-11: D9-110, D9-111, D9-112 closed 2026-07-15

Evidence

Read at 009d40f5; nothing was built or executed. The contradiction is between two files of the CNA repository. Whether DIRECTX9 custom effects behave correctly at this snapshot is not asserted here; only that the document's status statement is stale. Found by the independent adversarial review of the graphics entries and re-verified by the orchestrator.

Focused reproduction

No focused reproduction is known. Nothing has been invented here; the evidence above is what exists.

Current tests

None: no test checks a renderer document's status statements against the plan.

Regression test

A documentation fix; a doc-consistency check would have to compare the document's D9-nn status lines with the plan's status column.

Blast radius

Readers of docs/directx9-renderer.md deciding whether custom ShaderEffect is available on DIRECTX9.

Workaround

Read the D9-11 section of plans/plan_dx9.md.