13 Commits

Include renames

Author	SHA1	Message	Date
NuklearRabbit	ae39a8947f	M39: harden application and acceptance gates	2026-08-17 03:17:44 +02:00
NuklearRabbit	e1b700b10e	M27: make backup checksums portable	2026-08-10 16:19:18 +02:00
NuklearRabbit	f0f1be83ae	M23: automate verified database backups	2026-08-10 15:46:06 +02:00
NuklearRabbit	689e499634	M22: implement operational observability	2026-08-10 15:42:26 +02:00
NuklearRabbit	5d7a5e7359	M19: harden performance and recovery	2026-08-10 12:51:41 +02:00
NuklearRabbitandClaude Sonnet 5	e0c107a94a	n8n: store cleaned workflow definitions as repo source of truth ... Move the two live-validated workflows into n8n/workflows/ (credential- based auth referenced by name only, no secret values), add a manifest covering all 4 canonical workflows and a read-only drift-check script against n8n's Public API. Retire the pre-integration root-level starter files that still carried the literal-token pattern, and repoint the Unraid deploy scripts, Makefile targets and runbook at the new files. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-04 13:34:51 +02:00
NuklearRabbit	824048b9d4	fix(deploy): mark setup-scheduled-scan.sh executable ... Matches the other deploy/unraid/*.sh scripts; was committed 644 instead of 755, caught while running it directly against the Unraid deployment.	2026-08-02 07:20:48 +02:00
NuklearRabbit	e115031a57	feat(n8n): add scheduled quality-scan workflow ... The original docs described two n8n workflows but the repository only ever shipped one (return-processing); the sketched second workflow (knowledge sync) depends on RAGcore, which isn't connected here, so it stays deferred. Add POST /api/v1/integrations/n8n/scheduled-scan (X-Service-Token protected, same pattern as the return callback), calling the same run_scan() the manual "Run quality scan" UI action uses and recording a service-actor data_quality_scan_run audit event. run_scan() already only creates an issue for a condition without one open, so overlapping triggers do no duplicate domain work. n8n/mobilityops-scheduled-quality-scan.json (hourly schedule + manual test trigger, both feeding the same HTTP call) ships "active": false so it can't fire anywhere until deliberately published. Verified live against the local n8n instance via the Manual test trigger: full green execution, and the resulting data_quality_scan_run audit event (actor_type=service, actor_label="n8n scheduled scan") confirms the real round trip, not just a contract test. deploy/unraid/setup-scheduled-scan.sh mirrors the existing return-workflow publish script for the shared Unraid n8n.	2026-08-02 06:59:17 +02:00
NuklearRabbit	1f292e14bb	fix(deploy): reuse shared server n8n	2026-08-02 03:56:17 +02:00
NuklearRabbit	1e13943cff	chore(deploy): automate private n8n bootstrap	2026-08-02 01:55:33 +02:00
NuklearRabbit	e1a1c6792d	fix(deploy): avoid existing n8n maintenance port	2026-08-02 01:52:56 +02:00
NuklearRabbit	847cd059cc	chore(deploy): generate server environment safely	2026-08-02 01:48:56 +02:00
NuklearRabbit	07ab7a3501	chore(deploy): add reproducible Unraid deployment	2026-08-02 01:47:27 +02:00