Converts the two-node database bed off the retired two-postgres model (which ADR 0079 now refuses) to the one-store model: adopt the store AND broker on the control-node, deliver the store's genesis superuser via secret accept, inject the provider seal key (open issue 022 workaround), push the provider node after the remote consumers (issue 057), and tolerate provisioner-runtime startup churn. baserow and letta on the joined node get their databases from the one foundation store over the overlay. Green.
Converts the two-node database bed off the retired two-postgres model (which ADR 0079 now refuses) to the one-store model: adopt the store AND broker on the control-node, deliver the store's genesis superuser via `secret accept`, inject the provider seal key (open issue 022 workaround), push the provider node after the remote consumers (issue 057), and tolerate provisioner-runtime startup churn. baserow and letta on the joined node get their databases from the one foundation store over the overlay. Green.
https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx
The bed assigned a separate app-postgres, which ADR 0079 now refuses. Converted to
adopt the foundation store on anchor and have baserow/letta consume it cross-node over
the overlay, with the 057 push-ordering. The store DB path reaches its asserts, but the
run is blocked by issue 058: redis's host-networked provisioner cannot reach the broker
across nodes (bridge consumers can). Committed as WIP until 058 is fixed.
https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx
The complete recipe, found across five runs: adopt BOTH the store (postgres) and broker
(lavinmq) on the control-node — the broker's `listens` is what opens 5671 in the firewall
for cross-node bus access; deliver the store's genesis superuser via `secret accept` (else
the module mints a random one that cannot log in to the running store); inject the provider
seal key (open hq issue 022 workaround); push the provider node again after the remote
consumers (issue 057); and tolerate provisioner-runtime startup churn — a cross-node
provisioner exits until the overlay tunnel is up, then settles. baserow and letta on the
joined node get their databases from the one foundation store over the overlay.
https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Converts the two-node database bed off the retired two-postgres model (which ADR 0079 now refuses) to the one-store model: adopt the store AND broker on the control-node, deliver the store's genesis superuser via
secret accept, inject the provider seal key (open issue 022 workaround), push the provider node after the remote consumers (issue 057), and tolerate provisioner-runtime startup churn. baserow and letta on the joined node get their databases from the one foundation store over the overlay. Green.https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx