Activity feed — recent vault activity surface

[unforced]

Why

"What have I been touching lately" is a meaningful surface separate from the default list sort. Activity = created + updated + deleted events, chronological, optionally filtered.

Scope

• Route /activity — chronological feed of recent vault changes
• Each entry: timestamp, kind (created/updated/deleted), note path or title, small diff summary (for updates — "added 2 tags", "added 150 words")
• Groups: Today / Yesterday / This week / Older
• Click → note view (if the note still exists — deleted entries are read-only)
• Default limit: 50 entries, "Load more" at bottom

Implementation notes

• For created/updated: use the vault's query-notes with sort: "updated:desc" and a small window (last ~30 days)
• For deleted: vault doesn't currently track a deletion log. Options:
  • Skip delete entries for v1 (feed is only create/update). Still useful.
  • Ask vault for a /api/activity or /api/deletions endpoint — vault dependency; check with Aaron
• Probably ship as create+update only first; file a follow-up for deletion tracking once we see if it's missed

⚠️ Vault dependency (soft)

To include deletion events, vault would need to track them (currently DELETE is immediate, no tombstone). Check with Aaron before scoping that as part of this issue vs. deferring.

Tests

• Renders entries in correct groups
• Click → note view works
• Load more paginates

Out of scope

• Activity across multiple vaults (different surface)
• Real-time updates / websocket (polling-every-N-seconds on the page is fine)
• Per-user activity in multi-user contexts (vault is currently single-owner)

Priority

Mid-low. Nice-to-have, shares plumbing with saved views.