From eec908bdb79e7b07b9fe7fa3a3f5c7833cea0a2a Mon Sep 17 00:00:00 2001 From: atlas Date: Mon, 21 Sep 2026 18:52:33 +0200 Subject: [PATCH] fix tracker-tag lint and vale prose reds on #4624 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Rewrite two bare issue references (#4472, #4477) as self-standing prose per check-issue-refs.sh's requirement — no markdown exemption, hash-number tags are dead weight to a public forge-mirror reader. Apply iris's vale fix to docs/agent-lifecycle/approvals.md (passive voice, two contractions, one auto- hyphenation). --- docs/agent-lifecycle/approvals.md | 10 +++++----- hive-c0re/src/lifecycle/host_config.rs | 2 +- hive-c0re/src/workers/auto_update.rs | 2 +- 3 files changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/agent-lifecycle/approvals.md b/docs/agent-lifecycle/approvals.md index 0ec41bb6..bfdcca48 100644 --- a/docs/agent-lifecycle/approvals.md +++ b/docs/agent-lifecycle/approvals.md @@ -511,16 +511,16 @@ host-side bind mounts via `set_nspawn_flags`: An agent without the capability only has its direct children's config dirs. -⚠️ nspawn bind flags are baked at container start, so granting or -revoking this capability does not change any mount until that agent's +⚠️ nspawn bakes bind flags at container start, so granting or +revoking this capability doesn't change any mount until that agent's container is rebuilt/restarted. -The root agent gets the capability by default, seeded on its auto-deploy +The root agent gets the capability by default, seeded on its autodeploy path (`workers::auto_update::ensure_root_agent`) so the recovery mounts are there from its first container. That seed only fires while -`capabilities.json` has never been written: any grant or revoke through +`capabilities.json` doesn't exist yet: any grant or revoke through the dashboard creates the file, so a revoked root-agent grant stays -revoked and is not re-applied on the next hive-c0re restart. +revoked and isn't re-applied on the next hive-c0re restart. Each proposed repo (`/agents//config/`) is pre-configured with `applied` as a git remote pointing at diff --git a/hive-c0re/src/lifecycle/host_config.rs b/hive-c0re/src/lifecycle/host_config.rs index 88b7ab75..88aa6d3e 100644 --- a/hive-c0re/src/lifecycle/host_config.rs +++ b/hive-c0re/src/lifecycle/host_config.rs @@ -334,7 +334,7 @@ async fn set_nspawn_flags( // accident of how the set is computed. The grant used to hang off a // `can_manage_top_level_agents` role and cover `top_level_agents()` // — i.e. `parent.is_none()` — which was "everything outside the - // hierarchy". With the hierarchy gone (#4472) every agent is + // hierarchy". With that hierarchy removed, every agent is // parentless, so that set *was* every agent anyway; the capability // now says so out loud instead of deriving it from a field that no // longer discriminates. diff --git a/hive-c0re/src/workers/auto_update.rs b/hive-c0re/src/workers/auto_update.rs index 05c2a848..2e441ec0 100644 --- a/hive-c0re/src/workers/auto_update.rs +++ b/hive-c0re/src/workers/auto_update.rs @@ -211,7 +211,7 @@ fn should_seed_manager_caps(store_written: bool) -> bool { /// `topology::reconcile_roles` seeded `can_manage_top_level_agents` onto /// `MANAGER_NAME` on every meta sync, and that role is what put the other /// agents' state/config dirs, `/applied` and `/meta` into her nspawn binds. -/// #4477 collapsed the role into the capability, so without a seed here she +/// Collapsing the role into the capability means that without a seed here she /// loses those recovery mounts at her next container rebuild — silently, and /// only then, because nspawn bakes bind flags at container start. ///