otpGarmin/source/app, branch main

chore(release): 1.0.0, with the Connect IQ Store listing

2026-10-27T23:03:01+00:00

The second real-watch round on the Forerunner 70 passed: codes from otpauth:// links, the 4-digit PIN, touch scrolling and Aegis JSON import. Version 1.0.0 ships the fixes of the 0.9.0 review. - docs/STORE_LISTING.md: title, description and What's New for the Garmin developer page, with measured character counts. - docs/store/: hero (1440x720), cover (500x500) and seven round screen images, built by tools/store_assets.py from the fr70 goldens. - CHANGELOG 1.0.0, README status, TESTING round 2 results, YOUR_STEPS marked done, fr70 about.png golden at 1.0.0. make ci green on fr70. Co-Authored-By: Claude Opus 5.5

test(ui): second UI scenario, and the fixes it found

2026-10-25T22:51:52+00:00

A second UI-test build (uitest-extra.jungle) covers the legacy PIN and the forced new PIN, Change and Reset PIN, a queued Require PIN, UPC-A, Code 39, the code error screen, the encoding progress, auto-lock on a barcode, the light theme and the glance without a code; the main flow adds the Steam and Library details and the menu's text screens. Fixed from what it found: Entry IDs tripped the watchdog with 110 entries; auto-lock didn't close a locked barcode; a queued Require PIN showed "Confirm in menu"; locked barcodes lacked the padlock; the PIN keypad's bottom row, the Reset PIN question, text-screen bottoms, the glance title and the light-theme warning colour. Goldens approved on all seven watches; only the Forerunner 70 was re-verified after the version bump. Co-Authored-By: Claude Opus 5.5

feat(pin): exactly 4 digits, entered on the 4th digit

2026-10-25T11:46:42+00:00

The keypad has no OK key; the 4th digit submits, so a tap that also arrives as START can no longer submit a partial PIN (the likely cause of "Wrong PIN" before the code opened). PINs set by earlier versions still unlock and are then replaced by a 4-digit one. Opening an entry ignores a second request from the same tap. A Require PIN sent from the phone while the watch is locked now applies at the next PIN instead of waiting for Confirm all. The linter skips .claude. Co-Authored-By: Claude Opus 5.5

docs: user guide, known limitations and M8 results; bump to 0.8.0

2026-10-21T01:55:15+00:00

0.8.0 is the release candidate: 1.0.0 is tagged after the on-watch checklist (docs/TESTING.md). Co-Authored-By: Claude Opus 5.5

test(build): add make watchdog, the glance memory budget and the glance screenshot

2026-10-21T01:55:10+00:00

- make watchdog (in make ci): a stress build encodes, packs, turns into runs and draws the largest code of every 2D symbology at two steps per event on the Forerunner 255S and 70; it fails on a watchdog trip, and the last code left on the screen must decode (bitmap path on the 70). - make memtest checks the glance (DIAG glance, budget 70 % of 64 KB). - screenshots.sh launches the app again after the flow and compares the glance with the favourite's code (glance_code.png on 7 watches); the About goldens show 0.8.0. Co-Authored-By: Claude Opus 5.5

feat(glance): show the favourite code in the glance (opt-in)

2026-10-21T01:55:10+00:00

With "Show the favourite code in the glance" on, the glance shows the code of the first favourite TOTP or Steam entry without the PIN, with a countdown bar. The glance can't open the vault, so the About scan seals that entry under "g" (device key, aad OTPW-GL-1) after every change, and removes it when the option is off or no entry qualifies; the glance also reads the option itself. HKDF moves to its own module so the glance loads only the crypto it needs (37 % of its 64 KB). Manage entry gains "Mark as favourite (glance)" and "Remove favourite", queued for locked entries like the other changes. Lines are inset on round screens so the Instinct 3's curved glance corner doesn't cut them. Co-Authored-By: Claude Opus 5.5

docs: record M7 (settings forms) results; bump to 0.7.0

2026-10-20T16:36:54+00:00

Co-Authored-By: Claude Opus 5.5

test(settings): cover every form, symbology and Manage action; send the forms end to end in the UI flow

2026-10-20T16:36:54+00:00

34 Monkey C tests (154 per device): validation messages, idempotency, the queue, the About scan, "Encrypt names" and the properties contract. The UI-test build fills in Add OTP, Add code and Manage like the phone; the flow checks the new TOTP (309 848 at the frozen time), decodes the Code 128 card and confirms the queued change to the locked entry with the PIN. Co-Authored-By: Claude Opus 5.5

feat(settings): add the Add OTP, Add code and Manage entry forms with a PIN queue for locked entries

2026-10-20T16:36:54+00:00

The full phone settings form (README 10.2) and its processing (10.3) as one resumable job: Import, Add OTP, Add code, Manage, then the About fields. Forms are applied only when their switch is on, cleared afterwards (secret first; only the secret after a problem), deduplicated by keyed hash, and report into their Result field and the results screen. - Add OTP validates per README 10.4; Add code runs the real encoder (CodeCheck, a job for 2D codes) and caches 2D codes on the way in. - Manage entry: edit, move, require/drop PIN, replace, counter, delete. Changes to locked entries are sealed under "q" and applied only after the PIN is entered under "Phone changes" in the menu. - About: catalog (800 characters max), version, storage use. - "Encrypt names" now applies to new and existing entries. Co-Authored-By: Claude Opus 5.5

test(codes): compare Aztec with aztec_code_generator, decode it and its screenshot

2026-10-20T10:16:59+00:00

Co-Authored-By: Claude Opus 5.5