M14: add n8n execution health telemetry

n8n/workflows/MANIFEST.md

@@ -17,8 +17,9 @@ credential values are never embedded; nodes reference named n8n credentials inst
 | Live workflow ID | `mobilityops-return-processing` |
 | Active status (as of 2026-08-04) | Active / Published |
 | Error Workflow | `Fleet Ops — Workflow Error Handler` (wired) |
-| Timeouts / bounded retries | `Record follow-up` HTTP node: 15s timeout, retry on fail (3 tries, 1000ms wait) |
-| Checksum (sha256) | `e5b6ba02a7824867620ceaf214224521d52de76337604b947f26f1b0b5432358` (updated 2026-08-05 — the committed file had invalid JSON, a missing `},` between two node objects; fixed, no live workflow change) |
+| Timeouts / bounded retries | `Record follow-up` and heartbeat HTTP nodes: 15s timeout, retry on fail (3 tries, 1000ms wait) |
+| Execution telemetry | Successful runs POST execution ID and status to `/api/v1/integrations/n8n/heartbeat`; failed runs are registered by the Error Workflow. |
+| Checksum (sha256) | `17b8dd5b8e7ab5d0c0856a40f4199a401ad38f63895f611a096a80c9740f1e99` (heartbeat-enabled definition, 2026-08-10) |
 
 ## 2. Fleet Ops — Scheduled Data Quality Scan
 
@@ -32,13 +33,14 @@ credential values are never embedded; nodes reference named n8n credentials inst
 | Live workflow ID | `mobilityops-scheduled-quality-scan` |
 | Active status (as of 2026-08-04) | Active / Published |
 | Error Workflow | `Fleet Ops — Workflow Error Handler` (wired) |
-| Timeouts / bounded retries | `Run quality scan` HTTP node: 15s timeout, retry on fail (3 tries, 1000ms wait) |
-| Checksum (sha256) | `c0d46e0519118e6336e35c4ea2a67edb2f14bd007909ccf9256c93733751244a` |
+| Timeouts / bounded retries | Scan and heartbeat HTTP nodes: 15s timeout, retry on fail (3 tries, 1000ms wait) |
+| Execution telemetry | Every successful scheduled/manual run posts an idempotent heartbeat with its n8n execution ID. |
+| Checksum (sha256) | `f0bda8b0fa99d1a2403e970e00bd1f896cd4d10eaa626147fcca577a7ad7cb46` |
 
 ## 3. Fleet Ops — RAGcore Procedure Sync
 
-Fully built and saved live (6 real nodes: Schedule Trigger → List procedures → Prepare
-uploads → Upload to RAGcore → Summarize sync result → Report sync result to Fleet Ops).
+Fully built with 7 real nodes: Schedule Trigger → List procedures → Prepare uploads →
+Upload to RAGcore → Summarize sync result → Report sync result → Report heartbeat.
 
 **Published/active as of 2026-08-05**, once RAGcore itself went live (see
 `PROJECT_STATE.md`'s "RAGcore actually went live" entry): the workflow's `RAGcore Sync
@@ -69,7 +71,8 @@ the same way via the same CLI import path, re-verified.
 | Live workflow ID | `6wbkc4d1AouGpmWT` |
 | Active status (as of 2026-08-05) | **Active / Published** |
 | Error Workflow | `Fleet Ops — Workflow Error Handler` (wired) |
-| Checksum (sha256) | `643c0515a50fed3d35e28f0b8cb17841f6f8d91699944980b5c56e619d5bf2a6` |
+| Execution telemetry | Successful syncs report both the bounded sync result and the canonical workflow heartbeat. |
+| Checksum (sha256) | `8644d9faec4d17a43ba797e300b91fff976881c9b259e457fadd5a7cfaf39c6f` |
 
 ## 4. Fleet Ops — Workflow Error Handler
 
@@ -89,7 +92,8 @@ Ops, which registers an audit event idempotently keyed on `execution_id`.
 | Live workflow ID | `Xppn2rAEqUuyiCJF` |
 | Active status (as of 2026-08-04) | Active / Published |
 | Error Workflow (on itself) | `- No Workflow -` (deliberately unset — prevents a recursive error loop) |
-| Checksum (sha256) | `d9e2795b917a89a9b4a733e435661585f8011bc97f134d3643dee93ea05b0be6` |
+| Execution telemetry | A successfully handled failure posts its own execution heartbeat after registering the target failure. |
+| Checksum (sha256) | `1e50cf8b679b9e9f9b5cf4a1594bda459597ade40f44e8a68f540890f9c4b61d` |
 
 Validated this round: mock-data run (Error Trigger pinned to a realistic payload)
 produced a real `200 {"status":"registered", ...}` from the live Fleet Ops server;