hive-sh4re + docs: extract HelperEvent prose (#717 batch 7)
This commit is contained in:
parent
d59bfb899f
commit
f3fefe7f7e
2 changed files with 29 additions and 61 deletions
|
|
@ -497,6 +497,17 @@ regular claude turn so the manager can react. Variants
|
|||
The recipient responds via `Answer { id, answer }` and the
|
||||
asker sees the matching `QuestionAnswered`.
|
||||
|
||||
Optional `sha` / `tag` fields on `ApprovalResolved`, `Spawned`, and
|
||||
`Rebuilt` carry the canonical hive-c0re-vouched commit sha plus the
|
||||
applied-repo's terminal tag (`deployed/<id>` / `failed/<id>` /
|
||||
`denied/<id>` for approval-driven flows; `approved/<id>` for the
|
||||
rare bare-approval case where no underlying action runs). Both are
|
||||
`Option`: `None` on the paths 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.
|
||||
|
||||
To add a new event: new `HelperEvent` variant + call sites + update
|
||||
`prompts/system.md` (`<!-- role:manager -->` block, the lifecycle-
|
||||
event list) so the manager knows the new shape.
|
||||
|
|
|
|||
Loading…
Reference in a new issue