jschoubben
d68e241724
ADR 0593 §7: the composer with its refusals leaves mesh-sdk, so mesh-sdk carries no composition rule. The catalogue functions only the node-engine's composition reaches (Resolve, Resolution's Compose, Declaration, DataItems, LeftOut, Rules and the rest, the settings, placeholder and template refusals, the rendering helpers) are copied with their tests into internal/compose/resolution; a method of a mesh-sdk shape becomes a function taking it first. The composition calls its own copies, and the captured catalogue its tests read lives here now, shared by mesh-compose's tests. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL
11 lines
901 B
Bash
Executable File
11 lines
901 B
Bash
Executable File
#!/bin/sh
|
|
# Betterbird's start, written by the mesh (module betterbird, novox/hq ADR 0316). Replaced at every push.
|
|
#
|
|
# Before Betterbird starts, the module's tools place its user.js in the profile (the settings prefs, accounts, identities, calendars,
|
|
# address-books and tags) and write what Betterbird rewrites itself: the account lists and each declared account's filters. They do
|
|
# it only while no Betterbird of this account runs, because Betterbird rewrites its saved preferences when it quits; a
|
|
# second start while one runs only hands over to it. What the preparation could not do it says here, and
|
|
# betterbird_check says it too. Betterbird starts either way: its configuration never holds the mail back.
|
|
/usr/local/lib/mesh-betterbird/betterbird-tools prepare || echo "betterbird: the mesh's preparation did not complete; betterbird_check says why" >&2
|
|
exec /opt/betterbird/betterbird "$@"
|