dev-environment
Minimum release age gate for developer CLI auto-updates
A supply-chain mitigation that delays devcontainer CLI updates until they are at least three days old.
The package a grep could not judge
A devcontainer bloat audit removes an unused compiler toolchain, keeps two expensive dependencies, and gives maintenance scripts a CI gate.
Done is not committed
Context7 and browser automation reach all three developer CLIs, after live verification exposes two integrations lost with an ephemeral worktree.
The fourth status line
A stale three-tool test turned pnpm support into a devcontainer startup failure, and the repair had to model the new update path properly.
The fourth tool in the manifest
Bringing pnpm into the developer-tool update policy, replacing manual version chores while keeping CI reproducible.
Keeping developer CLIs fresh without breaking the build
Unifying developer CLI lifecycle management in the devcontainer, auto-updating on startup without mutating reviewed build pins, and handling package manager regressions.
The apple moved overnight
A date-seeded apple invalidates the daily recording route, so the scripted player learns to search for a verified two-word opener.
More than one agent in the workshop
Codex and Antigravity join Claude Code inside the devcontainer, with pinned versions, shared skills, and checks that the safety boundaries are real.
Tuning the agent workbench: from game log polish to MCP servers
A solo-plus-agents project spends real time on its own tooling. Three days of making the workshop pleasant.
A room where the agent can work
The project moves into a devcontainer with local data, restricted networking, scoped Git identity, and enough browser tooling to run the whole development loop safely.