docs: add release runbook to AGENTS.md

[itsmiso-ai]

Adds the full release cut process to AGENTS.md so both human and agent operators can follow the same steps.

Covers:

• Branching from up-to-date main
• npm version bump (package.json + package-lock.json)
• Full validation: lint → typecheck → test → build
• PR creation and squash-merge
• Tag and gh release create
• CI image build trigger on tag push

[its-saffron]

AI Automated Review

Analysis engine: MiniMax@https://litellm.jory.dev/v1 (anthropic)

Recommendation

Approve — This is a clean, well-structured documentation PR that adds a Release cut process runbook to AGENTS.md. The content is internally consistent, follows the existing section style, and references real repository infrastructure.

Change-by-change findings

AGENTS.md (+63, -0)

• Section placement: The new ### Release cut process section is appended at the end of the file after the Worker cron prompt migration section, which is a natural location alongside the other operational runbooks (Worker execution contract, Worker cron prompt migration).
• Style consistency: Uses the same ### subsection + numbered steps + bash code fences pattern as the surrounding sections in AGENTS.md.
• Workflow steps are correct and ordered: branch → bump → validate → PR → merge → tag → release. This is a sound release-cut sequence.
• Validation commands (npm run lint, npm run typecheck, npm run test, npm run build) match the Key Commands block at the top of AGENTS.md.
• Image workflow claim: The closing line states the tag push triggers the Build Dispatch Image workflow and publishes to ghcr.io/misospace/dispatch:v<version>. This aligns with .github/workflows/image.yaml (builds/publishes to GHCR on v* tags per the README) and the ghcr host pattern used in README/Dockerfile examples.
• Branch naming: Uses chore/release-v<version> consistently between the local branch command, the gh pr create flags, and the commit message.
• No agent-specific names: The new section uses generic placeholders (<version>), satisfying the "No agent-specific names in generic docs" code standard.

Sources

• PR metadata, diff, and patch (provided in corpus)
• .github/workflows/image.yaml (referenced in repo scan; publishes GHCR images on v* tags)
• README.md (confirms "image workflow builds the Docker image, publishes GHCR images on main and v* tags")
• Repository scan and history (no conflicting release runbook previously existed; latest commit is this PR)

Standards Compliance

• Code Standards #1 (no agent-specific names in generic docs): ✅ Satisfied — only generic placeholders are used.
• Style and structure: ✅ Matches the ### subsection + numbered steps + bash code fences pattern of neighboring sections.
• Validation command references: ✅ All four commands listed in the Key Commands block of AGENTS.md.
• Workflow reference accuracy: ✅ The claimed Build Dispatch Image workflow trigger on v* tag push is consistent with image.yaml and README descriptions.
• Branch/PR/merge/tag convention: ✅ Self-consistent across all steps and matches chore: conventional-commit prefix used elsewhere in the repo history.

No standards violations detected.

Linked Issue Fit

No linked issue references were found in the PR body, so there are no external acceptance criteria to compare against. The PR is self-contained and the stated intent in the body matches the diff exactly: a full release-cut runbook covering branching, version bump, validation, PR creation/merge, tag, and gh release create.

Evidence Provider Findings

No evidence providers were configured for this run. No findings to report.

Tool Harness Findings

Tool harness reported Planned requests: 0 and a planning warning ("Could not parse planning response as JSON"). No actionable tool-derived findings; nothing in the harness output indicates a problem with the PR content.

Unknowns or Needs Verification

• Workflow exact name: The runbook names the workflow Build Dispatch Image. I did not have direct access to the workflow file in the corpus to confirm the workflow name: field string verbatim. README and image.yaml presence in the repo scan confirm a build/publish workflow exists and triggers on v* tags, but if the literal display name differs slightly, a tiny wording tweak may be warranted in a follow-up. Not a blocker for merge.
• CI validation match: The runbook does not explicitly call out that the CI workflow (.github/workflows/ci.yaml) also runs lint/typecheck/test/build on the release PR. This is implicit but could be made explicit in a future revision to make provenance of the validation clearer. Not a blocker.

No blocking unknowns.

[itsmiso-ai]

Adds the full release cut process to AGENTS.md so both human and agent operators can follow the same steps.

Covers:

• Branching from up-to-date main
• npm version bump (package.json + package-lock.json)
• Full validation: lint → typecheck → test → build
• PR creation and squash-merge
• Tag and gh release create
• CI image build trigger on tag push

[its-saffron]

AI Automated Review

Analysis engine: MiniMax@https://litellm.jory.dev/v1 (anthropic)

Recommendation

Approve — This is a clean, well-structured documentation PR that adds a Release cut process runbook to AGENTS.md. The content is internally consistent, follows the existing section style, and references real repository infrastructure.

Change-by-change findings

AGENTS.md (+63, -0)

• Section placement: The new ### Release cut process section is appended at the end of the file after the Worker cron prompt migration section, which is a natural location alongside the other operational runbooks (Worker execution contract, Worker cron prompt migration).
• Style consistency: Uses the same ### subsection + numbered steps + bash code fences pattern as the surrounding sections in AGENTS.md.
• Workflow steps are correct and ordered: branch → bump → validate → PR → merge → tag → release. This is a sound release-cut sequence.
• Validation commands (npm run lint, npm run typecheck, npm run test, npm run build) match the Key Commands block at the top of AGENTS.md.
• Image workflow claim: The closing line states the tag push triggers the Build Dispatch Image workflow and publishes to ghcr.io/misospace/dispatch:v<version>. This aligns with .github/workflows/image.yaml (builds/publishes to GHCR on v* tags per the README) and the ghcr host pattern used in README/Dockerfile examples.
• Branch naming: Uses chore/release-v<version> consistently between the local branch command, the gh pr create flags, and the commit message.
• No agent-specific names: The new section uses generic placeholders (<version>), satisfying the "No agent-specific names in generic docs" code standard.

Sources

• PR metadata, diff, and patch (provided in corpus)
• .github/workflows/image.yaml (referenced in repo scan; publishes GHCR images on v* tags)
• README.md (confirms "image workflow builds the Docker image, publishes GHCR images on main and v* tags")
• Repository scan and history (no conflicting release runbook previously existed; latest commit is this PR)

Standards Compliance

• Code Standards #1 (no agent-specific names in generic docs): ✅ Satisfied — only generic placeholders are used.
• Style and structure: ✅ Matches the ### subsection + numbered steps + bash code fences pattern of neighboring sections.
• Validation command references: ✅ All four commands listed in the Key Commands block of AGENTS.md.
• Workflow reference accuracy: ✅ The claimed Build Dispatch Image workflow trigger on v* tag push is consistent with image.yaml and README descriptions.
• Branch/PR/merge/tag convention: ✅ Self-consistent across all steps and matches chore: conventional-commit prefix used elsewhere in the repo history.

No standards violations detected.

Linked Issue Fit

No linked issue references were found in the PR body, so there are no external acceptance criteria to compare against. The PR is self-contained and the stated intent in the body matches the diff exactly: a full release-cut runbook covering branching, version bump, validation, PR creation/merge, tag, and gh release create.

Evidence Provider Findings

No evidence providers were configured for this run. No findings to report.

Tool Harness Findings

Tool harness reported Planned requests: 0 and a planning warning ("Could not parse planning response as JSON"). No actionable tool-derived findings; nothing in the harness output indicates a problem with the PR content.

Unknowns or Needs Verification

• Workflow exact name: The runbook names the workflow Build Dispatch Image. I did not have direct access to the workflow file in the corpus to confirm the workflow name: field string verbatim. README and image.yaml presence in the repo scan confirm a build/publish workflow exists and triggers on v* tags, but if the literal display name differs slightly, a tiny wording tweak may be warranted in a follow-up. Not a blocker for merge.
• CI validation match: The runbook does not explicitly call out that the CI workflow (.github/workflows/ci.yaml) also runs lint/typecheck/test/build on the release PR. This is implicit but could be made explicit in a future revision to make provenance of the validation clearer. Not a blocker.

No blocking unknowns.

[itsmiso-ai]

Adds the full release cut process to AGENTS.md so both human and agent operators can follow the same steps.

Covers:

• Branching from up-to-date main
• npm version bump (package.json + package-lock.json)
• Full validation: lint → typecheck → test → build
• PR creation and squash-merge
• Tag and gh release create
• CI image build trigger on tag push

[its-saffron]

AI Automated Review

Analysis engine: MiniMax@https://litellm.jory.dev/v1 (anthropic)

Recommendation

Approve — This is a clean, well-structured documentation PR that adds a Release cut process runbook to AGENTS.md. The content is internally consistent, follows the existing section style, and references real repository infrastructure.

Change-by-change findings

AGENTS.md (+63, -0)

• Section placement: The new ### Release cut process section is appended at the end of the file after the Worker cron prompt migration section, which is a natural location alongside the other operational runbooks (Worker execution contract, Worker cron prompt migration).
• Style consistency: Uses the same ### subsection + numbered steps + bash code fences pattern as the surrounding sections in AGENTS.md.
• Workflow steps are correct and ordered: branch → bump → validate → PR → merge → tag → release. This is a sound release-cut sequence.
• Validation commands (npm run lint, npm run typecheck, npm run test, npm run build) match the Key Commands block at the top of AGENTS.md.
• Image workflow claim: The closing line states the tag push triggers the Build Dispatch Image workflow and publishes to ghcr.io/misospace/dispatch:v<version>. This aligns with .github/workflows/image.yaml (builds/publishes to GHCR on v* tags per the README) and the ghcr host pattern used in README/Dockerfile examples.
• Branch naming: Uses chore/release-v<version> consistently between the local branch command, the gh pr create flags, and the commit message.
• No agent-specific names: The new section uses generic placeholders (<version>), satisfying the "No agent-specific names in generic docs" code standard.

Sources

• PR metadata, diff, and patch (provided in corpus)
• .github/workflows/image.yaml (referenced in repo scan; publishes GHCR images on v* tags)
• README.md (confirms "image workflow builds the Docker image, publishes GHCR images on main and v* tags")
• Repository scan and history (no conflicting release runbook previously existed; latest commit is this PR)

Standards Compliance

• Code Standards #1 (no agent-specific names in generic docs): ✅ Satisfied — only generic placeholders are used.
• Style and structure: ✅ Matches the ### subsection + numbered steps + bash code fences pattern of neighboring sections.
• Validation command references: ✅ All four commands listed in the Key Commands block of AGENTS.md.
• Workflow reference accuracy: ✅ The claimed Build Dispatch Image workflow trigger on v* tag push is consistent with image.yaml and README descriptions.
• Branch/PR/merge/tag convention: ✅ Self-consistent across all steps and matches chore: conventional-commit prefix used elsewhere in the repo history.

No standards violations detected.

Linked Issue Fit

No linked issue references were found in the PR body, so there are no external acceptance criteria to compare against. The PR is self-contained and the stated intent in the body matches the diff exactly: a full release-cut runbook covering branching, version bump, validation, PR creation/merge, tag, and gh release create.

Evidence Provider Findings

No evidence providers were configured for this run. No findings to report.

Tool Harness Findings

Tool harness reported Planned requests: 0 and a planning warning ("Could not parse planning response as JSON"). No actionable tool-derived findings; nothing in the harness output indicates a problem with the PR content.

Unknowns or Needs Verification

• Workflow exact name: The runbook names the workflow Build Dispatch Image. I did not have direct access to the workflow file in the corpus to confirm the workflow name: field string verbatim. README and image.yaml presence in the repo scan confirm a build/publish workflow exists and triggers on v* tags, but if the literal display name differs slightly, a tiny wording tweak may be warranted in a follow-up. Not a blocker for merge.
• CI validation match: The runbook does not explicitly call out that the CI workflow (.github/workflows/ci.yaml) also runs lint/typecheck/test/build on the release PR. This is implicit but could be made explicit in a future revision to make provenance of the validation clearer. Not a blocker.

No blocking unknowns.

[itsmiso-ai]

Adds the full release cut process to AGENTS.md so both human and agent operators can follow the same steps.

Covers:

• Branching from up-to-date main
• npm version bump (package.json + package-lock.json)
• Full validation: lint → typecheck → test → build
• PR creation and squash-merge
• Tag and gh release create
• CI image build trigger on tag push

[its-saffron]

AI Automated Review

Analysis engine: MiniMax@https://litellm.jory.dev/v1 (anthropic)

Recommendation

Approve — This is a clean, well-structured documentation PR that adds a Release cut process runbook to AGENTS.md. The content is internally consistent, follows the existing section style, and references real repository infrastructure.

Change-by-change findings

AGENTS.md (+63, -0)

• Section placement: The new ### Release cut process section is appended at the end of the file after the Worker cron prompt migration section, which is a natural location alongside the other operational runbooks (Worker execution contract, Worker cron prompt migration).
• Style consistency: Uses the same ### subsection + numbered steps + bash code fences pattern as the surrounding sections in AGENTS.md.
• Workflow steps are correct and ordered: branch → bump → validate → PR → merge → tag → release. This is a sound release-cut sequence.
• Validation commands (npm run lint, npm run typecheck, npm run test, npm run build) match the Key Commands block at the top of AGENTS.md.
• Image workflow claim: The closing line states the tag push triggers the Build Dispatch Image workflow and publishes to ghcr.io/misospace/dispatch:v<version>. This aligns with .github/workflows/image.yaml (builds/publishes to GHCR on v* tags per the README) and the ghcr host pattern used in README/Dockerfile examples.
• Branch naming: Uses chore/release-v<version> consistently between the local branch command, the gh pr create flags, and the commit message.
• No agent-specific names: The new section uses generic placeholders (<version>), satisfying the "No agent-specific names in generic docs" code standard.

Sources

• PR metadata, diff, and patch (provided in corpus)
• .github/workflows/image.yaml (referenced in repo scan; publishes GHCR images on v* tags)
• README.md (confirms "image workflow builds the Docker image, publishes GHCR images on main and v* tags")
• Repository scan and history (no conflicting release runbook previously existed; latest commit is this PR)

Standards Compliance

• Code Standards #1 (no agent-specific names in generic docs): ✅ Satisfied — only generic placeholders are used.
• Style and structure: ✅ Matches the ### subsection + numbered steps + bash code fences pattern of neighboring sections.
• Validation command references: ✅ All four commands listed in the Key Commands block of AGENTS.md.
• Workflow reference accuracy: ✅ The claimed Build Dispatch Image workflow trigger on v* tag push is consistent with image.yaml and README descriptions.
• Branch/PR/merge/tag convention: ✅ Self-consistent across all steps and matches chore: conventional-commit prefix used elsewhere in the repo history.

No standards violations detected.

Linked Issue Fit

No linked issue references were found in the PR body, so there are no external acceptance criteria to compare against. The PR is self-contained and the stated intent in the body matches the diff exactly: a full release-cut runbook covering branching, version bump, validation, PR creation/merge, tag, and gh release create.

Evidence Provider Findings

No evidence providers were configured for this run. No findings to report.

Tool Harness Findings

Tool harness reported Planned requests: 0 and a planning warning ("Could not parse planning response as JSON"). No actionable tool-derived findings; nothing in the harness output indicates a problem with the PR content.

Unknowns or Needs Verification

• Workflow exact name: The runbook names the workflow Build Dispatch Image. I did not have direct access to the workflow file in the corpus to confirm the workflow name: field string verbatim. README and image.yaml presence in the repo scan confirm a build/publish workflow exists and triggers on v* tags, but if the literal display name differs slightly, a tiny wording tweak may be warranted in a follow-up. Not a blocker for merge.
• CI validation match: The runbook does not explicitly call out that the CI workflow (.github/workflows/ci.yaml) also runs lint/typecheck/test/build on the release PR. This is implicit but could be made explicit in a future revision to make provenance of the validation clearer. Not a blocker.

No blocking unknowns.

[itsmiso-ai]

Adds the full release cut process to AGENTS.md so both human and agent operators can follow the same steps.

Covers:

• Branching from up-to-date main
• npm version bump (package.json + package-lock.json)
• Full validation: lint → typecheck → test → build
• PR creation and squash-merge
• Tag and gh release create
• CI image build trigger on tag push

[its-saffron]

AI Automated Review

Analysis engine: MiniMax@https://litellm.jory.dev/v1 (anthropic)

Recommendation

Approve — This is a clean, well-structured documentation PR that adds a Release cut process runbook to AGENTS.md. The content is internally consistent, follows the existing section style, and references real repository infrastructure.

Change-by-change findings

AGENTS.md (+63, -0)

• Section placement: The new ### Release cut process section is appended at the end of the file after the Worker cron prompt migration section, which is a natural location alongside the other operational runbooks (Worker execution contract, Worker cron prompt migration).
• Style consistency: Uses the same ### subsection + numbered steps + bash code fences pattern as the surrounding sections in AGENTS.md.
• Workflow steps are correct and ordered: branch → bump → validate → PR → merge → tag → release. This is a sound release-cut sequence.
• Validation commands (npm run lint, npm run typecheck, npm run test, npm run build) match the Key Commands block at the top of AGENTS.md.
• Image workflow claim: The closing line states the tag push triggers the Build Dispatch Image workflow and publishes to ghcr.io/misospace/dispatch:v<version>. This aligns with .github/workflows/image.yaml (builds/publishes to GHCR on v* tags per the README) and the ghcr host pattern used in README/Dockerfile examples.
• Branch naming: Uses chore/release-v<version> consistently between the local branch command, the gh pr create flags, and the commit message.
• No agent-specific names: The new section uses generic placeholders (<version>), satisfying the "No agent-specific names in generic docs" code standard.

Sources

• PR metadata, diff, and patch (provided in corpus)
• .github/workflows/image.yaml (referenced in repo scan; publishes GHCR images on v* tags)
• README.md (confirms "image workflow builds the Docker image, publishes GHCR images on main and v* tags")
• Repository scan and history (no conflicting release runbook previously existed; latest commit is this PR)

Standards Compliance

• Code Standards #1 (no agent-specific names in generic docs): ✅ Satisfied — only generic placeholders are used.
• Style and structure: ✅ Matches the ### subsection + numbered steps + bash code fences pattern of neighboring sections.
• Validation command references: ✅ All four commands listed in the Key Commands block of AGENTS.md.
• Workflow reference accuracy: ✅ The claimed Build Dispatch Image workflow trigger on v* tag push is consistent with image.yaml and README descriptions.
• Branch/PR/merge/tag convention: ✅ Self-consistent across all steps and matches chore: conventional-commit prefix used elsewhere in the repo history.

No standards violations detected.

Linked Issue Fit

No linked issue references were found in the PR body, so there are no external acceptance criteria to compare against. The PR is self-contained and the stated intent in the body matches the diff exactly: a full release-cut runbook covering branching, version bump, validation, PR creation/merge, tag, and gh release create.

Evidence Provider Findings

No evidence providers were configured for this run. No findings to report.

Tool Harness Findings

Tool harness reported Planned requests: 0 and a planning warning ("Could not parse planning response as JSON"). No actionable tool-derived findings; nothing in the harness output indicates a problem with the PR content.

Unknowns or Needs Verification

• Workflow exact name: The runbook names the workflow Build Dispatch Image. I did not have direct access to the workflow file in the corpus to confirm the workflow name: field string verbatim. README and image.yaml presence in the repo scan confirm a build/publish workflow exists and triggers on v* tags, but if the literal display name differs slightly, a tiny wording tweak may be warranted in a follow-up. Not a blocker for merge.
• CI validation match: The runbook does not explicitly call out that the CI workflow (.github/workflows/ci.yaml) also runs lint/typecheck/test/build on the release PR. This is implicit but could be made explicit in a future revision to make provenance of the validation clearer. Not a blocker.

No blocking unknowns.

[itsmiso-ai]

Adds the full release cut process to AGENTS.md so both human and agent operators can follow the same steps.

Covers:

• Branching from up-to-date main
• npm version bump (package.json + package-lock.json)
• Full validation: lint → typecheck → test → build
• PR creation and squash-merge
• Tag and gh release create
• CI image build trigger on tag push

[its-saffron]

AI Automated Review

Analysis engine: MiniMax@https://litellm.jory.dev/v1 (anthropic)

Recommendation

Approve — This is a clean, well-structured documentation PR that adds a Release cut process runbook to AGENTS.md. The content is internally consistent, follows the existing section style, and references real repository infrastructure.

Change-by-change findings

AGENTS.md (+63, -0)

• Section placement: The new ### Release cut process section is appended at the end of the file after the Worker cron prompt migration section, which is a natural location alongside the other operational runbooks (Worker execution contract, Worker cron prompt migration).
• Style consistency: Uses the same ### subsection + numbered steps + bash code fences pattern as the surrounding sections in AGENTS.md.
• Workflow steps are correct and ordered: branch → bump → validate → PR → merge → tag → release. This is a sound release-cut sequence.
• Validation commands (npm run lint, npm run typecheck, npm run test, npm run build) match the Key Commands block at the top of AGENTS.md.
• Image workflow claim: The closing line states the tag push triggers the Build Dispatch Image workflow and publishes to ghcr.io/misospace/dispatch:v<version>. This aligns with .github/workflows/image.yaml (builds/publishes to GHCR on v* tags per the README) and the ghcr host pattern used in README/Dockerfile examples.
• Branch naming: Uses chore/release-v<version> consistently between the local branch command, the gh pr create flags, and the commit message.
• No agent-specific names: The new section uses generic placeholders (<version>), satisfying the "No agent-specific names in generic docs" code standard.

Sources

• PR metadata, diff, and patch (provided in corpus)
• .github/workflows/image.yaml (referenced in repo scan; publishes GHCR images on v* tags)
• README.md (confirms "image workflow builds the Docker image, publishes GHCR images on main and v* tags")
• Repository scan and history (no conflicting release runbook previously existed; latest commit is this PR)

Standards Compliance

• Code Standards #1 (no agent-specific names in generic docs): ✅ Satisfied — only generic placeholders are used.
• Style and structure: ✅ Matches the ### subsection + numbered steps + bash code fences pattern of neighboring sections.
• Validation command references: ✅ All four commands listed in the Key Commands block of AGENTS.md.
• Workflow reference accuracy: ✅ The claimed Build Dispatch Image workflow trigger on v* tag push is consistent with image.yaml and README descriptions.
• Branch/PR/merge/tag convention: ✅ Self-consistent across all steps and matches chore: conventional-commit prefix used elsewhere in the repo history.

No standards violations detected.

Linked Issue Fit

No linked issue references were found in the PR body, so there are no external acceptance criteria to compare against. The PR is self-contained and the stated intent in the body matches the diff exactly: a full release-cut runbook covering branching, version bump, validation, PR creation/merge, tag, and gh release create.

Evidence Provider Findings

No evidence providers were configured for this run. No findings to report.

Tool Harness Findings

Tool harness reported Planned requests: 0 and a planning warning ("Could not parse planning response as JSON"). No actionable tool-derived findings; nothing in the harness output indicates a problem with the PR content.

Unknowns or Needs Verification

• Workflow exact name: The runbook names the workflow Build Dispatch Image. I did not have direct access to the workflow file in the corpus to confirm the workflow name: field string verbatim. README and image.yaml presence in the repo scan confirm a build/publish workflow exists and triggers on v* tags, but if the literal display name differs slightly, a tiny wording tweak may be warranted in a follow-up. Not a blocker for merge.
• CI validation match: The runbook does not explicitly call out that the CI workflow (.github/workflows/ci.yaml) also runs lint/typecheck/test/build on the release PR. This is implicit but could be made explicit in a future revision to make provenance of the validation clearer. Not a blocker.

No blocking unknowns.

[itsmiso-ai]

Adds the full release cut process to AGENTS.md so both human and agent operators can follow the same steps.

Covers:

• Branching from up-to-date main
• npm version bump (package.json + package-lock.json)
• Full validation: lint → typecheck → test → build
• PR creation and squash-merge
• Tag and gh release create
• CI image build trigger on tag push

[its-saffron]

AI Automated Review

Analysis engine: MiniMax@https://litellm.jory.dev/v1 (anthropic)

Recommendation

Approve — This is a clean, well-structured documentation PR that adds a Release cut process runbook to AGENTS.md. The content is internally consistent, follows the existing section style, and references real repository infrastructure.

Change-by-change findings

AGENTS.md (+63, -0)

• Section placement: The new ### Release cut process section is appended at the end of the file after the Worker cron prompt migration section, which is a natural location alongside the other operational runbooks (Worker execution contract, Worker cron prompt migration).
• Style consistency: Uses the same ### subsection + numbered steps + bash code fences pattern as the surrounding sections in AGENTS.md.
• Workflow steps are correct and ordered: branch → bump → validate → PR → merge → tag → release. This is a sound release-cut sequence.
• Validation commands (npm run lint, npm run typecheck, npm run test, npm run build) match the Key Commands block at the top of AGENTS.md.
• Image workflow claim: The closing line states the tag push triggers the Build Dispatch Image workflow and publishes to ghcr.io/misospace/dispatch:v<version>. This aligns with .github/workflows/image.yaml (builds/publishes to GHCR on v* tags per the README) and the ghcr host pattern used in README/Dockerfile examples.
• Branch naming: Uses chore/release-v<version> consistently between the local branch command, the gh pr create flags, and the commit message.
• No agent-specific names: The new section uses generic placeholders (<version>), satisfying the "No agent-specific names in generic docs" code standard.

Sources

• PR metadata, diff, and patch (provided in corpus)
• .github/workflows/image.yaml (referenced in repo scan; publishes GHCR images on v* tags)
• README.md (confirms "image workflow builds the Docker image, publishes GHCR images on main and v* tags")
• Repository scan and history (no conflicting release runbook previously existed; latest commit is this PR)

Standards Compliance

• Code Standards #1 (no agent-specific names in generic docs): ✅ Satisfied — only generic placeholders are used.
• Style and structure: ✅ Matches the ### subsection + numbered steps + bash code fences pattern of neighboring sections.
• Validation command references: ✅ All four commands listed in the Key Commands block of AGENTS.md.
• Workflow reference accuracy: ✅ The claimed Build Dispatch Image workflow trigger on v* tag push is consistent with image.yaml and README descriptions.
• Branch/PR/merge/tag convention: ✅ Self-consistent across all steps and matches chore: conventional-commit prefix used elsewhere in the repo history.

No standards violations detected.

Linked Issue Fit

No linked issue references were found in the PR body, so there are no external acceptance criteria to compare against. The PR is self-contained and the stated intent in the body matches the diff exactly: a full release-cut runbook covering branching, version bump, validation, PR creation/merge, tag, and gh release create.

Evidence Provider Findings

No evidence providers were configured for this run. No findings to report.

Tool Harness Findings

Tool harness reported Planned requests: 0 and a planning warning ("Could not parse planning response as JSON"). No actionable tool-derived findings; nothing in the harness output indicates a problem with the PR content.

Unknowns or Needs Verification

• Workflow exact name: The runbook names the workflow Build Dispatch Image. I did not have direct access to the workflow file in the corpus to confirm the workflow name: field string verbatim. README and image.yaml presence in the repo scan confirm a build/publish workflow exists and triggers on v* tags, but if the literal display name differs slightly, a tiny wording tweak may be warranted in a follow-up. Not a blocker for merge.
• CI validation match: The runbook does not explicitly call out that the CI workflow (.github/workflows/ci.yaml) also runs lint/typecheck/test/build on the release PR. This is implicit but could be made explicit in a future revision to make provenance of the validation clearer. Not a blocker.

No blocking unknowns.

[itsmiso-ai]

Adds the full release cut process to AGENTS.md so both human and agent operators can follow the same steps.

Covers:

• Branching from up-to-date main
• npm version bump (package.json + package-lock.json)
• Full validation: lint → typecheck → test → build
• PR creation and squash-merge
• Tag and gh release create
• CI image build trigger on tag push

[its-saffron]

AI Automated Review

Analysis engine: MiniMax@https://litellm.jory.dev/v1 (anthropic)

Recommendation

Approve — This is a clean, well-structured documentation PR that adds a Release cut process runbook to AGENTS.md. The content is internally consistent, follows the existing section style, and references real repository infrastructure.

Change-by-change findings

AGENTS.md (+63, -0)

• Section placement: The new ### Release cut process section is appended at the end of the file after the Worker cron prompt migration section, which is a natural location alongside the other operational runbooks (Worker execution contract, Worker cron prompt migration).
• Style consistency: Uses the same ### subsection + numbered steps + bash code fences pattern as the surrounding sections in AGENTS.md.
• Workflow steps are correct and ordered: branch → bump → validate → PR → merge → tag → release. This is a sound release-cut sequence.
• Validation commands (npm run lint, npm run typecheck, npm run test, npm run build) match the Key Commands block at the top of AGENTS.md.
• Image workflow claim: The closing line states the tag push triggers the Build Dispatch Image workflow and publishes to ghcr.io/misospace/dispatch:v<version>. This aligns with .github/workflows/image.yaml (builds/publishes to GHCR on v* tags per the README) and the ghcr host pattern used in README/Dockerfile examples.
• Branch naming: Uses chore/release-v<version> consistently between the local branch command, the gh pr create flags, and the commit message.
• No agent-specific names: The new section uses generic placeholders (<version>), satisfying the "No agent-specific names in generic docs" code standard.

Sources

• PR metadata, diff, and patch (provided in corpus)
• .github/workflows/image.yaml (referenced in repo scan; publishes GHCR images on v* tags)
• README.md (confirms "image workflow builds the Docker image, publishes GHCR images on main and v* tags")
• Repository scan and history (no conflicting release runbook previously existed; latest commit is this PR)

Standards Compliance

• Code Standards #1 (no agent-specific names in generic docs): ✅ Satisfied — only generic placeholders are used.
• Style and structure: ✅ Matches the ### subsection + numbered steps + bash code fences pattern of neighboring sections.
• Validation command references: ✅ All four commands listed in the Key Commands block of AGENTS.md.
• Workflow reference accuracy: ✅ The claimed Build Dispatch Image workflow trigger on v* tag push is consistent with image.yaml and README descriptions.
• Branch/PR/merge/tag convention: ✅ Self-consistent across all steps and matches chore: conventional-commit prefix used elsewhere in the repo history.

No standards violations detected.

Linked Issue Fit

No linked issue references were found in the PR body, so there are no external acceptance criteria to compare against. The PR is self-contained and the stated intent in the body matches the diff exactly: a full release-cut runbook covering branching, version bump, validation, PR creation/merge, tag, and gh release create.

Evidence Provider Findings

No evidence providers were configured for this run. No findings to report.

Tool Harness Findings

Tool harness reported Planned requests: 0 and a planning warning ("Could not parse planning response as JSON"). No actionable tool-derived findings; nothing in the harness output indicates a problem with the PR content.

Unknowns or Needs Verification

• Workflow exact name: The runbook names the workflow Build Dispatch Image. I did not have direct access to the workflow file in the corpus to confirm the workflow name: field string verbatim. README and image.yaml presence in the repo scan confirm a build/publish workflow exists and triggers on v* tags, but if the literal display name differs slightly, a tiny wording tweak may be warranted in a follow-up. Not a blocker for merge.
• CI validation match: The runbook does not explicitly call out that the CI workflow (.github/workflows/ci.yaml) also runs lint/typecheck/test/build on the release PR. This is implicit but could be made explicit in a future revision to make provenance of the validation clearer. Not a blocker.

No blocking unknowns.