From 6039571d70b1f6de1ae384e58e11879869be356c Mon Sep 17 00:00:00 2001 From: cirakg Date: Tue, 20 Oct 2026 18:36:54 +0200 Subject: docs: record M7 (settings forms) results; bump to 0.7.0 Co-Authored-By: Claude Opus 5.5 --- docs/FEASIBILITY.md | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'docs/FEASIBILITY.md') diff --git a/docs/FEASIBILITY.md b/docs/FEASIBILITY.md index f586f10..08e9461 100644 --- a/docs/FEASIBILITY.md +++ b/docs/FEASIBILITY.md @@ -274,6 +274,11 @@ With SDK 9.2.0 and the device files of all 72 products installed: - **Properties:** reading a property that isn't declared in `properties.xml` stops the app with an error `try` can't catch. The option properties are declared ahead of M7's form. - **Touch input:** on watches with touch and buttons, a tap arrives first as the select behaviour. The Venu X1 has no MENU button, and the Venu Sq 2 has no UP/DOWN. +## Verified during M7 (2026-10-20) + +- **Settings schema.** The SDK's `bin/resources.xsd` allows property types `string`, `number`, `long`, `float`, `double`, `boolean` and `array`, and setting types `list`, `boolean`, `numeric`, `alphaNumeric`, `phone`, `email`, `url`, `date`, `password` and `array`, with `readonly`, `min`, `max`, `maxLength` and `errorMessage`. The form uses `long` for HOTP counters and `readonly` for the Result and About fields. Every resource file validates against it (`make lint`). +- **Still open (3d, 3e):** how the phone shows values the watch writes back (Result fields, cleared forms, the About catalog), and how long a text field may be. The catalog is capped at 800 characters, the Garmin Express limit reported in 3d. Your M1 spike and the M7 beta check answer these. + ## Decisions Answered on 2026-10-18: -- cgit v1.2.3