Skip to content

docs(parity): set 5 sibling rows from the OpenSpec pass - #1143

Merged
rubenvdlinde merged 1 commit into
developmentfrom
parity/sibling-rows
Sep 28, 2026
Merged

rubenvdlinde merged 1 commit into
developmentfrom
parity/sibling-rows

Conversation

@rubenvdlinde

Copy link
Copy Markdown
Contributor

Sibling-rows pass that closes the OpenSpec pass (27 and 28 Sep 2026). Every product lane handed back rows in other products' matrices whose state, owner or rating had to change once the owning repo's change existed. This PR applies the rows listed for the stackiq matrix in openspec/parity/capabilities.json and changes nothing else: no other row, no top-level key, no other file.

Before each change I checked that the named change directory exists on the owning repo's development (openspec/changes/<name> or openspec/changes/archive/<name>). Owning repos read, at their development tips: integriq 413357ec9, nextcloud-vue f2bc02c30, openregister 555af7212. The change reference goes where this matrix already keeps it: the row note. Where a built correction or an owner move rests on code, the note names the file and the sha it was read at.

Rows changed (5)

row before after change what from lane
conn-impact-analysis built, openregister, rated partial specified, openregister, rated partial openregister relations-that-travel-and-what-they-expose (open) specified openregister
land-custom-fields none, openregister, rated no specified, openregister, rated no openregister fields-a-user-adds-and-choices-a-record-narrows (open) specified openregister
life-new-version-notice specified, openregister, rated no specified, openregister, rated no openregister notifications-new-notes-and-referrers (open) specified openregister
conn-integration-registry built, integriq, rated partial building, integriq, rated partial integriq connection-registry (open) building integriq
land-copy-entry built, nextcloud-vue, rated partial specified, nextcloud-vue, rated partial nextcloud-vue index-copy-with-relations (open) specified nextcloud-vue

Checks

  • hydra parity-verify --strict (hydra development 6ce49e3, jsonschema 4.10.3): 175 rated rows, 40 pending, 6 systems; strict findings 0 and schema errors 0, only the census of 469 unknown cells. The output is identical before and after this change.
  • Toolchain: npm ci with npm 10.8.2; scripts run once on Node 24.11.1, by exit code:
    • npm run lint: exit 0
    • npm run format: exit 0
    • npm run check:manifest: exit 0
    • npm run check:schema-l10n: exit 0
    • npm run test:l10n: exit 0
  • composer check:strict: not run. No lane reported it finishing in a bare clone within 10 minutes, and this PR changes only openspec/parity/capabilities.json, which no PHP gate reads.

🤖 Generated with Claude Code

Rows in this matrix whose state, owner or rating changes now that the owning repo's OpenSpec change exists (sibling-rows pass, 2026-09-28). Only the listed rows change; parity-verify --strict output is identical before and after.
@github-actions

Copy link
Copy Markdown
Contributor

Quality Report — ConductionNL/stackiq @ e38e97b

Check PHP Vue Security License Tests
lint ✅
phpcs ✅
phpmd ✅
psalm ✅
phpstan ✅
phpmetrics ✅
eslint ✅
stylelint ✅
build ✅
check-manifest ✅
check-vue-demi ✅
test-l10n ✅
format ✅
check-schema-l10n ✅
check-l10n-js ✅
composer ✅ ✅ 130/130
npm ✅ ✅ 807/807
app:check-code ⏭️
info.xml ✅
REUSE ❌
lockfile sync ✅
PHPUnit ⏭️ not run for this diff — no file in this diff matches the code globs, and none carries a source extension — the heavy tier has nothing to decide about it.
Newman ⏭️
Playwright ⏭️ deferred: E2E runs locally and on the promotion path only. This pull request targets development, so the suite is asked once per promotion into beta and main rather than once per push per open pull request. Run it on any branch from the Actions tab, or locally with npx playwright test.
Hydra gates ❌

Quality workflow — 2026-09-27 23:06 UTC

Download the full PDF report from the workflow artifacts.

@rubenvdlinde
rubenvdlinde merged commit d22033a into development Sep 28, 2026
45 of 47 checks passed
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.

1 participant