docs(architecture): adopt inline synchronous ingestion (ADR-0017)

Why:
- ingestion is inline in the request instead of dispatched through RabbitMQ/outbox/worker; ADR-0014 is superseded (not deleted) and named as the design to adopt once ingestion needs to move off the request path.

Changes:
- new ADR-0017 plus amendments to every ADR/plan that referenced the job-shaped/broker contract, so none silently contradict it.

Impact:
- no broker, outbox, or worker code; rabbitmq test marker removed.

docs/adr/0014-durable-job-dispatch-with-rabbitmq.md

@@ -2,7 +2,14 @@
 
 ## Status
 
-Proposed
+Superseded by
+[0017](0017-synchronous-ingestion-in-the-request-path.md)
+
+ADR-0017 defers this decision rather than rejecting it: ingestion currently runs
+inline in the `POST /v1/files` request, with no broker, no outbox, and no queue.
+This ADR remains the intended design for when ingestion becomes slow enough to
+need one — ADR-0017 lists the triggers, and names an in-process Postgres-claimed
+runner as the likely intermediate step before adopting a broker.
 
 ## Context