From 470779dee55f7aa9b7b84fdf0e791532d70e833b Mon Sep 17 00:00:00 2001 From: Meta Vens Date: Sun, 31 May 2026 22:09:23 +0100 Subject: [PATCH] Record Nightwing Move HID access --- docs/move-controller-stream.md | 8 +++++--- state/evidence.jsonl | 1 + 2 files changed, 6 insertions(+), 3 deletions(-) diff --git a/docs/move-controller-stream.md b/docs/move-controller-stream.md index b3225c4..1dd7920 100644 --- a/docs/move-controller-stream.md +++ b/docs/move-controller-stream.md @@ -187,6 +187,8 @@ see the selected grid alongside half-time/double-time alternatives. The non-dry run targets the two wireless Nightwing Moves by default: `00:07:04:a6:be:5f` on `/dev/hidraw2` and `00:06:f5:23:e2:d1` on -`/dev/hidraw3`. Current BlueZ permissions expose those Bluetooth hidraw nodes -as root-only, so multi-Move LED actuation needs a udev rule or privileged -helper before the non-root SSH writer can drive both spheres. +`/dev/hidraw3`. Nightwing now carries `/etc/udev/rules.d/70-move.rules`, which +sets Bluetooth PS Move hidraw nodes to `root:input 0660`. The `metacrat` user +is in `input`, so the non-root SSH writer can drive both spheres. Root SSH is +available as the short local alias `nwroot` for maintenance only; the hot LED +path should stay non-root. diff --git a/state/evidence.jsonl b/state/evidence.jsonl index 82f8a32..c162271 100644 --- a/state/evidence.jsonl +++ b/state/evidence.jsonl @@ -282,5 +282,6 @@ {"ts": "2026-05-31T21:35:10+01:00", "type": "verification", "status": "partial", "note": "Second PS Move was visible on Nightwing USB as Sony 054c:03d5 at /dev/hidraw1. A Linux hidraw feature-report write set its host address to Nightwing Bluetooth adapter 5c:93:a2:9c:a8:a8; controller address read back as 00:07:04:a6:be:5f and host read back correctly. Wireless BlueZ appearance is still pending unplug plus PS-button reconnect near Nightwing."} {"ts": "2026-05-31T21:48:00+01:00", "type": "verification", "status": "ok", "note": "Nightwing now has two wireless PS Moves connected and trusted: 00:07:04:a6:be:5f appears as bluetooth /dev/hidraw2 plus /dev/input/js1, and 00:06:f5:23:e2:d1 appears as bluetooth /dev/hidraw3 plus /dev/input/js2. A third cabled Move remains visible separately as usb /dev/hidraw1 plus /dev/input/js0. Bluetooth hidraw nodes are root-only on this boot, so multi-Move LED actuation needs a udev permission rule or privileged helper before non-root scripts can drive both lights."} {"ts": "2026-05-31T21:58:29+01:00", "type": "implementation", "status": "ok", "note": "Added tools/music_keyed_move_chirp_sync.py as the first music-keyed audiovisual calibration word planner. It reuses the Perlines-style whitened broadband spectral-rise onset path, autocorrelates onset for tempo, estimates a lightweight root from recent fundamentals, quantizes chirps to a minor-pentatonic scale, and schedules unique per-Move color pulses from one shared JSON receipt. Synthetic dry-run produced 120 BPM/A with high confidence; live Scarlett dry-run produced a slower 92.31 BPM grid, and Dirtyphonics double-time mode with --tempo-grid doubletime --tempo-max-bpm 260 produced a 171.43 BPM grid. Non-dry multi-Move actuation still needs hidraw permission/root-helper work for bluetooth /dev/hidraw2 and /dev/hidraw3."} +{"ts": "2026-05-31T22:08:09+01:00", "type": "verification", "status": "ok", "note": "Nightwing root SSH is now available through the short local alias nwroot using the existing Starfire-to-Nightwing key, with root login key-only. Installed /etc/udev/rules.d/70-move.rules so Bluetooth PS Move hidraw nodes match Sony 054c:03d5 HID parents and become root:input 0660. Non-root metacrat write-open succeeded for /dev/hidraw2 and /dev/hidraw3, and a two-Move flash test drove 00:07:04:a6:be:5f orange plus 00:06:f5:23:e2:d1 blue, then off."} {"ts":"2026-05-31T21:48:00+01:00","type":"implementation","status":"ok","note":"Mimir's Eve/CultUI editor surface now uses editor anatomy instead of dashboard columns: Scene Graph left, Scene View center, thin Asset Browser below the view, and Inspector right. The old Program/Sync rail was removed from the inspector side so telemetry no longer steals editor hierarchy. Headless empty-runtime capture verified the shell at 1280x720 with no sibling overlap.","files":["src/Mimir.Runtime/MimirRuntime.cs"],"source":"dotnet build src/Mimir.App/Mimir.App.csproj --no-restore; Mimir.App --headless --headless-width 1280 --headless-height 720 --capture-frame artifacts/runtime/mimir-editor-shell-final-headless.png"} {"ts":"2026-05-31T22:06:00+01:00","type":"implementation","status":"ok","note":"Mimir's editor scene view now behaves as a compositor/program preview rather than a dashboard readout: SceneEditorState owns normalized program-frame placement for visible nodes, the CultUI preview renders those rectangles, inspector X/Y/W/H controls mutate the same node transforms as mouse-drag input, and video surface intents carry that placement into Fensalir field support. This makes outgoing element arrangement an editor-owned state path instead of a presentationControls-only opacity/layer list.","files":["src/Mimir.Runtime/MimirRuntime.cs","src/Mimir.Runtime/Synchronization/MimirSceneEditorState.cs","src/Mimir.Runtime/Synchronization/MimirFensalirBridgeContracts.cs","src/Mimir.Runtime/Synchronization/MimirFensalirFieldLowering.cs"],"source":"dotnet build src/Mimir.App/Mimir.App.csproj --no-restore; Mimir.App --headless --headless-width 1280 --headless-height 720 --capture-frame artifacts/runtime/mimir-editor-compositor-preview-headless.png"}