@vgai/engine 0.5.4 → 0.5.6

package/dist/input/input-manager.d.ts

@@ -0,0 +1,944 @@
+import type { ActionValueOf, ActionValueSource, ActionValueType, BindingConflict, BindingPrompt, InputBinding, InputMapFile, PromptDevice, Vector2 } from './input-types';
+/**
+ * Thrown by `InputManager.setVirtualAction`/`tapVirtualAction` (Task 1.4)
+ * for an action name that was never `registerAction`/`loadMap`-ed. Carries a
+ * machine-readable `code` and `data.registered` (every declared action name)
+ * rather than requiring a caller to parse the message.
+ */
+export declare class InputActionError extends Error {
+    readonly code: "INPUT_ACTION_NOT_FOUND";
+    readonly data: {
+        registered: string[];
+    };
+    constructor(action: string, method: string, registered: string[]);
+}
+/**
+ * Thrown by `InputManager.scheduleActionAtTick` (D15/T-D15.5) when the
+ * named `tick` has already elapsed — scheduling only ever applies to the
+ * CURRENT or a future tick, never one already serviced by `poll()`.
+ * Carries `data.currentTick` — the NEXT tick `poll()` will service (not
+ * the tick that just elapsed) — so a caller can retry by scheduling for
+ * `data.currentTick` or later.
+ */
+export declare class InputTickError extends Error {
+    readonly code: "TICK_ALREADY_PASSED";
+    readonly data: {
+        currentTick: number;
+    };
+    constructor(tick: number, currentTick: number);
+}
+/**
+ * Maps raw keyboard/mouse/gamepad events → named actions.
+ *
+ * Usage:
+ *   const input = new InputManager();
+ *   await input.loadMap('inputmaps/default.inputmap.json');
+ *   // In game loop:
+ *   input.poll();  // call at start of frame
+ *   if (input.isPressed('jump')) { ... }
+ *   if (input.isJustPressed('attack')) { ... }
+ *   input.endFrame();  // call at end of frame
+ *
+ * F1 (spec §12 "Define Typed Action Values") — typed action values:
+ *
+ * Every action DECLARES a value shape (`InputAction.valueType`, defaulted to
+ * `'digital'` — see `input-types.ts`'s `ActionValueType`). Each shape has its
+ * own typed getter, none of which return `any`:
+ *
+ *   - `'digital'`         — `isPressed`/`isJustPressed`/`isJustReleased` -> `boolean`
+ *   - `'scalar'`           — `getScalar` -> `number`
+ *   - `'vector2'`          — `getVector2` -> `Vector2` ({x,y})
+ *   - `'pointerDelta'`     — `getPointerDelta` -> `Vector2`
+ *   - `'pointerPosition'`  — `getPointerPosition` -> `Vector2`
+ *
+ * Reading an action through the WRONG getter (e.g. `getScalar` on a
+ * `'digital'` action) throws — that's the type-safety enforcement point,
+ * since actions are declared in data (JSON), not TS types, so there's no
+ * compiler backstop otherwise. `readAction(name, expectedType)` is a generic
+ * entry point over the same getters, typed via `ActionValueOf<T>`.
+ *
+ * Each typed getter has a `*Source` sibling (e.g. `getScalarSource`) that
+ * returns `ActionValueSource | null` — which binding (and, for gamepad
+ * bindings, which connected gamepad, or for injected test bindings, which
+ * named source) produced the current value. That's the "device/source
+ * metadata" AC.
+ *
+ * Deadzone + normalization:
+ *   - scalar: below `deadzone` magnitude -> 0; at/above it, rescaled from 0
+ *     (at the deadzone edge) to ±1 (at |raw| = 1), sign preserved
+ *     (`rescaleScalar`).
+ *   - vector2: below `deadzone` magnitude -> {0,0}; at/above it, direction is
+ *     preserved and magnitude is rescaled the same way, then the result is
+ *     clamped to the unit circle — magnitude never exceeds 1 even for a raw
+ *     diagonal input like {1,1} (`rescaleVector2`).
+ *
+ * Simultaneous-binding combine rules (documented here, spec §12 F1
+ * "simultaneous bindings combine predictably"):
+ *   - digital: OR — any one satisfied binding makes the action pressed
+ *     (pre-existing behavior, unchanged).
+ *   - scalar: max-magnitude across contributing bindings' (deadzone-applied)
+ *     values, sign preserved; ties keep the first-listed binding
+ *     (deterministic given binding array order).
+ *   - vector2: sum contributing (deadzone-applied) {x,y} values component-
+ *     wise, then clamp the sum to the unit circle (never renormalized UP —
+ *     only ever scaled down if the sum exceeds magnitude 1).
+ *   - pointerDelta: sum contributing deltas (matches the existing
+ *     mouseDeltaX/Y + lookStick accumulation precedent below).
+ *   - pointerPosition: last-write-wins — the contributing source most
+ *     recently updated (by injection call order) wins; position isn't
+ *     additive so summing would be meaningless.
+ *
+ * Synthetic input injection (test hook, also the shape of F2's "injected
+ * test input" backend): `injectAxis`/`injectVector2`/`injectPointerDelta`/
+ * `injectPointerPosition` push a raw value into a named source, read back by
+ * binding an action to `{ type: 'test_axis' | 'test_vector2' |
+ * 'test_pointer_delta' | 'test_pointer_position', sourceId }` — the exact
+ * same aggregation path (deadzone/normalize/combine) real device bindings
+ * use.
+ *
+ * F2 (spec §12 "Complete Device Backends") completes the real-device side of
+ * that same typed-value path:
+ *
+ *   - `mouse_move` — un-rejected (schema.ts). Feeds `getPointerDelta` (raw
+ *     accumulated `mouseDeltaX/Y`, no deadzone) and `getVector2` (the same
+ *     delta, deadzone-rescaled + unit-circle-clamped).
+ *   - `gamepad_axis_pair` — un-rejected (schema.ts). Feeds `getVector2` with
+ *     the coupled `(xAxis, yAxis)` reading, deadzone-rescaled like a real
+ *     stick (default deadzone 0.15, matching `gamepad_axis`).
+ *   - `touch_button`/`touch_stick` — new binding kinds for touch/virtual
+ *     controls. `setTouchButton(sourceId, pressed)` feeds a digital action
+ *     (edge-tracked like `mouse_button`); `setTouchStick(sourceId, value)`
+ *     feeds a vector2 action (deadzone-rescaled like a gamepad stick). These
+ *     are the injectable entry points a real on-screen touch UI's own
+ *     touchstart/touchmove/touchend handlers would call — that DOM wiring is
+ *     a thin adapter at the edge (browser-verified separately, e.g. F4/e2e);
+ *     the mapping logic here is unit-tested headlessly with no DOM.
+ *   - Focus gating — `blur`/`focus` on `window` (guarded, real DOM only) now
+ *     drop input the same way `setEnabled(false)` does (flushing held
+ *     key/mouse/touch-button state) without touching the `enabled` flag the
+ *     editor drives — see `focused`/`inputActive` below. This is what stops
+ *     a stuck key/button when the user alt-tabs away mid-press.
+ *   - Pointer lock — `pointerlockchange` on `document` (guarded) tracks
+ *     `isPointerLocked()`; losing lock flushes mouse-button state (a click
+ *     held at the moment lock exits must not stick).
+ *   - Gamepad device identity — `getGamepadInfo(index)` exposes `{index, id,
+ *     mapping, connected}`; `ActionValueSource.gamepadId` (in addition to the
+ *     pre-existing `gamepadIndex`) is populated for every
+ *     gamepad_button/gamepad_axis/gamepad_axis_pair source.
+ *   - Disconnection/reconnection needs no new tracking: `poll()` already
+ *     re-reads `navigator.getGamepads()` every frame and every read (digital
+ *     edges, scalar/vector2 contributions) already skips a `null` gamepad
+ *     entry, so a disconnected gamepad's bound actions go neutral (and a
+ *     previously-held button correctly fires `isJustReleased`) with no
+ *     special-cased code — see the state-transition tests.
+ *
+ * F3 (spec §12 "Add Rebinding and Prompts") completes the input system with
+ * rebinding, structural conflict detection, and device-prompt resolution:
+ *
+ *   - Listing/mutating: `getBindings`/`setBindings`/`addBinding`/
+ *     `removeBinding`/`replaceBinding` — the same `this.actions` map F1/F2
+ *     already read, now with a public read + mutation surface (there was
+ *     previously none — every existing call site either loaded a map once or
+ *     read through the typed getters).
+ *   - Reset-to-defaults: `registerAction`/`loadMap`/`loadMapObject` snapshot
+ *     each action's bindings into `defaultBindings` (a deep clone) at
+ *     registration/load time; `resetBindings`/`resetAllBindings` restore from
+ *     that snapshot. Later rebinding calls do NOT touch the snapshot, so
+ *     "reset" always means "back to what was authored/loaded", not "back to
+ *     the last reset".
+ *   - Persist: `toInputMapFile()` serializes the live action set back into
+ *     the exact `.inputmap.json` shape (`InputMapFile`) `loadMap` reads;
+ *     `loadMapObject(data)` is `loadMap`'s synchronous, no-`fetch` sibling —
+ *     both funnel through the same `InputMapFileSchema`-validated
+ *     `applyParsedMap`. This is the round-trip seam: serialize, write/hand to
+ *     something else, reload, and rebound actions survive. It complements —
+ *     doesn't replace — the SDK's `project.inputMap.read/validate/update`
+ *     operations (B2, `packages/vgai-sdk/src/project/input-map-operations.ts`):
+ *     those are FILE-level (a CLI/agent editing the `.inputmap.json` on disk,
+ *     no running game involved); this is RUNTIME-level (a live game rebinding
+ *     while playing). Both validate through the identical
+ *     `InputMapFileSchema`, so a file B2 wrote loads here unchanged, and a
+ *     map this class serializes is a valid document for B2 to read back.
+ *   - Conflicts: `findConflicts(proposed, excludeActionName?)` scans every
+ *     OTHER registered action's bindings for one that's structurally
+ *     equivalent to `proposed` (see the private `bindingsCollide` — same
+ *     physical input identity: same key code, same mouse button, the same
+ *     gamepad button/axis/axis-pair, the same touch `sourceId`, etc.) and
+ *     returns the (possibly empty) list as plain `BindingConflict` data —
+ *     never throws. A rebinding UI calls this BEFORE calling
+ *     `addBinding`/`replaceBinding`/`setBindings` and decides what to do with
+ *     a non-empty result (block, warn, let the user steal the binding by
+ *     removing it from the other action first).
+ *   - Prompts: `getPrompt(actionName, device?, gamepadIndex?)` resolves a
+ *     `BindingPrompt` (display label + icon name) for whichever of the
+ *     action's bindings belongs to the requested `PromptDevice` family
+ *     (keyboard/mouse/gamepad/touch — `bindingDeviceFamily` in
+ *     `prompt-labels.ts`), using `getGamepadInfo` to prefer the standard
+ *     mapping's canonical glyph names (`'A'`, `'LB'`, ...) for gamepad
+ *     buttons and falling back to a raw index label (or a "disconnected"
+ *     label) when the pad isn't in standard mapping or isn't connected.
+ *     `device` is optional (F4 below) — omit it to resolve against
+ *     `getLastActiveDevice()` instead.
+ *
+ * F4 (spec §12 "Schema and Examples") closes F3's one open gap — a
+ * current-ACTIVE-device tracker, so a prompt UI can switch its displayed
+ * label as the player switches controllers instead of the caller having to
+ * track that itself:
+ *
+ *   - `getLastActiveDevice()` returns the `PromptDevice` family of whichever
+ *     input arrived most recently — keyboard on `keydown`, mouse on
+ *     `mousedown`/a real `mousemove`, gamepad on a button press or a stick
+ *     pushed meaningfully off-center (checked in `poll()`), touch on
+ *     `setTouchButton(_, true)` or `setTouchStick` pushed meaningfully
+ *     off-center. `null` before any input has arrived.
+ *   - `getPrompt(actionName)` (device omitted) resolves against it directly,
+ *     falling back to `'keyboard'` before any input has arrived — a HUD can
+ *     call it every frame with no extra bookkeeping and the label switches on
+ *     its own.
+ */
+export declare class InputManager {
+    private actions;
+    private actionValueTypes;
+    private defaultBindings;
+    private loadedMapVersion;
+    private keysDown;
+    private keysJustDown;
+    private keysJustUp;
+    private mouseButtons;
+    private mouseButtonsJustDown;
+    private mouseButtonsJustUp;
+    private mouseDeltaX;
+    private mouseDeltaY;
+    private gamepads;
+    private gamepadButtonsDown;
+    private gamepadButtonsPrev;
+    private gamepadButtonsJustDown;
+    private gamepadButtonsJustUp;
+    private gamepadAxesCurrent;
+    private gamepadAxesPrev;
+    private lookStickX;
+    private lookStickY;
+    private testAxisValues;
+    private testVector2Values;
+    private testPointerDeltaAccum;
+    private testPointerPositionValues;
+    private pointerPositionSeq;
+    private touchButtonsDown;
+    private touchButtonsJustDown;
+    private touchButtonsJustUp;
+    private touchStickValues;
+    private lastActiveDevice;
+    /** Coarse "is this stick meaningfully off-center" check shared by the
+     *  gamepad and touch-stick active-device heuristics above — deliberately a
+     *  higher bar than a binding's own (often much smaller) configured
+     *  deadzone, since this is "did the player just grab this control", not
+     *  "does this binding's value count as non-zero". */
+    private static isStickActive;
+    private virtualDigitalHeld;
+    private virtualDigitalTapQueued;
+    private virtualDigitalTapActive;
+    /** pulse-runner friction #4 — the release-edge mirror of
+     *  `virtualDigitalTapActive`: a direct `setVirtualAction(action, false)` (or
+     *  `clearVirtualActions()`) on an action that WAS held writes here so
+     *  `isJustReleased` fires exactly once, mirroring real `onKeyUp`'s
+     *  immediate `keysJustUp` write (no queue/promotion needed — unlike the
+     *  press edge, nothing in `poll()` reassigns this set out from under a
+     *  write that lands before `poll()` runs). Cleared every `endFrame()`,
+     *  same bracket as every other just-* edge set. */
+    private virtualDigitalJustReleased;
+    private virtualScalarValues;
+    private virtualVector2Values;
+    private currentTick;
+    /** The last tick value `poll()` actually serviced, or `-1` before the
+     *  first call. Used to detect a GAP (this world's input phase didn't run
+     *  for one or more intervening ticks — e.g. frozen/paused while other
+     *  roots kept advancing the shared game tick) so any schedule entries
+     *  inside that gap can be dropped (with an observable event) instead of
+     *  silently rotting in {@link scheduledActions} forever. */
+    private lastServicedTick;
+    /** Pending `scheduleActionAtTick` actuations, grouped by their exact target
+     *  tick. Applied (and removed) at the START of that tick's `poll()` — see
+     *  `applyScheduledActionsForTick`. A tick whose input phase is skipped
+     *  entirely (this world paused/frozen, or a gap between two serviced
+     *  ticks) never reaches it — its scheduled entries are dropped, each
+     *  emitting one `'input.schedule.dropped'` debug event (`{tick, action}`)
+     *  via {@link setDebugEmit}'s sink if one is wired — NOT retried on a
+     *  later tick (mirrors `clearVirtualActions`-on-gate-close: no stuck
+     *  actuation ever silently fires late). */
+    private scheduledActions;
+    /** Optional sink for the `'input.schedule.dropped'` debug event (`{tick,
+     *  action}`) emitted whenever a scheduled entry is discarded because its
+     *  target tick's input phase never ran. Wired by whoever constructs this
+     *  `InputManager` with access to a `DebugRegistry`
+     *  (`setup-three-root-adapter.ts`, the same seed spot as
+     *  `setVirtualInputTarget`/`setInputActionsSource`) — `null` (the
+     *  default) for a bare/headless `InputManager`, in which case a drop
+     *  stays silent (matching pre-D15/T-D15.5 behavior). */
+    private debugEmit;
+    /** D15/T-D15.5 recording toggle — see {@link startInputRecording}. */
+    private inputRecording;
+    /** The post-gate action-delta trace (§2.c's format sketch) — capped so an
+     *  accidentally-long recording session can't grow this unboundedly. */
+    private inputTrace;
+    /** Last value recorded per action, so `recordPostGateTick` only ever
+     *  appends a DELTA (the format sketch's "deltas only" line), not a full
+     *  snapshot every tick. Cleared on `startInputRecording()`. */
+    private lastTraceSnapshot;
+    private disposed;
+    /**
+     * When false, all raw input is ignored and held/transient state is cleared.
+     * The editor host drives this (T6.3, `packages/editor/src/play-mode.ts`) so
+     * the running game only receives input while its viewport is the active,
+     * focused surface — keystrokes typed into the editor (Scene tab, inspector
+     * fields) must not leak into the game. A standalone game leaves this true
+     * for its whole lifetime.
+     */
+    private enabled;
+    /**
+     * F2 — real window focus, distinct from `enabled` (which is the editor's
+     * explicit play-mode gate). `false` while the tab/window is blurred (real
+     * `blur`/`focus` events — see the constructor). Held keyboard/mouse/touch
+     * state is flushed on blur so a key/button held at alt-tab time doesn't
+     * stick (the browser stops delivering keyup/mouseup while blurred).
+     */
+    private focused;
+    /** Both gates a standalone game must pass for input to be live (spec §12
+     *  F2 "focus gating"): the editor's explicit `enabled` flag AND real
+     *  window focus. Used everywhere `enabled` alone used to be checked. */
+    private get inputActive();
+    /** #144 — the gate MACHINE input passes (virtual actions and
+     *  tick-scheduled actuations): the editor's explicit `enabled` flag ONLY.
+     *  Window focus deliberately does not participate: a synthetic player
+     *  drives the shared editor tab precisely while the human's focus is
+     *  elsewhere (their terminal, another window) — the first live in-editor
+     *  E2E run froze mid-suite the moment the owner started typing to their
+     *  agent, which is the bug this gate split fixes. Real-device input keeps
+     *  the stricter `inputActive` (enabled AND focused) gate above. */
+    private get machineInputActive();
+    /** F2 — real pointer-lock state (`document.pointerLockElement`), tracked via
+     *  `pointerlockchange` (see the constructor). */
+    private pointerLocked;
+    /** Element currently wired for click-to-pointer-lock, and its listener. */
+    private pointerLockElement;
+    private onPointerLockClick;
+    private onPointerLockChange;
+    private onKeyDown;
+    private onKeyUp;
+    private onMouseDown;
+    private onMouseUp;
+    private onMouseMove;
+    /** F2 — real window blur: drop focus and flush held REAL-device state
+     *  (the browser stops delivering keyup/mouseup while blurred, so a key
+     *  held at alt-tab time would stick). #144: virtual-action state is
+     *  deliberately NOT flushed here — a bot's held action survives the human
+     *  looking away (see `machineInputActive`); only `setEnabled(false)`
+     *  clears it. */
+    private onWindowBlur;
+    /** F2 — real window focus regain. No flush needed (there's nothing held to
+     *  flush — a fresh keydown/mousedown is required to register pressed
+     *  again, exactly like re-enabling via `setEnabled(true)`). */
+    private onWindowFocus;
+    /** Clear held/transient REAL-device state (keyboard/mouse/touch-button) —
+     *  shared by `setEnabled(false)` (via `flushHeldState`) and real blur
+     *  (`onWindowBlur`), so a key/button physically held when input is
+     *  suspended doesn't linger. Level values (gamepad axes, touch sticks,
+     *  injected test axes) are deliberately NOT flushed here — they are gated
+     *  at READ time instead (see `inputActive` checks in `poll()`/the
+     *  `collect*Contributions` methods), matching the pre-existing
+     *  gamepad-axis convention. */
+    private flushRealHeldState;
+    /** The full flush `setEnabled(false)` performs: real-device state AND
+     *  virtual-action state. Task 1.4's rule ("a bot's held action must not
+     *  survive input being suspended") now applies only to the editor's
+     *  explicit gate — #144 moved real window blur onto `flushRealHeldState`
+     *  alone, so machine input survives the human's focus leaving the tab.
+     *  No release edge is manufactured here (`manufactureReleaseEdge: false`,
+     *  the default) — this is a SUSPEND, not a deliberate release, and mirrors
+     *  `flushRealHeldState`'s own silence (a key physically held at
+     *  suspend/blur time is wiped with no `keysJustUp`, "flush held state,
+     *  don't corrupt history", see `poll()`'s doc comment). */
+    private flushHeldState;
+    /** Shared by the public `clearVirtualActions()` and `flushHeldState()`
+     *  above — clears every virtual-action store (held digitals, queued/active
+     *  taps, scalar/vector2 values, the release-edge set itself).
+     *
+     *  `manufactureReleaseEdge` (default `false`): when `true` — only
+     *  `clearVirtualActions()`'s own deliberate "let go" passes this — every
+     *  currently-held digital in `virtualDigitalHeld` first gets an
+     *  `isJustReleased` edge written to `virtualDigitalJustReleased`, mirroring
+     *  a real key-up (`onKeyUp` → `keysJustUp`). `flushHeldState()` (the
+     *  editor-gate suspend path) deliberately passes `false` — see its own doc
+     *  comment for why a suspend must stay silent. */
+    private clearVirtualActionState;
+    constructor();
+    /**
+     * Load action map from a .inputmap.json file. Validated via
+     * `InputMapFileSchema` (T4.6) — a malformed input map throws a
+     * `AssetParseError` naming the file, not a deep TypeError once the bad
+     * data reaches `isPressed`/`isJustPressed`/`isJustReleased`.
+     */
+    loadMap(url: string): Promise<void>;
+    /**
+     * F3 — `loadMap`'s synchronous, no-`fetch` sibling: apply an already-in-
+     * memory (or freshly-deserialized) input-map DOCUMENT, validated through
+     * the identical `InputMapFileSchema` (throws `AssetParseError` naming no
+     * file, matching `loadMap`'s error shape minus the URL). This is the other
+     * half of the F3 persist round-trip: `toInputMapFile()` serializes,
+     * `loadMapObject` re-applies — no network/file I/O required, so it's also
+     * how a headless test proves a rebind survives a save/reload cycle.
+     */
+    loadMapObject(data: unknown): InputMapFile;
+    /** Shared apply step for `loadMap`/`loadMapObject`: copy each action's
+     *  bindings + declared valueType into the live maps, and snapshot the
+     *  bindings as that action's F3 reset-to-defaults baseline. */
+    private applyParsedMap;
+    /** Register an action programmatically. `valueType` declares the action's
+     *  value shape (F1) — defaults to `'digital'`, matching every call site
+     *  written before F1. F3 — also snapshots `bindings` as this action's
+     *  reset-to-defaults baseline (see `resetBindings`). */
+    registerAction(name: string, bindings: InputBinding[], valueType?: ActionValueType): void;
+    /** The declared value type for a registered/loaded action (F1) — `'digital'`
+     *  for an action that never specified one (including an unregistered/typo'd
+     *  name — harmless, since every typed getter already treats an unknown
+     *  action as inert). */
+    getActionValueType(actionName: string): ActionValueType;
+    /** Enforces the F1 type-safety AC: reading an action through a typed getter
+     *  whose value type doesn't match the action's DECLARED `valueType` throws,
+     *  naming both. Unknown actions (never registered/loaded) are exempt — they
+     *  already read as inert/zeroed by every getter, matching pre-F1 behavior
+     *  for a typo'd action name. */
+    private assertValueType;
+    /** The names of all registered actions (r3f `world-context` enumerates these
+     *  for its input-binding projection). */
+    actionNames(): string[];
+    /**
+     * Poll gamepads and virtual look stick (call at start of frame).
+     *
+     * `tick` (D15/T-D15.3/.5) — the GAME tick this call services. Pass the
+     * live, shared `Game` tick counter here (`setup-three-root-adapter.ts` does,
+     * via `DebugRegistry.getGameTick()`) so `scheduleActionAtTick`'s numbering
+     * never drifts from the actual game tick — the bug an earlier revision of
+     * this feature had: an InputManager-LOCAL counter, incremented once per
+     * `poll()` call, undercounts for a paused/frozen world (its `poll()` isn't
+     * called every game tick while frozen), so a schedule set against "tick
+     * 500" could fire at the wrong wall-tick once the world resumed. Omit it
+     * (every existing bare/headless caller does) to fall back to the
+     * self-incrementing `currentTick` counter — unchanged pre-D15 behavior.
+     */
+    poll(tick?: number): void;
+    /**
+     * D15/T-D15.5 — apply every actuation `scheduleActionAtTick` queued for
+     * exactly `tick`, then forget them (a tick is serviced at most once).
+     *
+     * Digital `true` gets SPECIAL handling (the objection-1 fix): it promotes
+     * the action into this tick's `virtualDigitalTapActive` set directly — the
+     * same one-tick "active" pulse `tapVirtualAction` uses — so `isJustPressed`
+     * reads true for EXACTLY this tick (false on the next, per `endFrame()`'s
+     * clear) while `isPressed` keeps reading true afterward (still held) until
+     * a later scheduled/explicit `false` releases it. This direct write is
+     * safe here (unlike `applyVirtualActionValue`'s equivalent direct-path
+     * case — see its doc comment) specifically because this method only ever
+     * runs from inside `poll()`, AFTER `poll()`'s own tap-queue-promotion
+     * reassignment of `virtualDigitalTapActive` has already happened for this
+     * tick (see `poll()`'s own comment on why it's placed after) — so there's
+     * no risk of this write being silently wiped by that reassignment.
+     *
+     * pulse-runner friction #4: a prior revision of this comment
+     * used to say `setVirtualAction`'s plain write "never produces a
+     * just-pressed edge at all" and that the edge fix landed ONLY here, for
+     * this scheduled path — true at the time, and exactly the gap a blind
+     * dogfood run (pulse-runner) hit through the direct `setVirtualAction`/
+     * `holdFor` path. `applyVirtualActionValue` now manufactures the same kind
+     * of edge for THAT path too (queued instead of written directly, for the
+     * timing reason above) — this is no longer the only path that does.
+     *
+     * A digital `false` here simply releases the hold — no edge is
+     * manufactured for it at a SCHEDULED tick (no caller needs a virtual
+     * `isJustReleased` fired at an exact future tick today); the direct
+     * `setVirtualAction(action, false)`/`clearVirtualActions()` paths DO
+     * manufacture one now (see `applyVirtualActionValue`/
+     * `clearVirtualActionState`). Scalar/vector2 values apply directly,
+     * unchanged.
+     */
+    private applyScheduledActionsForTick;
+    /** D15/T-D15.5 — append this tick's action-value DELTA to the recording
+     *  ring, iff a recording is active. Reads every declared digital/scalar/
+     *  vector2 action through the exact same typed getters gameplay code would
+     *  (`readAction`), so the trace reflects what a component reading these
+     *  actions THIS tick actually sees post-gate — never a raw/ungated value.
+     *  `pointerDelta`/`pointerPosition` actions are skipped (a different,
+     *  frame-accumulated shape, and not part of the virtual-action/schedule
+     *  surface this trace exists to prove).
+     *
+     *  Two replay-affecting caveats a future SP5 consumer must know:
+     *  1. A gated stretch never calls this at all (`poll()`'s gated branch
+     *     returns before reaching it) — no entries are recorded for ticks
+     *     input was suspended. Any change only OBSERVABLE once re-enabled (a
+     *     delta against `lastTraceSnapshot`) lands as a delta AT the re-enable
+     *     tick, not at whatever tick it actually happened.
+     *  2. This ring is capped (`INPUT_TRACE_CAP`) and evicts via `shift()` once
+     *     it fills — dropping the OLDEST entry. Because entries are DELTAS,
+     *     evicting the earliest entries drops the base state later deltas were
+     *     relative to — this ring is not safe to replay from its start once it
+     *     has ever been capped. */
+    private recordPostGateTick;
+    /** Has a `gamepad_axis` binding's raw value crossed its direction+deadzone
+     *  threshold (positive: `value > deadzone`; negative: `value < -deadzone`)? */
+    private static axisThresholdMet;
+    /** Is an action currently held down? */
+    isPressed(actionName: string): boolean;
+    /** Was an action pressed this frame (not held from previous)? */
+    isJustPressed(actionName: string): boolean;
+    /** Was an action released this frame (held last frame, up now)? */
+    isJustReleased(actionName: string): boolean;
+    /** Device/source metadata (F1 AC) for a digital action: which binding is
+     *  CURRENTLY satisfying `isPressed`, or `null` if none is (including an
+     *  unknown action). First-satisfied-binding-wins, mirroring isPressed's own
+     *  iteration order. */
+    getDigitalSource(actionName: string): ActionValueSource | null;
+    /** 1D deadzone rescale: magnitudes below `deadzone` become 0; magnitudes
+     *  at/above it rescale from 0 (at the deadzone edge) to ±1 (at |raw| = 1),
+     *  sign preserved. `raw` is clamped to [-1, 1] first so an out-of-range
+     *  input can't overshoot past ±1 the other end. */
+    private static rescaleScalar;
+    /** Radial deadzone + unit-circle normalization for a Vector2: magnitude
+     *  below `deadzone` snaps to {0,0}; at/above it, direction is preserved and
+     *  magnitude is rescaled the same way `rescaleScalar` rescales a 1D
+     *  magnitude (never renormalized UP past 1 — only ever scaled down). */
+    private static rescaleVector2;
+    /** Clamp a Vector2's magnitude to at most 1 (unit circle), preserving
+     *  direction — the second half of the vector2 "sum-then-clamp" combine
+     *  rule (a diagonal sum like {0.8, 0.8} has magnitude > 1). */
+    private static clampVector2;
+    /** Every `scalar`-relevant binding's (deadzone-applied) contribution for
+     *  `actionName`, one entry per binding that can produce a scalar value —
+     *  `gamepad_axis` (real device, already implemented pre-F1 for digital
+     *  thresholding — F1 additionally reads its raw signed value for scalar
+     *  actions, ignoring the binding's `direction` field, which is a digital-
+     *  only hint) and `test_axis` (F1's injected-test-input source). `mouse_move`
+     *  deliberately does NOT feed scalar (spec §12 F2 — no natural single-axis
+     *  selector field is defined for it; it feeds pointerDelta/vector2 only —
+     *  see `collectPointerDeltaContributions`/`collectVector2Contributions`). */
+    private collectScalarContributions;
+    private computeScalar;
+    /** Read a `'scalar'`-valueType action's current value: max-magnitude across
+     *  contributing (deadzone-applied) bindings, sign preserved (combine rule —
+     *  see the class doc comment). Throws if the action is declared a
+     *  different valueType. */
+    getScalar(actionName: string): number;
+    /** Device/source metadata for {@link getScalar} — which binding is
+     *  currently driving the combined value, or `null` if every contribution is
+     *  zero (including an unknown action). */
+    getScalarSource(actionName: string): ActionValueSource | null;
+    /** `gamepad_axis_pair` contribution(s) for {@link collectVector2Contributions} — one entry
+     *  per connected gamepad, deadzone-rescaled (default 0.15, matching `gamepad_axis`). Broken
+     *  out to a helper so the per-gamepad loop doesn't add to the main dispatcher's complexity. */
+    private contributeGamepadAxisPair;
+    /** Every `vector2`-relevant binding's (deadzone-applied) contribution:
+     *  `test_vector2` (F1's injected-test-input source), plus F2's real-device
+     *  cases — `gamepad_axis_pair` (see {@link contributeGamepadAxisPair}), `mouse_move` (the
+     *  accumulated mouse delta, deadzone default 0 — raw pixel deltas have no natural "at rest"
+     *  jitter floor the way an analog stick does), and `touch_stick` (a virtual on-screen stick,
+     *  deadzone default 0). */
+    private collectVector2Contributions;
+    private computeVector2;
+    /** Read a `'vector2'`-valueType action's current value: sum contributing
+     *  (deadzone-applied) {x,y} values component-wise, then clamp to the unit
+     *  circle (combine rule — see the class doc comment). Throws if the action
+     *  is declared a different valueType. */
+    getVector2(actionName: string): Vector2;
+    /** Device/source metadata for {@link getVector2} — the contributing binding
+     *  with the largest (pre-combine) magnitude, or `null` if the combined
+     *  value is {0,0} (including an unknown action). */
+    getVector2Source(actionName: string): ActionValueSource | null;
+    /** Every `pointerDelta`-relevant binding's contribution: `test_pointer_delta`
+     *  (F1's injected-test-input source) and — F2 — `mouse_move`, reading the
+     *  real accumulated `mouseDeltaX/Y` (the same accumulator `onMouseMove`
+     *  fills and `getMouseDelta()` reads). No deadzone for either (deltas are
+     *  not deadzoned). */
+    private collectPointerDeltaContributions;
+    private computePointerDelta;
+    /** Read a `'pointerDelta'`-valueType action's this-frame movement: sum of
+     *  contributing bindings' deltas (combine rule — see the class doc
+     *  comment). Throws if the action is declared a different valueType. */
+    getPointerDelta(actionName: string): Vector2;
+    /** Device/source metadata for {@link getPointerDelta}. */
+    getPointerDeltaSource(actionName: string): ActionValueSource | null;
+    /** Every `pointerPosition`-relevant binding's contribution, each tagged
+     *  with the injection-order sequence number used to break ties (last-
+     *  write-wins) — today only `test_pointer_position` (F1's injected-test-
+     *  input source). */
+    private collectPointerPositionContributions;
+    private computePointerPosition;
+    /** Read a `'pointerPosition'`-valueType action's current absolute position:
+     *  last-write-wins across contributing bindings (combine rule — see the
+     *  class doc comment; position isn't additive, so it is never summed).
+     *  Throws if the action is declared a different valueType. */
+    getPointerPosition(actionName: string): Vector2;
+    /** Device/source metadata for {@link getPointerPosition} — the most
+     *  recently-written contributing source. */
+    getPointerPositionSource(actionName: string): ActionValueSource | null;
+    /** Generic typed read (F1): dispatches to the matching typed getter based
+     *  on `expectedType`, returning `ActionValueOf<T>` — a caller with a
+     *  statically-known action-value-type map gets a fully-inferred, non-`any`
+     *  return type. Throws the same mismatch error as the dedicated getters if
+     *  the action's declared valueType disagrees with `expectedType`. */
+    readAction<T extends ActionValueType>(actionName: string, expectedType: T): ActionValueOf<T>;
+    /** Inject a synthetic scalar value for a named test source (F1's injected-
+     *  test-input hook — also the shape of F2's "injected test input" backend).
+     *  Bind an action to `{ type: 'test_axis', sourceId }` (`valueType:
+     *  'scalar'`) to read it back via {@link getScalar}. The value PERSISTS
+     *  across frames (like a real analog stick held in position) until changed
+     *  or cleared via {@link clearAxis}. */
+    injectAxis(sourceId: string, value: number): void;
+    /** Clear an injected scalar source (e.g. simulating an at-rest/disconnected
+     *  device). */
+    clearAxis(sourceId: string): void;
+    /** Inject a synthetic {x,y} value for a named test source. Bind an action
+     *  to `{ type: 'test_vector2', sourceId }` (`valueType: 'vector2'`) to read
+     *  it back via {@link getVector2}. Persists across frames until changed or
+     *  cleared via {@link clearVector2}. */
+    injectVector2(sourceId: string, value: Vector2): void;
+    /** Clear an injected Vector2 source. */
+    clearVector2(sourceId: string): void;
+    /** Accumulate a synthetic pointer delta for a named test source — mirrors
+     *  real mouse-move delta accumulation (`onMouseMove` above): multiple calls
+     *  within the same frame sum, and the accumulator is cleared in
+     *  {@link endFrame}. Bind an action to `{ type: 'test_pointer_delta',
+     *  sourceId }` (`valueType: 'pointerDelta'`) to read it back via
+     *  {@link getPointerDelta}. */
+    injectPointerDelta(sourceId: string, delta: Vector2): void;
+    /** Set a synthetic absolute pointer position for a named test source.
+     *  Persists (last-write-wins across contributing sources on read — see the
+     *  pointerPosition combine rule) until changed. Bind an action to `{ type:
+     *  'test_pointer_position', sourceId }` (`valueType: 'pointerPosition'`) to
+     *  read it back via {@link getPointerPosition}. */
+    injectPointerPosition(sourceId: string, value: Vector2): void;
+    /** Whether input capture is currently enabled (see {@link setEnabled}). */
+    isEnabled(): boolean;
+    /**
+     * Enable/disable input capture. The editor host disables the running game's
+     * input while its viewport isn't focused so keystrokes don't leak in from
+     * the editor. Disabling clears all held/transient keyboard/mouse/touch-button
+     * state (via {@link flushHeldState}) so nothing sticks (e.g. a held movement
+     * key when you switch back to the Scene tab mid-flight) — gamepad state
+     * doesn't need clearing here since `poll()` itself stops reading it while
+     * disabled (see poll()'s doc comment).
+     */
+    setEnabled(enabled: boolean): void;
+    /** Whether the window/tab is currently focused (F2, spec §12 "focus
+     *  gating") — `false` while blurred (real `blur`/`focus` events; see the
+     *  constructor). Distinct from {@link isEnabled}, which is the editor's
+     *  explicit play-mode gate. */
+    isFocused(): boolean;
+    /** Whether the pointer is currently locked to {@link requestPointerLock}'s
+     *  element (F2, spec §12 "pointer lock") — tracked via the real
+     *  `pointerlockchange` event. */
+    isPointerLocked(): boolean;
+    /** Device identity for a connected gamepad slot (F2, spec §12 "expose
+     *  device identity" + "prefer the standard mapping"), or `null` if nothing
+     *  is connected at `index` (including while input is disabled/unfocused,
+     *  since `poll()` empties `this.gamepads` then). `mapping` is the Gamepad
+     *  API's own `'standard'`/`''` value — bindings author button/axis indices
+     *  assuming the W3C Standard Gamepad layout, so a non-`'standard'` mapping
+     *  means those indices may not correspond as documented. */
+    getGamepadInfo(index: number): {
+        index: number;
+        id: string;
+        mapping: string;
+        connected: boolean;
+    } | null;
+    /** Get mouse movement delta this frame */
+    getMouseDelta(): {
+        x: number;
+        y: number;
+    };
+    /**
+     * F4 (spec §12 "Schema and Examples" — the F3 prompt-switching gap): which
+     * device family most recently produced real input, or `null` before any
+     * input has arrived. A prompt UI polls this (or lets {@link getPrompt}
+     * consult it automatically by omitting `device`) to switch its displayed
+     * label as the player switches controllers — e.g. showing `'Space'` while
+     * they're on keyboard, then `'A'` the moment they touch a gamepad.
+     */
+    getLastActiveDevice(): PromptDevice | null;
+    /** The current bindings for `actionName` (F3 AC "listed") — a defensive
+     *  deep clone, so mutating the returned array/objects never affects the
+     *  live binding list. `[]` for an unknown/never-registered action. */
+    getBindings(actionName: string): InputBinding[];
+    /** Wholesale-replace `actionName`'s bindings array (F3 AC "replaced"). Does
+     *  NOT touch the reset-to-defaults snapshot — see `resetBindings`. A no-op
+     *  target for an action that was never registered is allowed (it simply
+     *  registers one with `valueType: 'digital'`, matching `registerAction`'s
+     *  own default) since a rebinding UI operates on actions it already knows
+     *  about, but shouldn't have to special-case "brand new action" separately. */
+    setBindings(actionName: string, bindings: InputBinding[]): void;
+    /** Append one binding to `actionName` (F3 AC "added"). */
+    addBinding(actionName: string, binding: InputBinding): void;
+    /** Remove the binding at `index` from `actionName` (F3 AC "removed"). A
+     *  no-op if the action is unknown or `index` is out of range (rather than
+     *  throwing) — mirrors every other getter's "unknown action is inert"
+     *  convention, so a UI doesn't need a separate existence check first. */
+    removeBinding(actionName: string, index: number): void;
+    /** Replace a single binding slot at `index` on `actionName` — the shape a
+     *  rebinding UI actually wants ("rebind THIS control"), built on
+     *  `getBindings`/`setBindings`. A no-op if the action is unknown or `index`
+     *  is out of range. */
+    replaceBinding(actionName: string, index: number, binding: InputBinding): void;
+    /** Restore `actionName`'s bindings to the snapshot taken at
+     *  `registerAction`/`loadMap`/`loadMapObject` time (F3 AC "reset"). A no-op
+     *  for an action with no snapshot (never registered/loaded — there is no
+     *  "default" to reset to). */
+    resetBindings(actionName: string): void;
+    /** Reset every action that has a snapshot back to its registered/loaded
+     *  defaults. Convenience batch form of `resetBindings`. */
+    resetAllBindings(): void;
+    /**
+     * Whether `a` and `b` are the SAME physical input (F3's structural-conflict
+     * identity check — see `findConflicts`). Deliberately narrower than deep
+     * equality: `deadzone` never participates (two bindings on the same key
+     * with different deadzones are still the same physical control), and a
+     * `gamepad_axis`'s `direction` DOES participate — opposite directions of one
+     * physical axis (e.g. "accelerate" on positive, "brake" on negative) are a
+     * legitimate, non-conflicting pair, not a collision.
+     */
+    private static bindingsCollide;
+    /**
+     * Every EXISTING binding, on every OTHER registered action, that is
+     * structurally the same physical input as `proposed` (F3 AC "conflicts are
+     * detected and returned structurally") — never throws, always a plain
+     * (possibly empty) array a rebinding UI inspects before committing a
+     * rebind. `excludeActionName` is normally the action being rebound itself
+     * (so an action isn't reported as conflicting with its own current
+     * binding when re-proposing an unchanged value).
+     */
+    findConflicts(proposed: InputBinding, excludeActionName?: string): BindingConflict[];
+    /**
+     * Serialize every registered/loaded action back into the `.inputmap.json`
+     * document shape (F3 AC "persisted") — the exact `InputMapFile` shape
+     * `loadMap`/`loadMapObject` read, so `manager.loadMapObject(manager.toInputMapFile())`
+     * on a fresh instance reproduces the same live bindings. `version` is
+     * carried forward from the last loaded map when known, else `1` (a
+     * manager built purely via `registerAction` calls, never `loadMap`, has no
+     * file-format version to preserve).
+     */
+    toInputMapFile(): InputMapFile;
+    /**
+     * Resolve a display prompt (F3 AC: labels/icons like `'Space'`, `'A'`, or a
+     * touch control's name) for whichever of `actionName`'s bindings belongs to
+     * the requested `device` family. `null` when the action has no binding for
+     * that device (including an unknown action). `gamepadIndex` (default 0)
+     * selects which connected pad's `mapping`/connected state to consult for a
+     * `gamepad_*` binding — see `getGamepadInfo`.
+     *
+     * F4 — `device` is now OPTIONAL: omit it (or pass `undefined`) to resolve
+     * against {@link getLastActiveDevice} instead (falling back to `'keyboard'`
+     * before any input has arrived), so a prompt UI that wants "show whatever
+     * the player is actually holding right now" doesn't have to track the
+     * active device itself — it can just call `getPrompt(actionName)` every
+     * frame and the label switches on its own as the player changes controllers.
+     * Passing an explicit `device` (as every pre-F4 caller does) is unaffected.
+     */
+    getPrompt(actionName: string, device?: PromptDevice, gamepadIndex?: number): BindingPrompt | null;
+    /** Call at end of frame to clear per-frame state */
+    endFrame(): void;
+    /** Inject synthetic key state from touch controls */
+    setVirtualKey(code: string, pressed: boolean): void;
+    /** Set virtual look stick position (-1..1). Injected as mouse delta during poll(). */
+    setLookStick(x: number, y: number): void;
+    /** Inject synthetic mouse delta (e.g. from touch controls) */
+    addMouseDelta(dx: number, dy: number): void;
+    /**
+     * F2 (spec §12 "Complete Device Backends") — the touch/virtual-control
+     * digital backend. Set a named virtual button's (`sourceId` — a zone/knob
+     * id the touch UI chooses) pressed state; edge-tracked exactly like a real
+     * mouse button (`onMouseDown`/`onMouseUp` above) so `isJustPressed`/
+     * `isJustReleased` work for `{ type: 'touch_button', sourceId }` bindings.
+     * This is the injectable entry point a real on-screen button's own
+     * touchstart/touchend handler would call — that DOM wiring is a thin
+     * adapter at the edge (browser-verified separately); this method is the
+     * MAPPING logic, unit-tested headlessly with no DOM.
+     */
+    setTouchButton(sourceId: string, pressed: boolean): void;
+    /**
+     * F2 — the touch/virtual-control analog backend. Set a named virtual
+     * stick's (`sourceId`) raw `{x,y}` position (e.g. -1..1 per axis, like a
+     * gamepad stick); read back via `getVector2` on a `{ type: 'touch_stick',
+     * sourceId }` binding, deadzone-rescaled the same way a gamepad stick is.
+     * Persists across frames (a level value, like a real analog stick held in
+     * position) until changed or cleared via {@link clearTouchStick}.
+     */
+    setTouchStick(sourceId: string, value: Vector2): void;
+    /** Clear a virtual stick's value (e.g. simulating the touch point lifting —
+     *  the knob returns to center). */
+    clearTouchStick(sourceId: string): void;
+    /** Existence check shared by `setVirtualAction`/`tapVirtualAction` — throws
+     *  `InputActionError` (`code: 'INPUT_ACTION_NOT_FOUND'`, `data.registered`
+     *  = every declared action name) for a name that was never
+     *  `registerAction`/`loadMap`-ed. */
+    private assertActionExists;
+    /** Which declared `ActionValueType` a `setVirtualAction` value shape
+     *  corresponds to — the type-safety check mirrors every typed getter's
+     *  `assertValueType` (F1). `pointerDelta`/`pointerPosition` actions aren't
+     *  drivable through `setVirtualAction` (no boolean/number/Vector2 call
+     *  shape maps to them) — use `injectPointerDelta`/`injectPointerPosition`. */
+    private static virtualValueCategory;
+    /**
+     * Set a virtual value for `action`, OR'd/summed into the same action reads
+     * humans drive (see the section doc comment above). A `boolean` holds a
+     * digital action pressed until set `false`/cleared; a `number` or `{x,y}`
+     * is a level value combined via the action's own scalar max-magnitude /
+     * vector2 sum-then-clamp rule.
+     *
+     * A digital `false`→`true` transition manufactures a genuine `isJustPressed`
+     * edge, exactly one real key-down does (pulse-runner friction #4 —
+     * previously this write-half only ever held the action pressed with NO
+     * edge at all; every edge-triggered ability driven through this direct
+     * path was unprovable). Re-setting `true` while already held (auto-repeat)
+     * does NOT re-fire it — see {@link applyVirtualActionValue}. The mirror
+     * `true`→`false` transition manufactures an `isJustReleased` edge the same
+     * way a real key-up does.
+     *
+     * Throws `InputActionError` for an unregistered `action`, and the same
+     * valueType-mismatch error every typed getter throws (`assertValueType`)
+     * when `value`'s shape doesn't match the action's declared `valueType`.
+     *
+     * Gated (`setEnabled(false)` — play stopped or editor-gated; #144: window
+     * focus no longer gates machine input): writes NOTHING — matching
+     * `setTouchButton`'s write-gate precedent above — and returns
+     * `{delivered: false, reason}` rather than a silent no-op, so a probe/bot
+     * never mistakes a swallowed actuation for a delivered one.
+     */
+    setVirtualAction(action: string, value: boolean | number | {
+        x: number;
+        y: number;
+    }): {
+        delivered: boolean;
+        reason?: string;
+    };
+    /**
+     * The write half of {@link setVirtualAction} — extracted so D15/T-D15.5's
+     * `scheduleActionAtTick` can apply a non-boolean (scalar/vector2) queued
+     * actuation through the exact same code path (no gate check here: the two
+     * callers gate differently — `setVirtualAction` above checks
+     * `inputActive` before calling this; `applyScheduledActionsForTick` is
+     * only ever reached from inside `poll()` AFTER its own gate check has
+     * already returned early on a gated tick). `applyScheduledActionsForTick`
+     * still handles digital `true` itself rather than calling here (its
+     * one-tick edge must land EXACTLY at the scheduled tick — see its own doc
+     * comment) — this method's digital branch is `setVirtualAction`'s direct
+     * path, called at an arbitrary point relative to the poll()/endFrame()
+     * bracket.
+     *
+     * pulse-runner friction #4 — the digital branch used to be a bare held-flag
+     * write with no manufactured edge at all (the comment that used to sit
+     * here read: "A digital value is handled by `applyScheduledActionsForTick`
+     * itself (it needs the extra just-pressed edge a plain held-value write
+     * doesn't produce)" — i.e. the edge fix shipped ONLY for the scheduled
+     * path, never for this one, which is exactly the gap a blind dogfood run
+     * hit: `setVirtualAction('jump', true)` held the action down but
+     * `isJustPressed('jump')` never fired). Fixed here by reusing
+     * `tapVirtualAction`'s exact one-tick-pulse queue mechanism for this
+     * DIRECT case, specifically because this method's caller can land at any
+     * point relative to `poll()`: writing `virtualDigitalTapActive` directly
+     * here (as the scheduled path safely does, from inside `poll()` itself)
+     * would risk being silently wiped by `poll()`'s own unconditional
+     * `virtualDigitalTapActive = virtualDigitalTapQueued` reassignment,
+     * depending on timing. Queueing side-steps that hazard by construction —
+     * the same reason `tapVirtualAction` queues instead of writing directly. A
+     * redundant `true` while already held (`virtualDigitalHeld` already has
+     * `action`) does not queue again, matching a real key's auto-repeat never
+     * re-firing `isJustPressed`. The `false` branch mirrors real `onKeyUp`
+     * instead (immediate write, no queue needed — nothing in `poll()`
+     * reassigns `virtualDigitalJustReleased`), and only fires when the action
+     * was actually held (no released→released re-fire).
+     */
+    private applyVirtualActionValue;
+    /**
+     * One-frame press of a `'digital'` action (Task 1.4): queues `action` so it
+     * reads `isJustPressed`/`isPressed` true for EXACTLY the next `poll()`'s
+     * frame — promoted to the "active" set at the top of `poll()`, cleared in
+     * `endFrame()` alongside every other just-pressed edge set (see both
+     * above). Hollowstone's `queued`/`beginFrame` tap contract, ported onto
+     * this engine's existing fixed-step `poll()`/`endFrame()` bracket instead
+     * of a bespoke `beginFrame()` hook.
+     *
+     * Throws the same errors as {@link setVirtualAction} (unknown action;
+     * non-digital valueType). A gated tap does NOT queue — it must not fire on
+     * a later frame once input becomes active again — and returns
+     * `{delivered: false, reason}`.
+     */
+    tapVirtualAction(action: string): {
+        delivered: boolean;
+        reason?: string;
+    };
+    /** Clear all virtual-action state — held digitals, queued/active taps, and
+     *  scalar/vector2 values. `flushHeldState()` (the same flush
+     *  `setEnabled(false)`/real blur apply to held keys/mouse/touch buttons)
+     *  shares the underlying wipe, so a bot's held action never survives input
+     *  being suspended — but only THIS public entry point (a deliberate "let
+     *  go", the mirror of `setVirtualAction(action, false)` below) manufactures
+     *  an `isJustReleased` edge for whatever was held; the suspend path stays
+     *  silent (see `flushHeldState`'s own doc comment). */
+    clearVirtualActions(): void;
+    /**
+     * D15/T-D15.5 — schedule a virtual actuation for exactly `tick`: applied
+     * at the START of that tick's `poll()` (composing with `runTicks` — a
+     * schedule for tick 500 fires exactly once the sim has been driven through
+     * tick 500, regardless of burst size). A digital `true` produces a genuine
+     * `isJustPressed` edge exactly at the target tick (not merely a held value
+     * — see `applyScheduledActionsForTick`).
+     *
+     * Throws `InputActionError` for an unregistered `action` and the same
+     * valueType-mismatch error every typed getter throws (`assertValueType`) —
+     * both checked EAGERLY, at schedule time, not deferred to the target tick.
+     * Throws `InputTickError` (`code: 'TICK_ALREADY_PASSED'`) when `tick` is
+     * strictly less than the tick `poll()` will service NEXT — scheduling only
+     * ever reaches the current or a future tick. A tick whose input phase
+     * never runs (this world paused/frozen at that point, or a multi-tick gap
+     * — see `poll()`) drops its scheduled entries rather than replaying them
+     * late — each drop emits one `'input.schedule.dropped'` debug event
+     * (`{tick, action}`) via {@link setDebugEmit}'s sink, if one is wired.
+     */
+    scheduleActionAtTick(tick: number, action: string, value: boolean | number | {
+        x: number;
+        y: number;
+    }): void;
+    /** Wire (or clear, via `null`) the sink `poll()` calls with
+     *  `'input.schedule.dropped'` (`{tick, action}`) whenever it discards a
+     *  scheduled entry for a tick whose input phase never ran. Called once by
+     *  whoever constructs this `InputManager` with a `DebugRegistry` behind it
+     *  (`setup-three-root-adapter.ts`), the same seed spot as
+     *  `setVirtualInputTarget`/`setInputActionsSource` — never called directly
+     *  by gameplay code. */
+    setDebugEmit(fn: ((event: string, detail?: unknown) => void) | null): void;
+    /** D15/T-D15.5 — start (or restart) recording the post-gate action-delta
+     *  trace: clears any prior trace/snapshot, so a fresh recording session
+     *  never carries over stale deltas from an earlier one. */
+    startInputRecording(): void;
+    /** D15/T-D15.5 — stop recording (the trace accumulated so far stays
+     *  readable via {@link getInputTrace} until the next `startInputRecording`
+     *  clears it). Idempotent. */
+    stopInputRecording(): void;
+    /** D15/T-D15.5 — whether a recording is currently active. */
+    isInputRecording(): boolean;
+    /** D15/T-D15.5 — the recorded trace so far (a defensive copy), versioned
+     *  per the design doc's format sketch (§2.c). SP5 (out of scope here) is
+     *  the eventual consumer that replays this; this module only ever
+     *  RECORDS. */
+    getInputTrace(): {
+        version: 1;
+        ticks: {
+            tick: number;
+            actions: Record<string, boolean | number | {
+                x: number;
+                y: number;
+            }>;
+        }[];
+    };
+    /** Request pointer lock for FPS-style mouse control */
+    requestPointerLock(element: HTMLElement): void;
+    /** Clean up event listeners */
+    dispose(): void;
+}
+//# sourceMappingURL=input-manager.d.ts.map