Update to codex-sdlc

{
  "description": "Use when a PM delivery assignment delegates a web or mobile implementation, target-specific experience coverage, API/design gap, or frontend evidence handoff.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 224
    },
    {
      "relative_path": "examples/mobile-full-task-response.md",
      "size_in_bytes": 2177
    },
    {
      "relative_path": "examples/web-full-task-response.md",
      "size_in_bytes": 2043
    },
    {
      "relative_path": "references/delivery-report-contract.md",
      "size_in_bytes": 4524
    },
    {
      "relative_path": "references/evidence-contract.md",
      "size_in_bytes": 954
    },
    {
      "relative_path": "references/mobile-rules.md",
      "size_in_bytes": 524
    },
    {
      "relative_path": "references/role-contract.md",
      "size_in_bytes": 1427
    },
    {
      "relative_path": "references/web-rules.md",
      "size_in_bytes": 506
    }
  ],
  "name": "sdlc-frontend",
  "skill_md_contents": "---\nname: sdlc-frontend\ndescription: Use when a PM delivery assignment delegates a web or mobile implementation, target-specific experience coverage, API/design gap, or frontend evidence handoff.\n---\n\n# SDLC frontend\n\nFor a normal 1.0.0 runtime assignment, use the prepared task packet and [runtime-assisted delivery](../sdlc-pm/references/task-operations.md). Implement only its selected web/mobile scope, produce substantive artifacts, collect assigned checks with `check-task`, and give actual requirement/capability outcomes and product changes to `handoff-task`. Return the saved report path and status; the runtime generates hashes and metadata. Never approve your own gate or complete the task. The strict envelope rules below apply to an explicitly supplied legacy evaluator stimulus or manual delivery contract.\n\nRead these references before responding:\n\n- `references/role-contract.md`\n- `references/delivery-report-contract.md`\n- `references/evidence-contract.md`\n- `references/web-rules.md` for target `web`, or `references/mobile-rules.md` for target `mobile`\n- `examples/web-full-task-response.md` for target `web`, or `examples/mobile-full-task-response.md` for target `mobile`\n\nConsume exactly one complete typed `structured_delivery_evaluation`: `assignment`, `authority_snapshot`, `authority_integrity`, and `artifact_integrity`. Treat every typed field as authoritative; do not infer control state from narrative prose. `artifact_integrity` is the sole authority for revision and SHA-256 metadata of produced artifacts.\n\nReturn exactly one `delivery_report` inside the closed response envelope. Do not add a preface, explanation, or trailing text. Preserve assignment identity and mirror every controlled collection exactly. Use the normative disposition order from the report contract. Never request `completed`.\n\nWork only for the selected target and only beneath `allowed_write_roots`. When the assignment declares `repository`, resolve every non-artifact source, test, and generated path in that mapped checkout, include the repository ID on product writes, and leave coordinator `.sdlc` artifacts in the coordinator checkout. Do not invent API fields, design decisions, approvals, artifacts, evidence, questions, or target coverage.\n"
}