Topic lifecycle status chips

[AndreRobitaille]

Summary

Standardize status chips for Topic lifecycle states.

Requirements

• Chips reflect lifecycle (active/dormant/resolved/recurring), not review state.
• Color/semantics derived from theme tokens.

Acceptance criteria

• Status chips used consistently on Topic cards, rows, and detail view.

[AndreRobitaille]

Closing as unnecessary. The lifecycle_status field already exists, is precomputed by ContinuityService, and is used for grouping on the public topics index. Adding visual chips doesn't enable any new workflow: admins triage based on topic validity (approve/block/merge), not lifecycle state, and already have Last Seen/Last Acted On dates for temporal context. Residents don't think in lifecycle terms per docs/AUDIENCE.md — they think in time orientation, which the site already communicates through page structure.