[OpenSpec] nc-events-start-or-flows

[github-actions]

⚠️ OpenSpec-managed issue — this content is automatically synced
from the openspec/ directory. Manual edits will be overwritten on next sync.

Artifacts

• ✅ Metadata
• ✅ Proposal
• ✅ Specs
• 🔲 Design
• ✅ Tasks
• 🔲 Plan
• 🔲 Review

Summary

Let a matched event subscription start an OpenRegister flow run. Integriq's
event hub already normalizes Nextcloud core events (files, calendar, Tables,
Forms) into CloudEvents and lets a subscription drive a synchronization, a
job or a signed webhook. The one engine those events cannot reach is the one
the fleet standardized on: an OpenRegister flow. This change adds flow as a
fourth subscription action kind (event_subscription.action = {kind: "flow", flowId}): on match, Integriq asks OpenRegister's FlowRunService to run the
named flow with the CloudEvent envelope as input. Nothing else: no scheduler,
no app-local orchestration, no new trigger machinery.

Specs

• 📄 nextcloud-event-triggers

Tasks

• Implement
• Test
• Implement
• Test
• Implement
• Test
• Implement
• Test
• All tasks checked off
• Manual testing against acceptance criteria
• Code review against spec requirements
• All tests pass (composer test, Playwright suite)

---

Synced from openspec/changes/nc-events-start-or-flows by OpenSpec workflow
App: integriq