Author orch Markdown test plan

docs/tests/orch/_shared/README.md

@@ -116,6 +116,22 @@ When worktree behavior is under test, assert at least:
 - attempt `worktree_path`
 - attempt `workspace_status`
 
+## Direct DB Inspection
+
+Most `orch` cases should stay at the CLI contract level, but a few manual reproduction flows need direct SQL reads to recover attempt-to-thread mappings that the current `orch` CLI does not print in a standalone query command.
+
+When a case truly needs that mapping:
+
+- use a read-only `sqlite3` query against `TMPDIR/coord.db`
+- prefer querying `task_attempts` by stable keys such as `run_id`, `task_id`, and `attempt_no`
+- treat the SQL read as fixture setup for the next CLI command, not as the main assertion target
+
+Typical example:
+
+```bash
+sqlite3 TMPDIR/coord.db "SELECT thread_id FROM task_attempts WHERE run_id = 'council_blog_001' AND task_id = 'CR1' AND attempt_no = 1;"
+```
+
 ## Workflow Authoring Rule
 
 If a case spans multiple `orch` commands, place the end-to-end narrative in `workflows/README.md` first, then add narrower command-level cases only when they are easier to reason about in isolation.