Document how philosophy governs the live lanes

[auscaster]

Please update the public docs so each live lane clearly ties back to automaton's governing philosophy.

Scope:

• docs only
• update docs/flows.md and docs/operations.md
• explain triage before mutation, recommendation before mutation, and receipts over claims
• keep the change bounded to the existing docs site

This should be a single governed PR-sized change.

Retry marker: rerun after scafld schema fix.

Retry marker: rerun after hosted scafld compatibility and triage comment fixes.

Retry marker: rerun after bridge timeout and Actions PR-permission fixes.

Retry marker: rerun after final Actions PR-create permission enablement.

Retry marker: rerun after validated final-answer extraction fix.

Retry marker: rerun after issue-supervisor repo-snapshot grounding.

Retry marker: rerun after task-id normalization and worker-summary persistence.

Retry marker: rerun after bridge transport-resume hardening.

Retry marker: rerun after merge-to-main and compact repo-context handoff.

Retry marker: rerun after OpenAI responses-scope fallback.

Retry marker: rerun after full mainline publish and workflow unification (2026-04-13).

[github-actions]

runx issue supervisor

• Commence: approve
• Next lane: issue-to-pr
• Action: proceed_to_build
• Review target: issue

Thanks for the clear scope. This is triaged as a bounded docs-only change and approved for a single governed PR. The requested work is to update docs/flows.md and docs/operations.md so the live lanes clearly tie back to automaton's governing philosophy, including triage before mutation, recommendation before mutation, and receipts over claims, while keeping the change within the existing docs site.

Rationale: The request is explicit, docs-only, names the target files, lists the concepts that must be covered, and says the work should stay PR-sized. That makes it suitable for one bounded repo-scoped remediation lane without a separate planning phase.

Operator notes:

• The issue body includes multiple retry markers from prior reruns; treat them as operational history, not documentation requirements.
• Keep the scope bounded to the existing docs site and centered on docs/flows.md and docs/operations.md.
• No repo snapshot was provided in this triage step, so the downstream lane should verify current headings and surrounding wording before editing.