docs: address thesis review nits

docs/add/system-design-implementation.md

@@ -46,6 +46,10 @@ header-includes:
   - \setkeys{Gin}{width=\linewidth,height=0.55\textheight,keepaspectratio}
   - \renewcommand{\arraystretch}{1.3}
   - \hypersetup{pdfauthor={lda.chat}, pdftitle={Design and Implementation of lda.chat}}
+diagram:
+  engine:
+    mermaid:
+      theme: neutral
 ---
 
 # Introduction
@@ -635,7 +639,8 @@ call, remote OAuth, or provider quota.
 
 ## Case Study Components
 
-The example bundle lives at `examples/report_workflow/` and contains:
+The example bundle lives at
+[`examples/report_workflow/`](../../examples/report_workflow/) and contains:
 
 - `ops.py` --- a Python source exposing `read_notes`, `extract_report`, and
   `render_markdown_report` as typed `NodeSpec` capabilities.
@@ -1170,7 +1175,7 @@ uv run wf --config examples/report_workflow/wf.config.json run trace <run_id> --
 
 ## Appendix B: Evidence Index
 
-See `evidence-index.md` for the full claim-to-evidence map.
+See [evidence-index.md](evidence-index.md) for the full claim-to-evidence map.
 
 | Claim | Evidence |
 | --- | --- |

docs/add/thesis-outline.md

@@ -64,7 +64,7 @@ The case study should exist as a runnable example, not only prose. Target shape:
 `README.md`, and commands for config validation, server startup, capability
 calls, draft/artifact/deployment creation, run, inspect, and trace.
 The runnable evidence bundle for this case study lives at
-`examples/report_workflow/README.md`.
+`examples/report_workflow/`.
 
 
 Keep the thesis-critical path deterministic. Do not require an LLM call inside

docs/current_roadmap.md

@@ -113,10 +113,11 @@ auth admin are implemented. The next work is polish, not new broad surfaces.
 - Completed source provider docs: `docs/source_provider_guide.md` now covers
   MCP HTTP, MCP stdio, Python sources, auth refs, OAuth refresh-token setup,
   diagnostics, and the Google Drive MCP caveat.
-- Completed platform source policy: `wf.*` process-provided sources are marked
-  as platform sources. They resolve by fixed source id, do not require
-  self-bindings, and deployment validation rejects explicit platform-source
-  bindings as stale configuration.
+- Completed platform source policy: documented fixed-id sources such as `wf.std`
+  and `wf.source` are platform sources. They resolve by fixed source id, do not
+  require self-bindings, and deployment validation rejects explicit
+  platform-source bindings as stale configuration. Other `wf.*` namespaces are
+  described by their own source docs/policies.
 - Completed `wf.source.read_resource`: resource refs are inert pass-by-value
   data using `logical_source`; explicit platform helper nodes dereference them
   through runtime/platform context with bounded output.

docs/project_map.md

@@ -72,8 +72,10 @@ see [`workflow platform presentation`](add/2026-06-workflow-platform-presentatio
 
 ## Documentation
 
-- `docs/add/system-design-implementation.md` — formal thesis/system-design draft.
-- `docs/add/evidence-index.md` — claim-to-evidence map for the thesis draft.
+- [`docs/add/system-design-implementation.md`](add/system-design-implementation.md)
+  — formal thesis/system-design draft.
+- [`docs/add/evidence-index.md`](add/evidence-index.md) — claim-to-evidence
+  map for the thesis draft.
 
 ## Tests