Add one-use consent for a named player to start seat AI

Let a human owner authorize another human in the started room to start a fixed difficulty once within 24 hours. The owner retains the seat, cookie, private hand, recovery setup and takeback control. Consent is explicit even while online; neither host status nor inactivity authorizes a takeover. Activation enters the existing paced private-view AI path without strategic changes.

Add additive migration 0006, both exact session fences, owner/delegate-only metadata in the authenticated room snapshot, atomic CAS activation and consumption, expiry and terminal retry receipts. Replacement hides older consent; own AI changes invalidate unused consent. Recovery or handover of either bound seat invalidates the grant. Future-version guards prevent stale computed state from overwriting a racing action. Exact browser retry records retain the original operation/version across refresh and cannot rearm old consent. Shared HTTP continuation preserves coalescing across ordinary and control routes.

Independent review found no material remaining issue. Revoke messaging accurately handles activation winning the race. Browser QA exercised grant/revoke, preserved consent after refresh, reciprocal fixed-profile activation, consumed receipts, keyboard takeback and private ownership. The panel now remains expanded after success and action buttons are at least 44px. Responsive screenshot acceptance remains open because the browser viewport override targeted a failed secondary-origin tab; desktop controls and no-overflow width were verified. The QA room is stopped at a genuine human setup decision with both seats taken back.

Types, lint, all 4906 offline tests, production build and all 45 HTTP tests pass on the stable source fingerprint. Seven new offline cases cover client consent/retry validation and real SQLite privacy, restart, one-use races, future versions, takeback, expiry and both-seat recovery/handover; two new HTTP cases cover authentication, injection, fixed-profile continuation and takeback. The first broad run exposed 68 legacy VM fixtures missing the new production dependency; their mappings were updated and the real shared continuation remains exercised. The historical 0005 migration test verifies backfill before applying 0006 for current code.

All 1174 original rooms, 2456 seats and every prior recovery/entry/handover/migration row remain unchanged. SQLite integrity and foreign keys pass; migration and QA added 88 rooms and 188 seats. No reset, server restart, usage check or automation was performed.

The current Sites integration has no supported durable Cron/DO provisioning path. Document this platform blocker rather than adding an inert scheduled export; unattended resumption and broader network-failure acceptance remain unfinished. Full rules, component, AI strength and publication gates remain closed.

Verified source tree: 2d86fc611e9ef4f5a10db10f96687a31db1ec238908ecf1e9333c50fac9ccaa8

docs/AUTOPILOT.md

@@ -18,7 +18,31 @@ An accepted API action processes a bounded AI batch. If more work is pending, th
 
 The current continuation has a sixteen-batch budget. It is **best effort, not a durable scheduler**. Cloudflare permits work after response/disconnect for a bounded period; runtime interruption or exhaustion can leave the persisted `botsPending` flag for a later explicit continuation. The existing browser reconnect/resume flow can resume it. No automatic platform alarm resumes a room after an unattended server restart. That remaining reliability requirement must be implemented and verified before claiming fully unattended operation. [Cloudflare duration limits](https://developers.cloudflare.com/workers/platform/limits/#duration), [module waitUntil export](https://blog.cloudflare.com/nodejs-workers-2025/).
 
-GET remains a private read and does not advance a game. The all-controlled HTTP acceptance case polls only GET after the final delegation request, proving the observed completion came from the request's server continuation.
+GET returns the caller's private view and can schedule pending automatic/AI work
+through the same bounded continuation used by POST. Polling or reopening can
+therefore wake persisted work. It does not establish unattended recovery after
+all requests stop.
+
+### Platform audit, 20 September 2026
+
+The current Sites integration exposes no supported Cron Trigger or Durable
+Object provisioning contract. Vinext can compile a custom Worker entry with a
+`scheduled` handler, but that export does nothing without an installed trigger.
+The generated local Wrangler configuration is not a Sites deployment contract.
+No inert handler or pretend scheduler has been added.
+
+Cloudflare Cron requires a separately configured trigger and has minute-level
+scheduling. It could enforce a minimum interval, but cannot provide regular
+1.5-second wakeups. Durable Object alarms provide finer scheduling, but this
+project has no supported binding/provisioning path. D1 due metadata alone cannot
+wake a Worker. This milestone is blocked on an available durable scheduler;
+independent multiplayer work continues. See [Cron configuration](https://developers.cloudflare.com/workers/configuration/cron-triggers/)
+and [Durable Object alarms](https://developers.cloudflare.com/durable-objects/api/alarms/).
+
+The optional [named-player permission](SEAT_AI_PERMISSION.md) now connects a
+one-use, fixed-difficulty activation without transferring the owner's seat or
+private information. It uses the same best-effort continuation and does not
+remove the scheduling limitation.
 
 ## Coverage ledger
 
@@ -30,7 +54,7 @@ GET remains a private read and does not advance a game. The all-controlled HTTP
 | Background batches cannot overwrite takeback      | Current-state read and version-fenced update per batch                     | Normal reconnect/resume controls                                | Only persisted bot/autopilot seats run        | Five SQLite `bot-continuation.test.ts` cases, including real authenticated takeover race |
 | Complete an all-controlled game                   | POST schedules background continuation                                     | Final outcome remains inspectable                               | Three original human credentials preserved    | HTTP final opt-in returned playing, later GET finished; no subsequent gameplay POST      |
 | Responsive and refresh flow                       | Saved mode read after refresh                                              | Mobile 44px takeback, separate opt-in, keyboard-native controls | Inspection remains readable during delegation | Browser room2SG3ZS3E; details in `VISUAL_PLAYTEST.md`                                    |
-| Durable unattended restart scheduling             | Missing                                                                    | Reopen/resume available                                         | No automatic host takeover                    | Not certified; next reliability work                                                     |
+| Durable unattended restart scheduling             | Blocked on supported platform trigger/binding                              | Reopen/resume available                                         | No automatic host takeover                    | Current Sites capability audit; no unattended certification                               |
 
 ## Validation checkpoint