feat: update ingest, registry, and UI flows

README.md

@@ -119,11 +119,18 @@ failure_events
 - `GET /assets/{id}`
 - `GET /assets/{id}/components`
 - `GET /assets/{id}/tickets`
+- `POST /machines/dispatch`
+- `POST /machines/return-to-stock`
 - `GET /components`
 - `GET /components/{id}`
 - `GET /assets/{id}/timeline`
 - `GET /components/{id}/timeline`
 
+### Organization Registry
+
+- `GET /customers`, `POST /customers`
+- `GET /locations`, `POST /locations`
+
 ### Tickets
 
 - `POST /connectors/tickets/sync`
@@ -201,3 +208,15 @@ is empty and no `DATABASE_DSN` env var is set, the discrete fields are used
 to build the DSN.
 
 An example file is available as `config.example.json`.
+
+## Database Bootstrap
+
+At this stage the project uses clean bootstrap instead of in-place schema migration for ownership changes.
+
+Use:
+
+```bash
+make db-reset
+```
+
+This command drops and recreates the configured database, then applies the current schema from `migrations/`.