Skip to content

docs(openspec): scope schedules-editor's migration off the classic OpenConnector dialect - #226

Merged
rubenvdlinde merged 1 commit into
developmentfrom
feat/schedules-editor-flow-migration
Aug 16, 2026
Merged

docs(openspec): scope schedules-editor's migration off the classic OpenConnector dialect#226
rubenvdlinde merged 1 commit into
developmentfrom
feat/schedules-editor-flow-migration

Conversation

@rubenvdlinde

Copy link
Copy Markdown
Contributor

Summary

  • New openspec change schedules-editor-flow-migration (kept separate from the already-shipped/closed schedules-editor change rather than reopening it).
  • Confirms current classic-dialect call sites: ScheduleEditDialog.vue (fetchSynchronizations, action openconnector:synchronization), SchedulesSection.vue, manifestValidation/schedules.js.
  • Flags an adjacent, explicitly out-of-scope finding: AutomationEditDialog.vue has an identical call but belongs to an unrelated page (Automations, not schedules-editor).
  • Blocked on openregister's flow-sync-decomposition landing — this PR is planning only.

Related

  • hydra ADR-092 (docs/adr-092-openconnector-dialect-retirement)
  • openregister feat/flow-sync-decomposition-tasks

Test plan

  • openspec validate schedules-editor-flow-migration --strict passes (skip_specs: true, planning-only change)

…hange, planning only)

schedules-editor shipped ScheduleEditDialog.vue / SchedulesSection.vue /
schedules.js reading and writing the classic OpenConnector dialect directly
(GET .../openconnector/synchronization, action: "openconnector:synchronization").
That dialect is being retired fleet-wide in favour of OpenRegister's native
Flow engine (ADR-065); the fleet-wide policy is being recorded in parallel as
hydra change adr-092-openconnector-dialect-retirement (renumbered from an
earlier ADR-091 attempt, which collided with an unrelated, already-merged
ADR-091). Actual cutover is gated on openregister's flow-sync-decomposition
change landing real decomposed nodes — that change has no tasks.md yet, so
implementation has not started there either.

This is a NEW change (not folded into schedules-editor): schedules-editor's
own tasks.md is fully checked off and its code is already merged
(0b6eddc), so it reads as closed work rather than in-progress. Planning
only — no code changes. Audits the current classic-dialect call sites,
flags AutomationEditDialog.vue as an adjacent surface with the identical
call that is NOT in scope here, defines the open design questions for the
Flow-native target shape, and gates all real implementation tasks behind
the two blocking dependencies above.
@github-actions

Copy link
Copy Markdown
Contributor

Quality Report — ConductionNL/openbuild @ 2c05177

Check PHP Vue Security License Tests
lint
phpcs
phpmd
psalm
phpstan
phpmetrics
eslint
stylelint
build
check-manifest
test-l10n
check-gitignore
check-nc-floor
format
composer ✅ 106/106
npm ✅ 626/626
app:check-code ⏭️
info.xml
REUSE
PHPUnit
Newman
Playwright
Hydra gates

Quality workflow — 2026-08-16 16:15 UTC

Download the full PDF report from the workflow artifacts.

@rubenvdlinde
rubenvdlinde merged commit d6469dd into development Aug 16, 2026
72 of 80 checks passed
@rubenvdlinde
rubenvdlinde deleted the feat/schedules-editor-flow-migration branch August 16, 2026 16:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants