vinzenz/hyperhive
vinzenz/hyperhive
Watch
0
0
Fork
You've already forked hyperhive
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 2

fix tracker-tag lint and vale prose reds on #4624

Browse source 
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).
This commit is contained in:
atlas 2026-09-21 18:52:33 +02:00 • committed by mara
commit eec908bdb7
3 changed files with 7 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

10
docs/agent-lifecycle/approvals.md
View file

@ -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/<n>/config/`) is pre-configured
with `applied` as a git remote pointing at