Topic continuity pipeline: lifecycle derivation + deferral/disappearance

[AndreRobitaille]

Summary

Implement continuity signals that derive Topic lifecycle status from observable evidence.

Scope

• Detect recurrence, deferrals, and disappearance without resolution.
• Track cross-body progression (committee → council).
• Update lifecycle status based on agenda anchors and resolution signals.

Requirements

• Prefer agenda evidence; do not infer resolution without artifacts.
• Log status transitions with timestamps.

Acceptance criteria

• Lifecycle status updates are explainable and reproducible.
• Disappearance without resolution is surfaced as a signal, not a conclusion.

[AndreRobitaille]

Implementation Complete

Summary

Implemented a deterministic continuity pipeline that derives Topic lifecycle status from observable evidence (agenda appearances, motions) without inferring intent.

Changes

1. Continuity Service ():

   • Derives lifecycle_status (Active, Dormant, Resolved, Recurring).
   • Detects signals: Deferral keywords, Disappearance gaps, Cross-body progression.
   • Logs all state changes and signals to TopicStatusEvent with evidence refs.
   • Constraint: Only marks 'Resolved' if an explicit motion outcome (passed/adopted) exists.

2. Job Orchestration:

   • Added Topics::UpdateContinuityJob for background processing.
   • Updated ExtractVotesJob to trigger continuity updates after motion extraction.
   • Updated AgendaItemTopic callbacks to trigger updates on new agenda associations.

3. Backfill:

   • Updated Topics::BackfillContinuityJob to use the new service.
   • Ran backfill on all topics; logs confirm signal detection (cross-body progression, deferrals) and correct active/dormant status.

Verification

• Unit tests () cover all lifecycle transitions and idempotency.
• Backfill logs show successful processing of existing topics with correct signal logging.

Ready for next phase: Topic-aware summarization (#49).

[AndreRobitaille]

Continuity pipeline is implemented and operational: ContinuityService derives lifecycle status from agenda anchors and resolution signals, UpdateContinuityJob runs on topic association and vote extraction, TopicStatusEvent records track transitions. Confirmed working during review of ingestion pipeline.