v0.10.1: the desktop walkthrough gets its article, with six figures captured from the v0.10.0 tag
One article per release, so the release that added the desktop walkthrough gets one. It covers why the third walkthrough keeps the shape of the first two, why the switch is the character of the desktop shape, why the map of what matters comes before the rules and why every rule...
Source: https://abp.sgit.ai/versions/v0.10.1/index.html↗ · site v0.11.0 · this file is generated from the same content
as the page, so the two cannot drift. Every page on this site has a .md twin; internal links
below point at them.
v0.10.1: the desktop walkthrough gets its article, with six figures captured from the v0.10.0 tag
One article per release, so the release that added the desktop walkthrough gets one. It covers why the third walkthrough keeps the shape of the first two, why the switch is the character of the desktop shape, why the map of what matters comes before the rules and why every rule names the group of the map it follows from, and why a toggle is a setting on your own machine and a boundary on a managed one. Six screenshots from a checkout of the v0.10.0 tag on the day it shipped.
| Field | Value |
|---|---|
| Version | v0.10.1 |
| Date | 2026-09-22 |
| Commit | git rev-list -n 1 v0.10.1. The tag is the record: CI derives it from admin/build/version.txt and creates it on the commit whose subject carries site v0.10.1:. The hash is not written into versions/v0.10.1.json↗, because a release commit cannot contain its own hash and reading it back from the tag made the build produce different bytes on a checkout with tags than on one without. |
| Reconstructed | no |
| Machine readable | versions/v0.10.1.json↗ |
What changed
- An article for v0.10.0, the fourteenth in the section, with six screenshots. It ends on what the release did not settle: the shape is derived, the map is the reader's and the site never sees it, the secrets prompt is a read of the record, the past conversations question is not measured, and the three walkthroughs share a shape and not a module.
What it was built against
- The v0.10.0 tag, checked out into a detached worktree and served locally, the same method as every other article's figures.