Add bot filtering modes to aggregation explorer

[SylvainChevalier]

Summary

This PR extends the aggregation explorer's bot filtering capabilities by replacing the binary include/exclude toggle with a three-mode selector that allows users to exclude bots, include bots, or view only bot forecasts.

Key Changes

• Frontend UI Updates

  • Replaced the Switch component for bot filtering with a StyledSelect dropdown offering three options: "Exclude Bots", "Include Bots", and "Only Bots"
  • Updated the bot mode state management from a boolean includeBots to a BotMode type with values "exclude", "include", or "only"
  • Added new translation keys: excludeBots, onlyBots, and bots

• API & Data Layer

  • Added onlyBots parameter throughout the aggregation data pipeline (frontend and backend)
  • Updated buildConfigId() to distinguish between include and only modes using "bots" and "obots" identifiers
  • Modified buildDisplayLabel() and buildChips() to handle the new "only bots" mode in display labels
  • Updated query state parsing to correctly deserialize the "obots" identifier

• Backend Logic

  • Extended get_aggregations_at_time() and get_aggregation_history() to filter for only bot forecasts when only_bots=True
  • Restructured bot filtering logic to handle three distinct cases: only bots, include bots, or exclude bots
  • Updated the DataGetRequestSerializer to validate the new only_bots parameter

• Type Updates

  • Added onlyBots field to SelectedAggregationConfig, AggregationQueryResult, and related types
  • Updated API parameter types to include the new onlyBots option

Implementation Details

The bot filtering now follows a priority order: if only_bots is true, only bot forecasts are included; otherwise, if include_bots is true, bots are included; otherwise, bots are excluded. This ensures mutually exclusive filtering modes while maintaining backward compatibility.

https://claude.ai/code/session_01Ncpz4kH3oett2Wonz1TMaQ

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: e1079095-8817-4511-84fe-8f65fd16aafc

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/relaxed-dijkstra-Z1T0v

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

🚀 Preview Environment

Your preview environment is ready!

Resource	Details
🌐 Preview URL	https://metaculus-pr-4806-claude-relaxed-dijkstra-z1t0v-preview.mtcl.cc
📦 Docker Image	ghcr.io/metaculus/metaculus:claude-relaxed-dijkstra-z1t0v-a809d00
🗄️ PostgreSQL	NeonDB branch preview/pr-4806-claude-relaxed-dijkstra-z1t0v
⚡ Redis	Fly Redis mtc-redis-pr-4806-claude-relaxed-dijkstra-z1t0v

Details

• Commit: a809d00d4ae6233cb38cd18e34191c5eaf3bf815
• Branch: claude/relaxed-dijkstra-Z1T0v
• Fly App: metaculus-pr-4806-claude-relaxed-dijkstra-z1t0v

---

ℹ️ Preview Environment Info

Isolation:

• PostgreSQL and Redis are fully isolated from production
• Each PR gets its own database branch and Redis instance
• Changes pushed to this PR will trigger a new deployment

Limitations:

• Background workers and cron jobs are not deployed in preview environments
• If you need to test background jobs, use Heroku staging environments

Cleanup:

• This preview will be automatically destroyed when the PR is closed

[SylvainChevalier]

@claude resolve the conflicts.

[claude]

Claude finished @SylvainChevalier's task in 12m 18s —— View job

---

Resolving merge conflicts

• Fetch latest main and check conflict status
• Identify conflicting files
• Resolve conflicts
• Verify resolution and commit
• Push to PR branch

Summary

Resolved two conflicting files against origin/main (the other 9 PR files merge cleanly because main hasn't touched them).

utils/the_math/aggregations.py — main added forecasts.exclude_blacklisted_users() after exclude_non_primary_bots() in both get_aggregations_at_time() and get_aggregation_history(). The PR was restructuring the same else block to introduce elif only_bots: and to scope if not include_bots: inside the else. Merged result keeps both: the new elif only_bots: branch sits before else, and inside else the call order is exclude_non_primary_bots() → exclude_blacklisted_users() → conditional bot exclude. Comment updated to "non-primary bots or blacklisted users".

front_end/messages/en.json — main added openOnMetaculus and the laborHubJobs* / midtermsHub* translation keys (≈130 entries). Pulled them all into the PR while keeping the new excludeBots, onlyBots, bots keys next to includeBots.

Pushed as commit 2a88af1 to claude/relaxed-dijkstra-Z1T0v. The PR should now be mergeable; CI will revalidate.
• Branch: claude/relaxed-dijkstra-Z1T0v