chore(openspec): Chain meeting/docs/analytics specs to openregister integration registry#133
Open
rubenvdlinde wants to merge 1 commit into
Open
chore(openspec): Chain meeting/docs/analytics specs to openregister integration registry#133rubenvdlinde wants to merge 1 commit into
rubenvdlinde wants to merge 1 commit into
Conversation
…ntegration registry Adds cross-repo dependency links so Hydra can sequence decidesk's spec implementation behind the shared integration registry: - p2-agenda-management, p2-meeting-management (+ 5 variants) → integration-calendar - p3-document-management → pluggable-integration-registry (files integration) - p4-reporting-and-analytics → integration-analytics Introduces three "cross-repo stub" directories under openspec/changes/ — each containing only hydra.json + a short README. The stubs point at their upstream openregister tracking issues. Hydra's sibling-based dependency check reads `depends_on: [slug]` -> `changes/<slug>/hydra.json` -> `.issue` URL -> GitHub state, so the stubs let Hydra block these specs on openregister merges without modifying hydra itself. Authoritative specs for the stubs live at ConductionNL/openregister — edits do not belong here. Related: - Openregister spec PR #1300 - Hydra ADR-019 PR #116 - Openregister tracking issues: #1307 umbrella, #1308 calendar, #1321 analytics
Contributor
Quality Report — ConductionNL/decidesk @
|
| Check | PHP | Vue | Security | License | Tests |
|---|---|---|---|---|---|
| lint | ✅ | ||||
| phpcs | ✅ | ||||
| phpmd | ✅ | ||||
| psalm | ✅ | ||||
| phpstan | ✅ | ||||
| phpmetrics | ✅ | ||||
| eslint | ✅ | ||||
| stylelint | ✅ | ||||
| composer | ✅ | ✅ 100/100 | |||
| npm | ✅ | ✅ 416/416 | |||
| PHPUnit | ❌ | ||||
| Newman | ✅ | ||||
| Playwright | ⏭️ |
Coverage: 0% (0/115 statements)
Quality workflow — 2026-04-23 08:04 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 9 decidesk specs to the OpenRegister integration registry so Hydra can sequence them behind the shared integration work. Introduces a "cross-repo stub" pattern under
openspec/changes/that lets Hydra's existing dependency mechanism resolve upstream issues.What changes
9 specs gain a cross-repo
depends_onp2-agenda-management,p2-meeting-management+ 5 variants (Core T1/T2/T3, Other T1/T2) →integration-calendarp3-document-management→pluggable-integration-registry(umbrella — satisfies files-integration dep)p4-reporting-and-analytics→integration-analytics3 cross-repo stub directories added
openspec/changes/integration-calendar/— stub hydra.json pointing at Implement: Integration: Calendar (Meetings) openregister#1308openspec/changes/integration-analytics/— stub hydra.json pointing at Implement: Integration: Analytics openregister#1321openspec/changes/pluggable-integration-registry/— stub hydra.json pointing at Implement: Pluggable Integration Registry openregister#1307Each stub is a directory with only
hydra.json+ a short README explaining that the authoritative spec lives upstream. Hydra's sibling-based dep check reads the stub's.issueURL and polls that issue's state viagh api— so when the upstream openregister issue closes, these decidesk specs automatically unblock.Why this pattern
Hydra's
cron-hydra.sh/hydra-supervisor.shresolvedepends_onby looking forchanges_dir/<dep>/hydra.json. Without the stub, a cross-repo dep would silently stay blocked forever. With the stub, Hydra reads the stub's.issueURL, checks that issue's state, and proceeds normally.No hydra code changes required. No new machinery — just the discipline of keeping one stub per cross-repo dep.
Related
Test plan
openspec/changes/<integration>/the right location, or should stubs live elsewhere?