Complete Gotcha issue CLI workflow

AGENTS.md

@@ -2,14 +2,21 @@
 
 ## Gitea issue workflow
 
-Use the `tea` command-line tool as the preferred way to list, inspect, create,
-and update Gitea issues. Run it from the repository root so it can use the
-configured remote, for example `tea issues` or `tea issues 1`.
+Use this repository's `gotcha` CLI to list, inspect, create, update, comment on,
+and close Gitea issues. Run it from the repository root so the configured Git
+remote selects the server and repository:
 
-Run issue-detail commands directly, for example `tea issues 7`. In a sandboxed
-runner, grant network access before invoking `tea`. Without DNS/network access,
-the current `tea` detail path may panic inside Gitea SDK version handling
-instead of returning the underlying connection error.
+```sh
+cargo run -q -p gotcha-cli -- issue list
+cargo run -q -p gotcha-cli -- issue list --milestones "first feature complete release"
+cargo run -q -p gotcha-cli -- issue show 7
+cargo run -q -p gotcha-cli -- issue comment 7 < comment.txt
+cargo run -q -p gotcha-cli -- issue close 7
+```
+
+Use `gotcha issue list --help` for state, kind, keyword, label, milestone,
+author, assignee, mention, date, and pagination filters. Grant network access
+before invoking commands that contact Gitea in a sandboxed runner.
 
 ## Required pre-commit gates
 
@@ -114,6 +121,20 @@ iPhone (currently `xcrun simctl boot "iPhone 17 Pro"`) and open Simulator.
 CoreSimulator access may require running `xcodebuild` and `simctl` outside the
 workspace sandbox.
 
+## Post-issue release deployment
+
+After an issue is verified, committed, pushed, commented on, and closed, deploy
+the completed version according to the code it changes:
+
+- For CLI changes, build `gotcha-cli` in release mode and install the resulting
+  `gotcha` executable in `~/.local/bin/` so the command is available on `PATH`.
+- For iOS app changes, install the completed app on the currently paired iPhone.
+- The Gitea crate is shared by the CLI and iOS app, so changes to that crate also
+  require installing the completed app on the paired iPhone.
+
+A purely CLI change does not require an iPhone deployment. If an issue changes
+both release surfaces, perform both deployments.
+
 ## Generated build data
 
 Use Xcode's default DerivedData location; do not pass `-derivedDataPath`.