Render supersession and parentage lineage

[timeleft--]

Parent

Parent PRD: #51

What to build

Render supersession and parentage lineage in the local FAVA reader.

The reader should make it obvious when a thought is superseded, what superseded it, whether it has a parent, and how to move through the current and historical chain. Same-title or similar-title thoughts must remain distinct through ULID-backed identity.

Acceptance criteria

• Superseded thoughts show a clear supersession banner or equivalent status cue.
• Current replacement thoughts link back to the superseded thought when the source record provides parentage or supersession data.
• A lineage route or section renders parentage and supersession chains for a thought.
• Scope dashboard and thought detail pages expose enough lineage cues to avoid relying on stale conclusions.
• Same-title or similar-title thoughts remain distinct in routes, links, and lineage.
• Fixture coverage includes a superseded thought, a current replacement, and same-title or similar-title records with different ULIDs.
• Tests verify that lineage uses FAVA parentage and supersession fields rather than human title matching.

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.