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. |
||
|---|---|---|
| .. | ||
| ISSC-WP-0001-rename-and-task-ingestion.md | ||
| ISSUE-WP-0002-gitea-pypi-publication.md | ||
| ISSUE-WP-0003-railiance01-deployment.md | ||