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. |
||
|---|---|---|
| .. | ||
| argocd-gitops.md | ||
| nats-task-ingestion.md | ||
| package-release.md | ||