- Shipped
- September 18, 2026 at 3:43 AM UTC
- Author
- Kamo
- Commit
- 4b77e37
kbservice answers GET /articles/{guid} with its entity, so authorMemberId is a JSON number, and JSON.parse rounds a 19-digit member id. The article route compared that rounded number with the directory's ids — which are text — so no byline ever named its author; and it passed the rounded id on, which would open somebody else's member card, or nobody's. The route now reads the author's id exactly off the raw body, names them by it, and hands it on as text. The page's type says so.