[OpenSpec] leaf-integrations

[github-actions]

⚠️ 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

Portaliq consumes exactly one of OpenRegister's app-agnostic integration leaves today: a single
files widget on the DocumentDetail manifest page (src/manifest.json, widget document-files,
{"type": "integration", "integrationId": "files"}). No portaliq schema declares linkedTypes, no
page declares configuration.linkedTypes, and no configuration.mailObjectTemplate exists. This
change adopts three more leaves where portaliq's internal staff view has a real, grounded need —
forms (portal submissions), talk (staff discussion on a portal message), and calendar
(appointments around a portal account) — and makes the ADR-046 boundary normative for every leaf:
integration leaves render for internal Nextcloud staff only; an external portal visitor never
touches a Nextcloud app, and anything visitor-facing stays mediated by the portal edge.

Specs

• 📄 portaliq-leaf-integrations

Tasks

• Implement
• Test
• Implement
• Test
• Implement
• Test
• Implement
• Test
• Implement
• Test

Design

See design.md for technical design details.

---

Synced from openspec/changes/leaf-integrations by OpenSpec workflow
App: portaliq