5 Commits

Include renames

Author	SHA1	Message	Date
twislaandClaude Opus 5.5	305818466f	LoRa Scanner: MeshCore by default, and its public channel read ... The MeshCore preset is the default for a new device, in the Settings and in the radio before the Scanner is opened. The setting now accepts it: it only took the 7 Meshtastic presets, so MeshCore picked in the App was not saved. Messages on MeshCore's public channel are decrypted with the channel's published key (AES-128, checked with 2 bytes of HMAC-SHA256): the row shows who says they sent it and the start of the text, the details the sender, the time and the whole text. Other channels and private messages stay encrypted. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0162FokPdvY2KsS4NBfwyWPk	2026-10-09 22:19:14 +02:00
twislaandClaude Opus 5.5	3339d9ee59	LoRa Scanner: MeshCore searches for nodes and their answers, read ... The first two MeshCore packets heard were these: a search for repeaters and a repeater answering. Both are in clear; they are the test's bytes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0162FokPdvY2KsS4NBfwyWPk	2026-10-09 20:51:15 +02:00
twislaandClaude Opus 5.5	8ba41f72b6	LoRa Scanner: a MeshCore preset, and its packets read ... - MeshCore joins the presets (EU/UK Narrow: 869.618 MHz, 62.5 kHz, SF8, CR 4/8, sync 0x12), after the Meshtastic ones so stored choices keep their number; `lora preset MeshCore` on the console - lib/meshcore reads what MeshCore sends in clear: header, path, and a node's advert (name, kind, key, position) - the list row, the details, a Capture's viewer and the console echo read a packet by the sync word it was received on - the bandwidth is printed as 62.5, not 62 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0162FokPdvY2KsS4NBfwyWPk	2026-10-09 20:30:29 +02:00
twislaandClaude Opus 5.5	34e6714785	Keys: one table file for the device's help panel and the website's key tables (#72) ... Every screen's keys are constant tables in lib/core/src/app_keys.h (52 of them, each under an `// id: Title` comment). An App's help() picks the table of the state it is in. site/tools/gen_dev_docs.py reads the same file and writes site/data/keys.toml; the `keys` shortcode shows a screen's tables on its guide page, and /guide/keys/ shows all of them. The Site job fails when the data file is out of date or a page asks for a table that doesn't exist, and now also runs when app_keys.h changes. A key added to an App shows up on the website without anyone editing a page. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EhqxQ49eCju4CzKYNjZzwT	2026-10-07 01:42:48 +02:00
twislaandClaude Sonnet 5.5	2f1befa7f5	Site: the user guide (phase 2): the basics, one page per App, Settings and Updates ... Eleven pages under /guide/, written from the README, the milestone documents and the Apps' own source: the keys, the Launcher, the Status Bar and the first start; the LoRa Scanner, GNSS, Gemini, IRC, Wi-Fi tools, Notes, Storage and System; Settings (with Wi-Fi) and Updates. Real screenshots where the site has them, a Guide link in the navigation, and the home page points to it. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EhqxQ49eCju4CzKYNjZzwT	2026-10-06 20:38:40 +02:00