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

refactor(#2416): drop the now-always-none Spawned.sha field + deny tag leftover

Browse source
This commit is contained in:
damocles 2026-07-15 20:58:37 +02:00 • committed by mara
commit 12ce346d02
4 changed files with 8 additions and 17 deletions
Download patch file Download diff file Expand all files Collapse all files

15
docs/approvals.md
View file

@ -576,15 +576,12 @@ root agent. Variants (`hive_sh4re::HelperEvent`):
The recipient responds via `Answer { id, answer }` and the
asker sees the matching `QuestionAnswered`.
Optional `sha` field on `ApprovalResolved`, `Spawned`, and `Rebuilt`
carries the canonical hive-c0re-vouched commit sha. Optional `tag`
on `ApprovalResolved` and `Rebuilt` only — the spawn path always
lands at `deployed/0`, so the tag is implicit and not echoed. The
tag values for the variants that do carry it: `deployed/<id>` /
`failed/<id>` / `denied/<id>` for approval-driven flows;
`approved/<id>` for the rare bare-approval case where no underlying
action runs. Both fields are `Option`: `None` on the rebuild paths
that don't change the deployed commit (e.g.
Optional `sha` field on `ApprovalResolved` and `Rebuilt` carries the
canonical hive-c0re-vouched commit sha. Optional `tag` on the same two
carries the deploy bookkeeping tag — `deployed/<id>` on a successful
build or `failed/<id>` on a failed one, planted by the `MergeConfigPr`
deploy. Both fields are `Option`: `None` on the paths that don't deploy
a new commit (spawn / init_config / meta-update / deny, and
`auto_update::rebuild_agent` reapplying the existing main, or the
dashboard `↻ R3BU1LD` button when the lock didn't move). When set,
`git show <sha>` against `/agents/<n>/applied.git` inside the