diff --git a/PROJECT_STATE.md b/PROJECT_STATE.md
index 3060a5b..51295dd 100644
--- a/PROJECT_STATE.md
+++ b/PROJECT_STATE.md
@@ -1666,3 +1666,35 @@ Handler — both net-new, not yet built.
   source of truth alongside the other 3 workflows. (3) MCP Hub: registry push + production
   deployment of the now-committed connector remain separate, explicitly-gated checkpoints.
   WF4's own timeout/retry gap remains open, deferred, non-blocking.
+
+## Branch push and Unraid redeploy (2026-08-05)
+
+- Pushed `feat/live-n8n-ragcore-integration` to `origin` (Gitea on the same Unraid host),
+  now tracking `origin/feat/live-n8n-ragcore-integration` (`0571a40`).
+- **Redeployed the live Fleet Ops instance** (`http://192.168.10.150:1236`) from this
+  branch, bringing it from the previously-deployed `0da5251` up to `0571a40` — 5 commits,
+  the meaningful one being the `RAGcoreKnowledgeProvider` rewrite (`e5d8466`); the rest
+  are `PROJECT_STATE.md`-only evidence commits.
+  - Followed the deployment directory's own established archive convention
+    (`deploy/unraid/README.md`: "deployed from a committed source archive"): `git archive`
+    of `HEAD` as `source-0571a40.tar.gz`, matching the naming pattern of the existing
+    archives already in `/mnt/user/appdata/mobilityops/.deploy/`; `scp`'d it there;
+    extracted over the deployment directory excluding `.env` and `.deploy` itself (so the
+    live secrets file and archive history were never touched); updated
+    `.deploy/source-revision` to the new full commit hash, matching its existing format.
+  - `docker compose -p mobilityops -f compose.yaml -f compose.unraid.yaml up --build -d db
+    api web` — `api` image rebuilt and the container recreated (picked up the new code);
+    `web` rebuilt too but didn't need recreating (no frontend changes this branch); `db`
+    untouched. Migrations ran automatically in the `api` entrypoint with no errors.
+  - **Verified live**: `/health` returns `200` from inside the `api` container; the new
+    `/api/v1/integrations/n8n/procedures` endpoint (added this branch, needed for n8n
+    workflow 3) is reachable through the public web proxy and correctly enforces auth
+    (`422`, missing `X-Service-Token`, not a `404` — proves the route exists and is live,
+    not just that the proxy responds). `KNOWLEDGE_PROVIDER=demo` confirmed unchanged in the
+    live `.env` (only extracted new source files, never touched it) — the demo Knowledge
+    Assistant is still what's live, exactly as intended.
+  - No seed reset run (this was an update to a running instance with real accumulated
+    demo data, not the initial deploy — re-seeding would have been destructive and wasn't
+    warranted by anything in this branch's changes).
+- **Not done**: no PR opened/merged to `master` — the user asked for commit, push, and
+  redeploy, not a merge; `master` is untouched and still 19 commits behind this branch.