Webhook delivery engine never landed in git despite issue #1 closed #44

Closed
opened 2026-08-11 02:49:25 +00:00 by Mark · 1 comment
Owner

Issue #1 (Webhook System Implementation) was closed 2026-06-08 and docs/IMPLEMENTATION_STATUS.md says the webhook system is fully implemented, but the delivery engine code (backend/services/webhook_service.py, backend/tasks/webhook_tasks.py, backend/models/webhook_delivery_log.py, and its Alembic migration) is not tracked in git. It exists only as untracked worktree files, so a fresh clone gets just the WebhookRegistry model and a hooks router stub. Either commit the engine after wiring it correctly, or reopen #1; the docs claim is currently false.

Issue #1 (Webhook System Implementation) was closed 2026-06-08 and docs/IMPLEMENTATION_STATUS.md says the webhook system is fully implemented, but the delivery engine code (backend/services/webhook_service.py, backend/tasks/webhook_tasks.py, backend/models/webhook_delivery_log.py, and its Alembic migration) is not tracked in git. It exists only as untracked worktree files, so a fresh clone gets just the WebhookRegistry model and a hooks router stub. Either commit the engine after wiring it correctly, or reopen #1; the docs claim is currently false.
Author
Owner

Same uncommitted batch also breaks docker-compose.prod.yml: the db and backup service blocks were re-indented by one space, so the file no longer parses as YAML (verified: python yaml.safe_load fails at line 89 col 4). HEAD version is valid. Do not commit that file as-is.

Same uncommitted batch also breaks docker-compose.prod.yml: the db and backup service blocks were re-indented by one space, so the file no longer parses as YAML (verified: python yaml.safe_load fails at line 89 col 4). HEAD version is valid. Do not commit that file as-is.
Mark closed this issue 2026-08-13 00:13:15 +00:00
Sign in to join this conversation.
No description provided.