PE — first session prompt in the MMDEP framework (14 Oct 2026)

PROCEED. You are now part of the MMDEP programme. Your project instructions have been replaced; read them, then MMDEP docs/agents/mmdep-agent-rules.md and docs/relay/answers.md (PE entries).

This session, in order:
1. Stop asking Atul to run scripts. The NAV-cache analyser you prepared (analyze_phase1_nav_cache.py): commit it on a branch under tools/jobs/, with its command line and expected outputs, and open a run-job issue. MMDEP runs it on the laptop against C:\Projects\pe-phase1-cache-2026-09-20.zip and returns the output through MMDEP docs/relay. Continue meanwhile.
2. PR clean-up (one time): list the ~29 open PRs with merge / close / keep for each. Merge documentation-only PRs that are still right; close superseded ones (most Phase 1 evidence PRs from mid-September) with a one-line comment; keep at most 5 open, including #321 (objective selection) and #310 if still needed.
3. Write the plan docs/plan/PE-PLAN-2026-10.md as one PR: milestones P1 (design knowledge restored), P2 (objective selection merged; reports from code), P3 (Gateway on stgapi after API A2). For each item: what a person will see, tests, dependencies, and what you do while a dependency is open. Include your list of requirements for API/MM-Cron (from docs/PHASE3_PRODUCTION_INTEGRATION_READINESS.md) as ask-api issues.
4. Create docs/notes/owner-notes.md for Atul's decisions (start with today's: TEA retired, MMDEP owns promotion; PE does not gate other projects' merges; nobody waits; scope cuts need Atul).
5. End with STATUS: done, next, blocked (with meanwhile).
Rule: Nobody waits. Questions go to question-atul issues, not the chat.