Render thought detail pages with provenance and slug routes

[timeleft--]

Parent

Parent PRD: #51

What to build

Render thought detail pages with FAVA provenance, full Markdown bodies, and canonical human slug routes.

An operator should be able to drill in from a scope dashboard record and see the thought's FAVA context before the prose: identity, lifecycle state, source type, confidence, agent, tags, scope, namespace, source provenance, and relationship summary. The full Markdown body remains available on the detail page as the evidence layer.

This slice is also the home for canonical human thought URLs unless a dedicated adjacent slug-routing issue supersedes it before implementation.

Route contract for this slice

• Canonical human thought URLs should include the full scope path plus a human slug, for example /mwai/eng/fava-trails/rich-views/readable-title/.
• The slug is a navigation/display affordance derived from human-readable display metadata, not from the ULID filename itself.
• /id/<UID>/ remains the durable UID lookup/fallback route.
• Bare UID routes such as /thoughts/<UID>/ or /<UID>/ must not be introduced.
• If two thoughts in the same scope collide on the same human slug, append a short UID suffix only for the colliding records unless a later slug-routing issue defines a different policy.

Acceptance criteria

• Dashboard records link to thought detail pages through generated route metadata or a shared route helper.
• Thought detail pages are reachable by canonical full-scope human slug routes.
• Thought detail pages remain reachable by /id/<UID>/ fallback routes.
• Generated route metadata distinguishes canonical human routes from durable UID fallback routes.
• Thought detail pages do not expose bare UID routes such as /thoughts/<UID>/ or /<UID>/.
• Thought detail pages show lifecycle metadata before the Markdown body.
• Thought detail pages show source type, validation status, confidence, agent, tags, scope, namespace, created time, and source provenance where available.
• Thought detail pages preserve and render the full Markdown body.
• Thought detail pages distinguish display title, human slug, and durable ULID identity.
• Thought detail pages include outbound and inbound relationship summaries when data is available.
• Fixture coverage verifies metadata rendering, full-body preservation, full-scope slug routes, /id/<UID>/ fallback routes, and slug collision handling.
• Browser verification confirms detail pages are readable on desktop and mobile.

Blocked by

• Render a descendant-aware scope dashboard #54

[yia-mw-agent]

Carrying forward the PR #61 review note about raw HTML in Markdown bodies.

The minimal #52 reader writes thought bodies into Markdown pages, so embedded raw HTML follows Astro's Markdown behavior. I do not think that should block #52. #55 is the right place to decide it because this issue explicitly owns full Markdown body rendering for thought detail pages.

When implementing #55, make the trust-boundary choice explicit: either preserve raw Markdown/HTML as trusted FAVA content, or add sanitization / renderer configuration if these detail pages are meant to handle untrusted or public inputs. The acceptance criteria should include whichever choice we make.

[timeleft--]

Paused by MachineWisdomAI/WisdomLoop#35 and its five-task pilot. Minimum FAVA truth/readiness work in #72, #73, and #74 now precedes renderer and search expansion. The ready-for-agent label is removed so automated intake cannot start this work during the pilot.

Resume only if the pilot identifies human or agent retrieval as a measured bottleneck. The existing specification remains preserved as prior design context.