Refresh Flow README positioning

[jmcte]

Summary

• Replace bootstrap-derived README boilerplate with Flow-specific positioning.
• Document the protocol surface: state machine, worker lanes, autonomy classes, PR-first queue policy, and merge gate.
• Add a repository map and validation commands that point at the actual Flow artifacts.

Governing Issue

No issue linked; public README representation cleanup from the org profile audit.

Validation

• Relevant local checks passed
  • python3 -m json.tool schemas/issue-contract.schema.json >/dev/null
  • python3 -m json.tool schemas/pr-contract.schema.json >/dev/null
  • python3 -m py_compile scripts/flow/inspect_repo_flow.py
• Required PR checks are expected to satisfy CI Gate
• Skipped checks are explained below
  • Documentation-only change; no product runtime tests apply.

Bootstrap Governance

• Changes are scoped to the linked issue
  • No issue linked; this is a README-only public representation cleanup.
• Contributor or PR guidance changes are reflected in CONTRIBUTING.md, .github/PULL_REQUEST_TEMPLATE.md, and docs/bootstrap/onboarding.md when applicable
  • Not applicable; no contributor or PR contract changes.
• Auto-merge is enabled, or GitHub plan-limit evidence is recorded and the fallback merge-readiness policy applies
• No real secrets, runtime auth, or machine-local env files are committed

Flow Contract

• Owner lane: Apollo
• Repair owner: Hephaestus
• Autonomy class: Class 1 - Safe autonomous
• Risk class: Low, documentation-only

Flow Merge Readiness

• Every blocker has a next actor and next action
• No active blocking requested changes remain
• Non-author approval is present when required
• Auto-merge is appropriate when gates pass

Merge Automation

• Auto-merge is enabled, or the reason it is unavailable or unsafe is noted below

Notes

• Auto-merge and approval state must be checked after PR creation.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 9eb8f093c7

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".