Files
Frametop--frametop/pointer
DeeJanuzandClaude Opus 5.5 ece9f88637 Testing sessions record what the panels and pointer did with the hands
A testing session had the cameras, the tracker's output, poses, marks
and voice, but not whether a poke pressed, a pinch clicked or a stroke
turned the lazy susan. Those decisions were only in logs: the pointer
helper's in the journal, ft-screens' in /tmp without times.

- hands/include/fh_events.h: one JSON line per decision (CLOCK_MONOTONIC
  time, kind, outcome, hand, panel, the log line) appended to
  events.jsonl in the run directory, only while events-want exists.
- ft-screens: HandInput's decisions tagged with kind and outcome (Did,
  acts()); vr.cpp writes them, plus the lazy susan's result, grab that,
  the palm menu and the far stretch.
- ft-pointer: each pinch line classified (click, drag, right-click,
  scroll: done, refused, passed, lost), hand ray changes, handoffs.
- hands/rec/eventlog.py: asks for events while a part records, keeps
  the part's lines as events.jsonl in the take, counts them per kind and
  outcome in take.json; exported only encrypted (events.jsonl.zst.age),
  checked by validate.py.
- TESTING.md 2026-10-14c says so (asks again).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-14 20:00:12 -06:00
..