Update hivegrid-cloud reference to latest main

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
davidandClaude Fable 5 committed 2026-07-08 16:15:37 +02:00
1 parent e98d38e716
commit 7b21524c86
3781 files changed
+373484 -225607

No files matched your search

@@ -76,7 +76,7 @@ plugin runtime gate on `worker-general` and `worker-plugin`. Both groups require
the outbox dispatcher is not enabled or plugin hook fanout/capability-use
subscribers are explicitly disabled. With the production gate unset or `false`,
the production `worker-plugin` service may still be deployed as an idle topology
placeholder, but it must not consume `toolctrl.plugin-invoke`.
placeholder, but it must not consume `hivegrid.plugin-invoke`.
For the first tenant-facing plugin rollout, run the explicit live gate inside
both relevant worker containers after Coolify reports them healthy:
@@ -133,11 +133,11 @@ Coolify deployments must run five separate persistent worker applications from t
execution is not automatically enabled by deploying it. Until the external WASM
sandbox signoff is complete and `PLUGIN_RUNTIME_PRODUCTION_ENABLED=true` is
set, `worker-plugin` is expected to remain idle and must not consume
`toolctrl.plugin-invoke`.
`hivegrid.plugin-invoke`.
`worker-import` is provisioned the same way: keep it as a separate internal app,
but leave `IMPORT_QUEUE_ENABLED` and `IMPORT_QUEUE_RUNTIME_READY` unset until
the import, export, and scan services are wired. While idle, it must not consume
`toolctrl.imports` or `toolctrl.exports`; once both gates are enabled, startup
`hivegrid.imports` or `hivegrid.exports`; once both gates are enabled, startup
fails closed unless those services are present.
| Coolify app | Required env | Public FQDN | Health port | Admin/metrics port |