c74dd63281
- GET /api/docs serves a Swagger UI and GET /api/openapi.json serves an OpenAPI 3 spec built by walking the live chi router, so documented paths always match what the build serves. A small registry adds rich detail (request bodies, params, schemas) for the automation-critical operations (auth login, rule create/update/preview, connection introspection); RuleInput and friends are defined as reusable component schemas. - Add docs/examples/Create-OrchestrADRule.ps1: a no-alias PowerShell sample that builds headers/body as typed dictionaries, serializes with ConvertTo-Json, logs in, creates a SyncGroupMembership rule, and runs it. - README: new "API & Automation" section (Swagger + PowerShell), and a "Logging & Retention" section documenting log rotation and the new database maintenance/retention knobs. Tests cover spec generation from a router and registry well-formedness. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>