docs: refresh per-package AGENTS.md + di-explainer to current binders

Six per-package AGENTS.md tables and the di-explainer wiring trace all
showed pre-ADR-014 binder shapes. Refreshed to the post-ADR-015
reality:

- Per-package "Public exports" tables now show the
  (config, tracer, logger, bus, queue) production signature and the
  (tracer, logger, bus, queue) dev-seed companion. auth and
  marketing-pages also list their newly-public ./di/container,
  ./di/symbols, and (marketing-pages only) ./services/mailer +
  ./services/recording-mailer subpaths.
- di-explainer's wiring trace adds the resolveEventsAndJobs* step in
  bindAll(), the (config, tracer, logger, bus, queue) binder
  signature, and the // <gen:event-handlers> / // <gen:jobs>
  injection sites.

No code change; pre-existing AGENTS.md staleness predates ADR-014 +
ADR-015 — this commit catches both up.

docs/architecture/di-explainer.html

@@ -1188,9 +1188,12 @@ footer .colophon {
       <pre class="trace-tree"><code>bindAll()
   └─ resolveInstrumentation()         ← Rule 0 (DSN check)
        └─ Noop or Sentry binders      ← bind to sharedContainer
-  └─ bindProductionX(config, tracer, logger)
+  └─ resolveEventsAndJobs*()          ← ADR-015 (env-driven bus + queue)
+       └─ Payload-backed in prod, in-memory in dev-seed
+  └─ bindProductionX(config, tracer, logger, bus, queue)
        └─ feature container also binds TRACER + LOGGER
-       └─ withSpan(withCapture(...)) at every use case + controller</code></pre>
+       └─ withSpan(withCapture(...)) at every use case + controller
+       └─ // &lt;gen:event-handlers&gt; / // &lt;gen:jobs&gt; injection sites</code></pre>
 
       <p class="trace-p"><strong>Why per-feature containers also get the binding:</strong> repository classes resolve TRACER/LOGGER through the container; controllers and use cases receive instrumentation via the bind-time wrapper instead.</p>
     </div>