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
|
|
@ -65,7 +65,7 @@ fn matrix_base() -> Result<&'static str> {
|
|||
///
|
||||
/// # Errors
|
||||
/// When `HYPERHIVE_HIVE_NAME` is unset or empty. That is the same variable
|
||||
/// [`stored_sender_token`] logs in with and `hive-c0re`'s meta flake asserts
|
||||
/// [`stored_sender_token`] logs in with and the swarm meta flake asserts
|
||||
/// for every hive, so its absence is a broken deployment rather than a
|
||||
/// supported one — and there is no safe default to fall back to: the only one
|
||||
/// available is the shared account this replaced.
|
||||
|
|
|
|||
Loading…
Reference in a new issue