Block a user
marcel
pushed to worktree-feat+issue-698-themen-subtree-count at marcel/familienarchiv
2026-05-31 12:32:27 +02:00
As a reader browsing topics I want each theme box to count documents across its whole sub-topic tree so I can judge a topic's depth at a glance
Implemented ✅
Built on a worktree branch (worktree-feat+issue-698-themen-subtree-count) following Option B — a new subtreeDocumentCount field, reader surfaces read the rollup, admin…
feat(transcription): let read-only users read transcriptions (read tab only, no edit)
Implemented in PR #700 (branch feat/issue-697-readers-read-transcriptions), TDD throughout — red test → minimum green → atomic commit.
Resolved-decision alignment: hasTranscription =…
feat(transcription): let read-only users read transcriptions (read tab only, no edit) (#697)
marcel
pushed to feat/issue-697-readers-read-transcriptions at marcel/familienarchiv
2026-05-31 12:23:38 +02:00
marcel
created branch feat/issue-697-readers-read-transcriptions in marcel/familienarchiv
2026-05-31 12:23:38 +02:00
marcel
deleted branch feat/issue-696-hide-write-controls from marcel/familienarchiv
2026-05-31 11:31:36 +02:00
fix(ui): hide write/edit controls from READ_ALL (read-only) users (#696)
fix(ui): hide write/edit controls from READ_ALL (read-only) users
fix(ui): hide write/edit controls from READ_ALL (read-only) users
🗳️ Decision Queue — Action Required
1 decision needs your input — and it is a follow-up, not a blocker for #696. The upload-button fix can ship as-is.
Product / UX
- **Do…
fix(ui): hide write/edit controls from READ_ALL (read-only) users
📋 Elicit — Requirements Engineer & Business Analyst
Observations
- Strong issue hygiene. The acceptance criteria are in testable Given-When-Then Gherkin, scope boundaries are explicit…
fix(ui): hide write/edit controls from READ_ALL (read-only) users
⚙️ Tobias Wendt — DevOps & Platform Engineer
Observations
- Zero infrastructure surface. No Docker service, no env var, no Caddy rule, no CI workflow change. A
{#if}gate plus tests —…
fix(ui): hide write/edit controls from READ_ALL (read-only) users
🎨 Leonie Voss — UX Designer & Accessibility Strategist
Observations
- This is a genuine UX defect, not just a security tidy-up. A reader clicking "Hochladen" and getting silently bounced…
fix(ui): hide write/edit controls from READ_ALL (read-only) users
🧪 Sara Holt — QA Engineer & Test Strategist
Observations
- Test placement on the pyramid is correct. UI visibility → component test (
layout.svelte.spec.ts, vitest-browser-svelte…
fix(ui): hide write/edit controls from READ_ALL (read-only) users
🛡️ Nora "NullX" Steiner — Application Security Engineer
Observations
- This issue gets the threat model right, and says so explicitly: **hiding the button is not the control — the…
fix(ui): hide write/edit controls from READ_ALL (read-only) users
👨💻 Felix Brandt — Senior Fullstack Developer
Observations
- Clean implementation. The gate became
{#if canUpload}backed by `const canUpload = $derived(Boolean(data?.user &&…
fix(ui): hide write/edit controls from READ_ALL (read-only) users
🏛️ Markus Keller — Application Architect
Observations
- The layering is exactly right: the issue states up front that backend authz (
@RequirePermission(WRITE_ALL)+ server-side route…
marcel
pushed to feat/issue-696-hide-write-controls at marcel/familienarchiv
2026-05-31 11:22:44 +02:00
fix(ui): hide write/edit controls from READ_ALL (read-only) users (#696)
📋 Elicit — Requirements Engineer & Business Analyst
Verdict: ⚠️ Approved with one traceability concern
The change is well-scoped and the implementation matches the stated intent. My…