move resolve tool plan and propose to completed (#141)

Track PR #135 and #140 as landed; fix cross-links for new paths.

Co-authored-by: Cursor <cursoragent@cursor.com>

Author: HumanBean17

plans/CURSOR-PROMPTS-RESOLVE-TOOL.md …completed/CURSOR-PROMPTS-RESOLVE-TOOL.mdplans/CURSOR-PROMPTS-RESOLVE-TOOL.md renamed to plans/completed/CURSOR-PROMPTS-RESOLVE-TOOL.md plans/CURSOR-PROMPTS-RESOLVE-TOOL.md renamed to plans/completed/CURSOR-PROMPTS-RESOLVE-TOOL.md

@@ -1,8 +1,8 @@
 # Cursor task prompts — `resolve` tool (PR-RESOLVE-1 → PR-RESOLVE-2)
 
-Status: **active**. Plan:
+Status: **completed** (historical handoff prompts). Plan:
 [`PLAN-RESOLVE-TOOL.md`](PLAN-RESOLVE-TOOL.md); propose:
-[`propose/RESOLVE-TOOL-PROPOSE.md`](../propose/RESOLVE-TOOL-PROPOSE.md).
+[`propose/completed/RESOLVE-TOOL-PROPOSE.md`](../propose/completed/RESOLVE-TOOL-PROPOSE.md).
 
 One prompt per PR. Copy the prompt verbatim into Cursor agent mode with the
 listed `@-files` attached.
@@ -27,13 +27,13 @@ listed `@-files` attached.
 
 **Branch:** `feat/resolve-tool` off `master`.
 **Base:** `master`.
-**Plan section:** `plans/PLAN-RESOLVE-TOOL.md` § PR-RESOLVE-1.
+**Plan section:** `plans/completed/PLAN-RESOLVE-TOOL.md` § PR-RESOLVE-1.
 **PR title:** `add resolve mcp tool for identifier-shaped lookups`
 
 **Attach (`@-files`):**
 
-- `@plans/PLAN-RESOLVE-TOOL.md` (PR-RESOLVE-1 section only)
-- `@propose/RESOLVE-TOOL-PROPOSE.md`
+- `@plans/completed/PLAN-RESOLVE-TOOL.md` (PR-RESOLVE-1 section only)
+- `@propose/completed/RESOLVE-TOOL-PROPOSE.md`
 - `@java_ontology.py`
 - `@mcp_v2.py`
 - `@server.py`
@@ -44,9 +44,9 @@ listed `@-files` attached.
 **Prompt:**
 
 ````
-You are implementing PR-RESOLVE-1 from `plans/PLAN-RESOLVE-TOOL.md`.
+You are implementing PR-RESOLVE-1 from `plans/completed/PLAN-RESOLVE-TOOL.md`.
 
-Read the **PR-RESOLVE-1** section and `propose/RESOLVE-TOOL-PROPOSE.md` §3–§6
+Read the **PR-RESOLVE-1** section and `propose/completed/RESOLVE-TOOL-PROPOSE.md` §3–§6
 before writing code. If this prompt and the plan disagree, the plan wins.
 
 ## Scope
@@ -92,7 +92,7 @@ but do not edit AGENT-GUIDE/README in this PR):
 
 ## Deliverables
 
-Match `plans/PLAN-RESOLVE-TOOL.md` § PR-RESOLVE-1 definition of done.
+Match `plans/completed/PLAN-RESOLVE-TOOL.md` § PR-RESOLVE-1 definition of done.
 
 ## Validation
 
@@ -131,14 +131,14 @@ that ontology_version is unchanged and PR-RESOLVE-2 will sweep descriptions.
 
 **Branch:** `feat/resolve-tool-docs` off `master` (after PR-RESOLVE-1 merged).
 **Base:** `master`.
-**Plan section:** `plans/PLAN-RESOLVE-TOOL.md` § PR-RESOLVE-2.
+**Plan section:** `plans/completed/PLAN-RESOLVE-TOOL.md` § PR-RESOLVE-2.
 **Blocked on:** PR-RESOLVE-1 merged to `master`.
 **PR title:** `point agent docs at resolve for identifier lookups`
 
 **Attach (`@-files`):**
 
-- `@plans/PLAN-RESOLVE-TOOL.md` (PR-RESOLVE-2 section only)
-- `@propose/RESOLVE-TOOL-PROPOSE.md` (§3.7, §6 checklist)
+- `@plans/completed/PLAN-RESOLVE-TOOL.md` (PR-RESOLVE-2 section only)
+- `@propose/completed/RESOLVE-TOOL-PROPOSE.md` (§3.7, §6 checklist)
 - `@server.py`
 - `@mcp_v2.py` (hint_message only)
 - `@docs/AGENT-GUIDE.md`
@@ -153,7 +153,7 @@ that ontology_version is unchanged and PR-RESOLVE-2 will sweep descriptions.
 **Prompt:**
 
 ````
-You are implementing PR-RESOLVE-2 from `plans/PLAN-RESOLVE-TOOL.md`.
+You are implementing PR-RESOLVE-2 from `plans/completed/PLAN-RESOLVE-TOOL.md`.
 
 PR-RESOLVE-1 (`resolve` tool) is already on master. This PR is **docs and
 agent-facing prose only** plus test expectation updates — no new resolve logic.
@@ -185,7 +185,7 @@ agent-facing prose only** plus test expectation updates — no new resolve logic
 - Changing `describe(fqn=…)` first-match behavior.
 - Adding `microservice` to `describe`.
 
-Sentinel grep — run the **canonical** command from `plans/PLAN-RESOLVE-TOOL.md`
+Sentinel grep — run the **canonical** command from `plans/completed/PLAN-RESOLVE-TOOL.md`
 § “Canonical sentinel grep (PR-RESOLVE-2)”. Review output; expect no
 identifier-resolution fallback recommendations. Allow `search` only inside
 `resolve` tool description / `status="none"` messages.

plans/PLAN-RESOLVE-TOOL.md plans/completed/PLAN-RESOLVE-TOOL.mdplans/PLAN-RESOLVE-TOOL.md renamed to plans/completed/PLAN-RESOLVE-TOOL.md

@@ -1,9 +1,9 @@
 # Plan: `resolve` tool — identifier-shaped lookup primitive
 
-Status: **active (planning)**. This plan implements
-[`propose/RESOLVE-TOOL-PROPOSE.md`](../propose/RESOLVE-TOOL-PROPOSE.md).
+Status: **completed (landed)** — PR #135 (`resolve`) + PR #140 (tool-description sweep). Implements
+[`propose/completed/RESOLVE-TOOL-PROPOSE.md`](../propose/completed/RESOLVE-TOOL-PROPOSE.md).
 
-Depends on: **MCP filter frame landed** ([`plans/completed/PLAN-MCP-FILTER-FRAME.md`](completed/PLAN-MCP-FILTER-FRAME.md) — PR-FRAME-1 → PR-FRAME-3). No graph-builder or Lance work.
+Depends on: **MCP filter frame landed** ([`PLAN-MCP-FILTER-FRAME.md`](PLAN-MCP-FILTER-FRAME.md) — PR-FRAME-1 → PR-FRAME-3). No graph-builder or Lance work.
 
 Per-PR Cursor prompts: [`CURSOR-PROMPTS-RESOLVE-TOOL.md`](CURSOR-PROMPTS-RESOLVE-TOOL.md).
 
@@ -277,7 +277,7 @@ Optional MCP registration smoke (if lightweight): extend existing server tool-li
 
 ## Canonical sentinel grep (PR-RESOLVE-2)
 
-Use this exact command in PR descriptions and `CURSOR-PROMPTS-RESOLVE-TOOL.md` (allow `search` only inside `resolve` tool description / `status="none"` messages):
+Use this exact command in PR descriptions and [`CURSOR-PROMPTS-RESOLVE-TOOL.md`](CURSOR-PROMPTS-RESOLVE-TOOL.md) (allow `search` only inside `resolve` tool description / `status="none"` messages):
 
 ```bash
 grep -En 'per\.candidate|until.*resolve|promising candidates|search\(query=.*\).*describe' \
@@ -351,10 +351,10 @@ Manual evidence (PR description): run the **canonical sentinel grep** above, the
 2. No agent-facing doc or tool description recommends `search` + `describe`-per-candidate for identifier-shaped lookups.
 3. `describe` FQN-collision hint points at `resolve`.
 4. README, AGENT-GUIDE, AGENTS.md, and `project-overview.mdc` list five MCP tools with `resolve` documented.
-5. Propose moved to `propose/completed/RESOLVE-TOOL-PROPOSE.md` after both PRs merge.
-6. Plan + prompts moved to `plans/completed/` after both PRs merge.
+5. Propose lives at `propose/completed/RESOLVE-TOOL-PROPOSE.md`.
+6. Plan + prompts live in `plans/completed/` (this file and `CURSOR-PROMPTS-RESOLVE-TOOL.md`).
 
 # Tracking
 
-- `PR-RESOLVE-1`: _pending_
-- `PR-RESOLVE-2`: _pending_ (blocked on RESOLVE-1)
+- `PR-RESOLVE-1`: merged (#135)
+- `PR-RESOLVE-2`: merged (#140)

propose/RESOLVE-TOOL-PROPOSE.md propose/completed/RESOLVE-TOOL-PROPOSE.mdpropose/RESOLVE-TOOL-PROPOSE.md renamed to propose/completed/RESOLVE-TOOL-PROPOSE.md

@@ -1,6 +1,6 @@
 # `resolve` tool — strict-frame identifier resolution for the MCP V2 surface
 
-**Status**: active (plan: [`plans/PLAN-RESOLVE-TOOL.md`](../plans/PLAN-RESOLVE-TOOL.md), PR #135)
+**Status**: completed (landed: PR #135 + PR #140; plan: [`plans/completed/PLAN-RESOLVE-TOOL.md`](../plans/completed/PLAN-RESOLVE-TOOL.md))
 **Author**: Dmitriy Teriaev + Computer
 **Date**: 2026-05-15
 **Builds on**: [`propose/completed/MCP-FILTER-FRAME-PROPOSE.md`](completed/MCP-FILTER-FRAME-PROPOSE.md) (locked, #117 shipped via PR-FRAME-1 → PR-FRAME-3)