From cb88a0644ed6cf11e3927cba02c0d803919c92fa Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Tue, 8 Sep 2026 10:53:41 +0000
Subject: [PATCH] Version Packages

---
 .changeset/look-input-3d.md                   |  51 ---------
 .changeset/look-input-input.md                |  47 --------
 .changeset/physics-poses-physics-2d.md        |  38 -------
 .changeset/physics-poses-physics.md           |  28 -----
 .changeset/post-process-live-tuning.md        |  31 ------
 .changeset/shape-cast-ignore.md               |  34 ------
 .changeset/third-person-orbit-roll.md         |  21 ----
 packages/2d/CHANGELOG.md                      |   7 ++
 packages/2d/package.json                      |   2 +-
 packages/2d/skills/2d/SKILL.md                |   2 +-
 packages/3d/CHANGELOG.md                      | 105 ++++++++++++++++++
 packages/3d/package.json                      |   2 +-
 packages/3d/skills/3d/SKILL.md                |   2 +-
 packages/audio/CHANGELOG.md                   |   7 ++
 packages/audio/package.json                   |   2 +-
 packages/audio/skills/audio/SKILL.md          |   2 +-
 packages/cli/CHANGELOG.md                     |   4 +
 packages/cli/package.json                     |   2 +-
 packages/core/CHANGELOG.md                    |  32 ++++++
 packages/core/package.json                    |   2 +-
 packages/devtools/CHANGELOG.md                |  16 +++
 packages/devtools/package.json                |   2 +-
 packages/devtools/skills/devtools/SKILL.md    |   2 +-
 packages/electron/CHANGELOG.md                |   7 ++
 packages/electron/package.json                |   2 +-
 packages/electron/skills/electron/SKILL.md    |   2 +-
 packages/ignifx/CHANGELOG.md                  |  22 ++++
 packages/ignifx/package.json                  |   2 +-
 packages/input/CHANGELOG.md                   |  50 +++++++++
 packages/input/package.json                   |   2 +-
 packages/input/skills/input/SKILL.md          |   2 +-
 packages/physics-2d/CHANGELOG.md              |  42 +++++++
 packages/physics-2d/package.json              |   2 +-
 .../physics-2d/skills/physics-2d/SKILL.md     |   2 +-
 packages/physics/CHANGELOG.md                 |  60 ++++++++++
 packages/physics/package.json                 |   2 +-
 packages/physics/skills/physics/SKILL.md      |   2 +-
 packages/ui/CHANGELOG.md                      |   9 ++
 packages/ui/package.json                      |   2 +-
 packages/ui/skills/ui/SKILL.md                |   2 +-
 packages/vite-plugin/CHANGELOG.md             |   7 ++
 packages/vite-plugin/package.json             |   2 +-
 skills/ignifx/SKILL.md                        |   2 +-
 .../references/formats/ignifx.schemas.json    |   2 +-
 44 files changed, 392 insertions(+), 274 deletions(-)
 delete mode 100644 .changeset/look-input-3d.md
 delete mode 100644 .changeset/look-input-input.md
 delete mode 100644 .changeset/physics-poses-physics-2d.md
 delete mode 100644 .changeset/physics-poses-physics.md
 delete mode 100644 .changeset/post-process-live-tuning.md
 delete mode 100644 .changeset/shape-cast-ignore.md
 delete mode 100644 .changeset/third-person-orbit-roll.md

diff --git a/.changeset/look-input-3d.md b/.changeset/look-input-3d.md
deleted file mode 100644
index ef136fc..0000000
--- a/.changeset/look-input-3d.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-"@ignifx/3d": patch
----
-
-The look rigs re-arm pointer lock, ignore an unlocked mouse, and read a stick as a rate
-
-`FirstPersonController` and `ThirdPersonCamera` were each doing their own look arithmetic, and both
-were wrong in the same four ways. The look half of both now lives in one internal module and the
-four defects are fixed together.
-
-**Pointer lock re-arms.** `FirstPersonController` set a latch on its first request and never cleared
-it, so once the browser released the lock — Escape, which the templates also bind to the pause menu,
-or a focus change — no later click could take it back and the player finished the session with an
-unlocked mouse. The lock is now requested on **every** frame that carries a `pointerdown`
-while the lock is not held; the only guard is a request already in flight. A refusal is logged and
-dropped, exactly as before.
-
-**An unlocked mouse no longer turns the view.** While `lockPointerOnClick` is on and the lock is not
-held, a `Look` reading whose `InputAction.activeDevice` is `Mouse` or `Pointer` is ignored. Before,
-the view spun whenever the cursor crossed the canvas — on its way to a menu button, say — and stopped
-dead when the cursor left the frame. Gamepad, touch, and virtual sticks are never gated: they have no
-cursor to lose. `lockPointerOnClick: false` keeps unconditional mouse look for drag-to-look designs.
-
-**A stick is a rate, a pointer is a displacement.** Both rigs did `yaw += look.x * sensitivity` for
-every device. That is right for a pointer delta, which is this frame's motion, and wrong for a stick,
-whose value is a deflection: at 120 Hz the stick turned twice as fast as at 60 Hz, and games papered
-over it with a `scale(18)` processor. A gamepad or virtual reading is now multiplied by the new
-`stickLookSpeed` (degrees per second at full deflection, default 180) and the frame delta, so the
-same push turns through the same angle in the same second at any frame rate, and slow motion slows
-the look with everything else. `sensitivity` keeps its meaning for pointer readings — degrees per unit,
-which with `@ignifx/input`'s CSS-pixel deltas is degrees per CSS pixel, so 0.08–0.15 suits most mice
-on every display and at every render scale.
-
-**Up is up on every device.** A screen's `movementY` grows downward and a stick's `y` grows upward,
-and both rigs subtracted `look.y` from their pitch regardless — so one `invertY` could only ever suit
-one device family, and a first-person mouse looked *down* when it was pushed forward. The pitch axis
-is normalised where the device is known: `Mouse`, `Pointer`, and `Touch` readings are negated, gamepad
-and virtual are not, and the rigs apply their own sign and `invertY` on top as before. Moving the
-mouse forward and pushing a stick up now both look up in first person, and both lower the boom and
-aim the camera up in third person; `invertY` flips every device together.
-
-`ThirdPersonCamera` also gains `lockPointerOnClick`, defaulting to **`false`**: a rig that orbits on a
-held mouse button needs its cursor, so nothing changes for an existing third-person game until it
-opts in to the console-style "click to capture, Escape to release" behaviour.
-
-Public API change: `FirstPersonController.stickLookSpeed`, `ThirdPersonCamera.stickLookSpeed`, and
-`ThirdPersonCamera.lockPointerOnClick` are new schema fields. No field was removed or renamed. Two
-behaviour changes need a look from any game that ships a look binding: drop the `scale(...)`
-processors from stick look bindings, which double-count against `stickLookSpeed`, keeping the
-`deadzone(...)`; and drop any `scale(1, -1)` that existed to line a stick up with the mouse, because
-the rigs agree on which way is up now — reach for `invertY` instead.
diff --git a/.changeset/look-input-input.md b/.changeset/look-input-input.md
deleted file mode 100644
index eeab452..0000000
--- a/.changeset/look-input-input.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-"@ignifx/input": patch
----
-
-Pointer deltas are CSS pixels, the canvas wheel no longer scrolls the page, `InputAction.activeDevice`, and pointer lock asks for raw mouse motion
-
-Four fixes to the things a look control is built out of, all found while chasing "the camera on the
-third-person example does not behave correctly" and "scroll interferes with page scrolling".
-
-**The wheel is taken non-passively.** The canvas `wheel` listener was registered `{ passive: true }`,
-which forbids `preventDefault`, so a wheel over a running game zoomed the camera _and_ scrolled the
-page underneath it — obvious on ignifx.com, where the examples live in an `<iframe>` and the wheel
-took the article with it. The listener is now non-passive and prevents the default on every event it
-queues. The wheel is still read from the canvas alone, so a wheel over the page's own chrome is
-untouched, and the queued entry is unchanged.
-
-**Pointer deltas are CSS pixels; positions stay backing-store pixels.** `<Mouse>/delta`,
-`<Pointer>/delta`, `<Touch>/…/delta` and `event.deltaX`/`deltaY` were multiplied by
-`canvas.width / rect.width`, the same scale positions need. A delta is hand motion, not a place on
-the render target: the scale doubled every look sensitivity on a device-pixel-ratio-2 display and
-moved it again whenever a settings screen changed `renderer.resolutionScale`. Deltas are now the
-browser's raw `movementX`/`movementY`, and for the pointer types that leave those at zero (touch,
-some pens) the DOM adapter derives the motion from that pointer's own successive `clientX`/`clientY`
-— in CSS pixels, never from the queued position. `DeviceWriter` derives nothing at all now, so
-`simulateEvent` reports exactly the delta a test states. Positions are unchanged, so
-`renderer.pickAsync(pointer.position)` and `Camera.screenToRay` are still exact at every ratio.
-A game author sees one number to tune: a mouse look sensitivity in degrees per CSS pixel, around
-0.08–0.15, the same on every display.
-
-**`InputAction.activeDevice`** names the device family behind the binding whose magnitude won the
-frame, and `null` when the action is at rest or disabled — stable for the frame like every other
-reading. One `Look` action bound to both a mouse and a stick carries two different quantities, and
-this is what lets a rig tell them apart: `@ignifx/3d` uses it to ignore mouse look until the pointer
-is locked and to read a stick as a rate. A composite reports the device of its first part, which is
-the only sensible answer for a `2DVector` whose four parts are one device.
-
-**`PointerLock.request()` asks for `unadjustedMovement: true`** before it asks plainly, falling back
-when the browser rejects the option by throwing or by rejecting the returned promise. That is raw
-mouse motion with the desktop's pointer-acceleration curve removed, which is what a first-person look
-wants — with acceleration on, a fast flick turns further than a slow one over the same desk distance,
-which is most of what players describe as a jumpy look. Settle semantics are unchanged: `true` on
-`pointerlockchange`, `false` on `pointerlockerror`, `IGX-0809` on a headless app.
-
-Public API change: `InputAction.activeDevice: DeviceKind | null` is new. No signature changed, but
-the **meaning** of `<Mouse>/delta`, `<Pointer>/delta` and `<Touch>/…/delta` did: they are CSS pixels
-now, so a project that tuned its sensitivity on a retina display re-tunes it once (`invert` and
-`scale(...)` processors still apply as before).
diff --git a/.changeset/physics-poses-physics-2d.md b/.changeset/physics-poses-physics-2d.md
deleted file mode 100644
index 512b99c..0000000
--- a/.changeset/physics-poses-physics-2d.md
+++ /dev/null
@@ -1,38 +0,0 @@
----
-"@ignifx/physics-2d": patch
----
-
-A `CharacterController2D` walks through triggers instead of bouncing off them, and the display pose is written before `update` so follow cameras stop juddering
-
-**Triggers were walls.** Rapier's `KinematicCharacterController.computeColliderMovement` takes
-`filterFlags` as its third argument, and the adapter passed `undefined`, which leaves sensors in the
-obstacle set. Measured on 2026-09-08 against `@dimforge/rapier2d-compat@0.20.0` (macOS arm64,
-Node 24): a kinematic box driven by the controller towards a static sensor ball stops dead at the
-sensor's surface — `x = 0.49` for a sensor at `x = 1` with radius 0.3, a 0.2 half-width character and
-a 0.01 offset — and because it never overlaps, `drainCollisionEvents` reports nothing at all. With
-`QueryFilterFlags.EXCLUDE_SENSORS` the same character reaches `x = 3.0` and the queue reports the
-`started`/`stopped` pair. Every controller move now passes that flag.
-
-What a game author sees: a collectible finally works. The side-scroller template's coins are a
-`CircleCollider2D { isTrigger: true }` on an entity with no rigidbody, and the player is a
-`CharacterController2D` — so every coin was an invisible bump the player stopped against and
-`onTriggerEnter` never fired. The same was true of the top-down template's shrine pads and of any
-trigger zone a controller-driven character is meant to enter. The flip side is intended: a sensor no
-longer appears in `CharacterController2D.onCollided`, because a trigger is not an obstacle. Use
-`onTriggerEnter`/`onTriggerExit` for pickups and zones and `onCollided` for the walls and floors the
-character actually pushed against.
-
-**The display pose is written at the top of `Update`, not in `PreRender`.** Poses are still
-snapshotted on the fixed step and interpolated with `time.fixedStepAlpha`, but the system that writes
-`lerp(prev, cur, alpha)` moved from `Systems(PreRender, −500)` to `Systems(Update, −900)`, which runs
-straight after the fixed loop and before `scripts.update`. `Camera2DFollow` and every hand-written
-follow camera run in `update`/`lateUpdate`, so they used to frame the character where the last fixed
-step left it while the renderer drew it interpolated: up to one fixed step of relative motion — about
-0.1 m at sprint speed — of judder every frame, and with the pixel-perfect camera the two poses are
-quantised independently, so the sprite visibly shook while running. Now scripts, animation, camera
-rigs and the render sync all read the pose the frame presents, which is Unity's model. `fixedUpdate`
-and Rapier are unaffected: the restore system at `FixedUpdate −100` still runs before
-`scripts.fixedUpdate`, so the simulation only ever sees authoritative poses, and a kinematic body
-moved by writing its transform behaves exactly as before.
-
-Public API change: none. The order constants and both systems are `@internal`.
diff --git a/.changeset/physics-poses-physics.md b/.changeset/physics-poses-physics.md
deleted file mode 100644
index f3630ad..0000000
--- a/.changeset/physics-poses-physics.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-"@ignifx/physics": patch
----
-
-The interpolated display pose is written before `update`, so camera rigs and scripts see the pose the frame draws
-
-Poses are still snapshotted on the fixed step and interpolated with `time.fixedStepAlpha`, but the
-system that writes `lerp(prev, cur, alpha)` into a `Rigidbody`'s or `CharacterController`'s node
-moved from `Systems(PreRender, −500)` to `Systems(Update, −900)` — straight after the fixed loop and
-lifecycle flush B, in front of `scripts.update`.
-
-Why: `ThirdPersonCamera`, `FirstPersonController`, bone attachments and every hand-written follow camera
-run in `update`/`lateUpdate`, which used to be *before* the display pose existed. They framed the
-character where the last fixed step left it while the renderer drew it at `lerp(prev, cur, alpha)`,
-so at any refresh rate the character juddered against the camera by up to one fixed step of motion —
-about 0.1 m at sprint speed, every frame. Writing the pose at the top of `Update` means `update`,
-`lateUpdate`, animation, camera rigs and the render sync all read the same pose the frame presents.
-This is Unity's model.
-
-What a game author sees: a smooth third- or first-person camera, and `transform.position` read from
-`update`/`lateUpdate` now returning the interpolated pose rather than the last fixed one. The
-simulation is unchanged: the restore system at `FixedUpdate −100` still runs before
-`scripts.fixedUpdate`, so `fixedUpdate` and Havok only ever see authoritative poses, and a kinematic
-body moved by writing its transform behaves exactly as before — the restore already overwrote such a
-write before the step read it. A system that must read an authoritative pose outside the fixed loop
-registers at `Phase.Update` with an order below `−900`.
-
-Public API change: none. The order constant and the interpolation system are `@internal`.
diff --git a/.changeset/post-process-live-tuning.md b/.changeset/post-process-live-tuning.md
deleted file mode 100644
index e522373..0000000
--- a/.changeset/post-process-live-tuning.md
+++ /dev/null
@@ -1,31 +0,0 @@
----
-"@ignifx/core": patch
----
-
-`PostProcessStack` fields are live: a slider bound to `bloom.threshold` now changes the picture
-
-The stack built its chain once, the first time any effect was enabled, and every `sync` after that
-only flipped the chain's `executionEnabled` to match the component. The bloom and SMAA records were
-read at that one moment and never again, so `post.bloom.threshold = 0.4` on a running game did
-nothing — the website's bloom example had four sliders and none of them moved the frame — and
-`post.bloom.enabled = false` on a one-effect chain left bloom running, because the chain's identity
-was checked only while no chain existed yet.
-
-Lite's `BloomPostProcessTask` exposes `weight`, `kernel`, `threshold` and `exposure` as writable
-fields and `updateUniforms()` re-uploads every sub-pass from them; `SmaaPostProcessTask` documents
-the same for `threshold`, `maxSearchSteps`, `diagonalDetection` and `cornerDetection` (verified
-against `@babylonjs/lite@1.27.0`, `index.d.ts` 1287 and 11622). The chain now keeps a typed handle
-to each of those tasks and, once per frame, uploads whatever changed since the last upload — a frame
-in which nothing moved uploads nothing. The one tuning Lite fixes at creation is bloom's
-`bloomScale`, which sizes the blur targets, so `bloom.scale` joins "which effects, in which order"
-in the chain's identity: a change to any of them disposes the old chain and records a new one. Lite
-cannot remove a task from a frame graph, so the old tasks stay in it, disabled and with their GPU
-resources freed, at one branch per frame each — toggling an effect's `enabled` in a settings menu
-costs a rebuild per click, whereas toggling the whole component's `enabled` keeps the chain and
-skips it, which is what the templates' settings screens do.
-
-What a game author sees: an inspector edit, a settings slider or a script write to any bloom or SMAA
-field takes effect on the next frame, and turning a single effect off actually turns it off.
-
-Public API change: none. `PostProcessChain.applySettings` and the two adapter functions it calls are
-`@internal`.
diff --git a/.changeset/shape-cast-ignore.md b/.changeset/shape-cast-ignore.md
deleted file mode 100644
index 82a6d6d..0000000
--- a/.changeset/shape-cast-ignore.md
+++ /dev/null
@@ -1,34 +0,0 @@
----
-"@ignifx/physics": patch
-"@ignifx/3d": patch
----
-
-`shapeCast` can sweep past one body, and the third-person boom and step probe no longer report the character's own capsule
-
-Lite's `ShapeCastQuery` carries no collision masks — unlike `physicsRaycast` — so a shape sweep
-cannot be filtered by layer inside Havok; `layerMask` only ever decided which hit was *attributed*
-an entity, and a body outside the mask still stopped the sweep, reported with `entity: null`. Two
-callers in `@ignifx/3d` were sweeping from inside the character's own capsule and were stopped by it
-at fraction zero every time:
-
-- `ThirdPersonCamera` sweeps from its shoulder pivot, which sits inside the capsule, out along the
-  boom. For every yaw whose boom crossed the capsule the sweep hit it immediately, `currentDistance`
-  collapsed to `0` and the camera sat inside the character's head — measured on 2026-09-08 in the
-  third-person template at every yaw from 30° to 180° at the spawn, with no wall anywhere near.
-  `collisionLayers: ["Level", "Prop"]` could not prevent it, because the mask never reached the sweep.
-- `ThirdPersonController`'s step probe sweeps a sphere forward from the character's feet; both of its
-  sweeps found the capsule first, so `stepHeight` never lifted anything.
-
-`ShapeCastOptions` — `QueryOptions` plus `ignore?: Entity | null` — names the one body the sweep
-passes through, resolved to its Havok body whether the entity is a `Rigidbody`, a collider-only
-static, or a `CharacterController` (whose capsule body Lite exposes through `getBody()`). The camera
-rig ignores its `target`; the step probe ignores its own entity. A masked-out body other than the
-ignored one still shortens the boom, which for scenery is the point and is now said so on
-`collisionLayers`.
-
-What a game author sees: a third-person camera that holds its distance through a full orbit and a
-`stepHeight` that climbs steps; and, for their own queries, a way to sweep out of a body they are
-standing in.
-
-Public API change: `ShapeCastOptions` is new and `PhysicsService.shapeCast` takes it in place of
-`QueryOptions` (a widening — every existing call compiles). Nothing was removed or renamed.
diff --git a/.changeset/third-person-orbit-roll.md b/.changeset/third-person-orbit-roll.md
deleted file mode 100644
index 1a25774..0000000
--- a/.changeset/third-person-orbit-roll.md
+++ /dev/null
@@ -1,21 +0,0 @@
----
-"@ignifx/3d": patch
----
-
-`ThirdPersonCamera` no longer rolls the horizon when the mouse moves sideways
-
-The rig built its rotation with one `Quat.fromEulerDegrees(pitch, yaw, 0)` call. That helper composes
-in intrinsic XYZ order, so the boom was pitched first and then yawed about the *tilted* axis: with
-any pitch at all — and the template starts twelve degrees down — a horizontal mouse motion tilted the
-camera rather than turning it, and the camera rose and fell as it went round (measured 2026-09-08:
-at 15 degrees of pitch its height followed `cos(yaw)`).
-
-The rotation is now `Ry(yaw) * Rx(pitch)`: yaw about the world's up, then pitch about the camera's
-own right, which is the one order in which looking sideways is a turn about the vertical. The
-starting angles are read off the entity's forward vector at `awake` instead of its Euler angles, so
-an authored downward tilt seeds the same pitch whatever Euler order wrote it.
-
-What a game author sees: a third-person camera whose horizon stays level and whose height stays put
-through a full orbit, at every pitch.
-
-Public API change: none.
diff --git a/packages/2d/CHANGELOG.md b/packages/2d/CHANGELOG.md
index 30d8ff0..e44f6e9 100644
--- a/packages/2d/CHANGELOG.md
+++ b/packages/2d/CHANGELOG.md
@@ -1,5 +1,12 @@
 # @ignifx/2d
 
+## 0.2.1
+
+### Patch Changes
+
+- Updated dependencies [388b0f6]
+  - @ignifx/core@0.2.1
+
 ## 0.2.0
 
 ### Patch Changes
diff --git a/packages/2d/package.json b/packages/2d/package.json
index 62af20e..f298b1d 100644
--- a/packages/2d/package.json
+++ b/packages/2d/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@ignifx/2d",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "description": "ignifx 2D toolkit: Camera2D, sprites, sprite animation, atlases, tilemaps, sorting layers, pixel-perfect, parallax.",
   "keywords": [
     "ignifx",
diff --git a/packages/2d/skills/2d/SKILL.md b/packages/2d/skills/2d/SKILL.md
index e09428f..6c4b538 100644
--- a/packages/2d/skills/2d/SKILL.md
+++ b/packages/2d/skills/2d/SKILL.md
@@ -3,7 +3,7 @@ name: 2d
 description: Builds 2D games in ignifx with @ignifx/2d: Camera2D, SpriteRenderer, SpriteAnimator, texture atlases, Tilemap rendering and import, sorting layers and Y-sort, pixel-perfect cameras, parallax layers, and 2D picking. Use when adding or editing sprites, sprite animation, tilemaps, atlases, sorting layers, or a 2D camera in an ignifx project, or when the user mentions @ignifx/2d, Camera2D, SpriteRenderer, or Tilemap.
 license: Apache-2.0
 metadata:
-  ignifx-version: "0.2.0"
+  ignifx-version: "0.2.1"
 ---
 
 # @ignifx/2d
diff --git a/packages/3d/CHANGELOG.md b/packages/3d/CHANGELOG.md
index b32c49c..105440a 100644
--- a/packages/3d/CHANGELOG.md
+++ b/packages/3d/CHANGELOG.md
@@ -1,5 +1,110 @@
 # @ignifx/3d
 
+## 0.2.1
+
+### Patch Changes
+
+- 7adf987: The look rigs re-arm pointer lock, ignore an unlocked mouse, and read a stick as a rate
+  
+  `FirstPersonController` and `ThirdPersonCamera` were each doing their own look arithmetic, and both
+  were wrong in the same four ways. The look half of both now lives in one internal module and the
+  four defects are fixed together.
+  
+  **Pointer lock re-arms.** `FirstPersonController` set a latch on its first request and never cleared
+  it, so once the browser released the lock — Escape, which the templates also bind to the pause menu,
+  or a focus change — no later click could take it back and the player finished the session with an
+  unlocked mouse. The lock is now requested on **every** frame that carries a `pointerdown`
+  while the lock is not held; the only guard is a request already in flight. A refusal is logged and
+  dropped, exactly as before.
+  
+  **An unlocked mouse no longer turns the view.** While `lockPointerOnClick` is on and the lock is not
+  held, a `Look` reading whose `InputAction.activeDevice` is `Mouse` or `Pointer` is ignored. Before,
+  the view spun whenever the cursor crossed the canvas — on its way to a menu button, say — and stopped
+  dead when the cursor left the frame. Gamepad, touch, and virtual sticks are never gated: they have no
+  cursor to lose. `lockPointerOnClick: false` keeps unconditional mouse look for drag-to-look designs.
+  
+  **A stick is a rate, a pointer is a displacement.** Both rigs did `yaw += look.x * sensitivity` for
+  every device. That is right for a pointer delta, which is this frame's motion, and wrong for a stick,
+  whose value is a deflection: at 120 Hz the stick turned twice as fast as at 60 Hz, and games papered
+  over it with a `scale(18)` processor. A gamepad or virtual reading is now multiplied by the new
+  `stickLookSpeed` (degrees per second at full deflection, default 180) and the frame delta, so the
+  same push turns through the same angle in the same second at any frame rate, and slow motion slows
+  the look with everything else. `sensitivity` keeps its meaning for pointer readings — degrees per unit,
+  which with `@ignifx/input`'s CSS-pixel deltas is degrees per CSS pixel, so 0.08–0.15 suits most mice
+  on every display and at every render scale.
+  
+  **Up is up on every device.** A screen's `movementY` grows downward and a stick's `y` grows upward,
+  and both rigs subtracted `look.y` from their pitch regardless — so one `invertY` could only ever suit
+  one device family, and a first-person mouse looked *down* when it was pushed forward. The pitch axis
+  is normalised where the device is known: `Mouse`, `Pointer`, and `Touch` readings are negated, gamepad
+  and virtual are not, and the rigs apply their own sign and `invertY` on top as before. Moving the
+  mouse forward and pushing a stick up now both look up in first person, and both lower the boom and
+  aim the camera up in third person; `invertY` flips every device together.
+  
+  `ThirdPersonCamera` also gains `lockPointerOnClick`, defaulting to **`false`**: a rig that orbits on a
+  held mouse button needs its cursor, so nothing changes for an existing third-person game until it
+  opts in to the console-style "click to capture, Escape to release" behaviour.
+  
+  Public API change: `FirstPersonController.stickLookSpeed`, `ThirdPersonCamera.stickLookSpeed`, and
+  `ThirdPersonCamera.lockPointerOnClick` are new schema fields. No field was removed or renamed. Two
+  behaviour changes need a look from any game that ships a look binding: drop the `scale(...)`
+  processors from stick look bindings, which double-count against `stickLookSpeed`, keeping the
+  `deadzone(...)`; and drop any `scale(1, -1)` that existed to line a stick up with the mouse, because
+  the rigs agree on which way is up now — reach for `invertY` instead.
+- 6a39fae: `shapeCast` can sweep past one body, and the third-person boom and step probe no longer report the character's own capsule
+  
+  Lite's `ShapeCastQuery` carries no collision masks — unlike `physicsRaycast` — so a shape sweep
+  cannot be filtered by layer inside Havok; `layerMask` only ever decided which hit was *attributed*
+  an entity, and a body outside the mask still stopped the sweep, reported with `entity: null`. Two
+  callers in `@ignifx/3d` were sweeping from inside the character's own capsule and were stopped by it
+  at fraction zero every time:
+  
+  - `ThirdPersonCamera` sweeps from its shoulder pivot, which sits inside the capsule, out along the
+    boom. For every yaw whose boom crossed the capsule the sweep hit it immediately, `currentDistance`
+    collapsed to `0` and the camera sat inside the character's head — measured on 2026-09-08 in the
+    third-person template at every yaw from 30° to 180° at the spawn, with no wall anywhere near.
+    `collisionLayers: ["Level", "Prop"]` could not prevent it, because the mask never reached the sweep.
+  - `ThirdPersonController`'s step probe sweeps a sphere forward from the character's feet; both of its
+    sweeps found the capsule first, so `stepHeight` never lifted anything.
+  
+  `ShapeCastOptions` — `QueryOptions` plus `ignore?: Entity | null` — names the one body the sweep
+  passes through, resolved to its Havok body whether the entity is a `Rigidbody`, a collider-only
+  static, or a `CharacterController` (whose capsule body Lite exposes through `getBody()`). The camera
+  rig ignores its `target`; the step probe ignores its own entity. A masked-out body other than the
+  ignored one still shortens the boom, which for scenery is the point and is now said so on
+  `collisionLayers`.
+  
+  What a game author sees: a third-person camera that holds its distance through a full orbit and a
+  `stepHeight` that climbs steps; and, for their own queries, a way to sweep out of a body they are
+  standing in.
+  
+  Public API change: `ShapeCastOptions` is new and `PhysicsService.shapeCast` takes it in place of
+  `QueryOptions` (a widening — every existing call compiles). Nothing was removed or renamed.
+- ef054ec: `ThirdPersonCamera` no longer rolls the horizon when the mouse moves sideways
+  
+  The rig built its rotation with one `Quat.fromEulerDegrees(pitch, yaw, 0)` call. That helper composes
+  in intrinsic XYZ order, so the boom was pitched first and then yawed about the *tilted* axis: with
+  any pitch at all — and the template starts twelve degrees down — a horizontal mouse motion tilted the
+  camera rather than turning it, and the camera rose and fell as it went round (measured 2026-09-08:
+  at 15 degrees of pitch its height followed `cos(yaw)`).
+  
+  The rotation is now `Ry(yaw) * Rx(pitch)`: yaw about the world's up, then pitch about the camera's
+  own right, which is the one order in which looking sideways is a turn about the vertical. The
+  starting angles are read off the entity's forward vector at `awake` instead of its Euler angles, so
+  an authored downward tilt seeds the same pitch whatever Euler order wrote it.
+  
+  What a game author sees: a third-person camera whose horizon stays level and whose height stays put
+  through a full orbit, at every pitch.
+  
+  Public API change: none.
+- Updated dependencies [21a4ba7]
+- Updated dependencies [6a39fae]
+- Updated dependencies [388b0f6]
+- Updated dependencies [6a39fae]
+  - @ignifx/input@0.2.1
+  - @ignifx/physics@0.2.1
+  - @ignifx/core@0.2.1
+
 ## 0.2.0
 
 ### Patch Changes
diff --git a/packages/3d/package.json b/packages/3d/package.json
index 9fa93a9..1a5957f 100644
--- a/packages/3d/package.json
+++ b/packages/3d/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@ignifx/3d",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "description": "ignifx 3D toolkit: character and camera rigs, Animator state machine, navigation.",
   "keywords": [
     "ignifx",
diff --git a/packages/3d/skills/3d/SKILL.md b/packages/3d/skills/3d/SKILL.md
index 767f063..26038e2 100644
--- a/packages/3d/skills/3d/SKILL.md
+++ b/packages/3d/skills/3d/SKILL.md
@@ -3,7 +3,7 @@ name: 3d
 description: Builds 3D games in ignifx with @ignifx/3d: third-person and first-person character controllers and camera rigs, the Animator state machine with blend trees and animation events, navigation meshes and agents, LOD groups, and billboards. Use when adding or editing 3D character movement, camera rigs, animation state machines, or navigation in an ignifx project, or when the user mentions @ignifx/3d, Animator, ThirdPersonController, or NavMeshAgent.
 license: Apache-2.0
 metadata:
-  ignifx-version: "0.2.0"
+  ignifx-version: "0.2.1"
 ---
 
 # @ignifx/3d
diff --git a/packages/audio/CHANGELOG.md b/packages/audio/CHANGELOG.md
index d97fa59..d5e58b7 100644
--- a/packages/audio/CHANGELOG.md
+++ b/packages/audio/CHANGELOG.md
@@ -1,5 +1,12 @@
 # @ignifx/audio
 
+## 0.2.1
+
+### Patch Changes
+
+- Updated dependencies [388b0f6]
+  - @ignifx/core@0.2.1
+
 ## 0.2.0
 
 ### Patch Changes
diff --git a/packages/audio/package.json b/packages/audio/package.json
index e513064..69f88cb 100644
--- a/packages/audio/package.json
+++ b/packages/audio/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@ignifx/audio",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "description": "ignifx audio: bus tree, AudioSource, AudioListener, AudioClip assets, unlock handling.",
   "keywords": [
     "ignifx",
diff --git a/packages/audio/skills/audio/SKILL.md b/packages/audio/skills/audio/SKILL.md
index 0d10751..6a8d355 100644
--- a/packages/audio/skills/audio/SKILL.md
+++ b/packages/audio/skills/audio/SKILL.md
@@ -3,7 +3,7 @@ name: audio
 description: Adds sound and music to an ignifx game with @ignifx/audio: the bus tree, AudioSource and AudioListener components, static and streaming AudioClip assets, spatial audio, a music player, and the browser unlock flow. Use when adding or editing sound effects, music, audio buses, mixing, or spatial audio in an ignifx project, or when the user mentions @ignifx/audio, AudioSource, AudioListener, or audio buses.
 license: Apache-2.0
 metadata:
-  ignifx-version: "0.2.0"
+  ignifx-version: "0.2.1"
 ---
 
 # @ignifx/audio
diff --git a/packages/cli/CHANGELOG.md b/packages/cli/CHANGELOG.md
index da0a999..873dc96 100644
--- a/packages/cli/CHANGELOG.md
+++ b/packages/cli/CHANGELOG.md
@@ -1,5 +1,9 @@
 # @ignifx/cli
 
+## 0.2.1
+
+No changes in this release.
+
 ## 0.2.0
 
 ### Patch Changes
diff --git a/packages/cli/package.json b/packages/cli/package.json
index 255f7c3..d89fbfb 100644
--- a/packages/cli/package.json
+++ b/packages/cli/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@ignifx/cli",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "description": "create-ignifx: scaffolds an ignifx project by copying a template directory.",
   "keywords": [
     "cli",
diff --git a/packages/core/CHANGELOG.md b/packages/core/CHANGELOG.md
index 8c25f5c..30fa6a9 100644
--- a/packages/core/CHANGELOG.md
+++ b/packages/core/CHANGELOG.md
@@ -1,5 +1,37 @@
 # @ignifx/core
 
+## 0.2.1
+
+### Patch Changes
+
+- 388b0f6: `PostProcessStack` fields are live: a slider bound to `bloom.threshold` now changes the picture
+  
+  The stack built its chain once, the first time any effect was enabled, and every `sync` after that
+  only flipped the chain's `executionEnabled` to match the component. The bloom and SMAA records were
+  read at that one moment and never again, so `post.bloom.threshold = 0.4` on a running game did
+  nothing — the website's bloom example had four sliders and none of them moved the frame — and
+  `post.bloom.enabled = false` on a one-effect chain left bloom running, because the chain's identity
+  was checked only while no chain existed yet.
+  
+  Lite's `BloomPostProcessTask` exposes `weight`, `kernel`, `threshold` and `exposure` as writable
+  fields and `updateUniforms()` re-uploads every sub-pass from them; `SmaaPostProcessTask` documents
+  the same for `threshold`, `maxSearchSteps`, `diagonalDetection` and `cornerDetection` (verified
+  against `@babylonjs/lite@1.27.0`, `index.d.ts` 1287 and 11622). The chain now keeps a typed handle
+  to each of those tasks and, once per frame, uploads whatever changed since the last upload — a frame
+  in which nothing moved uploads nothing. The one tuning Lite fixes at creation is bloom's
+  `bloomScale`, which sizes the blur targets, so `bloom.scale` joins "which effects, in which order"
+  in the chain's identity: a change to any of them disposes the old chain and records a new one. Lite
+  cannot remove a task from a frame graph, so the old tasks stay in it, disabled and with their GPU
+  resources freed, at one branch per frame each — toggling an effect's `enabled` in a settings menu
+  costs a rebuild per click, whereas toggling the whole component's `enabled` keeps the chain and
+  skips it, which is what the templates' settings screens do.
+  
+  What a game author sees: an inspector edit, a settings slider or a script write to any bloom or SMAA
+  field takes effect on the next frame, and turning a single effect off actually turns it off.
+  
+  Public API change: none. `PostProcessChain.applySettings` and the two adapter functions it calls are
+  `@internal`.
+
 ## 0.2.0
 
 ### Minor Changes
diff --git a/packages/core/package.json b/packages/core/package.json
index 99c2eea..9957487 100644
--- a/packages/core/package.json
+++ b/packages/core/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@ignifx/core",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "description": "ignifx core: app, world, entities, components, scripts, and the Babylon Lite adapter boundary.",
   "homepage": "https://ignifx.com",
   "license": "Apache-2.0",
diff --git a/packages/devtools/CHANGELOG.md b/packages/devtools/CHANGELOG.md
index 31c9d2b..d9d239a 100644
--- a/packages/devtools/CHANGELOG.md
+++ b/packages/devtools/CHANGELOG.md
@@ -1,5 +1,21 @@
 # @ignifx/devtools
 
+## 0.2.1
+
+### Patch Changes
+
+- Updated dependencies [21a4ba7]
+- Updated dependencies [6a39fae]
+- Updated dependencies [6a39fae]
+- Updated dependencies [388b0f6]
+- Updated dependencies [6a39fae]
+  - @ignifx/input@0.2.1
+  - @ignifx/physics-2d@0.2.1
+  - @ignifx/physics@0.2.1
+  - @ignifx/core@0.2.1
+  - @ignifx/ui@0.2.1
+  - @ignifx/audio@0.2.1
+
 ## 0.2.0
 
 ### Patch Changes
diff --git a/packages/devtools/package.json b/packages/devtools/package.json
index f6602df..eddb4f6 100644
--- a/packages/devtools/package.json
+++ b/packages/devtools/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@ignifx/devtools",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "description": "ignifx devtools: stats overlay, scene tree and component inspector, physics debug view, script hot reload.",
   "keywords": [
     "ignifx",
diff --git a/packages/devtools/skills/devtools/SKILL.md b/packages/devtools/skills/devtools/SKILL.md
index 8426718..4b581f9 100644
--- a/packages/devtools/skills/devtools/SKILL.md
+++ b/packages/devtools/skills/devtools/SKILL.md
@@ -3,7 +3,7 @@ name: devtools
 description: Inspects and debugs a running ignifx game with @ignifx/devtools: the stats and diagnostics overlay, the scene tree browser, the schema-driven component inspector, the physics debug view, the console, and the script hot-reload reports. Use when diagnosing frame time, entity counts, component values, asset refcounts, or physics behaviour in an ignifx project, or when the user mentions @ignifx/devtools, the stats overlay, the inspector, or app.devtools.
 license: Apache-2.0
 metadata:
-  ignifx-version: "0.2.0"
+  ignifx-version: "0.2.1"
 ---
 
 # @ignifx/devtools
diff --git a/packages/electron/CHANGELOG.md b/packages/electron/CHANGELOG.md
index 81459b1..ac0a32d 100644
--- a/packages/electron/CHANGELOG.md
+++ b/packages/electron/CHANGELOG.md
@@ -1,5 +1,12 @@
 # @ignifx/electron
 
+## 0.2.1
+
+### Patch Changes
+
+- Updated dependencies [388b0f6]
+  - @ignifx/core@0.2.1
+
 ## 0.2.0
 
 ### Patch Changes
diff --git a/packages/electron/package.json b/packages/electron/package.json
index cb7f2b8..a8c3221 100644
--- a/packages/electron/package.json
+++ b/packages/electron/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@ignifx/electron",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "description": "ignifx Electron support: main-process window factory with WebGPU flags, typed preload bridge, file-system storage.",
   "keywords": [
     "ignifx",
diff --git a/packages/electron/skills/electron/SKILL.md b/packages/electron/skills/electron/SKILL.md
index 8d69755..8342636 100644
--- a/packages/electron/skills/electron/SKILL.md
+++ b/packages/electron/skills/electron/SKILL.md
@@ -3,7 +3,7 @@ name: electron
 description: Ships an ignifx game as an Electron desktop app with @ignifx/electron: the main-process window factory that enables WebGPU, a typed and sandboxed preload bridge, the ignifx:// asset protocol, the file-system storage backend, and the renderer-side extension that exposes app.desktop. Use when packaging, configuring, or debugging an ignifx desktop build, or when the user mentions @ignifx/electron, createGameWindow, the preload bridge, or desktop templates.
 license: Apache-2.0
 metadata:
-  ignifx-version: "0.2.0"
+  ignifx-version: "0.2.1"
 ---
 
 # @ignifx/electron
diff --git a/packages/ignifx/CHANGELOG.md b/packages/ignifx/CHANGELOG.md
index 6d27a10..77e1708 100644
--- a/packages/ignifx/CHANGELOG.md
+++ b/packages/ignifx/CHANGELOG.md
@@ -1,5 +1,27 @@
 # ignifx
 
+## 0.2.1
+
+### Patch Changes
+
+- Updated dependencies [7adf987]
+- Updated dependencies [21a4ba7]
+- Updated dependencies [6a39fae]
+- Updated dependencies [6a39fae]
+- Updated dependencies [388b0f6]
+- Updated dependencies [6a39fae]
+- Updated dependencies [ef054ec]
+  - @ignifx/3d@0.2.1
+  - @ignifx/input@0.2.1
+  - @ignifx/physics-2d@0.2.1
+  - @ignifx/physics@0.2.1
+  - @ignifx/core@0.2.1
+  - @ignifx/devtools@0.2.1
+  - @ignifx/electron@0.2.1
+  - @ignifx/ui@0.2.1
+  - @ignifx/2d@0.2.1
+  - @ignifx/audio@0.2.1
+
 ## 0.2.0
 
 ### Patch Changes
diff --git a/packages/ignifx/package.json b/packages/ignifx/package.json
index ba549d0..1fbc27b 100644
--- a/packages/ignifx/package.json
+++ b/packages/ignifx/package.json
@@ -1,6 +1,6 @@
 {
   "name": "ignifx",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "description": "ignifx umbrella package: re-exports @ignifx/core and the standard extensions, and ships the ignifx Agent Skill.",
   "keywords": [
     "ignifx"
diff --git a/packages/input/CHANGELOG.md b/packages/input/CHANGELOG.md
index 0f05dc5..1ece38d 100644
--- a/packages/input/CHANGELOG.md
+++ b/packages/input/CHANGELOG.md
@@ -1,5 +1,55 @@
 # @ignifx/input
 
+## 0.2.1
+
+### Patch Changes
+
+- 21a4ba7: Pointer deltas are CSS pixels, the canvas wheel no longer scrolls the page, `InputAction.activeDevice`, and pointer lock asks for raw mouse motion
+  
+  Four fixes to the things a look control is built out of, all found while chasing "the camera on the
+  third-person example does not behave correctly" and "scroll interferes with page scrolling".
+  
+  **The wheel is taken non-passively.** The canvas `wheel` listener was registered `{ passive: true }`,
+  which forbids `preventDefault`, so a wheel over a running game zoomed the camera _and_ scrolled the
+  page underneath it — obvious on ignifx.com, where the examples live in an `<iframe>` and the wheel
+  took the article with it. The listener is now non-passive and prevents the default on every event it
+  queues. The wheel is still read from the canvas alone, so a wheel over the page's own chrome is
+  untouched, and the queued entry is unchanged.
+  
+  **Pointer deltas are CSS pixels; positions stay backing-store pixels.** `<Mouse>/delta`,
+  `<Pointer>/delta`, `<Touch>/…/delta` and `event.deltaX`/`deltaY` were multiplied by
+  `canvas.width / rect.width`, the same scale positions need. A delta is hand motion, not a place on
+  the render target: the scale doubled every look sensitivity on a device-pixel-ratio-2 display and
+  moved it again whenever a settings screen changed `renderer.resolutionScale`. Deltas are now the
+  browser's raw `movementX`/`movementY`, and for the pointer types that leave those at zero (touch,
+  some pens) the DOM adapter derives the motion from that pointer's own successive `clientX`/`clientY`
+  — in CSS pixels, never from the queued position. `DeviceWriter` derives nothing at all now, so
+  `simulateEvent` reports exactly the delta a test states. Positions are unchanged, so
+  `renderer.pickAsync(pointer.position)` and `Camera.screenToRay` are still exact at every ratio.
+  A game author sees one number to tune: a mouse look sensitivity in degrees per CSS pixel, around
+  0.08–0.15, the same on every display.
+  
+  **`InputAction.activeDevice`** names the device family behind the binding whose magnitude won the
+  frame, and `null` when the action is at rest or disabled — stable for the frame like every other
+  reading. One `Look` action bound to both a mouse and a stick carries two different quantities, and
+  this is what lets a rig tell them apart: `@ignifx/3d` uses it to ignore mouse look until the pointer
+  is locked and to read a stick as a rate. A composite reports the device of its first part, which is
+  the only sensible answer for a `2DVector` whose four parts are one device.
+  
+  **`PointerLock.request()` asks for `unadjustedMovement: true`** before it asks plainly, falling back
+  when the browser rejects the option by throwing or by rejecting the returned promise. That is raw
+  mouse motion with the desktop's pointer-acceleration curve removed, which is what a first-person look
+  wants — with acceleration on, a fast flick turns further than a slow one over the same desk distance,
+  which is most of what players describe as a jumpy look. Settle semantics are unchanged: `true` on
+  `pointerlockchange`, `false` on `pointerlockerror`, `IGX-0809` on a headless app.
+  
+  Public API change: `InputAction.activeDevice: DeviceKind | null` is new. No signature changed, but
+  the **meaning** of `<Mouse>/delta`, `<Pointer>/delta` and `<Touch>/…/delta` did: they are CSS pixels
+  now, so a project that tuned its sensitivity on a retina display re-tunes it once (`invert` and
+  `scale(...)` processors still apply as before).
+- Updated dependencies [388b0f6]
+  - @ignifx/core@0.2.1
+
 ## 0.2.0
 
 ### Patch Changes
diff --git a/packages/input/package.json b/packages/input/package.json
index 2417ebc..7876b9a 100644
--- a/packages/input/package.json
+++ b/packages/input/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@ignifx/input",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "description": "ignifx input: action maps, bindings, keyboard/mouse/pointer/gamepad/touch devices, pointer lock, rebinding.",
   "keywords": [
     "ignifx",
diff --git a/packages/input/skills/input/SKILL.md b/packages/input/skills/input/SKILL.md
index c5e3754..3d56909 100644
--- a/packages/input/skills/input/SKILL.md
+++ b/packages/input/skills/input/SKILL.md
@@ -3,7 +3,7 @@ name: input
 description: Wires player input into an ignifx game with @ignifx/input: action maps, bindings, composites and processors, control schemes, keyboard, mouse, pointer, gamepad and touch devices, pointer lock, cursor handling, .input.json action assets, and runtime rebinding. Use when adding or editing input actions, bindings, devices, or a rebinding screen in an ignifx project, or when the user mentions @ignifx/input, PlayerInput, action maps, or input.json.
 license: Apache-2.0
 metadata:
-  ignifx-version: "0.2.0"
+  ignifx-version: "0.2.1"
 ---
 
 # @ignifx/input
diff --git a/packages/physics-2d/CHANGELOG.md b/packages/physics-2d/CHANGELOG.md
index ec6d4ce..0e1e9b9 100644
--- a/packages/physics-2d/CHANGELOG.md
+++ b/packages/physics-2d/CHANGELOG.md
@@ -1,5 +1,47 @@
 # @ignifx/physics-2d
 
+## 0.2.1
+
+### Patch Changes
+
+- 6a39fae: A `CharacterController2D` walks through triggers instead of bouncing off them, and the display pose is written before `update` so follow cameras stop juddering
+  
+  **Triggers were walls.** Rapier's `KinematicCharacterController.computeColliderMovement` takes
+  `filterFlags` as its third argument, and the adapter passed `undefined`, which leaves sensors in the
+  obstacle set. Measured on 2026-09-08 against `@dimforge/rapier2d-compat@0.20.0` (macOS arm64,
+  Node 24): a kinematic box driven by the controller towards a static sensor ball stops dead at the
+  sensor's surface — `x = 0.49` for a sensor at `x = 1` with radius 0.3, a 0.2 half-width character and
+  a 0.01 offset — and because it never overlaps, `drainCollisionEvents` reports nothing at all. With
+  `QueryFilterFlags.EXCLUDE_SENSORS` the same character reaches `x = 3.0` and the queue reports the
+  `started`/`stopped` pair. Every controller move now passes that flag.
+  
+  What a game author sees: a collectible finally works. The side-scroller template's coins are a
+  `CircleCollider2D { isTrigger: true }` on an entity with no rigidbody, and the player is a
+  `CharacterController2D` — so every coin was an invisible bump the player stopped against and
+  `onTriggerEnter` never fired. The same was true of the top-down template's shrine pads and of any
+  trigger zone a controller-driven character is meant to enter. The flip side is intended: a sensor no
+  longer appears in `CharacterController2D.onCollided`, because a trigger is not an obstacle. Use
+  `onTriggerEnter`/`onTriggerExit` for pickups and zones and `onCollided` for the walls and floors the
+  character actually pushed against.
+  
+  **The display pose is written at the top of `Update`, not in `PreRender`.** Poses are still
+  snapshotted on the fixed step and interpolated with `time.fixedStepAlpha`, but the system that writes
+  `lerp(prev, cur, alpha)` moved from `Systems(PreRender, −500)` to `Systems(Update, −900)`, which runs
+  straight after the fixed loop and before `scripts.update`. `Camera2DFollow` and every hand-written
+  follow camera run in `update`/`lateUpdate`, so they used to frame the character where the last fixed
+  step left it while the renderer drew it interpolated: up to one fixed step of relative motion — about
+  0.1 m at sprint speed — of judder every frame, and with the pixel-perfect camera the two poses are
+  quantised independently, so the sprite visibly shook while running. Now scripts, animation, camera
+  rigs and the render sync all read the pose the frame presents, which is Unity's model. `fixedUpdate`
+  and Rapier are unaffected: the restore system at `FixedUpdate −100` still runs before
+  `scripts.fixedUpdate`, so the simulation only ever sees authoritative poses, and a kinematic body
+  moved by writing its transform behaves exactly as before.
+  
+  Public API change: none. The order constants and both systems are `@internal`.
+- Updated dependencies [388b0f6]
+  - @ignifx/core@0.2.1
+  - @ignifx/2d@0.2.1
+
 ## 0.2.0
 
 ### Patch Changes
diff --git a/packages/physics-2d/package.json b/packages/physics-2d/package.json
index 8ff60ff..28de9df 100644
--- a/packages/physics-2d/package.json
+++ b/packages/physics-2d/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@ignifx/physics-2d",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "description": "ignifx 2D physics: Rigidbody2D, 2D colliders, CharacterController2D, queries.",
   "keywords": [
     "ignifx",
diff --git a/packages/physics-2d/skills/physics-2d/SKILL.md b/packages/physics-2d/skills/physics-2d/SKILL.md
index e34083f..fb87471 100644
--- a/packages/physics-2d/skills/physics-2d/SKILL.md
+++ b/packages/physics-2d/skills/physics-2d/SKILL.md
@@ -3,7 +3,7 @@ name: physics-2d
 description: Adds 2D physics to an ignifx game with @ignifx/physics-2d: Rapier 2D simulation on the fixed loop, Rigidbody2D, box/circle/capsule/polygon/edge/tilemap colliders, physics materials, 2D triggers, CharacterController2D with slopes, autostep, snap-to-ground and one-way platforms, 2D raycasts and shape queries, the collision layer matrix, and render interpolation. Use when adding or editing 2D physics bodies, 2D colliders, platformer movement, 2D triggers, or 2D queries in an ignifx project, or when the user mentions @ignifx/physics-2d, Rigidbody2D, Rapier, or CharacterController2D.
 license: Apache-2.0
 metadata:
-  ignifx-version: "0.2.0"
+  ignifx-version: "0.2.1"
 ---
 
 # @ignifx/physics-2d
diff --git a/packages/physics/CHANGELOG.md b/packages/physics/CHANGELOG.md
index da6cbeb..ab55795 100644
--- a/packages/physics/CHANGELOG.md
+++ b/packages/physics/CHANGELOG.md
@@ -1,5 +1,65 @@
 # @ignifx/physics
 
+## 0.2.1
+
+### Patch Changes
+
+- 6a39fae: The interpolated display pose is written before `update`, so camera rigs and scripts see the pose the frame draws
+  
+  Poses are still snapshotted on the fixed step and interpolated with `time.fixedStepAlpha`, but the
+  system that writes `lerp(prev, cur, alpha)` into a `Rigidbody`'s or `CharacterController`'s node
+  moved from `Systems(PreRender, −500)` to `Systems(Update, −900)` — straight after the fixed loop and
+  lifecycle flush B, in front of `scripts.update`.
+  
+  Why: `ThirdPersonCamera`, `FirstPersonController`, bone attachments and every hand-written follow camera
+  run in `update`/`lateUpdate`, which used to be *before* the display pose existed. They framed the
+  character where the last fixed step left it while the renderer drew it at `lerp(prev, cur, alpha)`,
+  so at any refresh rate the character juddered against the camera by up to one fixed step of motion —
+  about 0.1 m at sprint speed, every frame. Writing the pose at the top of `Update` means `update`,
+  `lateUpdate`, animation, camera rigs and the render sync all read the same pose the frame presents.
+  This is Unity's model.
+  
+  What a game author sees: a smooth third- or first-person camera, and `transform.position` read from
+  `update`/`lateUpdate` now returning the interpolated pose rather than the last fixed one. The
+  simulation is unchanged: the restore system at `FixedUpdate −100` still runs before
+  `scripts.fixedUpdate`, so `fixedUpdate` and Havok only ever see authoritative poses, and a kinematic
+  body moved by writing its transform behaves exactly as before — the restore already overwrote such a
+  write before the step read it. A system that must read an authoritative pose outside the fixed loop
+  registers at `Phase.Update` with an order below `−900`.
+  
+  Public API change: none. The order constant and the interpolation system are `@internal`.
+- 6a39fae: `shapeCast` can sweep past one body, and the third-person boom and step probe no longer report the character's own capsule
+  
+  Lite's `ShapeCastQuery` carries no collision masks — unlike `physicsRaycast` — so a shape sweep
+  cannot be filtered by layer inside Havok; `layerMask` only ever decided which hit was *attributed*
+  an entity, and a body outside the mask still stopped the sweep, reported with `entity: null`. Two
+  callers in `@ignifx/3d` were sweeping from inside the character's own capsule and were stopped by it
+  at fraction zero every time:
+  
+  - `ThirdPersonCamera` sweeps from its shoulder pivot, which sits inside the capsule, out along the
+    boom. For every yaw whose boom crossed the capsule the sweep hit it immediately, `currentDistance`
+    collapsed to `0` and the camera sat inside the character's head — measured on 2026-09-08 in the
+    third-person template at every yaw from 30° to 180° at the spawn, with no wall anywhere near.
+    `collisionLayers: ["Level", "Prop"]` could not prevent it, because the mask never reached the sweep.
+  - `ThirdPersonController`'s step probe sweeps a sphere forward from the character's feet; both of its
+    sweeps found the capsule first, so `stepHeight` never lifted anything.
+  
+  `ShapeCastOptions` — `QueryOptions` plus `ignore?: Entity | null` — names the one body the sweep
+  passes through, resolved to its Havok body whether the entity is a `Rigidbody`, a collider-only
+  static, or a `CharacterController` (whose capsule body Lite exposes through `getBody()`). The camera
+  rig ignores its `target`; the step probe ignores its own entity. A masked-out body other than the
+  ignored one still shortens the boom, which for scenery is the point and is now said so on
+  `collisionLayers`.
+  
+  What a game author sees: a third-person camera that holds its distance through a full orbit and a
+  `stepHeight` that climbs steps; and, for their own queries, a way to sweep out of a body they are
+  standing in.
+  
+  Public API change: `ShapeCastOptions` is new and `PhysicsService.shapeCast` takes it in place of
+  `QueryOptions` (a widening — every existing call compiles). Nothing was removed or renamed.
+- Updated dependencies [388b0f6]
+  - @ignifx/core@0.2.1
+
 ## 0.2.0
 
 ### Patch Changes
diff --git a/packages/physics/package.json b/packages/physics/package.json
index b15ae02..8b5a5a1 100644
--- a/packages/physics/package.json
+++ b/packages/physics/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@ignifx/physics",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "description": "ignifx 3D physics on Havok through Babylon Lite: rigidbodies, colliders, triggers, character controller, queries.",
   "keywords": [
     "ignifx",
diff --git a/packages/physics/skills/physics/SKILL.md b/packages/physics/skills/physics/SKILL.md
index 7d1ffac..000fa56 100644
--- a/packages/physics/skills/physics/SKILL.md
+++ b/packages/physics/skills/physics/SKILL.md
@@ -3,7 +3,7 @@ name: physics
 description: Adds 3D physics to an ignifx game with @ignifx/physics: Havok simulation on a separate headless scene, Rigidbody, box/sphere/capsule/mesh colliders, physics materials, triggers, CharacterController, raycasts and shape queries, the collision layer matrix, and render interpolation. Use when adding or editing 3D physics bodies, colliders, triggers, character movement, or physics queries in an ignifx project, or when the user mentions @ignifx/physics, Rigidbody, Havok, or collision layers.
 license: Apache-2.0
 metadata:
-  ignifx-version: "0.2.0"
+  ignifx-version: "0.2.1"
 ---
 
 # @ignifx/physics
diff --git a/packages/ui/CHANGELOG.md b/packages/ui/CHANGELOG.md
index da80488..a1f1516 100644
--- a/packages/ui/CHANGELOG.md
+++ b/packages/ui/CHANGELOG.md
@@ -1,5 +1,14 @@
 # @ignifx/ui
 
+## 0.2.1
+
+### Patch Changes
+
+- Updated dependencies [21a4ba7]
+- Updated dependencies [388b0f6]
+  - @ignifx/input@0.2.1
+  - @ignifx/core@0.2.1
+
 ## 0.2.0
 
 ### Patch Changes
diff --git a/packages/ui/package.json b/packages/ui/package.json
index 4b5f655..d54b304 100644
--- a/packages/ui/package.json
+++ b/packages/ui/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@ignifx/ui",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "description": "ignifx UI: DOM overlay host, focus routing, world and HUD text.",
   "keywords": [
     "ignifx",
diff --git a/packages/ui/skills/ui/SKILL.md b/packages/ui/skills/ui/SKILL.md
index f944147..fbdc834 100644
--- a/packages/ui/skills/ui/SKILL.md
+++ b/packages/ui/skills/ui/SKILL.md
@@ -3,7 +3,7 @@ name: ui
 description: Builds game UI in ignifx with @ignifx/ui: the DOM overlay host and layers, scaling modes, input focus routing, world-space anchors, world and HUD text on Babylon Lite's text renderer, menus and menu stacks, virtual joysticks and buttons for touch, dialogs, toasts, loading screens, and localization. Use when adding or editing menus, title/pause/settings screens, HUDs, on-screen text, touch controls, or overlay UI in an ignifx project, or when the user mentions @ignifx/ui, Menu, MenuStack, HudText, WorldAnchor, VirtualJoystick, or app.i18n.
 license: Apache-2.0
 metadata:
-  ignifx-version: "0.2.0"
+  ignifx-version: "0.2.1"
 ---
 
 # @ignifx/ui
diff --git a/packages/vite-plugin/CHANGELOG.md b/packages/vite-plugin/CHANGELOG.md
index 9ed417b..ea52b97 100644
--- a/packages/vite-plugin/CHANGELOG.md
+++ b/packages/vite-plugin/CHANGELOG.md
@@ -1,5 +1,12 @@
 # @ignifx/vite-plugin
 
+## 0.2.1
+
+### Patch Changes
+
+- Updated dependencies [388b0f6]
+  - @ignifx/core@0.2.1
+
 ## 0.2.0
 
 ### Patch Changes
diff --git a/packages/vite-plugin/package.json b/packages/vite-plugin/package.json
index c984910..5f9e96c 100644
--- a/packages/vite-plugin/package.json
+++ b/packages/vite-plugin/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@ignifx/vite-plugin",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "description": "ignifx Vite plugin: asset manifest generation, scene/prefab JSON validation, WASM/asset handling, HMR hooks.",
   "keywords": [
     "ignifx"
diff --git a/skills/ignifx/SKILL.md b/skills/ignifx/SKILL.md
index af0fb0c..92ce6ac 100644
--- a/skills/ignifx/SKILL.md
+++ b/skills/ignifx/SKILL.md
@@ -3,7 +3,7 @@ name: ignifx
 description: Builds 2D and 3D web games with the ignifx TypeScript game engine (WebGPU-only, Babylon Lite based, browser and Electron). Use when creating or editing ignifx apps, entities, scripts, scenes, prefabs, assets, input actions, physics, audio, sprites, or tilemaps, or when the user mentions ignifx, @ignifx packages, createApp, Script lifecycle, or ignifx scene JSON.
 license: Apache-2.0
 metadata:
-  ignifx-version: "0.2.0"
+  ignifx-version: "0.2.1"
   babylon-lite-version: "1.27.0"
 ---
 
diff --git a/skills/ignifx/references/formats/ignifx.schemas.json b/skills/ignifx/references/formats/ignifx.schemas.json
index 807ed9f..e54bf08 100644
--- a/skills/ignifx/references/formats/ignifx.schemas.json
+++ b/skills/ignifx/references/formats/ignifx.schemas.json
@@ -1,6 +1,6 @@
 {
   "generatedBy": "pnpm docs:schemas",
-  "ignifxVersion": "0.2.0",
+  "ignifxVersion": "0.2.1",
   "schemas": {
     "ignifx/Animator": {
       "title": "Animator",