Bring the documentation up to the first release, and measure the update path - #4
Merged
Merged
Conversation
…te path A pass over every page and the comments the last two days touched. Lot 8 is closed in the index and its record, with the second machine's install as the one field check still outstanding; the record's claim that the summary bit alone makes a package per-user is corrected in place with the real package's measurement. The recipes told an installer user to run install-task after copying a configuration, which keeps a running watcher on the old file: they say stop then install-task now, as getting-started does. AGENTS.md says how a change is verified on a machine the installer owns. Comments in task.rs, the twin and msi.ps1 no longer describe the console binary as the only one that runs the setup commands. Lot 13's page records what v0.1.0 actually answers -- the redirect that carries the tag, the checksum file, the asset chain, the API's digest -- and what the package now does for the updater: it stops and restarts the watcher itself, so the earlier quit-then-relaunch plan is superseded, and the updater keeps only the failure path. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
A pass over every Markdown page and the comments touched since 2026-09-17, after
v0.1.0went out. No code change; three comments, one AGENTS.md paragraph, the design record and the user pages.ALLUSERS/MSIINSTALLPERUSERwere unnecessary. That was the probe's reading; the real package measured the opposite (bit alone →C:\Program Files (x86),ALLUSERS=2alone → per-machine, 1603) and the measurement had only lived in a comment inmsi.ps1. Both readings now stand in the record, dated.install-taskafter copying a configuration. For an installed copy the task exists and the watcher is already running, so it kept the old file until the next logon. They now saystoptheninstall-task, as Getting started does.stop, copy,install-task; uninstall/reinstall for a package change, since the product code is fixed per version).v0.1.0actually answers — the302carrying the tag,SHA256SUMS.txtby tag, the asset chain, the API'sdigestagreeing with the workflow's hash — and what the package now does for the updater: it stops and restarts the watcher itself, so the earlier quit-then-relaunch plan is superseded and the updater keeps only the failure path. Still a proposal; nothing built.stopjoins the list of commands that log undersetup, and three comments no longer describe the console binary as the only one running the setup commands.Test plan
.\scripts\build.ps1 test— 112 + 3 tests, 24 pages, every link resolves🤖 Generated with Claude Code