Propagate Fensalir texture leases to video drivers

notes/current-system-map.md

@@ -333,6 +333,9 @@ camera/decode producer writes that shared texture and signals the producer
 fence, then Mimir carries the same resource key through FieldEvidence. Fensalir
 waits on committed producer fence values before resolving shader reads. Shared
 foreign texture handles remain an import edge, not the primary camera authority.
+`MimirVideoCaptureDriverSource` propagates the lease client to drivers that
+implement `IMimirFensalirTextureLeaseReceiver`, so direct camera drivers can
+request the destination texture before emitting a frame descriptor.
 Metadata-only cadence frames do not create camera surface intents or fake
 payload requests. The old direct `AquariumGpuSensorFrame` bridge proof has been
 removed from Mimir's active proof path. Camera image claims currently defer

notes/fresh-workspace-handoff.md

@@ -47,6 +47,8 @@ Get-Content .\state\evidence.jsonl -Tail 8
   are rendering inputs: Mimir asks the engine broker for a keyed D3D12
   Texture2D/fence lease, writes decoded frames into that texture, commits the
   producer fence value, and lowers the same resource key through FieldEvidence.
+  `MimirVideoCaptureDriverSource` forwards that lease client to direct drivers
+  that implement `IMimirFensalirTextureLeaseReceiver`.
   Foreign shared texture handles are import edges, not the primary hot path.
 - The current Mimir/Fensalir rendering teardown map is
   [[docs/fensalir-rendering-rebuild-migration|Fensalir Rendering Rebuild