openclaw - 💡(How to fix) Fix Add collapsible agent-created PR guidance to the PR template

Problem

Openclaw's PR template already captures intent, proof, risk, and current review state, and it notes that ClawSweeper and Barnacle use the PR body to understand the change.

However, the template does not currently give agent-created PRs a clear PR creation contract.

This matters for ClawSweeper-created or agent-created PRs because maintainers need to know:

• what issue, command, comment, or workflow authorized the PR;
• whether the PR came from a ClawSweeper command such as /clawsweeper implement, /clawsweeper build, /clawsweeper fix, or @clawsweeper create pr;
• whether the branch allows maintainer edits;
• whether the template headings were preserved for reviewer and automation parsing;
• whether the PR is actually ready for review or still waiting on proof, validation, or risk notes.

One specific missing instruction: agent-created PRs should allow maintainer edits whenever the branch source supports it. For GitHub API/tooling this means setting maintainer_can_modify: true. In the GitHub UI this maps to leaving “Allow edits by maintainers” enabled.

Goal

Add a short collapsible agent-created PR guidance section near the bottom of .github/pull_request_template.md.

The guidance should be visible to agents and maintainers without making the main human-facing template longer.

Proposed placement

Place this after the existing Current review state guidance block, near the bottom of the PR template.

Proposed content

<details>
<summary>Agent-created PR guidance</summary>

If this PR was created by ClawSweeper, Codex, another agent, or a maintainer-operated automation lane:

- Keep the standard PR template headings intact. Maintainers, ClawSweeper, and Barnacle use these sections as durable review state.
- Link the issue, PR comment, maintainer command, or workflow run that authorized the work.
- When creating the PR, allow maintainer edits whenever the branch source supports it.
  - GitHub API/tooling: set `maintainer_can_modify: true`.
  - GitHub UI: leave “Allow edits by maintainers” enabled.
- If this came from a ClawSweeper issue implementation command such as `/clawsweeper implement`, `/clawsweeper build`, `/clawsweeper fix`, or `@clawsweeper create pr`, say so in the linked context or current review state.
- Do not mark the PR ready for review until the required proof, validation, and risk sections are filled in.
- If the branch cannot be edited by maintainers, say that explicitly in `Current review state` and explain whether a replacement PR may be needed.

</details>

Acceptance criteria

• .github/pull_request_template.md has a collapsible agent-created PR guidance section near the bottom.
• The section says agent-created PRs should preserve the standard template headings.
• The section says to link the authorizing issue, PR comment, maintainer command, or workflow run.
• The section explicitly says to enable maintainer edits when possible.
• The section names the GitHub API/tooling field: maintainer_can_modify: true.
• The section maps that to the GitHub UI wording: “Allow edits by maintainers.”
• The section mentions relevant ClawSweeper issue implementation commands, including /clawsweeper implement, /clawsweeper build, /clawsweeper fix, and @clawsweeper create pr.
• The section says not to mark the PR ready for review until proof, validation, and risk sections are filled in.
• The section says uneditable branches should be disclosed in Current review state.
• The update does not restructure the rest of the PR template.

Non-goals

• Do not split the PR template into quick/full templates in this issue.
• Do not document the full ClawSweeper command system here.
• Do not change ClawSweeper command behavior in this issue.
• Do not add PR template validation in this issue.