feat: gate agent management rollout

[danielkov]

Summary

Gates agent-management endpoints behind an organization-targeted agent-management feature flag and extends authorization and audit coverage for agent identity and setup. Endpoints fail closed unless the flag is explicitly enabled, and rollout requires administrator-grant verification before the feature flag is enabled.

Motivation

Agent-management surfaces must not become reachable until administrator grants are fully backfilled and verified.

Technical details

Rollout control

The feature flag is evaluated after session authentication using the authenticated organization ID and organization cohort. Disabled, missing, indeterminate, and provider-error results return a uniform not-found response before an endpoint can read or mutate agent state.

Grant verification

The operator runbook requires complete-database grant verification before enabling the feature for an environment or cohort. Verification fails when required grants are missing, unexpected agent grants exist, or administrator roles remain unresolved.

Rollout prerequisite

This PR targets main. The backfill command and runbook remain in #6044; they are an operational rollout prerequisite, not a runtime code or merge dependency of this PR.

Run the administrator-grant backfill and verify the complete target database before enabling the agent-management feature flag for an environment or cohort. Keep the flag disabled until verification exits zero and reports summary.verification.ready_for_enforcement=true.

Linear: AIM-190

[linear-code]

AIM-190

[changeset-bot]

🦋 Changeset detected

Latest commit: 1f0a170

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages

Name	Type
server	Minor
dashboard	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[cubic-dev-ai]

Running ultrareview automatically — This PR introduces a fail-closed authorization gate for agent management endpoints controlled by an org-targeted feature flag, with the gate applied in the auth path and a new CI gate; a subtle bug could expose or block agent management incorrectly, warranting a deeper review.. I'll post findings when complete.

[cubic-dev-ai]

Ultrareview completed in 3m 57s

All reported issues were addressed across 10 files

Linked issue analysis

Linked issue: AIM-190: test: gate M1 agent identity and setup authorization

Status	Acceptance criteria	Notes
✅	A standalone, non-retrying CI gate runs the combined M1 identity, lifecycle, authorization, policy, migration, audit, telemetry, and privacy test suites.	The new m1-agent-gate job runs the listed server packages with count=1 and is required by the main PR checks.
✅	M1 agent-management endpoints remain unavailable unless the organization-targeted rollout flag is authoritatively enabled.	Authentication is followed by per-organization flag evaluation, and disabled, missing, indeterminate, or provider-error states return a uniform not-found error.
✅	Rollout requires both the focused M1 CI result and complete-database administrator-grant verification before enforcement.	The runbook explicitly requires the published-SHA CI gate and successful migration verification before enabling the feature flag.
✅	M1 management audit actions emit the existing agent webhook event with the expected attribution.	Lifecycle, ownership, and policy tests now compare recorded audit actions with agent webhook outbox actions, while the helper validates organization and agent subject attribution.

<sub>Reply with feedback, questions, or to request a fix.

Fix all with cubic | Re-trigger cubic</sub>

[cubic-dev-ai]

All reported issues were addressed across 5 files (changes from recent commits).

<sub>Tip: Review your code locally with the cubic CLI to iterate faster.

Fix all with cubic | Re-trigger cubic</sub>

[github-actions]

Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

---

I have read the CLA Document and I hereby sign the CLA

---

7 out of 8 committers have signed the CLA.
✅ (bflad)[https://github.com/bflad]
✅ (daviddanialy)[https://github.com/daviddanialy]
✅ (chase-crumbaugh)[https://github.com/chase-crumbaugh]
✅ (danielkov)[https://github.com/danielkov]
✅ (simplesagar)[https://github.com/simplesagar]
✅ (disintegrator)[https://github.com/disintegrator]
✅ (bradcypert)[https://github.com/bradcypert]
❌ @speakeasyforgebot
_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}

[github-actions]

atlas migrate lint on server/migrations

Status	Step	Result
	No migration files detected
	ERD and visual diff generated	View Visualization
	No issues found	View Report
Read the full linting report on Atlas Cloud

[github-actions]

atlas migrate lint on clickhouse/migrations

Status	Step	Result
	No migration files detected
	ERD and visual diff generated	View Visualization
	No issues found	View Report
Read the full linting report on Atlas Cloud

[danielkov]

recheck