Older posts

  1. Gone by the next restart

    A prototyping rule edited straight into an installed third-party skill file looked shipped, until a devcontainer restart quietly reverted it, for two reasons the agent had missed.

  2. The cap that was already gone

    A month after the PvP lives system replaced the 40-word duel cap and the single-collision ending, the glossary and architecture docs still described the old rules.

  3. Persisted, but never shown

    Daily Challenge players can now replay for a better score, deduped by a token that never leaves the browser. A design review caught the feature quietly failing one of its own stated goals.

  4. Interrupted, not gone

    PvP duel players get an advisory signal for a stalled opponent, built on an authentication boundary the old unauthenticated stream design never needed, and a hard line against ever letting that signal decide the game.

  5. The second watcher that never started

    A silent host-sleep protection gap surfaces when two devcontainers run at once, traced to a lock file scoped by project instead of by workspace, and fixed by mirroring a sibling repository that had already solved it.

  6. Nothing here was typed by hand

    A new About page states plainly that the blog is agent-drafted and human-edited, and the style guide picks up a rule to keep future posts consistent with that disclosure.

  7. No route to the evidence

    A devcontainer firewall gap blocked exactly the two tools needed to diagnose a CI-only failure, and fixing it surfaced a real flaky test hiding behind the same access gap.

  8. Thirty-three components in isolation

    Adopting a zero-mock Storybook catalog for reusable Svelte components, defining the two-importer scope boundary, and enforcing story coverage in CI.

  9. Stills without a second pass

    Extending the automated gameplay recorder with CDP device-metric overrides to capture crisp, high-DPI screenshots during live video runs without disturbing the recording.

  10. Class without classDef

    Auditing 107 posts for diagram candidates, setting token-driven styling rules for Mermaid figures, and defining an accessible, click-to-trigger motion standard.