docs(render): Campaign V V11 status — deleted and statically green, runtime gates blocked

Records what V11 actually achieved and, more importantly, what it did not.

The deletion landed: 204 files, +1,870 / -27,607 lines across five commits.
Section 5.5.24 keeps the three findings that outlive the diff.

  * Chorizite could NOT be dropped, and not for the reason section 6 predicted.
    The risk register assumed the package survived only because the ManagedGL
    types implemented IUniformBuffer from it. The audit found TextureFormat in
    the IWorldTextureArray signature the VULKAN path implements, and
    BoundingBox serialized into the pak format. Dropping it is a slice that
    touches the on-disk format, not a V11 cleanup.

  * Two traps the V11 row did not know about. Studio/SampleData.cs is
    production code behind the character sheet's fallback, so it moved rather
    than died; ACDREAM_DEVTOOLS also gates Vulkan debug-utils, so the flag
    survives and now says out loud that its UI is gone.

  * Deleting GL surfaced a real bug: WbMeshAdapter.Dispose() was still
    pattern-matching the GpuFrameFlightController that V6a replaced, so its
    wait for submitted GPU work had been silently dead on every Vulkan run
    since. Removing the type turned a no-op into a compile error.

The runtime gates did not run, and the honest reason is written down rather
than smoothed over. The client dies at vkGetPhysicalDeviceSurfaceCapabilitiesKHR
in files V11 never touched. Bisecting put the failure at the PRE-V11 commit
whose Vulkan soak had passed 91 checkpoints three hours earlier, and
`vulkaninfo --summary` -- a Khronos tool with none of our code -- fails at the
same call. Win32 surface creation is broken machine-wide; Vulkan itself is
fine. That is issue #259, with the one-line diagnosis at the top so the next
person checks the machine before bisecting the tree.

So the row reads DELETED AND STATICALLY GREEN, RUNTIME GATES BLOCKED. Release
build is 0/0 and the complete Release suite is 8,999 / 5 skipped (-218 against
V10, every one a test that lost its subject). Nothing was relaxed to
manufacture a pass: section 7.1 rule 2 cuts both ways, and a gate that could
not run is not a gate that passed. The rerun list is in 5.5.24, and the
pre-deletion pixel baseline was captured BEFORE the deletion, so the
self-differential is still available whenever a window can be made again.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

docs/ISSUES.md

@@ -97,6 +97,57 @@ Copy this block when adding a new issue:
 
 ---
 
+## #259 — Win32 Vulkan surface creation fails machine-wide (`ERROR_UNKNOWN`)
+
+**Status:** OPEN — environment fault, not a product defect; recorded so the next
+reader does not bisect the tree for it
+**Severity:** HIGH while it lasts (the client cannot start at all)
+**Filed:** 2026-07-29
+**Component:** host machine / AMD driver / Win32 WSI
+
+**Symptom:** every `AcDream.App` launch dies during startup with
+
+```
+VulkanCallException: vkGetPhysicalDeviceSurfaceCapabilitiesKHR returned ErrorUnknown
+  at VulkanSwapchain.QuerySurface()
+  at VulkanGraphicsContext.SelectDeviceAndGate()
+```
+
+**It is not our code.** Observed first during the V11 gate battery and bisected:
+the failure reproduces identically at V11 HEAD, at both V11 implementation
+commits, and at `db4426d5` — the **pre-V11** commit whose Vulkan soak had
+completed 91 checkpoints three hours earlier on the same machine.
+`VulkanSwapchain.cs` and `VulkanGraphicsContext.cs` were not modified by V11.
+
+**The one-line diagnosis.** Run the Khronos tool, which shares no code with us:
+
+```
+> vulkaninfo --summary
+ERROR while creating surface for extension VK_KHR_win32_surface : failed with ERROR_UNKNOWN
+```
+
+If `vulkaninfo` fails there too, the fault is the machine's, not acdream's, and
+no amount of bisecting the tree will find it. **Check this first** whenever the
+client will not open a window.
+
+**State when observed:** session not locked (`LogonUI` absent), desktop present
+at 2560x1440, both adapters (RX 9070 XT driver 32.0.31021.5001, and the
+integrated Radeon) reporting `Status = OK` and enumerating with Vulkan 1.4.
+Vulkan instance and device creation succeed; only Win32 *surface* creation
+fails. It followed several hours of continuous GPU-heavy soak runs.
+
+**Expected remedy:** restart the display driver or reboot. Not reproduced from a
+cold boot. If it recurs *after* a reboot, it stops being an environment note and
+becomes a real investigation — capture `vulkaninfo --summary` and the driver
+version at that point.
+
+**Blocked by this:** V11's runtime gate battery (offline pixel gate, both
+connected routes, validation run, working-set re-measure). The pre-deletion
+pixel baseline is already captured at `artifacts/v11-pre`, so the
+self-differential is still available once a window can be created.
+
+---
+
 ## #258 — Developer panels have no host after V11 deleted ImGui
 
 **Status:** OPEN