0.8.0

v0.8.0

10 changes · 1 Bugfix, 8 New UI Features, 1 Uncategorized · 51 points.

Bugfix

• RADD-744 A plugin's attachments would leak bytes forever: the GC's parent map is hardcoded _{attachments pluginmgr server · 2 pts · f0ea4b55} attachments/gc.py decides which events mean "a parent died" from a hardcoded dict:

New UI Feature

• RADD-717 Page comments: a discussion per page _{docs web · 5 pts · d591591e} Issues have comments; pages have none. A wiki page is where a decision gets written down, and the argument about it currently has nowhere to live except the issue tracker or chat — which is where it becomes unfindable.
• RADD-712 Page templates, and an extension button that creates one as a child _{docs web · 8 pts · 52c870ce} Recurring pages — runbooks, meeting notes, RFCs, postmortems — should start from a shape, not from a blank editor or a copy-paste.
• RADD-714 The hierarchy is not obvious _{docs web · 5 pts · e1cc427b} The only structural cue is a 250px tree rail. A page does not show where it sits, what is under it, or how big the section is. Landing on a page from search or a link tells you nothing about its context.
• RADD-719 Watch a page and be told when it changes _{docs web · 5 pts · 6d2e8686} Notifications and watchers exist for items (spec 26) but not pages, so the only way to know a runbook changed is to reread it. For a wiki that documents operations, silent edits are the failure mode.
• RADD-721 Export a page or a space _{docs web · 5 pts · 0e0dee35} Content can go in but not out — no markdown export, no space archive. For a tool whose pitch includes not being locked in, that is the wrong gap to have.
• RADD-720 Compare two versions of a page _{docs web · 3 pts · 5539cac9} Versions are stored and restorable (spec 43) but not comparable — you can restore a version you cannot read the difference of, which makes restore a guess.
• RADD-726 Inline comments on a page: anchored to the text, and resolvable _{docs web · 13 pts · 3c6905d7} Reviewing a page has exactly one channel: the whole-page thread RADD-717 adds. That answers "should we do this at all" and is useless for "this paragraph is wrong" — the reader has to quote the sentence back in a thread at the bottom and hope the author finds the original. Google Docs settled this shape years ago:…
• RADD-717 Page comments: a discussion per page _{docs web · 5 pts · 6cf7e20e} Issues have comments; pages have none. A wiki page is where a decision gets written down, and the argument about it currently has nowhere to live except the issue tracker or chat — which is where it becomes unfindable.

Uncategorized

• RADD-745 We own the editor chrome: replace Crepe, keep Milkdown and ProseMirror _{docs web · 2cfe77ba} The decision: Crepe is removed. Milkdown and ProseMirror stay, and the chrome becomes ours.

Changes from v0.7.1 to v0.8.0.

---

Mirrored from project.radd-hq.com on 2026-09-12. Documentation is written there; this copy is regenerated by scripts/publish_wiki.py and hand edits do not survive it.