Draft: Require explicit STA consent for AP-originated TWT execution

AP-originated TWT metadata can now enter explicit paired execution through the shared session controller. Installation requires the exact actual STA frame receipt, explicit caller STA consent and the matching native AP ACK, under a fixed exclusive deadline.

Add copied packet identity and read-only exact-version action evidence. Preserve independent requester flows when unsolicited transport is disabled. Bind requester starts to their own pre-callback transaction reservation so physical wake or earlier STARTED observers cannot cause cleanup to cancel an independent same-flow request.

Validation: both complete required CI scripts passed locally against frozen source: 1169 QUICK cases in 28 Debug suites; 380 repeated cases in 15 isolated address/undefined/leak suites; nine normal physical profiles, three instrumented MU profiles, 21 invalid-input checks per build and 100 exact mapper checks. Preserve the failing ownership reproduction and passing permanent regressions. No GitLab server pipeline result is asserted here.

Scope: explicit shared simulator control for one associated QoS HE link with a caller-provided common clock. Caller consent and native packet identity are local metadata. Autonomous distributed confirmation, measured TSF synchronization, airtime admission, protected/broadcast or MLO/EMLSR TWT execution, hardware energy calibration and full-frame SP containment remain outside this checkpoint. This repository contains reusable simulator capabilities and their validation.