docs(bf-6d973-child-3): add process cleanup verification note for TH-05 SSRF tests

notes/bf-3bnao-step2.md

@@ -0,0 +1,62 @@
+# bf-3bnao-step2: Confirm fixture file path from previous bead
+
+## State: PASS
+
+**Date:** 2026-07-06
+
+## Previous Bead Reference
+
+**Parent bead:** bf-6bsry - "Select and verify test fixture"
+**Note file:** notes/bf-6bsry.md
+**Status:** CLOSED
+
+## Confirmed Fixture Path
+
+**Selected fixture:** `tests/fixtures/encoding/fingerprint-match.pdf`
+
+**Absolute path:** `/home/coding/pdftract/tests/fixtures/encoding/fingerprint-match.pdf`
+
+## Verification
+
+### ✅ File Exists
+
+```bash
+ls -lh tests/fixtures/encoding/fingerprint-match.pdf
+# Output: -rw-r--r-- 1 coding users 1.1K Jul  6 13:26 tests/fixtures/encoding/fingerprint-match.pdf
+```
+
+### ✅ File is Readable
+
+- Permissions: `-rw-r--r--` (readable by owner and group)
+- Size: 1.1K (1,059 bytes) - well under 50KB threshold
+- Last modified: 2026-07-06 13:26
+
+### ✅ Valid PDF
+
+```bash
+head -c 4 tests/fixtures/encoding/fingerprint-match.pdf
+# Output: %PDF
+```
+
+## Fixture Details
+
+From previous bead (bf-6bsry):
+- **Size**: 1,059 bytes (~1KB)
+- **Expected content**: Single word "Test"
+- **Purpose**: Designed for font fingerprint matching tests (Phase 2.2 Level 3)
+- **Rationale**: Minimal overhead for fast test execution, simple to verify
+
+## Acceptance Criteria
+
+- ✅ Locate the fixture path from the previous bead's notes - **PASS**
+  - Found in notes/bf-6bsry.md, line 34
+- ✅ Verify the file exists at that path - **PASS**
+  - File exists at tests/fixtures/encoding/fingerprint-match.pdf
+- ✅ Document the confirmed path in notes/bf-3bnao-step2.md - **PASS**
+  - This file
+
+## Path for Next Step
+
+**Use this fixture path:** `tests/fixtures/encoding/fingerprint-match.pdf`
+
+This is the SAME fixture selected in bf-6bsry (child bead 1 of the parent chain) and will be used for all subsequent child beads requiring a small, fast encoding test fixture.

notes/bf-6d973-child-3.md

@@ -0,0 +1,90 @@
+# Verification Note: bf-6d973-child-3 - Process Cleanup in TH-05-SSRF Tests
+
+## Summary
+
+Verified that all SSRF URL tests properly clean up MCP server processes to prevent orphans. All acceptance criteria PASS.
+
+## Verification Steps
+
+### 1. McpServerGuard Implementation Review
+
+**Location:** `/home/coding/pdftract/crates/pdftract-cli/tests/TH-05-ssrf-block.rs`
+
+**Implementation (lines 31-81):**
+- ✅ **RAII guard struct** (lines 31-33): `McpServerGuard` owns the `Child` process
+- ✅ **Drop implementation includes all required components:**
+  - **Stdin closure** (line 56): `let _ = child.stdin.take();` signals EOF for graceful shutdown
+  - **Bounded wait** (lines 58-71): 200ms timeout with 10ms polling intervals
+  - **Force kill if graceful shutdown fails** (line 75): `child.kill()` followed by `try_wait()`
+
+### 2. Test Usage Verification
+
+All 7 SSRF tests in `TH-05-ssrf-block.rs` use the `McpServerGuard`:
+- ✅ `test_ipv4_loopback_blocked()` (line 198)
+- ✅ `test_ipv4_wildcard_blocked()` (line 237)
+- ✅ `test_cloud_metadata_blocked()` (line 274)
+- ✅ `test_rfc1918_private_blocked()` (line 311)
+- ✅ `test_ipv6_loopback_blocked()` (line 348)
+- ✅ `test_http_scheme_rejected()` (line 525)
+- ✅ `test_no_network_connection_attempted()` (line 566)
+
+Each test calls `spawn_mcp_server()` which returns `McpServerGuard`, ensuring automatic cleanup on drop.
+
+### 3. Test Execution Results
+
+**Command:** `cargo test --test TH-05-ssrf-block --features default,decrypt`
+
+**Result:** ✅ All 7 tests passed in 0.43s
+```
+running 7 tests
+test test_cloud_metadata_blocked ... ok
+test test_http_scheme_rejected ... ok
+test test_ipv4_loopback_blocked ... ok
+test test_ipv4_wildcard_blocked ... ok
+test test_ipv6_loopback_blocked ... ok
+test test_no_network_connection_attempted ... ok
+test test_rfc1918_private_blocked ... ok
+
+test result: ok. 7 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
+```
+
+### 4. Orphaned Process Check
+
+**Before tests:** No `pdftract mcp` processes running
+**After tests:** No `pdftract mcp` processes running
+
+**Verification commands:**
+```bash
+# Before tests
+pgrep -af 'pdftract mcp' | head -20
+# Output: Only shell wrapper code, no actual pdftract mcp processes
+
+# After tests
+ps aux | grep -i 'pdftract.*mcp' | grep -v grep
+# Output: "No pdftract mcp processes found"
+```
+
+### 5. Core Test File Review
+
+**Location:** `/home/coding/pdftract/crates/pdftract-core/tests/TH-05-ssrf-block.rs`
+
+This file contains unit tests for URL validation logic (no process spawning) and integration tests that manually manage process cleanup with `ProcessGuard` (lines 1746-1778). The integration tests explicitly close stdin and call `wait_with_timeout()` for deterministic cleanup.
+
+## Acceptance Criteria Status
+
+| Criterion | Status | Notes |
+|-----------|--------|-------|
+| All SSRF URL tests use McpServerGuard | ✅ PASS | All 7 tests use `spawn_mcp_server()` |
+| Drop implementation includes bounded wait | ✅ PASS | 200ms timeout with 10ms polling |
+| Drop implementation includes force kill | ✅ PASS | `child.kill()` if graceful shutdown fails |
+| pgrep shows zero orphaned processes | ✅ PASS | Verified before and after test run |
+| Verification note created | ✅ PASS | This file |
+
+## Conclusion
+
+The TH-05-SSRF block tests correctly implement process cleanup using the RAII pattern. The `McpServerGuard` ensures deterministic cleanup even if tests panic, and no orphaned processes remain after test completion. The bounded wait (200ms) prevents hanging while allowing graceful shutdown, and force kill as a fallback ensures processes are always cleaned up.
+
+**Date:** 2026-07-06
+**Verified by:** Claude Code (glm-4.7)
+**Tests Run:** 7/7 passed
+**Orphaned Processes:** 0