docs: fix live-site 404s from relative links to repo source paths

Docusaurus build flagged these as broken: they linked to repo source
directories/files (analysis/, core/, mcp/, stryker4s.conf,
compat-fixtures/src/main) that the published docs site does not serve —
correct as GitHub-relative paths, but dead on the live site since Docusaurus
only hosts the docs/ tree. Converted to plain code spans instead of links,
since there's nowhere on the site for them to point.

Verified via a full local `docusaurus build` + `serve`: 0 broken links
except one pre-existing false positive (a fenced code sample meant for a
different file, correctly using its own relative path).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DYMBTKayWeQihL2YyQRUid

Author: MercurieVV

docs/research/stryker4s-alert-strategy.md

@@ -45,7 +45,7 @@ Due to the high runtime cost of running mutation tests (estimated 5-15 mins for
 - **Nightly Run**: Trigger a full mutation test run on the `master` branch every night via a cron schedule. This records the baseline health of the codebase.
 - **On-Demand PR Run (Label-Gated)**: Run mutation testing on a pull request only if:
    - The PR has the label `ci:run-mutation` applied.
-   - The PR modifies critical business logic inside the [analysis](../../analysis/) module.
+   - The PR modifies critical business logic inside the `analysis` module.
 
 ### Isolation (Avoiding SemanticDB Pollution)
 As identified in the research report, sbt compilation during a Stryker run overwrites target class directories and generates polluted SemanticDB files.
@@ -57,9 +57,9 @@ As identified in the research report, sbt compilation during a Stryker run overw
 
 We recommend rolling out mutation testing in phases:
 
-1. **Phase 1: `analysis` module** ([analysis](../../analysis/)): Focus here first. This contains the semantic analysis engine where logic is dense and test coverage is critical.
-2. **Phase 2: `core` module** ([core](../../core/)): Roll out once `analysis` is stable. Since `core` handles static SemanticDB parsing and has stable structure, its threshold can be set higher (e.g. `85%`).
-3. **Phase 3: `mcp` module** ([mcp](../../mcp/)): The stdio JSON-RPC loop contains infinite loops and blocking network channels that are difficult to mutate without triggering infinite loops or timeouts. We recommend excluding the stdio channel from mutations.
+1. **Phase 1: `analysis` module**: Focus here first. This contains the semantic analysis engine where logic is dense and test coverage is critical.
+2. **Phase 2: `core` module**: Roll out once `analysis` is stable. Since `core` handles static SemanticDB parsing and has stable structure, its threshold can be set higher (e.g. `85%`).
+3. **Phase 3: `mcp` module**: The stdio JSON-RPC loop contains infinite loops and blocking network channels that are difficult to mutate without triggering infinite loops or timeouts. We recommend excluding the stdio channel from mutations.
 
 ### Implementation note from #133
 
@@ -83,7 +83,7 @@ resolved:
 ## 5. Configuration Sketch
 
 ### HOCON Config (`stryker4s.conf`)
-The HOCON configuration file [stryker4s.conf](../../stryker4s.conf) should be structured as follows:
+The HOCON configuration file `stryker4s.conf` should be structured as follows:
 
 ```hocon
 stryker4s {

docs/testing/compat-strategy.md

@@ -25,9 +25,9 @@ For each compiler feature area and Scala version, we evaluate whether to (a) ven
 The new layout will introduce version-segregated files for newly-vendored and custom code:
 
 Status: this file list was the original plan; the fixtures actually landed under different names
-(see [`compat-fixtures/src/main`](../../compat-fixtures/src/main) for the current layout —
-`CallGraph.scala`, `ProductRecord.scala`, and, Scala-3-only, `VersionSpecific.scala`). Kept as a
-historical record of the intended structure, not a current file listing.
+in `compat-fixtures/src/main` (`CallGraph.scala`, `ProductRecord.scala`, and, Scala-3-only,
+`VersionSpecific.scala`). Kept as a historical record of the intended structure, not a current
+file listing.
 
 ### Scala 2.13 Files (as planned)
 Path: `compat-fixtures/src/main/scala-2.13/com/github/mercurievv/scalasemantic/compat/`