Feedback md links to mkdocs

When you reference a forge .md file by path in a response to Justin, render it as a markdown link to the MkDocs viewer at https://mkdocs.justinsforge.com/ — drop the .md extension and use directory URLs (mkdocs use_directory_urls: true).

Examples: - memory/handoffs/foo.md → [foo](https://mkdocs.justinsforge.com/memory/handoffs/foo/) - nexus/fleet.md → [fleet](https://mkdocs.justinsforge.com/nexus/fleet/) - CLAUDE.md → [CLAUDE](https://mkdocs.justinsforge.com/CLAUDE/)

Indexed scope (linkable): memory/, nexus/, docs/, brands/, infra/, root-level .md files.

Excluded scope (keep as raw path — those URLs 404): logs/, scripts/, sites/, comms/, dashboard/, tasks/, data/, assets/, personal/, clients/, agents/, skills/, notifications/, .claude/, .git/. Also external paths and any non-forge file.

Why: Justin built https://mkdocs.justinsforge.com/ (MkDocs Material behind CF Access) on 2026-04-28 specifically so he can tap any forge md from his phone. Bare paths force him to open VS Code; links open instantly in the browser.

How to apply: Apply on every response that mentions a forge md path — file references, "see X", citation tables, etc. Skip it for raw shell snippets the user will copy-paste (paths in Read tool calls, cat foo.md, etc.) since those need actual filesystem paths. Skip it when CLAUDE.md isn't loaded (e.g. claude -p --bare workers) — but those sessions usually don't write user-facing prose anyway.