chore: synchroniser main avec upstream 25cb255b #25

Merged
Blendman974 merged 18 commits from MasterControl/faceclaw:sync/upstream-main-20261119 into main 2026-11-19 22:03:23 +00:00
Contributor

Synchronisation upstream

  • Source : jimrandomh/faceclaw, branche main, commit 25cb255be23c0c6cdb399c3fb8a5ad43ff814f4a (récupéré le 19 novembre 2026).
  • Merge non destructif sur Blendman974/faceclaw:main, base 15d7e9482d8bf4a7679487c4379b38d144da782d.
  • Aucun conflit. Arbre final strictement identique à upstream/main ; les deux historiques sont conservés.
  • Nouveautés upstream : clavier/souris Bluetooth, terminal SSH/tmux, enregistrement multi-micro/relecture, réglages glanceboard/head-up, événements calendrier multi-jours, cache ressources et correctifs iOS.

Validation exécutée

  • npm ci --ignore-scripts --no-audit --no-fund avec NODE_ENV=development : OK.
  • npm exec -- tsc --noEmit : OK.
  • npm run lint : code retour 0, avertissements existants.
  • git diff --check : OK.
  • npm test : 1347 tests, 1342 réussis, 4 ignorés, 1 échec upstream dans tests/ios-onboarding.test.cjs:182 : le mock BLE ne fournit pas systemConnectedDevices(), utilisé par le nouveau scanner iOS. Cet échec est reproduit sur l'arbre upstream exact, sans modification locale.
  • npm run test:kotlin : 398 tests Android host réussis, zéro échec (JDK 21 et SDK Android temporaires fournis dans scratch). Pas de validation APK, appareil ou tests natifs iOS.

La propagation vers build/all-features est préparée dans une PR distincte, en conservant les fonctionnalités du fork. Aucun push direct sur main.

## Synchronisation upstream - Source : `jimrandomh/faceclaw`, branche `main`, commit `25cb255be23c0c6cdb399c3fb8a5ad43ff814f4a` (récupéré le 19 novembre 2026). - Merge non destructif sur `Blendman974/faceclaw:main`, base `15d7e9482d8bf4a7679487c4379b38d144da782d`. - Aucun conflit. Arbre final strictement identique à upstream/main ; les deux historiques sont conservés. - Nouveautés upstream : clavier/souris Bluetooth, terminal SSH/tmux, enregistrement multi-micro/relecture, réglages glanceboard/head-up, événements calendrier multi-jours, cache ressources et correctifs iOS. ## Validation exécutée - `npm ci --ignore-scripts --no-audit --no-fund` avec `NODE_ENV=development` : OK. - `npm exec -- tsc --noEmit` : OK. - `npm run lint` : code retour 0, avertissements existants. - `git diff --check` : OK. - `npm test` : 1347 tests, 1342 réussis, 4 ignorés, 1 échec upstream dans `tests/ios-onboarding.test.cjs:182` : le mock BLE ne fournit pas `systemConnectedDevices()`, utilisé par le nouveau scanner iOS. Cet échec est reproduit sur l'arbre upstream exact, sans modification locale. - `npm run test:kotlin` : 398 tests Android host réussis, zéro échec (JDK 21 et SDK Android temporaires fournis dans scratch). Pas de validation APK, appareil ou tests natifs iOS. La propagation vers `build/all-features` est préparée dans une PR distincte, en conservant les fonctionnalités du fork. Aucun push direct sur main.
MasterControl added 18 commits 2026-11-19 21:49:38 +00:00
- Head tilt angle setting (Glanceboard): sets the glasses' own head-up
  trigger through the stock settings message (g2_setting.proto
  DeviceReceiveInfoFromAPP.deviceReceiveHeadUpSetting), so detection stays
  on the glasses and nothing streams while the screen is off. The stored
  calibration is read back and compensated for, and the value is
  re-applied on every connect. "glasses" (the default) leaves the
  glasses' setting untouched.
- "Set to current head angle" measures the tilt from a ~1.2 s IMU burst
  and rounds it to the nearest 5 degrees.
- Glance down to hide: a head-tilt showing now stays up until the head comes back down
  (HEAD_DOWN, forwarded by Faceclaw/38) instead of a fixed timeout, with
  a 60 s safety cap. HEAD_DOWN goes only to the Glanceboard on Android
  and iOS, so it never counts as shell activity.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- A verification read that still disagrees no longer requeues the writes at
  once (which looped while the firmware refused the value); the next regular
  poll retries.
- "Glasses default" now writes back the glasses' own switch and angle, saved
  before Faceclaw first changed them (persisted across app restarts), and
  drops writes still queued. Disabling the Glanceboard does the same.
- "Set to current head angle" takes two readings, head level then tilted up,
  and uses the angle between them, so it no longer depends on the sensor's
  axes or folds past 45°. A head that did not move is reported, not stored
  as 5°. The math is in head-tilt-math.ts, with tests.
- A head-tilt that woke a suspended session, or a trigger under 25° (where a
  level gaze stays above the head-down threshold), hides after the tap
  duration instead of the 60 s cap. The setting's description explains it.
- The angle rows are hidden on iOS, which cannot change the setting.
- The capture row repaints while measuring, ignores repeat selects, and its
  status clears when the menu reopens or the angle changes; the angle is
  sent once, by the controller's settings listener.
- Comments describing a head-tilt as a timed press are updated.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
How long a head-tilt showing may last when no head-down arrives: 60 s
(the default, as before), 30, 15, 10 s, or never (it then stays until the
head comes down or a double-tap). Where the head-down is unlikely, the tap
duration still applies when it is shorter.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
G2 only: You can pair the glasses with a bluetooth keyboard. It will
relay key events, and you can use it to type in some apps and to
navigate the UI.
The glanceboard head-tilt option was more complicated than necessary,
because it wanted the user to take two angle measurements, a baseline
angle and a tilt angle. That was a workaround to not knowing the
accelerometer's orientation/calibration, but actually, we do know those.

(Except, as it turns out, on the G1, the accelerometer orientation is
different than it is on the G2, and there was a bug where EvenHub apps
got their accelerometer readings in the wrong orientation. So for
example the EvenHub Level app didn't work correctly.)
A multi-day all-day event that started yesterday read as yesterday's
("Mon Nov 16 (all day)"), so the assistant left it out of today's plans;
timed events had no end time. Format the span: the last day of an all-day
event (ends are exclusive) and the end time of a timed one.

The date formatting moves into a pure app/assistant/date-format.ts with
unit tests.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A three-day all-day event showed only under its first day, so on day three
the app had nothing under Today. An event that began on an earlier day and is
still going is now listed under today, and an event covering more than one
day shows its span ("Mon 16 – Wed 18 Nov").

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Calendar: include the end of each event, and list ongoing multi-day events under today
Blendman974 merged commit 597d38318e into main 2026-11-19 22:03:23 +00:00
Sign in to join this conversation.
No Reviewers
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Blendman974/faceclaw#25