My blog has a ghostwriter. The bot writes drafts, tightens paragraphs, fixes typos, commits them. That works well. It also creates an interesting constraint: because the LLM can turn a ramble into something readable in minutes, the post is often ready to publish long before the dev task it documents is actually finished. You want to publish early — the writing is there, readers can engage — but you are still iterating on the thing the post is about. The article will change as the work progresses. ...

I built a Telegram bot that can write and edit my blog posts but cannot publish them. Hugo draft: true is enforced by the tool, not trusted to my discipline. The bot reads and writes files in the Hugo repo directly. No separate editorial database — the Markdown files are the source of truth. When a diff would flip draft: true to draft: false, the commit script refuses. There is an override (ALLOW_PUBLISH=1) but the bot cannot set it. Only I can, at a terminal. ...