[codex] build FlowMemory HQ program manager OS

[FlowmemoryAI]

Summary

• Builds the FlowMemory HQ operating system into a multi-agent program manager layer.
• Adds source-of-truth backlog, agent prompts, PR process, daily runbook, decision workflow, and read-only status reporting.
• Creates and applies GitHub milestones/labels for issues [contracts] Add Foundry configuration for contract test commands #6-[indexer] Promote V0 local RPC reader toward live Base test indexing #55.

Scope

• Issue: HQ operating system program-management pass
• Allowed folders: docs/, .github/, infra/scripts/, README.md, AGENTS.md
• Forbidden folders: subsystem implementation folders outside docs/process scope
• Recommended agent/worktree: E:\FlowMemory\flowmemory-review / HQ Review Agent
• Risk level: Medium

Checks

• git diff --check
• PowerShell syntax parse for infra/scripts/status-report.ps1
• Ran infra/scripts/status-report.ps1
• Verified docs/ISSUE_BACKLOG.md maps issues [contracts] Add Foundry configuration for contract test commands #6-[indexer] Promote V0 local RPC reader toward live Base test indexing #55

Scope Discipline

• I read AGENTS.md.
• I read docs/START_HERE.md.
• I read docs/FLOWMEMORY_HQ_CONTEXT.md.
• I read docs/CURRENT_STATE.md.
• I only edited files in my assigned scope.
• I did not hardcode secrets.
• I did not add production deployment automation unless explicitly scoped.
• I did not add tokenomics or appchain/L1 implementation unless explicitly scoped.
• I did not add dynamic fees, production hook deployment, hardware manufacturing, GPU proofs, verifier economics, or full dashboard implementation unless explicitly scoped.

Risk And Follow-Ups

• Existing open draft PR [codex] Add FlowRouter V0 POC hardware package #56 touches hardware and should be reviewed separately against its issue scope.
• flowmemory-crypto is dirty and should be cleaned, split, or reviewed before assigning unrelated crypto work.
• Milestones and labels were created/applied through gh; reviewers should confirm the GitHub issue board matches docs/ISSUE_BACKLOG.md.

[FlowmemoryAI]

Rootflow / Flow Memory launch-core update added in commit 9522389.\n\nThis PR now includes:\n- docs/ROOTFLOW_V0.md\n- docs/FLOW_MEMORY_V0.md\n- docs/V0_LAUNCH_ACCEPTANCE.md\n- docs/DECISIONS/rootflow-v0.md\n- README/AGENTS/roadmap/current-state/runbook/backlog alignment\n\nCreated launch-core issues #63-#67 for contracts, crypto, indexer, dashboard, and review. The key rule is that Rootflow V0 and Flow Memory V0 are not considered complete until docs/V0_LAUNCH_ACCEPTANCE.md has concrete evidence for each row.

[FlowmemoryAI]

Added commit 3a3eb27 with docs/LAUNCH_CORE_AGENT_GOALS.md.

This gives copy-ready long-running goals for issues #63-#67 and the matching worktrees/PR branches, so builder chats have concrete launch-core instructions tied to the acceptance matrix and audit.

[FlowmemoryAI]

Added commit a0e7881 with docs/reviews/OPEN_PR_MERGE_READINESS.md and updated the Rootflow/Flow Memory acceptance audit with locally verified checks.

Locally verified:

• [codex] Build contracts v0 foundation #57 forge test -> 33 passing
• [codex] Build FlowMemory crypto v0 foundation #60 crypto npm test -> 13 passing; vector validation passed
• [codex] Build indexer verifier v0 fixture package #61 services npm test -> 24 passing; npm run e2e produced 7 observations and 7 reports; whitespace cleanup pushed in 125f84f
• Build FlowMemory Dashboard V0 #62 dashboard npm test -> 4 passing; npm run build passed; whitespace cleanup pushed in 4577968
• Add local FlowMemory devnet prototype #58 devnet cargo test -> 7 passing
• [codex] Add FlowRouter V0 POC hardware package #56 hardware fixture validation passed

The new readiness doc names the merge order and remaining build gaps.