[issue-to-pr] Clarify live PR triage behavior in docs

[auscaster]

Objective

Clarify in the public automaton docs that PR triage comments can run against real PRs, including draft PRs opened by automaton lanes.

Acceptance Criteria

• Update the docs so the PR triage behavior is clearly described.
• Keep the change docs-only.
• npm run docs:build should still pass.

Context

Relevant pages likely include docs/flows.md, docs/dogfood.md, or docs/operations.md.

Safety Constraints

No workflow logic changes. No secret handling changes. No unrelated file churn.

[auscaster]

Opened draft PR for this run: #108

[auscaster]

runx issue triage

• Commence: approve
• Next lane: issue-to-pr
• Action: proceed_to_build
• Worker fanout: 1

Thanks — this looks bounded enough for a docs-only PR. I’ll treat it as a clarification task to make the public docs explicitly say that PR triage comments can run against real PRs, including draft PRs opened by automaton lanes. I’ll keep the scope limited to docs and use npm run docs:build as the verification step.

Rationale: The issue is tightly scoped to one repository, limited to documentation, includes clear acceptance criteria, and has explicit safety constraints against workflow or secret-handling changes. That makes it suitable for one governed repo-scoped PR rather than a larger planning pass.

Operator notes:

• Confirm the exact doc location from the pages named in the issue before editing.
• Keep the change limited to documentation only.
• Verify the published wording matches current behavior rather than introducing a new behavioral claim.
• Run npm run docs:build as the stated validation step.

A matching draft PR is already open, so this run reused it instead of opening another one.

• existing draft PR: [runx] resolve issue #2 (01) #108

Issue Fingerprint: e133db5be54f544e