Show agent readiness and effective capabilities before delegation

[jusso-dev]

Context

Adapt the pre-delegation readiness model from Buzz PR #2957 to Muster. Operators should not need to infer whether an agent is healthy, authenticated, appropriately scoped, and safe to delegate to from several disconnected screens.

Proposed behaviour

Add an authorised readiness summary to agent detail and delegation flows using existing Muster evidence:

• configured runtime and provider/model identity;
• gateway health, authentication, process/run lifecycle, and last heartbeat;
• reported input/output capabilities;
• available commands and tool-source names;
• tool risk classes;
• requested permission mode versus observed effective mode;
• last verification time, freshness, and known limitations.

Use explicit states: reported, unavailable, and unknown. Missing or malformed evidence stays unknown. Stopped/failed lifecycle, stale heartbeat, closed observer, or evidence from an older process cannot produce a fresh ready state.

Security and data rules

• Enforce organisation scope and capability checks on the server, including every delegation endpoint.
• Expose only an allowlisted projection. Never surface credentials, environment values, executable paths, raw configuration, prompts, tool arguments/results, or external payloads.
• Treat runtime reports and external content as untrusted evidence, not policy.
• PostgreSQL stores authoritative agent configuration, capability assignments, readiness snapshots needed for decisions, and append-only audit/timeline events.
• A green readiness state never bypasses approval records or capability checks for dangerous actions.

UI direction

Keep Buzz-like simplicity. Default view shows one clear state—Ready, Needs attention, or Unknown—plus the most important reason and verification age. Put detailed capabilities, permissions, and tools behind progressive disclosure. Avoid a dense always-open matrix.

Acceptance criteria

• Agent detail and delegation UI show a clear, freshness-aware readiness state.
• Requested and effective permission modes appear together; divergence is visible.
• Unknown, unavailable, and reported evidence remain distinct.
• Stale or previous-process evidence cannot yield Ready.
• Non-authorised users cannot access readiness or capability details.
• No sensitive runtime/config/tool data crosses the allowlist boundary.
• Delegation still performs server-side capability checks and creates required approval/audit records.
• Unit tests cover evidence reduction, staleness, process identity, permission divergence, and redaction.
• Browser tests cover ready, needs-attention, unknown, and unauthorised views using synthetic data.

[jusso-dev]

Parent: #21

Additional small UX reference: block/buzz#2699. Show each agent short role/description in mention and delegation pickers, truncated to one line, with readiness detail remaining behind progressive disclosure.

[jusso-dev]

Implemented end to end on main in three reviewable commits:

• cb5e5ea models freshness-aware Ready / Needs attention / Unknown evidence, process identity, requested/effective permission divergence, and allowlisted projection.
• d5a0d41 persists append-only PostgreSQL snapshots, records gateway/runtime evidence, exposes organisation-scoped authorised APIs, and enforces Ready server-side before delegation without bypassing approval/capability checks.
• c9721b7 replaces static agent UI with live readiness detail, progressive disclosure, one-line role descriptions in delegation, and non-ready delegation controls.

Verification:

• pnpm check passed across all 22 packages.
• Readiness Chromium test passed Ready, Needs attention, Unknown, and unauthorised cases.
• Durable task delegation/cancel/retry/completion Chromium flow passed with readiness enforcement.
• CI passed: https://github.com/jusso-dev/Muster/actions/runs/30219115760
• Security, CodeQL, dependency/secret, Trivy, and SBOM checks passed: https://github.com/jusso-dev/Muster/actions/runs/30219115759

Deployed exact revision c9721b767adea3a22d57882a6536623f6b31951d using public image digest sha256:c9d6a9d794cc7779f90b24199d83c69aac7b0bfd84f989ccafb7e652ed9afba5. Migration applied; web, worker, and gateway healthy with zero restarts. Private DB backup and rollback image retained. Core domain counts preserved. Deployed Chromium readiness/authorisation proof passed with synthetic snapshots, then cleaned up. Operator handbook updated.