plan: schema-v2 and hints-v3 execution plans

[HumanBean17]

Summary

• Adds plans/PLAN-SCHEMA-V2.md and plans/CURSOR-PROMPTS-SCHEMA-V2.md for PR-A/B/C (EDGE_SCHEMA, ontology v14, HTTP_CALLS Client→Route, Producer + ASYNC_CALLS flip).
• Adds plans/PLAN-HINTS-V3.md and plans/CURSOR-PROMPTS-HINTS-V3.md for PR-D (EDGE_SCHEMA-driven empty neighbors hints).
• Implements the plan-artefact gates described in docs/PROPOSES-ORDER.md and SCHEMA-V2 Decision 29.

Test plan

• Docs-only change; CI should skip pytest per paths-filter.
• Review PR breakdown tables, per-PR test names, and sentinel grep contracts before merging.
• After merge: SCHEMA-V2 PR-A implementation may start (HINTS-V3 propose already on master).

Made with Cursor

[HumanBean17]

Review summary

Verdict: approve with small doc fixes (before or immediately after merge).

This is the right artefact at the right time — satisfies Decision 29 / docs/PROPOSES-ORDER.md Phase 2 so SCHEMA-V2 PR-A can start. Structure matches completed PLAN-* / CURSOR-PROMPTS-* pairs; sequencing (A→B→C→D), sentinel greps, and verbatim test names are strong.

---

Recommended fixes on this PR (or tiny follow-up)

1. typical_traversals shape conflict — propose/SCHEMA-V2-PROPOSE.md Appendix A uses tuple[str, ...]; propose/HINTS-V3-PROPOSE.md §3.5 and these plans use dict[str, str] (role keys). PR-A should lock one line in PLAN-SCHEMA-V2.md + CURSOR-PROMPTS-SCHEMA-V2.md, e.g. PR-A contract: role-keyed dict[str, str] per HINTS-V3 §3.5; SCHEMA Appendix A tuple examples are illustrative only.

2. member_only vs DECLARES_PRODUCER — HINTS §3.4 sets member_only on DECLARES_PRODUCER, but PR-A only ships 10 edges. Clarify PR-A sets flags on DECLARES_CLIENT, EXPOSES, OVERRIDES, CALLS only; PR-C adds DECLARES_PRODUCER when the edge lands.

3. docs/PROPOSES-ORDER.md — Phase 2 still says plans “[not started]”; update after merge so the sequencing doc stays authoritative.

4. propose/HINTS-V3-PROPOSE.md — still Status: draft on master though #154 merged; small chore PR before PR-D lock gate.

---

Non-blocking (first code PR is fine)

• Add @tests/test_mcp_v2_compose.py to PR-B attach list (plan mentions it; prompt does not).
• PR-C file-by-file should list pr_analysis.py (implementation step table already does) for async two-hop after PR-B’s HTTP leg.
• Stale impact_analysis line anchor (~1335 vs ~1133 today).
• Consider making test_hints_neighbors_v2_empty_post_flip_method_http_calls required once post-flip fixtures exist.

---

Pre-implementation notes (code PRs)

• PR-A is not docs-only (workflow + generator) — full pytest will run; expected.
• v14 + pre-flip endpoints until B/C complete — README callout is critical.
• Freeze BROWNFIELD_RESOLVER_STRATEGY_SET members in PR-A body (same discipline as HTTP_CALLS grep).

Merge when the typical_traversals / member_only clarifications are in (here or immediate follow-up). Then SCHEMA PR-A can branch off master.