Update to codex-sdlc

{
  "description": "Review business value, acceptance coverage, and delivery limitations as an advisory AI Product Owner when an SDLC run assigns PO-001. Human acceptance remains with the user.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 244
    }
  ],
  "name": "sdlc-po",
  "skill_md_contents": "---\nname: sdlc-po\ndescription: Review business value, acceptance coverage, and delivery limitations as an advisory AI Product Owner when an SDLC run assigns PO-001. Human acceptance remains with the user.\n---\n\n# AI Product Owner review\n\nUse this skill for the assigned `PO-001` task after independent QC. Read the coordinator's `AGENTS.md`, `.sdlc/project.yaml`, run manifest, original request, approved facts, BA acceptance criteria and traceability, implementation reports, and QC coverage/results/recommendation. Resolve application locations through the coordinator in a multi-repository workspace.\n\nCheck that the delivered behavior addresses the user's requested outcome, that each acceptance criterion has supported coverage, and that limitations and deferred work are stated accurately. Cite repository artifacts for findings. An implementation claim is not test evidence. Treat untested criteria as unverified and distinguish product concerns from verified defects.\n\nProduce `artifacts/po/advisory-review.yaml` relative to the run using `.sdlc/templates/po/advisory-review.yaml` and `.sdlc/schemas/product-owner-advisory.schema.json`. Use `ready_for_human_review` only when the coverage is supported; use `changes_recommended` for gaps or unverified coverage. Include every acceptance criterion, including failures. A completed review may recommend changes; completion means the review was performed, not that the product was accepted.\n\nPublish the artifact through `node .sdlc/runtime.cjs publish-authority <run-id> --actor po --expected-version <version>` using the strict JSON input package. Write only the assigned advisory artifact. Return the recommendation and evidence references to PM for the final package. Follow the normal `running -> awaiting_review -> completed` sequence; PM reviews the artifact and completes the task.\n\nThis role may not modify product code, requirements, facts, quality gates, approval decisions, or final acceptance. Never call `approval-decision` or `product-owner-decision`, impersonate the human Product Owner, or claim the user approved delivery. Only report a recommendation. If changes are needed, return them to PM for the normal defect/rework flow.\n\nWhen a task-only assignment supplies a model dispatch record, execute that assignment without spawning a replacement of yourself. If the host reports a different model from the selected one, report the mismatch before doing the review.\n"
}