chore(deps): move to @conduction/nextcloud-vue 2.2.0-vue3.1

[rubenvdlinde]

Moves off the withdrawn 3.0.0-vue3.* line onto the resumed 2.x prerelease line.

The 3.0 major was cut from a genuine BREAKING CHANGE: footer (the retired action-list flow editors), but it applied to a prerelease channel only our own apps consume, so the line is resumed at 2.x rather than carried forward. The six 3.0.0-vue3.* versions are being withdrawn from npm once every app is off them — this PR is part of getting there.

Despite the lower version number this is not a downgrade in content. 2.2.0-vue3.1 is a superset of 3.0.0-vue3.6: it additionally carries the recovered Vue 2 -> Vue 3 component conversion (196 specs, 137 components, 51 missing emits) and the CnGraphCanvas port/loop work.

Verified, not assumed: npm install resolves node_modules/@conduction/nextcloud-vue -> 2.2.0-vue3.1 and npm run build exits 0.

[github-actions]

Quality Report — ConductionNL/openregister @ 14c7c40

Check	PHP	Vue	Security	License	Tests
lint	✅
phpcs	✅
phpmd	✅
psalm	✅
phpstan	✅
phpmetrics	✅
eslint		✅
stylelint		✅
build		✅
check-specs		✅
test-l10n		❌
composer			✅	✅ 173/173
npm			✅	✅ 713/713
PHPUnit					✅
Newman					✅
Playwright					✅

---

Quality workflow — 2026-08-05 11:26 UTC

Download the full PDF report from the workflow artifacts.

[rubenvdlinde]

Correction to the verification claim in this PR description.

The npm run build I originally cited did not exercise 2.2.0-vue3.1. The build worktree sat next to a stale nextcloud-vue checkout, and this repo's webpack.config.js aliases @conduction/nextcloud-vue to ../nextcloud-vue/src whenever that sibling exists — the exact hazard the config comment warns about. So the build compiled the sibling's source, not the published package. A green build there was evidence about the wrong artefact.

Re-run with the documented escape hatch, USE_LOCAL_LIB=false, which forces resolution to the npm package. I am reporting the corrected result below rather than the original claim.

Separately, the first lockfile regeneration used local npm 11, which prunes optional entries that do not apply to the current platform. CI runs npm 10.8.2 and its npm ci requires them, so eight jobs failed at Install dependencies with Missing: pinia@4.0.2 / vite@8.2.0 ... from lock file. Running npm ci locally did not catch it — npm 11 accepts its own lockfile. Fixed by regenerating with npx npm@10.8.2 install --package-lock-only and verifying via npx npm@10.8.2 ci --dry-run.

[github-actions]

Quality Report — ConductionNL/openregister @ 6da0334

Check	PHP	Vue	Security	License	Tests
lint	✅
phpcs	✅
phpmd	✅
psalm	✅
phpstan	✅
phpmetrics	✅
eslint		✅
stylelint		✅
build		✅
check-specs		✅
test-l10n		❌
composer			✅	✅ 173/173
npm			✅	✅ 713/713
PHPUnit					✅
Newman					✅
Playwright					✅

---

Quality workflow — 2026-08-05 12:06 UTC

Download the full PDF report from the workflow artifacts.