root/fusion
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat(FN-3561): wire permanent-agent approval context in runtime paths

Browse Source 
Wired permanent-agent approval context into runtime paths for FN-3561, updating the agents documentation and adding test coverage for the heartbeat executor to validate the runtime behavior.

Fusion-Task-Id: FN-3561
This commit is contained in:
Fusion
2026-05-07 19:51:02 -07:00
committed by gsxdsm
parent ff6a568f0c
commit a61ea03b13
12 changed files with 329 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/agents.md
View File

@@ -87,11 +87,11 @@ Unknown/unclassified tool fallback:
- In permanent-agent sessions, unknown tools default to `require-approval` (fail-safe).
- Category `none` only yields `allow` when the tool is positively recognized as read-only.
Interim enforcement behavior (pre-persistence path):
Interim enforcement behavior (persistence-integrated, pre-resume lifecycle):
- Permanent-agent gating short-circuits `block` and `require-approval` actions before tool execution and returns structured tool errors.
- `require-approval` is preserved as a distinct disposition for later approval workflow integration.
- This v1 gating layer does **not** create approval requests, pause agents, or depend on approval-request persistence APIs.
- Permanent-agent gating short-circuits `block` and `require-approval` actions before tool execution and returns structured non-success tool results.
- For `require-approval`, the engine now creates durable approval requests (via `ApprovalRequestStore`) with requester identity, task/run context, and tool/action metadata; the original mutation is not executed.
- Pause/resume execution, suspended-run continuation, and approve/deny continuation behavior remain deferred to FN-3548.
Default and legacy fallback behavior: