Update to Stride AI

{
  "description": "Finish the Stride story you are working on: check it against its acceptance criteria, record what changed, and move it to In Review.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 43
    }
  ],
  "name": "done",
  "skill_md_contents": "---\nname: \"done\"\ndescription: \"Finish the Stride story you are working on: check it against its acceptance criteria, record what changed, and move it to In Review.\"\n---\n\n# Finish the current Stride story\n\nStride is your team's delivery record. Use its MCP tools to read and update\nthe story. Their names end in the tool name: `update_story_status` appears as\n`stride.update_story_status` or `stride_update_story_status`, depending on\nyour agent.\n\nIf the user named a story key in their message, that is the story.\n\n1. **Find the story**: the ticket key the user named; else the story you\n   picked up in this conversation; else the key in the current git branch\n   name (`orb-526-export-csv` is `ORB-526`); else ask. Read it with\n   `get_story_context` so you have its acceptance criteria. If Stride's tools\n   are missing or not authorized, ask the user to open Stride AI in Plugins (`/plugins` in Codex CLI, or Plugins in ChatGPT) and connect it when prompted. A browser window opens to sign in to Stride.\n2. **Check the work.** Run the repository's own tests and linters for the\n   code you changed. If anything fails, report it and stop, unless the user\n   tells you to go on.\n3. **Check every acceptance criterion** against the change, and list each as\n   met, or not met with the reason.\n4. **Commit, if the user wants it.** If the changes are not committed yet,\n   ask whether to commit them; if yes, commit on the story's branch with a\n   message that starts with the key (`ORB-526: ...`). Push and open a pull\n   request only when the user asks for it. When GitHub is connected to\n   Stride, a branch or pull request whose name contains the key links to the\n   story by itself.\n5. **Record it in Stride.**\n   - Every criterion met: call `update_story_status` with the key, status\n     `IN_REVIEW`, and a comment that says what changed, which tests you ran,\n     and the pull request URL if there is one.\n   - Some not met: leave the status as it is, add a comment to the story\n     with `create_comment` (entity type `story`) saying what is done and what\n     remains, and ask the user how to go on.\n   If Stride reports a conflict because a person edited the story, read it\n   again with `get_story` and retry once. Never pass `force` without the\n   user's explicit approval.\n6. **Tell the user where the story stands**, with its key. To pick up the\n   next one, they can run `$stride:next`.\n"
}