describe core/meta as the legacy permission repo; drop stale meta-flake prose
Comments, docs and the hive-c0re README no longer say the hive renders, locks or pushes a meta flake. core/meta is the legacy permission-seed repo that meta::remove_permission_files still commits to; builds come from internal/meta (meta_rev.rs). Docs note that a start of a stale stopped agent can fail until the swarm's update pins the config.
This commit is contained in:
parent
633139069f
commit
bd54372fcc
9 changed files with 35 additions and 25 deletions
|
|
@ -41,8 +41,11 @@ to track it:
|
|||
per-agent sockets.
|
||||
- **`forge/`** — optional Forgejo wiring (`docs/integrations/forge.md`).
|
||||
- **`coordinator.rs`** — top-level wiring for `serve`.
|
||||
- **`meta.rs`**, **`migrate.rs`** — the meta flake + schema/state
|
||||
migrations.
|
||||
- **`meta_rev.rs`** — which `internal/meta` commit an agent builds from, and
|
||||
the markers a successful build writes. **`agent_set.rs`** — the files that
|
||||
follow the agent set (topology, gateway map). **`meta.rs`** — the commit
|
||||
that removes the legacy permission seed files. **`migrate.rs`** —
|
||||
schema/state migrations.
|
||||
- **`matrix.rs`**, **`gateway_nginx.rs`**, **`priv_client.rs`** —
|
||||
matrix provisioning, gateway vhosts, and the `hive-priv` client
|
||||
respectively.
|
||||
|
|
|
|||
Loading…
Reference in a new issue