rcourtman 06fd4fc89e Bypass approval gate for trusted internal Discovery commands ... Discovery wraps every probe in `docker exec <container> sh -c '...'`. The agentexec command policy lists `^docker\s+exec\s` as RequireApproval (a sound default for user-driven docker exec) and Discovery has no path to mint or supply an ApprovalID. Result: every probe was rejected, the scanner returned empty CommandOutputs, and the AI fell back to "Unknown Infrastructure Resource" at confidence 0. The Discovery sub-tab rendered empty after a "successful" run. Add a Trusted bool to ExecuteCommandPayload on both the server-facing agentexec type and the agent's wire struct. When set, the approval gate is skipped on both ends and the server does not attempt to auto-mint an approval grant (which would fail with "approval id is required"). PolicyBlock still applies; this is not a way to run arbitrary commands. Only the discoveryCommandAdapter sets Trusted=true. The flag is never populated from a deserialised HTTP body or any user-driven path. Patrol fixes, Assistant remediation, and AI tool calls continue to flow through the governed approval-record path with a real ApprovalID. Contracts: amend agent-lifecycle Completion Obligations and Current State to document the lone exception to the on-agent approval rail, and amend ai-runtime to fence the Trusted flag to the discovery adapter only.		2026-05-17 21:59:39 +01:00
..
internal	Clear v6 prerelease-to-GA promotion gate	2026-04-20 16:33:03 +01:00
v6	Bypass approval gate for trusted internal Discovery commands	2026-05-17 21:59:39 +01:00
control_plane.json	Capture Pulse Intelligence product direction	2026-05-06 15:56:45 +01:00
control_plane.schema.json	Map legacy stable releases in control plane	2026-04-11 13:23:07 +01:00