bugsage 0.2.0

data/ROADMAP.md

@@ -0,0 +1,217 @@
+# BugSage Roadmap
+
+This document describes where BugSage is today and where the project is headed. It is a living plan for contributors and users—not a contractual release schedule. Priorities may shift based on feedback, security needs, and community interest.
+
+> **Current release:** [v0.2.0](CHANGELOG.md)  
+> **Discuss ideas:** [GitHub Issues](https://github.com/MONARCHKOLI/bugsage/issues) · [Feature request template](https://github.com/MONARCHKOLI/bugsage/issues/new/choose)
+
+---
+
+## Vision
+
+BugSage aims to be the fastest path from a Rails failure to a confident fix.
+
+Today, developers often bounce between stack traces, logs, docs, and AI chat tools with little shared context. BugSage brings **classification, explanation, and actionable repair** into the development loop—starting with deterministic rules and layering optional AI only when you ask for it.
+
+Long term, BugSage should feel like a coherent debugging companion across:
+
+- Local Rails development (error pages, session dashboard, inline console)
+- CI and pull requests (automated failure analysis)
+- Editors (Cursor, VS Code, RubyMine)
+- Background jobs and production-adjacent log workflows—always with clear safety boundaries
+
+**Principles:**
+
+1. **Rules first, AI second** — instant, predictable baselines; AI on demand
+2. **Zero-config by default** — useful after `bundle install` in development
+3. **Safe by design** — write actions limited to development/test; production opt-in only with careful defaults
+4. **Open and extensible** — clear extension points for rules, providers, and plugins
+
+---
+
+## Current Status
+
+BugSage **v0.2.x** is a development-focused Rails gem with:
+
+| Capability | Status |
+|------------|--------|
+| Zero-config Railtie install | Shipped |
+| Exception classification (Ruby / Rails rules) | Shipped |
+| HTML error page + request context | Shipped |
+| Session dashboard at `/bugsage` | Shipped (in-memory, per process) |
+| Inline Rails console | Shipped |
+| HTTP 4xx/5xx capture (API responses) | Shipped |
+| On-demand AI (OpenAI / Cursor Cloud Agents) | Shipped |
+| Follow-up AI chat + surgical `code_patch` | Shipped |
+| Apply patch / editor deep links | Shipped (dev/test) |
+| I18n-backed user-facing strings | Shipped |
+| Community docs (README, CONTRIBUTING, SECURITY, `docs/`) | In progress / expanding |
+
+**Not yet productized:** persistent production analytics, CI GitHub Action, editor extensions, deep Sidekiq/ActiveJob runtime integration beyond exception rules, Docker/log pipelines, or a formal plugin API.
+
+---
+
+## Short-term Goals (v0.2–v0.5)
+
+Focus: harden the core gem, improve AI/editor workflows, and prepare for a trustworthy **v1.0**.
+
+### v0.2.x (stability)
+
+- Publish clear docs and community health files
+- Expand RSpec coverage for public APIs (Store, CodePatch, HTTP capture edges, CLI)
+- Gemspec / packaging polish for RubyGems release
+- Bug fixes for Rack body handling, chat→apply patch flow, and edge-case capture
+
+### v0.3 — Stronger AI error analysis
+
+- Richer AI prompts with safer, more reliable `code_patch` schemas
+- Better multi-file / multi-hunk patch previews
+- Provider resilience (retries, clearer timeouts, offline fallback messaging)
+- Optional “explain this HTTP 400 body” analysis from captured API errors
+
+### v0.4 — Rails dashboard 2.0
+
+- Persist session history across requests more usefully (optional file/SQLite/Redis store)
+- Filtering, search, and grouping (by exception class, path, confidence)
+- Clearer split between exception events and HTTP error events
+- Export a single error as a shareable Markdown / clipboard report
+
+### v0.5 — Jobs & CI foundations
+
+- Deeper **ActiveJob** and **Sidekiq** error context (queue, job class, arguments sanitization)
+- First **GitHub Action** prototype: annotate failing CI jobs with BugSage-style summaries
+- Public **plugin-ready hooks** for custom rules (preview of the later plugin system)
+
+---
+
+## Mid-term Goals (v1.0)
+
+**v1.0** marks BugSage as a stable, documented tool for day-to-day Rails development.
+
+### Release criteria (target)
+
+- SemVer stability commitments for public Ruby APIs (`Bugsage.configure`, rule result shape, patch schema)
+- Comprehensive docs and examples
+- Solid test matrix (Ruby 3.2+ × modern Rails)
+- Official RubyGems release with MFA and security policy
+
+### Headline v1.0 themes
+
+| Theme | Outcome |
+|-------|---------|
+| **AI Error Analysis** | Dependable on-demand analysis with structured patches and chat refinement |
+| **Rails Dashboard** | Polished session dashboard suitable as the default local error hub |
+| **Cursor Integration** | First-class Cursor provider + deep links + smoother “open and apply” loop |
+| **ActiveJob / Sidekiq Support** | First-class job failure context in dashboard and AI prompts |
+| **GitHub Action** | Supported action for PR/CI failure comments (opt-in) |
+| **Plugin System (v1)** | Documented API for custom rules and suggestion enrichers |
+
+v1.0 remains **development-first**. Production deployment, if offered, will be explicit, limited, and separately documented.
+
+---
+
+## Long-term Goals (v2.0+)
+
+**v2.0+** expands BugSage from an in-app development assistant into a broader debugging platform—without abandoning the rules-first identity.
+
+| Theme | Direction |
+|-------|-----------|
+| **Log Analyzer** | Parse Rails / job logs into classified events offline or in CI |
+| **Docker Logs** | Tail or batch-analyze container logs with the same rule engine |
+| **Production Log Analysis** | Redacted, privacy-aware analysis pipelines (never default-on) |
+| **Performance Analyzer** | Slow endpoints, N+1 hints, allocation hotspots as advisory findings |
+| **Security Checks** | Opinionated checks for risky patterns (open redirects, unsafe eval in captured context, secret leakage in error pages) |
+| **VS Code Extension** | Browse BugSage events, jump to frames, trigger explain/fix from the editor |
+| **RubyMine Plugin** | Parity features for JetBrains workflows |
+| **Plugin System (v2)** | Installable rule packs and provider plugins |
+| **Ecosystem** | Shared formats for CI annotations, editor protocols, and report export |
+
+These tracks are aspirational and may ship as companion repos (for example `bugsage-action`, `bugsage-vscode`) rather than inside the core gem.
+
+---
+
+## Planned Features
+
+Status key: **Shipped** · **Partial** · **Planned** · **Exploratory**
+
+| Feature | Status | Target window | Notes |
+|---------|--------|---------------|-------|
+| **AI Error Analysis** | Partial | v0.3 → v1.0 | On-demand OpenAI/Cursor + chat/patches shipped; depth & reliability ongoing |
+| **Rails Dashboard** | Partial | v0.4 → v1.0 | Session UI shipped; persistence, filters, exports planned |
+| **Cursor Integration** | Partial | v0.3 → v1.0 | Cloud Agents provider + editor links shipped; tighter UX planned |
+| **ActiveJob Support** | Partial | v0.5 → v1.0 | Deserialization/rules exist; richer job metadata planned |
+| **Sidekiq Support** | Planned | v0.5 → v1.0 | Failure middleware / context adapters |
+| **GitHub Action** | Planned | v0.5 → v1.0 | CI annotations from test/job failures |
+| **Plugin System** | Planned | v0.5 → v2.0 | Custom rules first; installable packs later |
+| **VS Code Extension** | Planned | v2.0+ | Companion extension |
+| **RubyMine Plugin** | Planned | v2.0+ | Companion plugin |
+| **Log Analyzer** | Planned | v2.0+ | Offline/CI log → classified events |
+| **Docker Logs** | Planned | v2.0+ | Container log ingestion |
+| **Production Log Analysis** | Exploratory | v2.0+ | Strict redaction & opt-in only |
+| **Performance Analyzer** | Exploratory | v2.0+ | Advisory performance findings |
+| **Security Checks** | Exploratory | v1.0 → v2.0 | Start with safe defaults in error presentation |
+
+---
+
+## Nice-to-have Features
+
+Ideas we like but are not committed to a milestone:
+
+- Slack / Discord webhook summaries for local session digests
+- Browser extension to pin the BugSage dashboard beside the app
+- Multi-language UI beyond English locale files
+- “Reproduction gist” exporter (redacted params + failing snippet)
+- Webhook provider plugins (non–OpenAI/Cursor HTTP endpoints)
+- Replayable fixture recorder for flaky request failures
+- Metrics: time-to-fix estimates from historical session data (local only)
+- Themeable error page / dashboard CSS tokens for host apps
+
+Propose additions via a [feature request](https://github.com/MONARCHKOLI/bugsage/issues/new/choose).
+
+---
+
+## Community Contributions
+
+BugSage welcomes contributions of all sizes. High-impact areas:
+
+| Area | How to help |
+|------|-------------|
+| **Bug reports** | Use the bug report template; include Ruby/Rails/BugSage versions |
+| **Rules** | Add deterministic matchers for common Rails/Ruby failures + specs |
+| **Docs** | Improve `docs/`, README examples, and troubleshooting |
+| **Tests** | Fill public API coverage gaps called out in reviews/issues |
+| **AI providers** | Hardening, fixtures, and safer patch schemas |
+| **Jobs** | Sidekiq / ActiveJob integrations with sanitized argument display |
+| **Tooling** | GitHub Action, editor extensions (often as companion repos) |
+
+### Getting started
+
+1. Read [CONTRIBUTING.md](CONTRIBUTING.md)
+2. Skim [docs/GettingStarted.md](docs/GettingStarted.md) (if present)
+3. Open an issue before large features
+4. Prefer small PRs with specs and changelog notes under `[Unreleased]`
+
+### Security
+
+Do **not** report vulnerabilities in public issues. Follow [SECURITY.md](SECURITY.md).
+
+### Roadmap feedback
+
+If a planned item should move up or down:
+
+- Comment on an existing related issue, or
+- Open a feature request describing user impact and whether it changes zero-config defaults
+
+---
+
+## Version legend
+
+| Range | Intent |
+|-------|--------|
+| **v0.2–v0.5** | Iterate quickly; APIs may refine before 1.0 |
+| **v1.0** | Stable core for Rails development workflows |
+| **v2.0+** | Broader platform (logs, CI depth, editors, production-adjacent tools) |
+
+---
+
+*Last updated: July 2026. Maintainers will revise this file as milestones land.*

data/SECURITY.md

@@ -0,0 +1,83 @@
+# Security Policy
+
+## Supported Versions
+
+The following versions of BugSage receive security updates:
+
+| Version | Supported          |
+| ------- | ------------------ |
+| 0.2.x   | :white_check_mark: |
+| 0.1.x   | :x:                |
+| < 0.1   | :x:                |
+
+Only the latest minor release line (`0.2.x`) is actively maintained. If you discover a vulnerability in an older release, please still report it — we may issue guidance or backport a fix when impact is high.
+
+## Reporting a Vulnerability
+
+**Please do not report security vulnerabilities through public GitHub issues, pull requests, or discussions.**
+
+### Preferred method
+
+Report vulnerabilities privately using [GitHub Security Advisories](https://github.com/MONARCHKOLI/bugsage/security/advisories/new):
+
+1. Open **Report a vulnerability** on the repository Security Advisories page.
+2. Include as much detail as you can (see below).
+3. Submit the report. Only maintainers will be able to see it until we choose to publish or request a CVE.
+
+### Alternative method
+
+If you cannot use private reporting, email the maintainer at [monarchkoli12@gmail.com](mailto:monarchkoli12@gmail.com) with the subject line:
+
+```text
+[SECURITY] BugSage vulnerability report
+```
+
+### What to include
+
+Please provide:
+
+- A clear description of the vulnerability and its potential impact
+- Affected BugSage version(s) (gem version or Git commit SHA)
+- Ruby and Rails versions used in reproduction
+- Step-by-step reproduction instructions
+- Proof of concept, logs, or patches (if available)
+- Any suggested remediation
+
+Redact secrets, API keys, and personal data from reproductions and logs.
+
+### What to expect
+
+| Stage | Expectation |
+| ----- | ----------- |
+| Acknowledgement | Within **5 business days** |
+| Initial triage | Within **10 business days** of acknowledgement |
+| Status updates | As progress is made, or at least every **30 days** until resolution |
+
+If the report is **accepted**, we will work on a fix, coordinate disclosure timing with you when possible, and publish a security advisory and/or `CHANGELOG.md` entry as appropriate.
+
+If the report is **declined** (for example, out of scope, already fixed, or not a security issue), we will explain why.
+
+We ask that you **do not publicly disclose** the vulnerability until we have released a fix or explicitly agreed on a disclosure date. Coordinated disclosure windows of up to **90 days** are typical unless a shorter or longer timeline is agreed.
+
+## Scope
+
+In scope for this policy includes, for example:
+
+- Remote or local privilege escalation via BugSage middleware or endpoints
+- Unintended exposure of application secrets, credentials, or user data through BugSage capture, logging, dashboard, console, or AI features
+- Path traversal or arbitrary file write through apply-fix / patch features outside intended development safeguards
+- Cross-site scripting or request forgery affecting BugSage-served pages or endpoints
+- Supply-chain issues in published gem artifacts
+
+Out of scope (please use public issues when appropriate):
+
+- Bugs with no security impact
+- Denial of service that only requires exhausting normal application resources
+- Vulnerabilities solely in third-party dependencies (report upstream; tell us if BugSage needs a dependency bump)
+- Security issues in host Rails applications that are not caused by BugSage
+
+## Safe Harbor
+
+We appreciate good-faith security research. If you report a vulnerability responsibly and in accordance with this policy, we will not pursue legal action related to that research.
+
+Thank you for helping keep BugSage and its users safe.

data/docs/AI.md

@@ -0,0 +1,167 @@
+# AI
+
+BugSage can optionally refine rule-based suggestions with OpenAI or Cursor. AI is **on-demand**: the error page stays fast, and the provider is called only when you click **Quick Fix Suggestion** or send a **Chat** message.
+
+Related docs: [GettingStarted.md](GettingStarted.md) · [Configuration.md](Configuration.md) · [Troubleshooting.md](Troubleshooting.md)
+
+## Enable AI
+
+### 1. Provide an API key
+
+In the same shell that starts Rails:
+
+```bash
+# OpenAI
+export OPENAI_API_KEY=sk-your-openai-key-here
+
+# or Cursor
+export CURSOR_API_KEY=crsr_your-cursor-key-here
+
+bin/rails server
+```
+
+Alternate variable names:
+
+| Provider | Environment variables |
+|----------|------------------------|
+| OpenAI | `OPENAI_API_KEY`, `BUGSAGE_OPENAI_API_KEY` |
+| Cursor | `CURSOR_API_KEY`, `BUGSAGE_CURSOR_API_KEY` |
+
+### 2. Confirm the panel appears
+
+On the BugSage error page or `/bugsage` dashboard you should see the **AI Suggestions** panel when AI is enabled.
+
+If no key is present, BugSage continues to work with rule-based suggestions only.
+
+### 3. Use Quick Fix and Chat
+
+1. Toggle **Enable AI** if your browser session has it turned off (`localStorage`).
+2. Click **Quick Fix Suggestion**.
+3. Wait for the loading animation (Cursor can take longer — up to ~90 seconds).
+4. Review fixes, AI notes, and the `code_patch` preview.
+5. Optionally open **Chat** to refine the patch (for example, “comment out that line instead of deleting it”).
+6. On the dashboard, use **Apply AI to Codebase** to write the latest patch to disk.
+
+## Provider selection
+
+| Situation | Provider used |
+|-----------|---------------|
+| `config.bugsage.ai_provider = :openai` | OpenAI |
+| `config.bugsage.ai_provider = :cursor` | Cursor |
+| Key starts with `crsr_` | Cursor (auto) |
+| Key starts with `sk-` / other OpenAI keys | OpenAI (auto) |
+| Cursor key stored in `OPENAI_API_KEY` | Cursor (prefix detected) |
+
+Explicit config example:
+
+```ruby
+Rails.application.configure do |config|
+  config.bugsage.ai_enabled = true
+  config.bugsage.ai_provider = :cursor
+  # config.bugsage.cursor_model = "composer-2.5"  # optional
+end
+```
+
+OpenAI model example:
+
+```ruby
+Rails.application.configure do |config|
+  config.bugsage.ai_provider = :openai
+  config.bugsage.openai_model = "gpt-4o-mini"
+  config.bugsage.openai_api_base = "https://api.openai.com/v1"
+end
+```
+
+## What AI receives
+
+When you request a Quick Fix, BugSage sends:
+
+- Exception class and message
+- Numbered source context around the failure (±20 lines)
+- Request context (path, controller, action, parameters when available)
+- Current rule-based classification
+
+Chat continues from that context and can return an updated `code_patch`.
+
+## Structured code patches
+
+AI responses should include a surgical `code_patch` instead of blind search/replace:
+
+| Action | Meaning |
+|--------|---------|
+| `delete_lines` | Remove one or more lines |
+| `replace_lines` | Replace specific lines (for example comment out code) |
+| `insert_before` | Insert code before a line |
+| `no_change` | File already contains the correct fix |
+
+BugSage:
+
+- Uses absolute line numbers from numbered source context
+- Rejects patches that would duplicate existing code
+- Preserves indentation when applying
+
+Chat-refined patches update the preview and the **Apply AI to Codebase** action. They are also persisted in the session store so the latest patch is used on apply.
+
+## Dashboard AI actions
+
+Available on `/bugsage` (not all actions appear on the full-page error view):
+
+| Action | Purpose |
+|--------|---------|
+| **Quick Fix Suggestion** | Request AI analysis |
+| **Chat** | Follow up and refine the patch |
+| **Apply AI to Codebase** | Write the current `code_patch` to the source file |
+| **Open in Cursor** / **Open in VS Code** | Jump to file and line |
+| **Copy Fix** | Copy a prompt for your editor AI |
+| **Apply Fix to File** | Insert a `# BUGSAGE:` comment (non-AI helper) |
+
+**Apply AI to Codebase** / apply-fix endpoints are limited to **development** and **test**.
+
+## Timeouts
+
+| Provider | Default behavior |
+|----------|------------------|
+| OpenAI | `ai_timeout` default `15` seconds |
+| Cursor | Effective timeout is at least `90` seconds (`[ai_timeout, 90].max`) |
+
+Cursor runs through the [Cloud Agents API](https://cursor.com/docs/cloud-agent/api/endpoints) and often needs the longer window on the first response.
+
+```ruby
+config.bugsage.ai_timeout = 120
+```
+
+## Disable AI
+
+```ruby
+Rails.application.configure do |config|
+  config.bugsage.ai_enabled = false
+end
+```
+
+Or simply unset the API keys before starting the server.
+
+## Failure behavior
+
+If the AI API fails (invalid key, rate limit, timeout, network error):
+
+- BugSage keeps the rule-based suggestion
+- A warning is logged, for example:
+
+```text
+[BugSage] AI enhancement failed: ...
+```
+
+The error page and dashboard remain usable without AI.
+
+## Related API endpoints
+
+| Endpoint | Method | Purpose |
+|----------|--------|---------|
+| `/bugsage/ai-suggest` | `POST` | Quick Fix |
+| `/bugsage/ai-chat` | `POST` | Chat + optional patch update |
+| `/bugsage/apply-fix` | `POST` | Apply `code_patch` (dev/test only) |
+
+## Related
+
+- [Configuration.md](Configuration.md) — all AI-related options
+- [Troubleshooting.md](Troubleshooting.md) — AI-specific failures

data/docs/Configuration.md

@@ -0,0 +1,168 @@
+# Configuration
+
+BugSage is designed for zero configuration. Use this guide when you need to override defaults.
+
+Related docs: [GettingStarted.md](GettingStarted.md) · [AI.md](AI.md) · [Troubleshooting.md](Troubleshooting.md)
+
+## How to configure
+
+### Rails initializer (recommended)
+
+```ruby
+# config/initializers/bugsage.rb
+Rails.application.configure do |config|
+  config.bugsage.enabled_environments = %i[development test staging]
+  config.bugsage.show_error_page = true
+  config.bugsage.show_dashboard = true
+  config.bugsage.ai_enabled = true
+  config.bugsage.ai_provider = :cursor
+end
+```
+
+Generate a commented starter file with:
+
+```bash
+bundle exec rails generate bugsage:install
+```
+
+### Runtime configuration
+
+```ruby
+Bugsage.configure do |config|
+  config.ai_enabled = true
+  config.openai_model = "gpt-4o-mini"
+  config.capture_http_errors = false
+end
+```
+
+### Environment variables
+
+| Variable | Purpose |
+|----------|---------|
+| `BUGSAGE_ENABLED_ENVIRONMENTS` | Comma-separated environments (for example `development,test,staging`) |
+| `OPENAI_API_KEY` / `BUGSAGE_OPENAI_API_KEY` | OpenAI key (`sk-...`) |
+| `CURSOR_API_KEY` / `BUGSAGE_CURSOR_API_KEY` | Cursor key (`crsr_...`) |
+
+Keys must be present in the environment of the process that starts `bin/rails server`.
+
+Restart the Rails server after changing configuration or environment variables.
+
+## Options reference
+
+| Option | Default | Description |
+|--------|---------|-------------|
+| `enabled_environments` | `development`, `test` | Environments where BugSage runs |
+| `show_error_page` | `true` in development only | Replace raised exceptions with the BugSage HTML page |
+| `show_dashboard` | `true` in development only | Serve `GET /bugsage` |
+| `show_inline_console` | `true` in development only | Enable the inline Rails console |
+| `capture_errors` | `true` | Store caught errors in the in-memory session store |
+| `capture_http_errors` | `true` | Capture HTTP status ≥ 400 when `capture_errors` is on |
+| `ai_enabled` | auto (`true` when an API key is present) | Show the AI panel; does not call the API until Quick Fix / Chat |
+| `ai_provider` | auto-detected | `:openai` or `:cursor` |
+| `openai_api_key` | `nil` (env fallback) | OpenAI API key |
+| `openai_model` | `gpt-4o-mini` | OpenAI model name |
+| `openai_api_base` | `https://api.openai.com/v1` | OpenAI-compatible base URL |
+| `cursor_api_key` | `nil` (env fallback) | Cursor API key |
+| `cursor_model` | `nil` (account default) | Cursor Cloud Agents model |
+| `cursor_api_base` | `https://api.cursor.com` | Cursor API base URL |
+| `ai_timeout` | `15` (minimum `90` for Cursor) | Request/poll timeout in seconds |
+| `ai_client` | `nil` | Custom AI client for tests or alternate providers |
+| `fallback_exceptions_app` | `nil` | Optional fallback Rack app for routing errors |
+
+## Default behavior by environment
+
+| Environment | Error page | Dashboard | Capture | AI (if configured) |
+|-------------|------------|-----------|---------|--------------------|
+| **development** | BugSage page | `/bugsage` | Yes | Available |
+| **test** | Rails default | Off | Yes (silent) | Available |
+| **production** | Off | Off | Off | Off |
+
+BugSage is **off** in production unless you explicitly add `production` to `enabled_environments`. Even then, prefer keeping `show_error_page` and `show_dashboard` disabled in production.
+
+## Common configuration recipes
+
+### Enable BugSage in staging
+
+```ruby
+Rails.application.configure do |config|
+  config.bugsage.enabled_environments = %i[development test staging]
+end
+```
+
+Or:
+
+```bash
+export BUGSAGE_ENABLED_ENVIRONMENTS=development,test,staging
+```
+
+### Capture errors silently (no BugSage HTML page)
+
+Useful when you want the dashboard/store without replacing Rails’ error UI:
+
+```ruby
+Rails.application.configure do |config|
+  config.bugsage.show_error_page = false
+  config.bugsage.capture_errors = true
+end
+```
+
+### Disable HTTP response capture
+
+```ruby
+Rails.application.configure do |config|
+  config.bugsage.capture_http_errors = false
+end
+```
+
+### Force OpenAI or Cursor
+
+```ruby
+Rails.application.configure do |config|
+  config.bugsage.ai_enabled = true
+  config.bugsage.ai_provider = :openai
+  # or
+  # config.bugsage.ai_provider = :cursor
+end
+```
+
+### Turn AI off completely
+
+```ruby
+Rails.application.configure do |config|
+  config.bugsage.ai_enabled = false
+end
+```
+
+### Disable the dashboard or inline console
+
+```ruby
+Rails.application.configure do |config|
+  config.bugsage.show_dashboard = false
+  config.bugsage.show_inline_console = false
+end
+```
+
+## Endpoints BugSage registers
+
+These are served by BugSage middleware when the gem is enabled:
+
+| Endpoint | Method | Purpose |
+|----------|--------|---------|
+| `/bugsage` | `GET` | Session dashboard |
+| `/bugsage/console` | `POST` | Inline console evaluation |
+| `/bugsage/ai-suggest` | `POST` | Quick Fix AI request |
+| `/bugsage/ai-chat` | `POST` | Follow-up chat / patch refinement |
+| `/bugsage/apply-fix` | `POST` | Apply a `code_patch` (development/test only) |
+| `/bugsage/clear` | `POST` | Clear session error store |
+
+## Internationalization
+
+User-facing strings ship in `lib/bugsage/locales/en.yml` and are read through `Bugsage.t`.
+
+Host apps can override keys via Rails I18n (for example `config/locales/bugsage.en.yml`) using the same key structure under the `bugsage` namespace.
+
+## Related
+
+- [GettingStarted.md](GettingStarted.md) — install and verify
+- [AI.md](AI.md) — providers, chat, and patches
+- [Troubleshooting.md](Troubleshooting.md) — common problems