Inspect the live issue-catalog Actions worker over SSH with ~/.ssh/aiplay-agentsweb; use a2 only if named. Verify SSH on an issue worker before editing its workflow YAML.
Open a real test issue automatically after changing the issue catalog workflow. Post the banner, 10–30-minute estimate, and Actions link before analysis. Merge eligible catalog branches directly by default; create an open PR only when manual merge is enabled. Publish the commit, manual PR, or recovery branch and the issue report, including branch README links for added games, before the owner-only 30-minute SSH hold. Keep the same worker and tunnel alive during the hold, including after analysis or publication failure. Skip the hold for non-owner issues. During analysis, SSH into the issue worker; inspect OpenCode records, logs, and processes; and assess progress directly. Report publication and issue-comment links as soon as they appear. Do not wait for the idle period to finish.
Use the game discovery dataset as a candidate-game reference. Verify entries before adding them to the catalog.
Use the local OpenCode source checkout at ../ChatGPT/opencode. Refer to the upstream repository for its GitHub page.
Use the VibeFin GitHub account for writes to repositories in the SubmitGame organization. Prefix each remote write with GH_TOKEN="$(gh auth token --hostname github.com --user VibeFin)".
Copy every live OpenCode session URL printed by scripts/test-oc.sh immediately into a visible chat response as a clickable Markdown link. Include every run link again in the final response. Return after launch; inspect per-run result.json only when asked for outcomes.
-
Read Reddit submissions before changing the Devvit integration.
-
Read Issue catalog publishing before changing issue publication.
-
Read OpenCode batch testing before changing the batch runner.
-
Read Submit-game button before changing the README call to action.
-
Read SVG parallax banner before changing the animated banner.
-
Read Issue-analysis animation before changing the layered issue banner.
-
Read Detective banner concept before changing the dramatic alternate banner.
-
Read Arcane game detective before changing the moonlit robot animation.
- Don't write or run unit tests, mock tests, or static analysis.
- Don't use mockups instead of a real end-to-end run.
- Don't ask the user to test or analyze; do it directly.
- Don't finish without running and analyzing the end-to-end flow.