A devlog post for v0.12.0: "It was off". The website in four phases, how documenting the Debug Console showed that only its builder could use it, the one firmware that replaced the Debug Build (ADR 0010), and the evening spent on a console that "wouldn't come back" (it was off) and a "leak" (TCP's two minutes).
Touches only site/: one new post with two screenshots.
Please look at before merging:
token.png shows a real token (T49R-…), the one that leaked into a screenshot during the tests. It was replaced that evening and I checked it is no longer the one in the token file, so it is dead; the post says so. If you'd rather not publish it anyway, say so and I'll swap the figure.
The post is written in the first person, as the others are: the typo, the dialog on Cancel and the wrong turn on the leak are told as "I".
Checked: Zola build, check_site.py 67 pages / 0 problems, the post and the devlog index in Chromium under the production CSP at 1000 and 390 px, no violation, no broken image, no sideways scroll. Every figure in it (sizes, heap readings, test counts, the lockout transcript) is from the measurements of the day.
A devlog post for v0.12.0: **"It was off"**. The website in four phases, how documenting the Debug Console showed that only its builder could use it, the one firmware that replaced the Debug Build (ADR 0010), and the evening spent on a console that "wouldn't come back" (it was off) and a "leak" (TCP's two minutes).
Touches only `site/`: one new post with two screenshots.
**Please look at before merging:**
- **`token.png` shows a real token** (`T49R-…`), the one that leaked into a screenshot during the tests. It was replaced that evening and I checked it is no longer the one in the token file, so it is dead; the post says so. If you'd rather not publish it anyway, say so and I'll swap the figure.
- The post is written in the first person, as the others are: the typo, the dialog on Cancel and the wrong turn on the leak are told as "I".
Checked: Zola build, `check_site.py` 67 pages / 0 problems, the post and the devlog index in Chromium under the production CSP at 1000 and 390 px, no violation, no broken image, no sideways scroll. Every figure in it (sizes, heap readings, test counts, the lockout transcript) is from the measurements of the day.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_01EhqxQ49eCju4CzKYNjZzwT
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
A devlog post for v0.12.0: "It was off". The website in four phases, how documenting the Debug Console showed that only its builder could use it, the one firmware that replaced the Debug Build (ADR 0010), and the evening spent on a console that "wouldn't come back" (it was off) and a "leak" (TCP's two minutes).
Touches only
site/: one new post with two screenshots.Please look at before merging:
token.pngshows a real token (T49R-…), the one that leaked into a screenshot during the tests. It was replaced that evening and I checked it is no longer the one in the token file, so it is dead; the post says so. If you'd rather not publish it anyway, say so and I'll swap the figure.Checked: Zola build,
check_site.py67 pages / 0 problems, the post and the devlog index in Chromium under the production CSP at 1000 and 390 px, no violation, no broken image, no sideways scroll. Every figure in it (sizes, heap readings, test counts, the lockout transcript) is from the measurements of the day.🤖 Generated with Claude Code
https://claude.ai/code/session_01EhqxQ49eCju4CzKYNjZzwT