#222: read-access trail for classified pages #278
No reviewers
Labels
No Label
area:auth
area:docs
area:export
area:ops
area:storage
area:supply-chain
auth
backend
blocked
collab
deployment
docs
effort:L
effort:M
effort:S
frontend
plugins
qa
vs-nfd
vs-nfd:blocker
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: stwaidele/dorfteich#278
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "issue-222-read-trail"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Instruments every full-content read channel for vs_nfd pages (ADR 0023 variant A): SPA state fetch and read rendering, public JSON, no-JS shell, expanded embeds, public API GET (incl. MCP read_page), attachment download (#212 effective classification), all export shapes, and collab-token issuance as the api-side proxy for the WS join. Events land in the new read_events table (no FKs - evidence survives purges and account deletion). Failure is hard by decision: a failed trail write aborts the read (documented in ADR 0023 + security.md, incl. recorded residuals: fragments and feeds). One e2e test per channel proves event and absence for unclassified; plus the hard-failure test. Part of M29; closes after CI+merge verification. Refs #222