jochen
ec4ab7afe7
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.
13 lines
263 B
JSON
13 lines
263 B
JSON
{
|
|
"policies": {
|
|
"DisableAppUpdate": true,
|
|
"ExtensionSettings": {
|
|
"owl@beonex.com": {
|
|
"installation_mode": "force_installed",
|
|
"install_url": "file:///opt/betterbird/owl/owl.xpi",
|
|
"updates_disabled": true
|
|
}
|
|
}
|
|
}
|
|
}
|