docs/approvals.md: split sha vs tag scoping per argus on #833
This commit is contained in:
parent
f3fefe7f7e
commit
29fda64866
1 changed files with 12 additions and 9 deletions
|
|
@ -497,15 +497,18 @@ regular claude turn so the manager can react. Variants
|
||||||
The recipient responds via `Answer { id, answer }` and the
|
The recipient responds via `Answer { id, answer }` and the
|
||||||
asker sees the matching `QuestionAnswered`.
|
asker sees the matching `QuestionAnswered`.
|
||||||
|
|
||||||
Optional `sha` / `tag` fields on `ApprovalResolved`, `Spawned`, and
|
Optional `sha` field on `ApprovalResolved`, `Spawned`, and `Rebuilt`
|
||||||
`Rebuilt` carry the canonical hive-c0re-vouched commit sha plus the
|
carries the canonical hive-c0re-vouched commit sha. Optional `tag`
|
||||||
applied-repo's terminal tag (`deployed/<id>` / `failed/<id>` /
|
on `ApprovalResolved` and `Rebuilt` only — the spawn path always
|
||||||
`denied/<id>` for approval-driven flows; `approved/<id>` for the
|
lands at `deployed/0`, so the tag is implicit and not echoed. The
|
||||||
rare bare-approval case where no underlying action runs). Both are
|
tag values for the variants that do carry it: `deployed/<id>` /
|
||||||
`Option`: `None` on the paths that don't change the deployed commit
|
`failed/<id>` / `denied/<id>` for approval-driven flows;
|
||||||
(e.g. `auto_update::rebuild_agent` reapplying the existing main, or
|
`approved/<id>` for the rare bare-approval case where no underlying
|
||||||
the dashboard `↻ R3BU1LD` button when the lock didn't move). When
|
action runs. Both fields are `Option`: `None` on the rebuild paths
|
||||||
set, `git show <sha>` against `/agents/<n>/applied.git` inside the
|
that don't change the deployed commit (e.g.
|
||||||
|
`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
|
||||||
manager container yields the exact tree that was referenced.
|
manager container yields the exact tree that was referenced.
|
||||||
|
|
||||||
To add a new event: new `HelperEvent` variant + call sites + update
|
To add a new event: new `HelperEvent` variant + call sites + update
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue