migration

docs/testing.md

@@ -29,14 +29,13 @@ tests/
     registry/
         test_read.py
         ingest/
-            conftest.py
             test_current_docs.py
             test_document.py
-            test_prompt.py
         models/
             test_document_validation.py
-            test_prompt_validation.py
-            test_registry_payload_models.py
+    prompts/
+        test_content_renderer.py
+        test_filesystem_provider.py
     skills/
         test_provider.py
     web/
@@ -49,6 +48,7 @@ tests/
 Source-to-test alignment today:
 - `src/personal_mcp/registry/ingest/` -> `tests/registry/ingest/`
 - `src/personal_mcp/registry/models/` -> `tests/registry/models/`
+- `src/personal_mcp/prompts/` -> `tests/prompts/`
 - `src/personal_mcp/skills/provider.py` -> `tests/skills/test_provider.py`
 - `src/personal_mcp/web/` and MCP HTTP surface -> `tests/web/`
 
@@ -65,8 +65,7 @@ Pytest runs with `--strict-markers`, so any unregistered marker fails the test r
 
 Fixture placement follows test scope:
 1. `tests/conftest.py` for cross-suite defaults.
-2. `tests/registry/ingest/conftest.py` for ingest-specific setup.
-3. `tests/web/conftest.py` for web and endpoint client setup.
+2. `tests/web/conftest.py` for web and endpoint client setup.
 
 Prefer adding fixtures at the narrowest scope that serves more than one test.
 
@@ -90,9 +89,11 @@ uv run pytest -m smoke -q
 ## Adding New Tests
 
 When adding coverage:
-1. Place tests under the nearest existing module subtree (`registry/`, `skills/`, or `web/`).
+1. Place tests under the nearest existing module subtree (`prompts/`, `registry/`, `skills/`, or `web/`).
 2. Mirror the source path where practical.
 3. Reuse existing `conftest.py` files before adding new fixture layers.
 4. Add markers only when they convey execution intent, and register new markers in `pyproject.toml` first.
 
-This keeps the suite aligned with the current architecture while preserving a fast local test loop.
+This keeps the suite aligned with the current architecture while preserving a fast local test loop.
+
+Prefer durable boundaries over implementation details: provider discovery, prompt rendering, traversal rejection, protocol behavior, and installed-package path resolution. Do not test deleted catalog projections, Pydantic immutability internals, or helper delegation.