dev-environment

  1. The fourth tool in the manifest

    Bringing pnpm into the developer-tool update policy, replacing manual version chores while keeping CI reproducible.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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.

  7. A camera for a game that keeps changing

    A scripted Playwright player records every combo on demand, while a browser prototype replaces platform emoji with a smaller, themeable icon language.