content options phase 2: backlog clearance (3 batches, 7 issues)

[gregoryfoster]

Summary

Prioritized execution plan for the post-#88 content options backlog (#89–#95). Three sequential batches using a hybrid parallel/sequential agent strategy. Pre-production context — full test coverage and clean abstractions throughout.

Design doc

docs/plans/2026-04-14-content-options-phase2-backlog.md

Scope

Batch A — 2 parallel agents (start immediately)

• A1: Watch - action buttons not inline with Notifications header #95 — button layout bug (isolated; watch_notifications.html only)
• A2: feat: content option — include last changed date (include_last_changed_at) #94 → feat: content option — include change significance score (include_significance) #93 → feat: content option — include dashboard link to change (include_change_dashboard_url) #92 — additive content options bundle (significance, last_changed_at, change_url + app_url extraction)

Batch B — 1 agent (after Batch A merged)

• B1: feat: add include_tags and include_description to ContentOptions #91 — Watch model migration (tags, description) + content option fields

Batch C — 1 agent (after Batch B merged)

• C1: feat: notification content options Phase 2 — Jinja2 title/body template strings #89 → feat: per-event-type content options UI accordion #90 — Jinja2 title/body templates (Phase 2) + per-event accordion UI

Deferred

• Template preview for feat: notification content options Phase 2 — Jinja2 title/body template strings #89 (deferred by issue; ship inputs without live preview)
• AI summaries, template autocomplete (out of scope per feat: notification content options Phase 2 — Jinja2 title/body template strings #89)