chore(openspec): Chain email/forms specs to openregister integration registry#310
Open
rubenvdlinde wants to merge 1 commit intodevelopmentfrom
Open
chore(openspec): Chain email/forms specs to openregister integration registry#310rubenvdlinde wants to merge 1 commit intodevelopmentfrom
rubenvdlinde wants to merge 1 commit intodevelopmentfrom
Conversation
…registry Adds cross-repo dependency links so Hydra can sequence pipelinq's spec work behind the shared integration registry: - email-calendar-sync → integration-email + integration-calendar - public-intake-forms → integration-forms Introduces five cross-repo stub dirs under openspec/changes/, each containing hydra.json + README pointing at the upstream openregister tracking issue. Covers all chained integrations referenced by pipelinq specs (including those currently DB-only in Specter that will push later): pluggable-integration-registry, integration-calendar, integration-email, integration-contacts, integration-forms. Note: contact-relationship-mapping, contacts-sync, and entity-notes are currently draft-only in Specter (not yet in this repo). When push_spec_pipeline.py pushes them, the integration-contacts stub is already here to resolve their upstream dep. Related: - Openregister spec PR #1300 - Hydra ADR PR #116 - Sibling PRs on decidesk + procest applying the same stub pattern
2 tasks
Contributor
Quality Report — ConductionNL/pipelinq @
|
| Check | PHP | Vue | Security | License | Tests |
|---|---|---|---|---|---|
| lint | ✅ | ||||
| phpcs | ❌ | ||||
| phpmd | ✅ | ||||
| psalm | ✅ | ||||
| phpstan | ✅ | ||||
| phpmetrics | ✅ | ||||
| eslint | ✅ | ||||
| stylelint | ✅ | ||||
| composer | ✅ | ✅ 100/100 | |||
| npm | ✅ | ✅ 249/249 | |||
| PHPUnit | ⏭️ | ||||
| Newman | ⏭️ | ||||
| Playwright | ❌ |
Spec coverage: 14% (42 tests / 298 specs)
Quality workflow — 2026-04-23 08:06 UTC
Download the full PDF report from the workflow artifacts.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Chains pipelinq specs to the OpenRegister integration registry. Same cross-repo stub pattern as decidesk (ConductionNL/decidesk#133) and procest (forthcoming).
Chained specs
email-calendar-sync→integration-email+integration-calendarpublic-intake-forms→integration-formsCross-repo stubs added (5)
pluggable-integration-registry→ Implement: Pluggable Integration Registry openregister#1307integration-calendar→ openregister#1308integration-email→ openregister#1309integration-contacts→ openregister#1311integration-forms→ openregister#1313Future drafts
Specter DB has
contact-relationship-mapping,contacts-sync, andentity-notesas drafts for this repo. They're not in the repo yet, so their hydra.json isn't updated here. Whenpush_spec_pipeline.pypushes them, theintegration-contactsandpluggable-integration-registrystubs will already be in place.Stub pattern
Each stub is a directory containing only
hydra.json+ short README. The hydra.json points at its upstream ConductionNL/openregister tracking issue. Hydra's sibling-based dep check reads the stub's.issueURL and polls that issue's state — so cross-repo deps resolve through the existing mechanism without modifying hydra code.Test plan