Wiki is nine months out of date with the shipped system #1

The wiki was last updated on 2025-12-07. Since then the API grew from a single item-store
service to eleven service modules (customers, orders, payments, inventory, fulfillment,
shipments, returns, webhooks, admin, health), gained a background worker, a transactional
outbox, MinIO object storage and a Stripe integration — and a storefront frontend landed
today in OpenTaberna/frontend.

None of that is in the wiki, and several pages actively mislead:

• home.md names MySQL for storage; the system runs PostgreSQL 17.
• home.md diagrams an Elasticsearch / Logstash / Kibana stack and an Nginx reverse proxy
  that exist in no compose file.
• Database/Architecture.md documents shops, categories, item_categories,
  item_media, attributes, item_attributes and item_events — none of these tables
  exist. The real schema is 12 tables and the item detail is held in JSONB columns.
• Getting-Started.md clones PhilippTheServer/opentaberna, a repository layout that does
  not exist; the project is four repositories.
• Getting-Started.md documents endpoints under /api/v1/...; the real prefix is /v1/....
• Getting-Started.md claims GET /health returns {"status":"healthy","version":"0.1.0"}
  and that GET / returns the API version. The real health payload is
  {"status":"ok","timestamp":...} and GET / is a 404.
• Nothing documents the authorization model (the admin role plus the azp client check),
  the order/payment/return/shipment state machines, or the storefront.

Expected once solved

The wiki describes the system that is actually running:

1. Every endpoint the API serves is documented, and every documented endpoint exists.
2. The schema page lists the tables that are really in the database.
3. Setup instructions work against the four real repositories and the real ports.
4. The authorization model and order lifecycle are documented.
5. An automated check fails when the wiki drifts from the API again.