Render typed relationship navigation

[timeleft--]

Parent

Parent PRD: #51

What to build

Render typed relationship navigation in the local FAVA reader.

The reader should expose explicit FAVA relationships as local navigation, not as a decorative global graph. Operators should be able to see what a thought references, depends on, revises, authors, or supersedes where those relationship types are present, and should be able to identify unresolved internal targets.

Acceptance criteria

• Thought detail pages show outbound relationships grouped by FAVA relationship type.
• Thought detail pages show inbound relationship summaries when other included records point to the current thought.
• A local relationship route, section, or view helps inspect typed relationships around a thought or scope.
• Relationship labels use existing FAVA relationship types and do not invent unsupported edge semantics.
• Broken or unresolved internal relationship targets are visible rather than silently omitted.
• Scope dashboard summaries show relationship counts where available.
• Fixture coverage verifies outbound relationships, inbound relationships, unresolved targets, and no invented edge types.

Blocked by

• Render thought detail pages with provenance and slug routes #55

[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.