- Shipped
- September 2, 2026 at 5:08 PM UTC
- Author
- Kamo
- Commit
- 74d64c9
The authoring convention is to name a sibling article by putting its title in italics — "Read *Security Roles Explained* before building them". 181 spans across the drafts do it and nothing ever turned them into links, so a published article tells the reader which one to go and read and then leaves them to find it. There is exactly one Markdown link in three hundred articles and it points off-site. It also fed the KB-link bug the assistant just had. contentPlainText is what gets embedded and what the assistant is shown, and a stripped italic reads as prose, so the setup checklist reached the model naming a dozen articles with no way to reach any of them. That is guarded in the AI service now, but a reference that is a link needs no guarding. Resolution happens at import, against the knowledge base being published into, because the address is a guid and a guid belongs to one knowledge base rather than to the drafts — writing them into the content files would tie the help center to a single organization. It runs on the converted tree, where a reference is already one italic text node holding exactly the title, which keeps markdown-to-lexical.mjs untouched so the other three hundred articles cannot regress. Only an exact title match is linked, and italics do double duty here — 62 italic spans are UI labels, emphasis or question titles and stay as they are. An article naming itself is not a reference, an author's own link always wins, and a second run is a no-op. Verified against the live knowledge base: 181 references, 119 distinct destinations, 110 articles gaining links, nothing unresolved.