docs/architecture/operations.md

@@ -146,6 +146,19 @@ A Site Admin can purge a trashed pond immediately
 event. Known residues by design: `page_links.target_slug` in OTHER
 ponds' pages (#235) and backups within their retention.
 
+Decision on `page_links` rows pointing at a purged page (issue #235,
+recorded on #231): they are KEPT, as an accepted residue. The row is
+only the index of a wikilink whose text — including the slug, which
+carries the page title — remains visible in the linking page's own
+content, governed by that page's permissions and written by an author
+who could read the target at the time. Deleting the index row would
+remove nothing the system still shows (content, content cache, and the
+linking page's search index all keep the text) while breaking the
+deliberate phantom-link behaviour: a page recreated under the same slug
+resolves those links again. An operator answering for deletion refers
+to this paragraph: the residue is the linking author's own document,
+not a copy of the purged page.
+
 ## Update strategy
 
 - **Own stages**: pipeline-driven (see `deployment.md`); Prod only via

docs/vs-nfd/20-massnahmenplan.md

@@ -253,7 +253,7 @@ fehlten — als Issues angelegt:
       unbefristet in `conversion_jobs` · 2 AT · #233 (M24, I-22)
 - [x] Retention für `mail_outbox` — Digest-Mails tragen Seitentitel
       · 1 AT · #234 (M24, I-23)
-- [ ] `page_links.target_slug`-Residuum nach Purge entscheiden
+- [x] `page_links.target_slug`-Residuum nach Purge entscheiden
       · 0,5 AT · #235 (M24, I-24)
 - [ ] Node-Version pinnen — Voraussetzung für #219 · 0,5 AT · #236 (M25, I-26)