Require workflow-critical agent outputs to be persisted to GitHub artifacts

[jflamb]

Summary

Require agents to post workflow-critical outputs to canonical GitHub artifacts by default, instead of leaving them only in chat/session output.

Problem

Some review and handoff steps have produced correct content in the agent session but did not post it to the relevant GitHub artifact. That breaks discoverability for the next workflow stage and weakens automation because subsequent agents or automation steps may not be able to find the result.

Required rule

If an output affects workflow state, it must be posted to the canonical GitHub artifact:

• PR review findings -> PR comment
• blocked-state handoff -> PR/issue/discussion comment
• design review dispositions -> discussion comment
• implementation verification -> PR comment
• closeout -> issue comment
• merge gate -> PR comment

Chat-only output is acceptable only as a fallback when posting truly fails.
If posting fails, the agent must:

• say that explicitly
• include the exact comment body
• explain why posting failed
• leave a blocked-state handoff instead of claiming the step completed normally

Scope

• Define the persistence rule in the canonical workflow guidance
• Update prompt/template sources so review/handoff/closeout prompts require posting, not optional drafting
• Clarify fallback behavior when posting fails
• Ensure workflow completion criteria depend on persisted artifact state, not just chat output

Acceptance criteria

• Canonical workflow guidance requires workflow-critical outputs to be posted to GitHub artifacts
• Review prompts no longer say "post or draft" for normal operation
• Fallback behavior for post failures is explicit and consistent
• Future workflow automation can rely on GitHub artifacts as the system of record

[github-actions]

Orchestration run — stage transition accepted

Field	Value
Run key	SlateLabs/github-project-automation/26/kickoff/1775324772832
Requested stage	kickoff
Actor	@jflamb
Result	✅ Eligible and gate passed
Actions run	23984221956

[github-actions]

Orchestration run — next stage queued

Field	Value
Run key	SlateLabs/github-project-automation/26/clarification/1775324796861
Requested stage	clarification
Actor	@jflamb
Result	🚀 Next stage queued automatically
Parent run	23984221956

The next stage was dispatched automatically after the current stage passed.

[github-actions]

Orchestration run — stage transition accepted

Field	Value
Run key	SlateLabs/github-project-automation/26/clarification/1775324796861
Requested stage	clarification
Actor	@jflamb
Result	✅ Eligible and gate passed
Actions run	23984229375

[github-actions]

Orchestration run — next stage queued

Field	Value
Run key	SlateLabs/github-project-automation/26/design/1775324819902
Requested stage	design
Actor	@jflamb
Result	🚀 Next stage queued automatically
Parent run	23984229375

The next stage was dispatched automatically after the current stage passed.

[github-actions]

Design discussion scaffold — created

Field	Value
Run key	SlateLabs/github-project-automation/26/design/1775324819902
Actor	@jflamb
Discussion	#32
Result	✅ Discussion created

A design discussion has been created with all required gate headings.
Fill in each section, resolve open questions, and get at least one review comment to pass the design gate.

[github-actions]

Orchestration run — gate not satisfied

Field	Value
Run key	SlateLabs/github-project-automation/26/design/1775324819902
Requested stage	design
Actor	@jflamb
Result	⚠️ Gate conditions not met
Actions run	23984234665

Unmet conditions:

• Discussion Design: Require workflow-critical agent outputs to be persisted to GitHub artifacts #32 has 1 unresolved open question(s) — strike through or mark DEFERRED-TO-PLAN
• Discussion Design: Require workflow-critical agent outputs to be persisted to GitHub artifacts #32 has no comments from anyone other than the author (github-actions) — at least one review comment is required

Waived conditions:

To override, post a comment: GATE-WAIVER: <condition> — <reason> and re-trigger.