Record M0-F rulings for auth profile, client registration, and monitoring

Outcome

Implementation has one evidence-backed authorization/client profile and an honest Path A or Path B monitoring claim.

Scope

• Compare co-hosted and managed authorization-server profiles only as needed by the spike.
• Record the supported client-registration profile.
• Test scheduled monitoring on the exact target host/product/plan.
• Select Path A only for observed behavior; retain deterministic Path B.

Acceptance

• One authorization-server profile is selected with reasons and required configuration.
• Client registration is recorded as CIMD, dynamic, or preregistered as observed.
• Path A availability and exact delivery behavior are documented; unsupported push claims are rejected.
• Path B status polling works in the active conversation.
• Any platform assumption that changed is reflected in the spec or a linked decision record.

Dependencies

• Throwaway remote MCP feasibility slice.

Review

Independent adversarial review of the evidence and resulting claims.

Start with the throwaway remote MCP feasibility slice and test scheduled monitoring on the exact target host, product, and plan. Record the observed authorization-server profile, client-registration mode, and monitoring delivery behavior. Update the spec or a linked decision record, preserve deterministic Path B polling, and submit the evidence for independent adversarial review.