4 Commits

Include renames

Author	SHA1	Message	Date
valknarandClaude Sonnet 5	401b9b5033	Remove recordings feature, replay sessions directly, bump to 0.6.0 ... Recordings were just a thin named pointer over an already-captured session's events, so the whole separate feature (recordings table, API routes, pages, UI) is gone: any completed session can now be named and replayed directly. Replaying no longer creates a session or duplicates events of its own - it just bumps the source session's playCount/lastPlayedAt. Also renames play_sessions/playSession(s) to sessions/session(s) throughout the schema, queries, API routes, and UI for consistency, and updates the README to match the new flow. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-27 21:38:51 +02:00
valknarandClaude Sonnet 5	5484d3cefe	Fix device/replay/session UX issues, add pagination, bump to 0.3.0 ... - Fix device rename input collapsing on mobile (fixed width vs w-full inside an auto-layout table column). - Add cascade-delete confirmation for sessions with a saved recording. - Fix header connection LED: derive state from scanning/device-count/ recording instead of the Buttplug client's raw connected flag; drop the label text and hide the indicator entirely when idle. - Add a per-device disconnect button (stop + remove from store, the closest equivalent Buttplug's protocol allows per device). - Fix replay ending early: duration now comes from the recording's actual durationMs, not the last event's timestamp. - Replay robustness: show which devices are being replayed to, reset actuators to zero on start/play/pause, fully disconnect devices and the whole client on stop/unmount, surface command failures via toast. - Stop flagging the header LED red during replay - recording is only for live sessions. - Add page-number pagination to recordings/sessions/devices lists. - Wordmark SEXY -> Sexy; add proper per-page <title>s including dynamic titles for recording/session detail and replay pages. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-25 21:26:18 +02:00
valknarandClaude Sonnet 5	0bd36b08c9	Upgrade to buttplug v5, add battery level display, bump to 0.2.0 ... buttplug-wasm@3.0.0 still declares buttplug@^4.0.2 as its dependency, and v5 changed the OutputCmd wire shape (Value: number[] -> number) - a real protocol difference, not just a type mismatch. Confirmed by testing against real Lovense hardware that device control still works in practice, so the bump stands; the risk is documented at the client.connect() cast in case a future device/build doesn't fare as well. Also fixes a Map vs ReadonlyMap mismatch in the version-agnostic feature-type extraction (v4 returns Map, v5 returns ReadonlyMap) that surfaced while making this change, and adds a battery indicator to each connected device's card - reads once on connect, refreshes every 60s, using device.hasInput("Battery") to detect support. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01W8WkFF5ppURBAB918593Eb	2026-08-25 17:33:48 +02:00
valknarandClaude Sonnet 5	1119c8eea0	Initial implementation of Bluetooth toy control app ... Next.js app with a browser-side buttplug/buttplug-wasm control layer (server never touches real-time device commands), SQLite storage via Drizzle, single-secret auth, recordings/replay with device remapping, a usage stats dashboard, Docker deployment, and Gitea CI. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01W8WkFF5ppURBAB918593Eb	2026-08-25 07:51:38 +02:00