prior-art

## Behavior Research how this codebase handles `$ARGUMENTS`. Explore the codebase thoroughly and report what you find. ### Step 1: Search Broadly Cast a wide net across the codebase. Use multiple search strategies: - **Grep for keywords** — search for terms related to the concern (e.g. for error reporting: `error`, `exception`, `rescue`, `Sentry`, `Bugsnag`, `notify`, `report`) - **Check common Rails locations** — initializers, middleware, concerns, base classes, config files, lib/ - **Check the Gemfile** — are there gems related to this concern? What do they tell you about the approach? - **Check application-level base classes** — `ApplicationController`, `ApplicationRecord`, `ApplicationJob` — these often set patterns that everything inherits - **Check for dedicated directories or files** — service objects, concerns, lib/ modules that handle this concern Don't stop at the first result. The goal is to find every place this concern is handled — the consistent pattern and the exceptions. ### Step 2: Check Git History For the key files involved in this concern: - `git log --oneline -10 <file>` to see recent changes - `git log --all --oneline --grep="<keyword>"` to find commits related to the concern - Look for: when the pattern was established, whether it's evolved, any recent changes or migrations from one approach to another Git history reveals whether a pattern is settled or in flux — critical context before you build on top of it. ### Step 3: Map What You Found R...