Roadmap hygiene: reconcile current state, frontend plan, and issue backlog

[Abiorh001]

Parent: #29

Why

Some repo-local status files lag GitHub reality. PR #28 is merged, but .agent-loop/LOOP_STATE.md and .agent-loop/WORK_QUEUE.md in main still describe it as awaiting approval. The new issue backlog also adds a frontend track that should be reflected in roadmap status.

Scope

• Update roadmap/status docs to reflect PR [codex] Implement submission artifact policy foundation #28 merged.
• Update .agent-loop memory only through the repository's zero-trust process.
• Add or reference the frontend issue track in roadmap status.
• Make the current next-step ordering explicit for maintainers and contributors.

Acceptance Criteria

• Roadmap status matches GitHub issue/PR state.
• Frontend is no longer implied as a vague future dashboard only.
• Contributors can tell what is ready now, blocked on backend, and maintainer-owned.
• Markdown links and stale wording checks pass.

Contributor Fit

Maintainer-owned hygiene task. It prevents contributors from following stale roadmap state.