django-explain-errors 0.6.0__tar.gz → 0.8.0__tar.gz

{django_explain_errors-0.6.0/django_explain_errors.egg-info → django_explain_errors-0.8.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: django-explain-errors
-Version: 0.6.0
+Version: 0.8.0
 Summary: Django middleware that explains unhandled exceptions in DEBUG using an LLM, optionally grounded in your own project source via a local vector index. Works with OpenAI, Claude, or any OpenAI-compatible endpoint including local models.
 Home-page: https://github.com/topunix/django-explain-errors
 Author: topunix
@@ -45,16 +45,23 @@ Dynamic: summary
 # Django Explain Errors Middleware
 
 This Django middleware captures unhandled errors and exceptions, sends them
-to a language model for explanation, and prints the explanation to stdout
-when debug mode is enabled. It works with the OpenAI API out of the box, with
-Anthropic's Claude models through Anthropic's OpenAI-compatible endpoint, and
-with any other OpenAI-compatible endpoint (Ollama, LM Studio, Azure, or a
-corporate gateway) by setting a base URL, so explanations can run entirely on
-a local model if you prefer not to send code off your machine.
-
-It can optionally ground explanations in your own project source using a
-local vector index (RAG), so explanations reference the actual code that
-failed instead of staying generic.
+to a language model for explanation, and, when debug mode is enabled, shows
+the explanation on Django's debug page directly under the exception
+headline, as well as printing it to stdout. It works with the OpenAI API
+out of the box, with Anthropic's Claude models through Anthropic's
+OpenAI-compatible endpoint, and with any other OpenAI-compatible endpoint
+(Ollama, LM Studio, Azure, or a corporate gateway) by setting a base URL,
+so explanations can run entirely on a local model if you prefer not to send
+code off your machine.
+
+Enabling RAG is strongly recommended. With it, the middleware retrieves the
+relevant parts of your own project source from a local vector index, so
+explanations name the actual file and function that failed instead of
+guessing. In the package's eval harness, RAG-grounded explanations won 35
+of 43 blind comparisons, with the gap concentrated in pointing at the right
+fix location and not inventing details (see "Does RAG actually help?"
+below). It is off by default because it needs an optional extra and a
+one-time index build.
 
 The middleware supports both synchronous (WSGI) and asynchronous (ASGI)
 views. It auto-detects the view chain at startup and routes requests through
@@ -62,11 +69,17 @@ the matching path, so no extra configuration is required for either server
 type. Tracebacks are sanitized before leaving the process, and API calls are
 rate limited.
 
+![Django debug page with the explanation banner under the exception headline](https://raw.githubusercontent.com/topunix/django-explain-errors/main/docs/images/debug-page-banner.png)
+
+*Real `gpt-4o-mini` output with RAG enabled, recorded by the eval harness
+on its `missing_fk` fixture.*
+
 ## Scope
 
 This package explains errors for a person, not for a coding agent to consume
-programmatically. The explanation is written for a human reader, in a terminal or an editor's
-integrated terminal, and the output format assumes that reader.
+programmatically. The explanation is written for a human reader, on Django's
+debug page in the browser or in a terminal, and the output format assumes
+that reader.
 
 If a coding agent is doing the debugging, it does not need this. Agents read tracebacks directly,
 and tools that expose live runtime state (debugger-over-MCP servers, `mcp-django`) serve that case
@@ -77,9 +90,16 @@ Local development only. It requires `DEBUG = True` and is inert otherwise.
 ## Features
 
 - Captures Django errors and exceptions
+- Shows the explanation on Django's debug page, directly under the
+  exception headline (`EXPLAIN_ERRORS_INJECT_DEBUG_PAGE`, on by default)
+- Prints the explanation to stdout, for terminal workflows and logs
+  (`EXPLAIN_ERRORS_PRINT_STDOUT`, on by default)
+- Optional JSON 500 response instead of the debug page
+  (`EXPLAIN_ERRORS_PRESERVE_DEBUG_PAGE = False`)
 - Explains errors using OpenAI, Anthropic's Claude models, or any other
   OpenAI-compatible endpoint (Ollama, LM Studio, Azure, gateways) via `OPENAI_BASE_URL`
-- Optional codebase-aware explanations (RAG) backed by a local sqlite-vec index (see the RAG section below)
+- Codebase-aware explanations via RAG over a local sqlite-vec index
+  (recommended; see "Codebase-aware explanations" below)
 - Explanations in your language via `EXPLAIN_ERRORS_LANGUAGE`, with exception names,
   identifiers, and code kept in English
 - Redacts secrets, tokens, and emails from tracebacks before sending
@@ -96,13 +116,16 @@ pip install django-explain-errors
 
 2. **Add the middleware to your Django project**:
 
-   - Open your `settings.py` file and add the middleware to the `MIDDLEWARE` list:
+   - Open your `settings.py` file and register the middleware only when `DEBUG` is on (see
+     Production Safety below for why):
 
      ```python
      MIDDLEWARE = [
          ...
-         'explain_errors.middleware.ExplainErrorsMiddleware',
      ]
+
+     if DEBUG:
+         MIDDLEWARE.append('explain_errors.middleware.ExplainErrorsMiddleware')
      ```
 
      In the default preserve mode, `process_exception` returns `None`, so exception handling
@@ -116,15 +139,39 @@ pip install django-explain-errors
 
 3. **Set up environment variables**:
 
-   - Create a `.env` file in your project's root directory and add your OpenAI API key. Alternatively, you can set the API key in `settings.py`:
+   - Create a `.env` file in your project's root directory and add your API key. Alternatively, you can set it in `settings.py`:
 
      ```plaintext
-     OPENAI_API_KEY=your_openai_api_key_here
+     OPENAI_API_KEY=your_api_key_here
      ```
 
    The API key is not required if you set `OPENAI_BASE_URL` to a local
    server such as Ollama, which does not authenticate requests.
 
+## Production Safety
+
+This middleware is intended for local development only. When active, it sends exception
+tracebacks to the configured LLM provider, which may include source code, file paths, and
+local variable values. Keep it out of production.
+
+**Primary safeguard:** register the middleware only when `DEBUG` is on, or only in your
+development settings module:
+
+```python
+# settings.py
+if DEBUG:
+    MIDDLEWARE.append("explain_errors.middleware.ExplainErrorsMiddleware")
+```
+
+See Installation above for where the middleware can sit in `MIDDLEWARE`.
+
+**Secondary safeguard:** run Django's deployment checks in CI against your production settings.
+This fails the build if `DEBUG = True` (`security.W018`):
+
+```bash
+python manage.py check --deploy --fail-level WARNING
+```
+
 ## Usage
 
 1. **Ensure DEBUG is set to True**:
@@ -137,17 +184,59 @@ pip install django-explain-errors
 
 2. **Trigger an error in your Django application**:
 
-   The middleware captures the error, sends it to the configured model for explanation, and prints the explanation to stdout. By default (`EXPLAIN_ERRORS_PRESERVE_DEBUG_PAGE=True`), it then lets exception handling continue normally, so Django (or whatever else is watching, such as `runserver_plus` or Sentry — see Compatibility below) renders exactly what it would without this middleware installed. Set `EXPLAIN_ERRORS_PRESERVE_DEBUG_PAGE = False` to instead get a JSON `500` response containing the error message and the explanation.
+   The middleware captures the error, sends it to the configured model for explanation, prints the explanation to stdout, and adds it as a banner on Django's debug page. By default (`EXPLAIN_ERRORS_PRESERVE_DEBUG_PAGE=True`), exception handling then continues normally, so Django (or whatever else is watching, such as `runserver_plus` or Sentry, see Compatibility below) renders its usual response. The only change is the banner on Django's own debug page. Set `EXPLAIN_ERRORS_INJECT_DEBUG_PAGE = False` to remove it, or `EXPLAIN_ERRORS_PRESERVE_DEBUG_PAGE = False` to instead get a JSON `500` response containing the error message and the explanation.
+
+   In the terminal, the explanation is printed with the model that produced it:
+
+   ```
+   Error explanation (gpt-4o-mini):
+    The view raised a ValueError because ...
+   ```
 
 ## Async Support
 
 The middleware exposes both `sync_capable = True` and `async_capable = True`. At initialization it inspects `get_response` to decide whether it is part of a sync or async chain:
 
 - Under WSGI (for example `runserver` with sync views), requests flow through the synchronous handler.
-- Under ASGI (for example with async views), requests are awaited through the async handler. The blocking OpenAI call is offloaded with `asgiref.sync.sync_to_async` so the event loop is not blocked.
+- Under ASGI (for example with async views), requests are awaited through the async handler. The blocking model API call is offloaded with `asgiref.sync.sync_to_async` so the event loop is not blocked.
 
 No additional settings are needed. See Installation above for where to place the middleware in `MIDDLEWARE`.
 
+## Debug page injection
+
+When Django renders its debug page for a 500, `explain_errors` also inserts a banner
+containing the explanation directly under the exception headline, in addition to printing
+it to stdout.
+
+Controlled by `EXPLAIN_ERRORS_INJECT_DEBUG_PAGE`, default `True`. Injection happens only
+when all of the following hold:
+
+- `DEBUG` is `True`
+- `EXPLAIN_ERRORS_INJECT_DEBUG_PAGE` is `True` (the default)
+- `EXPLAIN_ERRORS_PRESERVE_DEBUG_PAGE` is `True` (the default). With
+  `EXPLAIN_ERRORS_PRESERVE_DEBUG_PAGE=False`, the JSON 500 path runs instead and there is
+  no debug page to inject into.
+- an explanation was actually produced (not throttled, and the API call succeeded)
+
+The banner appears only on the HTML debug page, styled inline (bordered box, light
+background) so it reads on Django's page. The explanation is HTML-escaped first, then a small
+Markdown subset (inline code, code blocks, bold, lists) is rendered as HTML. Nothing from the
+model is ever marked safe.
+
+**Fails open.** Any problem building or inserting the banner (a missing request, an
+unexpected debug page layout, anything else) logs one warning and leaves Django's normal
+debug page untouched. This code can never turn a working debug page into a broken one.
+
+**Custom exception reporters.** If your project already sets a custom
+`DEFAULT_EXCEPTION_REPORTER`, or something earlier in the request sets
+`request.exception_reporter_class`, `explain_errors` leaves it alone and skips injection
+(logged at debug level) rather than overriding it.
+
+**Upgrading.** Turning this on, or upgrading to a version where it defaults on, changes
+what Django's debug page looks like: a new section appears above the request metadata
+table. If you rely on the debug page's exact markup (a scraper, a screenshot test), account
+for this.
+
 ## Compatibility
 
 How this middleware interacts with other error-handling and debugging tools, in the default
@@ -155,10 +244,10 @@ preserve mode and with `EXPLAIN_ERRORS_PRESERVE_DEBUG_PAGE=False`:
 
 | Package | Preserve mode (default) | `EXPLAIN_ERRORS_PRESERVE_DEBUG_PAGE=False` |
 | ------- | ------------------------ | ------------------------------------------- |
-| Django Debug Toolbar | Works — Django renders its normal debug page, and Debug Toolbar injects into it. | Broken — the JSON 500 response has no HTML to inject into. |
+| Django Debug Toolbar | Works — Django renders its debug page (with the explanation banner, unless `EXPLAIN_ERRORS_INJECT_DEBUG_PAGE = False`), and Debug Toolbar injects into it. | Broken — the JSON 500 response has no HTML to inject into. |
 | Sentry, Rollbar | Work — the exception propagates and Django re-raises it, so `got_request_exception` fires. | Broken — returning a response ends exception handling before `got_request_exception` fires. |
 | Django REST Framework | Partial — only exceptions DRF does not already handle itself reach this middleware. | Partial, same reason. |
-| Silk and other profiling panels | Timings are inflated by the OpenAI call, since `process_exception` blocks the request path. | Same. |
+| Silk and other profiling panels | Timings are inflated by the model API call, since `process_exception` blocks the request path. | Same. |
 | CORS, GZip, WhiteNoise | No interaction. | No interaction. |
 | `runserver_plus` / Werkzeug debugger | Works — returning `None` re-raises the original exception, and `django-extensions` replaces Django's debug-page renderer with one that re-raises instead, so Werkzeug's WSGI wrapper catches it and shows the interactive debugger. | Broken — the JSON 500 response ends exception handling before it reaches `runserver_plus`'s exception hook, so the Werkzeug debugger never appears. |
 
@@ -182,9 +271,11 @@ developer is actually investigating.
 | `DEBUG` | Yes | The middleware is only active when `DEBUG=True`. When `False`, requests pass through untouched. |
 | `OPENAI_MODEL` | No | Model used for explanations. Defaults to `gpt-4o-mini`. |
 | `OPENAI_MAX_TOKENS` | No | Ceiling on tokens generated for the explanation, not a target — the system prompt itself asks for a concise answer. Defaults to `1000`; scales up automatically when `EXPLAIN_ERRORS_LANGUAGE` is set (see below), unless you set this explicitly, which always overrides the scaling. |
-| `OPENAI_TIMEOUT` | No | Request timeout in seconds for the OpenAI client. Defaults to `10`. |
-| `OPENAI_MAX_TRACEBACK_CHARS` | No | Traceback is trimmed to its last N characters before being sent. Defaults to `3000`. |
-| `EXPLAIN_ERRORS_PRESERVE_DEBUG_PAGE` | No | When `True` (the default), the middleware prints the explanation to stdout and returns `None`, so exception handling continues normally and Django renders its standard debug page. Set to `False` to instead return a JSON 500 response, which ends exception handling early (see Compatibility above). |
+| `OPENAI_TIMEOUT` | No | Request timeout in seconds for model API calls. Defaults to `10`. |
+| `OPENAI_MAX_TRACEBACK_CHARS` | No | Total character budget for the traceback sent to the model. Application frames (your own code, as opposed to Django, the standard library, or installed packages) are always kept; library frames fill whatever budget remains, nearest the raise point first, with an `... N library frames omitted ...` line where frames are dropped. If the application frames alone exceed the budget, falls back to keeping the last N characters of the raw traceback. Defaults to `3000`. |
+| `EXPLAIN_ERRORS_PRESERVE_DEBUG_PAGE` | No | When `True` (the default), the middleware returns `None` (after printing the explanation to stdout, unless `EXPLAIN_ERRORS_PRINT_STDOUT = False`), so exception handling continues normally and Django renders its debug page (with the explanation banner, controlled by `EXPLAIN_ERRORS_INJECT_DEBUG_PAGE`). Set to `False` to instead return a JSON 500 response, which ends exception handling early (see Compatibility above). |
+| `EXPLAIN_ERRORS_INJECT_DEBUG_PAGE` | No | When `True` (the default), also injects the explanation as a banner into Django's debug page, in addition to stdout. Requires `EXPLAIN_ERRORS_PRESERVE_DEBUG_PAGE=True` (the default); see Debug Page Injection above. |
+| `EXPLAIN_ERRORS_PRINT_STDOUT` | No | When `True` (the default), prints the explanation to stdout. Set to `False` to suppress it, for example when `EXPLAIN_ERRORS_INJECT_DEBUG_PAGE` already shows it in the browser. The failure message (when the model API call itself errors) always prints. For requests where nobody views the debug page (API clients, which get Django's plain-text error response, and `fetch`/HTMX requests, whose HTML response is never displayed), stdout is the only channel that shows the explanation, so turn this off only in browser-first workflows. |
 | `OPENAI_BASE_URL` (env or settings) | No | Base URL for any OpenAI-compatible API (for example Ollama at `http://localhost:11434/v1`). When set, a missing API key is replaced with a placeholder since local servers do not require one. |
 | `EXPLAIN_ERRORS_MAX_CALLS` | No | Together with `EXPLAIN_ERRORS_WINDOW_SECONDS`, caps API spend to at most this many explanations within a rolling window; once the cap is hit, further errors in that window are not sent for explanation until an earlier call ages out. Defaults to `5`. |
 | `EXPLAIN_ERRORS_WINDOW_SECONDS` | No | Length in seconds of the rolling window `EXPLAIN_ERRORS_MAX_CALLS` is measured against. Defaults to `60` (with the defaults, at most 5 explanations per 60-second window). |
@@ -256,6 +347,13 @@ read them in another language instead:
 EXPLAIN_ERRORS_LANGUAGE = "Spanish"  # or the code form, "es"
 ```
 
+There is no fixed list of supported languages. `EXPLAIN_ERRORS_LANGUAGE` accepts
+any language the configured model can write, because the setting adds one clause
+to the system prompt (see `LANGUAGE_CLAUSE_TEMPLATE` in
+`explain_errors/middleware.py`), not a translation catalog with its own
+maintained language list. How well it works varies by model; see the known
+limitation below.
+
 This is independent of Django's own `LANGUAGE_CODE`, which controls the language your
 site serves to its users, not the language you read explanations in. Regardless of
 `EXPLAIN_ERRORS_LANGUAGE`, exception type names, Django and Python identifiers, code,
@@ -270,13 +368,18 @@ generally solid against OpenAI and Anthropic's APIs, but a small local model tha
 writes fluent English explanations may produce broken or mixed-language output once
 asked to switch languages.
 
-When a language is configured, the token ceiling (`OPENAI_MAX_TOKENS`) is scaled up
-automatically so explanations in languages that tokenize less efficiently than English
-aren't cut off mid-sentence. This scaling is deliberately generous — billing follows
-tokens actually generated, so unused headroom costs nothing — rather than precise: the
-underlying tokens-per-word figures are estimates, not direct measurements, and the
-default model (`gpt-4o-mini`) uses the `o200k_base` tokenizer, which handles non-Latin
-scripts considerably better than the `cl100k_base`-era ratios these estimates lean on.
+When a language is configured and `OPENAI_MAX_TOKENS` isn't set explicitly, the
+token ceiling defaults to 3,000 instead of 1,000, a flat 3x multiplier applied the
+same way regardless of how well or poorly a given language is known to tokenize, so
+explanations in languages that use more tokens per word than English aren't cut off
+mid-sentence. This is a ceiling, not a target: billing follows tokens actually
+generated, so the extra headroom costs nothing if unused. Setting `OPENAI_MAX_TOKENS`
+explicitly always overrides this scaling, at any value, including one lower than the
+unscaled 1,000 default. The multiplier itself is deliberately generous rather than
+precise: the underlying tokens-per-word figures are estimates, not direct
+measurements, and the default model (`gpt-4o-mini`) uses the `o200k_base` tokenizer,
+which handles non-Latin scripts considerably better than the `cl100k_base`-era ratios
+these estimates lean on.
 
 ## Codebase-aware explanations (RAG)
 
@@ -286,7 +389,9 @@ also retrieves the most relevant chunks of your own project's source code
 from a local vector index and includes them in the prompt, so explanations
 can reference your actual functions and classes instead of guessing at them.
 
-This feature is opt-in and adds no dependencies or behavior unless enabled.
+Recommended for most projects. It is opt-in only because setup takes three
+steps (install the extra, build the index, enable it), and it adds no
+dependencies or behavior until you do.
 
 ### Install the extra
 
@@ -309,7 +414,7 @@ python manage.py build_error_index
 
 This walks your project, chunks Python files by top-level function/class
 (and other text files by fixed-size line windows), embeds each chunk with
-the OpenAI embeddings API, and writes them to a local index file. Re-run it
+the configured endpoint's embeddings API, and writes them to a local index file. Re-run it
 whenever your source changes meaningfully. Indexing is not automatic.
 Rebuilding is idempotent: it builds into a temp file and atomically replaces
 the previous index.
@@ -329,15 +434,14 @@ EXPLAIN_ERRORS_RAG_ENABLED = True
 | `EXPLAIN_ERRORS_RAG_ENABLED` | `False` | Master switch for the RAG layer. |
 | `EXPLAIN_ERRORS_RAG_INDEX_PATH` | `<BASE_DIR>/.explain_errors_index.db` | Path to the local vector index file. |
 | `EXPLAIN_ERRORS_RAG_TOP_K` | `4` | Number of chunks retrieved and injected into the prompt. |
-| `EXPLAIN_ERRORS_RAG_EMBED_MODEL` | `"text-embedding-3-small"` | OpenAI embedding model used for indexing and retrieval. |
+| `EXPLAIN_ERRORS_RAG_EMBED_MODEL` | `"text-embedding-3-small"` | Embedding model used for indexing and retrieval. Must exist on the configured endpoint. |
 | `EXPLAIN_ERRORS_RAG_INCLUDE` | `None` (defaults to `BASE_DIR`) | List of directories to index. |
 | `EXPLAIN_ERRORS_RAG_EXCLUDE` | migrations, venvs, `node_modules`, static, media, `.git` | Directory names to skip while indexing. |
 | `EXPLAIN_ERRORS_RAG_MAX_PROMPT_CHARS` | `6000` | Combined character budget for the traceback + retrieved source sections of the prompt. |
 
 Every chunk of source code and every retrieval query is passed through the
 same `sanitize_traceback()` redaction used for tracebacks, which strips
-patterns that look like secrets, tokens, and emails before anything is sent
-to OpenAI or written to the index. It's a pattern-based filter, not a
+patterns that look like secrets, tokens, and emails before anything is sent to the model API or written to the index. It's a pattern-based filter, not a
 guarantee: it catches recognizable secret shapes, not arbitrary sensitive
 data that doesn't match one.
 
@@ -361,40 +465,112 @@ else.)
 
 ### Before / after
 
-**Without RAG**, traceback only:
-
-> Your `ValueError` is raised because the value passed to `foo()` couldn't
-> be converted to an integer. Check where `foo()` is called and make sure
-> you're passing a numeric string.
-
-**With RAG**, grounded in the actual function:
+A real result from the eval harness (`missing_fk`, one of the fixtures in
+`evals/fixtures.py`): a view creates a new `Post` without setting the
+required `author` foreign key. The traceback the model actually received
+was already truncated to `OPENAI_MAX_TRACEBACK_CHARS`, so it contains no
+application code at all, only Django/SQLite internals:
 
-> In `myapp/utils.py`, `foo()` calls `int(value)` on line 12 without a
-> `try`/`except`, so any non-numeric `value` raises `ValueError` straight
-> through to the caller. Since `foo()` is called from `myapp/views.py` with
-> unvalidated form input, add validation there or wrap the `int()` call in
-> `foo()` with a clear error message.
+This example was recorded before 0.7.0, when tracebacks were trimmed to
+their last N characters. Since 0.7.0 your application's frames are always
+kept, so a traceback-only explanation would now see `clone_latest_post`
+too. The measured results in "Does RAG actually help?" below were run
+after that change.
 
-## Example
-
-Here is an example of how to use the middleware in a Django project:
-
-```python
-# settings.py
-
-DEBUG = True
+```
+...(truncated)...
+  File ".../django/db/models/base.py", line 904, in save
+    self.save_base(
+  ...
+  File ".../django/db/backends/utils.py", line 105, in _execute
+    return self.cursor.execute(sql, params)
+           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+  File ".../django/db/backends/sqlite3/base.py", line 359, in execute
+    return super().execute(query, params)
+           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+django.db.utils.IntegrityError: NOT NULL constraint failed: blog_post.author_id
+```
 
-MIDDLEWARE = [
-    ...
-    'explain_errors.middleware.ExplainErrorsMiddleware',
-]
+**Without RAG**, traceback only:
 
-# .env
+> The error "django.db.utils.IntegrityError: NOT NULL constraint failed: blog_post.author_id" occurs when you attempt to save a model instance but the `author_id` field does not receive a value, even though it requires one (is defined as `NOT NULL`).
+>
+> This typically indicates that the `author` field in your `Post` model (or similar) is mandatory, but you did not provide an `author` when creating or updating the post.
+>
+> To fix this:
+>
+> 1. Ensure that you are assigning a valid user or author instance to the `author` field before saving the `Post` model. For example:
+>    ```python
+>    post.author = some_user_instance
+>    ```
+>
+> 2. If you intended for `author_id` to be optional, adjust the model definition to allow null values by modifying the field:
+>    ```python
+>    author = models.ForeignKey(User, on_delete=models.CASCADE, null=True)
+>    ```
+>
+> 3. If the migration is necessary (if you did change the model), run:
+>    ```bash
+>    python manage.py makemigrations
+>    python manage.py migrate
+>    ```
+>
+> Make sure that every time you save a `Post`, it has a valid author assigned.
 
-OPENAI_API_KEY=your_openai_api_key_here
-```
+**With RAG**, grounded in the actual function:
 
-When an error occurs, you will see an explanation printed to stdout.
+> The error `django.db.utils.IntegrityError: NOT NULL constraint failed: blog_post.author_id` occurs because when you're creating a new `Post` instance in `clone_latest_post`, you're not providing an `author` for the new draft. The `author` field in the `Post` model is a ForeignKey that cannot be null, and thus must be populated.
+>
+> To fix this, modify the `clone_latest_post` function to include an `author` when creating the draft. You could retrieve the author from the latest post and use it like so:
+>
+> ```python
+> def clone_latest_post(request):
+>     """Duplicate the most recent post as a new draft, ready for editing."""
+>     latest = Post.objects.order_by("-id").first()
+>     draft = Post.objects.create(
+>         title=f"Copy of {latest.title}",
+>         slug=f"copy-of-{latest.slug}",
+>         body=latest.body,
+>         author=latest.author,  # Add this line to specify the author
+>     )
+>     return HttpResponse(f"Created draft #{draft.id}")
+> ```
+>
+> This ensures the `draft` has a valid `author`, satisfying the NOT NULL constraint.
+
+### Does RAG actually help?
+
+To check whether RAG-grounded explanations are actually better, not just
+longer, the package ships an eval harness (`evals/`): fifteen deliberately
+broken Django views, each explained twice (once from the traceback alone,
+once with RAG enabled) and judged by a separate model, blind to which
+explanation is which, against the error's known cause and correct fix
+location. Which side the judge sees as "A" is randomized per comparison so
+position can't bias the result.
+
+Across three runs (45 judged comparisons, 2 judge failures, 43 scored),
+RAG-on won 35, RAG-off 5, and 3 tied. The gap isn't spread evenly across
+everything the judge checks. It's concentrated in whether the explanation
+names the right file and function, and whether it invents details along
+the way: on `points_to_fix_location`, RAG-on answered yes in 26 of the
+group-A comparisons against RAG-off's 13; on `no_fabrication`, 26 against
+17. Without source access, `gpt-4o-mini` tends to invent a
+plausible-sounding function name or parameter rather than say it doesn't
+know; given the actual code via RAG, it mostly does not.
+
+Three limitations are worth knowing before trusting this uncritically: RAG
+can anchor on the wrong retrieved chunk, as it did in one fixture
+(`missing_post_key`) where the fix got redirected to a retrieved template
+instead of the view; the judge is shown the failing function's own
+source, which is the same source RAG-on's retriever draws from, so part
+of RAG-on's `no_fabrication` advantage may be judge and generator
+overlapping on material RAG-off never sees rather than RAG-on being more
+careful; and claim statuses are spot-checked, not exhaustively audited --
+a script that flagged 14 of 363 claims on one run, all correct on manual
+inspection, is a sample that turned up no false positive, not a proof
+that none exists. Full per-fixture results, the judge prompt, and how to
+reproduce this (about $1.37 for a `--runs 3` pass, most of it judge cost)
+are in [`evals/README.md`](evals/README.md).
 
 ## License
 
@@ -407,5 +583,5 @@ Contributions are welcome! Please open an issue or submit a pull request for any
 ## Acknowledgements
 
 - [Django](https://www.djangoproject.com/)
-- [OpenAI](https://www.openai.com/)
+- [OpenAI Python SDK](https://github.com/openai/openai-python)
 - [python-dotenv](https://github.com/theskumar/python-dotenv)