fix(nightly): skip runtime-only agent settings in static capability check
Leo: "why are changes to these not in my current nightly"
The NEXT nightly compiled successfully but failed while bundling its cmux-tui client because the static manifest check required agent-session-settings-v1. The daemon advertises that capability only at runtime when agent-session attachment is available. Add it to the existing runtime-only exclusions so publication can proceed while missing static capabilities still fail.
The existing shell regression now includes agent settings among the runtime-only optional requirements and retains its missing required/static optional checks. Prior art: #29366 fixed the same class for agent folders; #30001 added the settings capability.
Validation: scoped fleet red/green checker tests pending. No app compile is needed for this portable checker change. Risk: low; runtime capability checks stay in daemon integration coverage.
Observed / Not run
Observed nightly failure: run 41279553524, build job, the bundled static capability manifest is missing agent-session-settings-v1. Scoped pre-push guard passed. Broad verify-local also reported existing localization debt and stale workspace package grouping in unchanged files.
Not run: app builds, display tests, or unrelated suites.
Agent session: agent session
š¤ Generated with Claude Code