[OpenSpec] nextcloud-vue-2-76-object-lock #3541

⚠️ OpenSpec-managed issue — this content is automatically synced
from the openspec/ directory. Manual edits will be overwritten on next sync.

Artifacts

• ✅ Metadata
• ✅ Proposal
• ✅ Specs
• 🔲 Design
• ✅ Tasks
• 🔲 Plan
• 🔲 Review

Summary

dossiq moves from @conduction/nextcloud-vue ^2.74.0 to ^2.76.0.

On 2.73.1 and 2.74.0 a case detail page never took its lock. CnDetailPage
passes getter functions for the register, schema and id, and useObjectLock
read them with unref, which hands a function back as it is. The lock
request went to /api/objects/() => .../() => .../() => .../lock, and
OpenRegister answered 404. 2.76.0 reads them with toValue and sends no
request until all three are known.

The same release also:

• loads CnRelatedObjectsWidget sections one by one, so one slow section no
  longer holds back the rest;
• translates the addLabel of CnObjectListWidget;
• writes the Credentials text in the settings dialog without em-dashes, in
  English and Dutch.

Specs

• 📄 admin-settings
• 📄 case-management

Tasks

• 1.1 package.json and package-lock.json on @conduction/nextcloud-vue ^2.76.0.
• 1.2 tests/schemas/app-manifest-v2.schema.json copied from the package (schema 2.73.0).
• 2.1 Comes with 2.76.0; dossiq ships the library's CnCredentials as it is.
• 3.1 On a case detail page the lock request carries the real register, schema and id and is not answered with 404.
• 3.2 The settings dialog's Credentials text has no em-dashes.

Synced from openspec/changes/nextcloud-vue-2-76-object-lock by OpenSpec workflow
App: dossiq