compliance_checklisted

# COMPLIANCE CHECK **Owner:** QA ## Goal Audit a target (file set or directory) against `.claude/checklists/openai-sdk-compliance-checklist.yaml` and deliver a Markdown report with evidence and actionable fixes. ## Workflow ### 1. Load Inputs - Read `target_path` (file, directory, or list). - Respect context: apply strictly to agent implementations, tools, and orchestration code. ### 2. Evaluate Rules - Process rules top-down (A1 → A11). - Apply `activation_hint` and `stop_condition`: - Stop on first HIGH unless `--exhaustive` is requested. - Stop if findings_count > 25. - Enforce **Kira Constitution** and **OpenAI Agents SDK** standards: - **A1. Primitives Only**: Orchestration uses only `run()`/`Runner.run()` and `handoff()`; no extra verbs like `routeAgent` or `pipeTo`. - **A2. Tool Categories Valid**: Every tool is one of: Function | Hosted | Agent-as-Tool | MCP. - **A3. No Custom Routing**: No bespoke agent-to-agent communication (axios/fetch/custom) beyond SDK patterns. - **A4. Tool Input Schema (Zod)**: All tools define parameters via `tool({ parameters: z.object({...}) })`. - **A5. Structured Outputs (Zod)**: Agents with non-text outputs declare `outputType: z.object({...})`. - **A6. Single RunContext<T>**: One canonical `RunContext<T>` shared across agents/tools/guardrails. - **A7. History Threading**: Conversation history flows via `result.history` → next `run()`. - **A8. Model Settings Casing**: Uses `modelSettings.toolChoice` (camelCase),