feature(area): acitvity feed json

[escapedcat]

Summary

• Add optional area query param to GET /v4/activity (accepts area ID or alias)
• When provided, filters events, comments, and boosts to places within that area
• When omitted, existing global behavior is unchanged
• Targeted error mapping: area not found returns 404, DB errors return 500

Why not the Atom feed?

The /feeds/ endpoints serve XML, split events and comments into separate feeds, and don't include boosts. The /v4/activity endpoint already merges all three into one JSON timeline — adding area scoping there was a one-param change vs
building a parallel feed system.

Tests

• 10 tests total (6 existing + 4 new)
• Area filtering tested for events, comments, and boosts separately
• Area not found returns 404

---

PR description for btcmap.org-2nd:

Summary

• New AreaFeed component replaces events-only list on area activity tab
• Fetches from /v4/activity?area={alias} — shows edits, comments, and boosts in one timeline
• Polymorphic cards: colored dots for edits, speech bubble for comments, lightning bolt for boosts
• Load-more expands time window (30 days increments)
• Race condition protection via generation counter
• Error state with retry button
• Vite dev proxy (/local-api -> localhost:8000) for local testing
• Dead code cleanup: removed unused eventElements, ActivityEvent, formatElementID

Frontend MVP

MVP only. UI should be adjusted alter on if the API is clear

Summary by CodeRabbit

• New Features

  • Added area-based activity filtering—retrieve events, comments, and boosts scoped to specific areas using the new optional area parameter.
  • Area aliases supported for streamlined filtering.
  • Returns 404 when the specified area does not exist.

• Documentation

  • Updated development guidelines for SQL query standards.

[coderabbitai]

🧹 Nitpick comments (1)

src/rest/v4/activity.rs (1)

218-220: Minor inconsistency in time boundary for boosts.

The boost time check uses now as the upper bound with inclusive comparison (> now means <= now for inclusion), while events and comments use period_end (now + 1s) with exclusive SQL boundaries (< period_end). This creates a subtle difference where boosts exclude items created exactly at now, but events/comments include items up to 1 second in the future.

For consistency, consider using period_end:

♻️ Optional: Align time boundaries with events/comments

-        if created_at < day_ago || created_at > now {
+        if created_at < day_ago || created_at > period_end {
             continue;
         }

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/rest/v4/activity.rs` around lines 218 - 220, The boost time filter in
activity.rs currently uses `if created_at < day_ago || created_at > now {
continue; }` which excludes items at exactly `now`; change it to use the same
`period_end` upper bound used by events/comments and the same exclusive
semantics: replace the check with `if created_at < day_ago || created_at >=
period_end { continue; }`, referencing the `created_at`, `day_ago`, and
`period_end` variables in the boosts processing logic so boosts align with
events/comments.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@src/rest/v4/activity.rs`:
- Around line 218-220: The boost time filter in activity.rs currently uses `if
created_at < day_ago || created_at > now { continue; }` which excludes items at
exactly `now`; change it to use the same `period_end` upper bound used by
events/comments and the same exclusive semantics: replace the check with `if
created_at < day_ago || created_at >= period_end { continue; }`, referencing the
`created_at`, `day_ago`, and `period_end` variables in the boosts processing
logic so boosts align with events/comments.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: bd465755-16f0-417d-8f02-0fe032765796

📥 Commits

Reviewing files that changed from the base of the PR and between 5ad6bb0 and aa006e3.

📒 Files selected for processing (6)

• AGENTS.md
• src/db/main/element_comment/blocking_queries.rs
• src/db/main/element_comment/queries.rs
• src/db/main/element_event/blocking_queries.rs
• src/db/main/element_event/queries.rs
• src/rest/v4/activity.rs

✅ Files skipped from review due to trivial changes (1)

• AGENTS.md

🚧 Files skipped from review as they are similar to previous changes (4)

• src/db/main/element_event/queries.rs
• src/db/main/element_comment/queries.rs
• src/db/main/element_event/blocking_queries.rs
• src/db/main/element_comment/blocking_queries.rs