4 Commits

Include renames

Author	SHA1	Message	Date
jochen	c9a711c259	betterbird: write the account lists only while the profile is closed, and never propose over an unreadable layer (hq issue 586, review 121) ... writeAccountLists checked only for a running Betterbird and wrote without a sync; it now waits for the profile's lock too and writes atomically. readLayer read any answer that was not JSON as an empty layer, and a proposal replaces the layer whole, so a changed wording would have dropped accounts; it now refuses. The README says the rollout order that leaves no node on Betterbird's defaults.	2026-10-13 02:12:06 +02:00
jochen	1835f0efad	betterbird: own Betterbird's whole configuration as settings, shown without a credential (hq issue 586, ADR 0329) ... The module owned only the accounts' server fields, so identities, signatures, calendars, address books, filters and tags could differ between desktop nodes unseen, and the operator's own preferences were shipped in the catalogue. prefs becomes one entry per preference (a node's layer overrides one key) and the defaults file keeps no value of the operator's; identities, calendars, address-books, filters and tags become settings, adopted like accounts, filters owned whole per account, and what Betterbird rewrites written only while it is closed. New tools list each kind, derive the layers from every desktop node and propose one at a time, and show drift; every answer passes a credential check.	2026-10-13 02:03:04 +02:00
jochen	263c86d2e5	betterbird: withhold account values in the user.js answer, never write a shared outgoing server, and say a newer Owl as a fact (review 34, hq issue 345, ADR 0317) ... The user.js answer carried declared addresses and hosts (ADR 0316 §16). An adopted identity's outgoing server may be shared with an account the module does not own, whose sending the declared values would change at every start: refused with the remedy, since ADR 0317 §2 leaves the identity's server and the lists as they are; a recorded adoption follows the identity's current server. Owl installed by policy cannot be removed, so a newer Owl than the pin is a fact whose remedy is moving the pin.	2026-10-12 14:49:21 +02:00
jochen	ec4ab7afe7	betterbird: install Betterbird from its pinned release, ship Owl by policy, and declare the accounts without credentials (hq issue 345, ADR 0316, ADR 0317) ... A module that cannot set Betterbird up is of little use (the operator, 2026-10-12). The module now declares the community package absent and unpacks the pinned upstream release where that package had it, so the same profile opens; places the enterprise policy that turns Betterbird's updater off and force-installs Owl from the xpi the mesh pinned by its vendor's digest (never in a repository); and takes the operator's accounts from the trusted setting accounts, without any password or token: an account the profile already holds is adopted under its own keys, a new one is created under the module's mesh_ keys, an ambiguous one is refused with the remedy, and the account lists are only written into. betterbird_accounts says the profile's accounts by count and proposes the setting built from them for the operator's Approve. Every new build waits for the operator's push. The reminder test is visibly a test (MESH TEST band, event name) and its description says it opens a window on the operator's screen.	2026-10-12 14:49:21 +02:00