aboutsummaryrefslogtreecommitdiff
path: root/CHANGELOG.md
Commit message (Collapse)AuthorAgeFilesLines
* fix(pin): the work after a PIN and the change queue run in stepscirakg2 days1-0/+26
| | | | | | | | | | | | | | | | | | | | | | | | After a correct or new PIN, promoting pending entries and applying waiting "Require PIN" changes ran in the event of the last PBKDF2 step; 16 waiting changes tripped the watchdog on the Forerunner 70. ChangeQueue.LockJob now does it in steps while the PIN screen shows "Checking...", saves what it did to the results and refreshes the glance after Set PIN too. The list title decrypted every waiting change at each start. Queue items are now [action, box] (aad OTPW-Q-2 + action code), so they are counted without decrypting; 0.9.0 items are still read. A replacement is checked when it arrives and its material is sealed apart (qm.<n>). Large buffers are wiped and UTF-8-checked in pieces (Jobs.Wiper, Bytes.utf8Prefix, SealedBox.openKeep/sealKeep). "Phone changes" reads behind "Reading...", and Confirm all / Reject all act only on the changes shown. Storage full no longer stops the app at the PIN. Found by the review of b8addc8/096b5a4 and a new make watchdog test; the diff was reviewed again and its findings fixed. fr70: make lint, make test (176), make watchdog (19 cases at two steps per event), make screenshots pass; list_locked and list_reset goldens show "Results ready (menu)". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(pin): START never submits on touch; Change PIN asks once after a legacy PINcirakg3 days1-0/+8
| | | | | | | | | | | | | A legacy PIN (0.8.0 or earlier) on a touch screen was still submitted by START, and a tap that also arrives as START could submit the digits typed so far as a counted wrong PIN. The OK key is tapped instead. "Change PIN" while locked with a legacy PIN asked for the new PIN twice: the forced new PIN after the unlock is now the change. Found in the review of b8addc8 and 096b5a4. make test and make screenshots pass on the Forerunner 70. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(release): 0.9.0, the fixes from the first real-watch roundv0.9.0cirakg3 days1-0/+51
| | | | Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs: user guide, known limitations and M8 results; bump to 0.8.0v0.8.0cirakg8 days1-0/+56
| | | | | | | 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 <noreply@anthropic.com>
* docs: record M7 (settings forms) results; bump to 0.7.0v0.7.0cirakg8 days1-0/+53
| | | | Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs: record M6 (all 12 symbologies) results; bump to 0.6.0v0.6.0cirakg9 days1-1/+10
| | | | Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs: record M6c (Data Matrix, PDF417) resultscirakg9 days1-0/+15
| | | | Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs: record M6b (QR) resultscirakg9 days1-0/+8
| | | | Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs: record M6a (linear barcodes) resultscirakg9 days1-0/+16
| | | | Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs: record M5 results; bump to 0.5.0v0.5.0cirakg9 days1-0/+38
| | | | Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs: record M4 results and simulator findings; bump to 0.4.0v0.4.0cirakg9 days1-0/+36
| | | | Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs: document the storage format and record M3 results; bump to 0.3.0v0.3.0cirakg10 days1-0/+24
| | | | Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs: record M2 results and bump version to 0.2.0v0.2.0cirakg10 days1-0/+30
| | | | | | | | | CHANGELOG 0.2.0; PERFORMANCE (simulator benchmarks and what they mean for the watch); TESTING (vector sources, M2 results, watchdog caveat); FEASIBILITY (verified: no native HMAC-SHA1, AES-256 works, Long semantics); README status and targets; developer-guide Monkey C facts. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs: add developer, testing and performance guides; record M0 resultsv0.1.0cirakg10 days1-6/+30
| | | | | | | | | | | | - DEVELOPER_GUIDE: workflow, how the tooling works (verified simulator behaviour), conventions and how to add devices. - TESTING and PERFORMANCE: test layers, M0 results and measured numbers. - FEASIBILITY: what M0 verified (watchdog 120k/240k, 10 MB storage in device profiles, unreliable monkeydo exit code, icon sizes). - README status, new make targets and layout; CHANGELOG 0.1.0. - Author/Summary headers on every document, including the original brief. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* build: add Docker-only Makefile, SDK setup and product manifestcirakg10 days1-0/+16
- Makefile: every target runs in a container as your UID/GID, with no capabilities, a read-only root filesystem, only the project folder mounted and no network except for image builds and `make sdk`. Serial even under `make -j`. `make nuke` removes containers, images, the dedicated buildx builder and .cache/ after confirmation. - sdk-setup.sh: agreement acceptance pinned to the hash you read, password login (never stored), SDK 9.2.0 and device download, and the login token deleted afterwards. - gen-key.sh: RSA-4096 developer key into .cache/keys, never overwritten, with backup instructions. - manifest.xml: watch-app, minApiLevel 5.0.0, no permissions, and the 72 watches with API 5.0+ and at least 512 KB for apps. - .gitignore, lint configs and CHANGELOG. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
generated by cgit v1.2.3 (git 2.39.1) at 2026-10-29 03:49:13 +0000