Tune center-column heights; note RawInput/DirectInput MKB + DX12 cost as future work

- Center stack heights set to Controllers 45% / Video 32% / Audio 23% (measured from
  the operator's preferred layout): Controllers has the most content, Audio the least.
- Future work: MKB forwarding for Raw Input / DirectInput games (the message +
  polling-state path doesn't reach them -- e.g. Trails through Daybreak uses Raw
  Input), and reducing the D3D11On12 (DX12) per-frame capture overhead.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

README.md

@@ -86,6 +86,16 @@ for what's left.
   readable image. Use WGC in the meantime.
 - **D3D9 hooked path.** Covered by WGC today; a dedicated `IDirect3DDevice9::Present`
   hook would be the lower-latency upgrade.
+- **Mouse + keyboard forwarding for Raw Input / DirectInput games.** The MKB
+  subsystem forwards via window messages (`PostMessage`) plus synthesized
+  `GetAsyncKeyState` / `GetKeyboardState` / `GetCursorPos`, which covers message-loop
+  and polling games. Games that read keyboard/mouse via **Raw Input** (`WM_INPUT` /
+  `GetRawInputData`, e.g. Trails through Daybreak) or **DirectInput**
+  (`IDirectInputDevice8::GetDeviceState/GetDeviceData`) don't see it. Add hooks for
+  those paths to synthesize the forwarded input there too.
+- **DX12 hooked-capture overhead.** The D3D11On12 bridge mirrors D3D12 games but is
+  noticeably heavier than the native D3D11 path (see Lessons learned); reducing its
+  per-frame cost (cache wrapped resources, lighter sync) is a follow-up.
 
 ## Building