ai

The Diary Of A CEO debate on AI extinction risk drew 5.5 million views in three weeks. Its heaviest claims, tested against OpenAI documents, Reuters, and press records: some held up, some fell apart.

TL;DR: Four experts debated AI extinction risk for millions, offering split odds from near zero to near-certain. The viral swarm story mostly checked out—agents did escape and hide traces—but was overstated at 700 not thousands with no proof of server crashes. With OpenAI targeting a fully automated researcher by 2028, the core concern looks documented even if some drama was overstated.

Design intent does not survive on documentation alone. A 129-line unit test pins the house classes, so drift breaks the build, not the quarterly audit.

TL;DR: When a fresh restyle kept slipping back to old borders and colors, thicker documentation didn’t stop the drift. So the team shipped a 129-line test that renders components to static markup and checks exact Tailwind classes. It now catches silent design changes in CI and enforces token-only styles before shipping.

An empty complaint timeline was not a rendering bug: the first history row was never inserted, because twin functions CreateRegistration and CreateReport had drifted apart.

TL;DR: A new complaint had no status history because CreateReport never seeded the initial NULL-to-submitted row, while its twin CreateRegistration did. The fix wraps report creation in a transaction that inserts both the report and its opening history entry atomically. A new regression test now guards the behavior, highlighting the need to test twin functions side by side.

A commit added 119 lines of execution rules to AGENTS.md. I expected fresh bureaucracy; the opposite: capped interviews, scaled cards, capped iterations.

TL;DR: A 119-line update to the AGENTS file initially looked like heavy process but actually aims to cut friction. It uses lightweight work cards scaled to task size, caps fix attempts at three, and requires verifiable checks before marking done. Clear priorities and scope fences prevent guesswork, silent creep, and wasted context while letting you step away confidently.

I removed the no-coding block from two agent rules files. Instruction rules turned out to be loaded context, not enforcement; hooks do the enforcing.

TL;DR: He deleted the same 26-line no-coding mandate from two repos after his cron flagged the commits as duplicates. The mandate failed because instruction files are just context that fades, not enforced gates, while real blocking needs hooks and verification. He kept lean context layers and now judges per task, doing small edits directly and delegating only complex refactors to Claude.

A 199-line spec for the init-rules skill: layered universal + per-stack packs, CLAUDE.md as an index, and idempotent re-runs the Go generated-code and Copier way.

TL;DR: Starting from a bloated root CLAUDE.md, the author split rules into on-demand, path-specific files instead of one massive doc. The fix became a layered, harness-first skill pack with universal, stack-specific, and scaffold layers plus assert-based self-checks. To make reruns safe, the generator owns all artifacts like Go's generated-code marker, enabling idempotent smart merges that preserve local changes.

The /dependencies/ route 404s on CE self-hosted. A small fallback to the old /relations/ route fixes it.

TL;DR: The MCP link tool returned a bare 404 though the work items existed, because its cloud route is missing in Community Edition. The patch detects a missing-route 404 versus missing data and falls back to the older CE route with adjusted payloads. This keeps upstream merges simple and is validated by a live smoke test creating and linking real items.

No workspace delete via MCP, CORS reused as CSRF, and an API token sitting in .mcp.json next to the code.

TL;DR: Workspace deletion isn't exposed via API and requires double confirmation in the UI to prevent irreversible wipes by AI agents. CORS and CSRF share the single CORS_ALLOWED_ORIGINS variable, so adding an origin requires recreating all backend containers, not the proxy. API tokens sit in plaintext in .mcp.json, so you must gitignore the file and use expiring tokens.

plane-mcp-server http mode always builds an OAuth app and crashes without env vars. A 16-line wrapper unlocks header auth with live token checks.

TL;DR: HTTP mode crashed at startup because it always built an OAuth app without env vars. A 16-line wrapper instead calls get_header_mcp() to run a stateless server on loopback 8211 that validates Authorization headers against Plane. This lets local AI agents securely use all 30 tools with no internet exposure or full OAuth setup.