tegwick 7693ef8680 Accept non-UUID triggering_event_id and add GitOps runbook ... Broaden POST /issues/ so triggering_event_id is any non-empty traceability string, enabling cron/scheduled activity-core emissions with stable keys like "scheduled" while event-driven paths still send UUIDs. Document the railiance01 ArgoCD deployment path in docs/argocd-gitops.md and update ISSUE-WP-0003 task status to reflect repo-side progress.		2026-06-24 14:52:47 +02:00
..
api	Accept non-UUID triggering_event_id and add GitOps runbook	2026-06-24 14:52:47 +02:00
backends	chore(consistency): sync task status from DB [auto]	2026-05-17 05:06:10 +02:00
cli	feat: restore issue-tracker console script as migration hint	2026-05-17 05:27:34 +02:00
core	chore(consistency): sync task status from DB [auto]	2026-05-17 05:06:10 +02:00
__init__.py	feat: rename to issue-core and add task ingestion endpoint	2026-05-17 05:16:27 +02:00