[DYN-023] Pantry presentation

[veryCrunchy]

Roadmap

• Task ID: DYN-023
• Priority: P1
• Parent epic: [EPIC] Adaptive Nextcloud apps #15
• Related foundation: [DYN-004] Semantic entity recognition #44, [DYN-005] Context-aware action binding #45, [DYN-006] Relationship and nested-resource planner #46, [DYN-007] Native list/detail/table/board/dashboard selection #47, [DYN-008] Editable structured forms #48

Verified upstream model

Pantry is scoped by a selectable House. Each House permission-gates three primary surfaces: Checklists, a photo board with folders, and a notes wall. The installed Pantry version must be verified before enabling mutations against its OCS API.

Acceptance criteria

• Discover Houses, restore an accessible selection, fall back safely, and show a useful welcome state when none exist.
• Default each House to the checklist overview and expose photo-board and notes-wall navigation only when permitted.
• Present checklist metadata, items, quantity, category, stores, recurrence, next due time, completion actor/time, images, archive, and trash states.
• Present root photos, photo folders, captions, upload state, move targets, trash, restore, and permanent-delete confirmation.
• Present pinned and unpinned notes with create/edit capability, color, selection, trash, and restore states.
• Gate navigation and actions from House permissions and per-record edit capability rather than role-name assumptions.
• Keep shared UI driven by workspace, collection, media-board, note, permission, and lifecycle semantics rather than an app-ID branch.
• Verify non-mutating reads against the installed app version before adding writes.
• Add checklist completion and other mutations only with exact payload, rollback, conflict, and destructive-action coverage.
• Cover phone, large-phone/tablet, and desktop loading, empty, populated, read-only, error, retry, and destructive-confirmation states with synthetic visual QA.