Tick what 0.2.0 closed and record the second machine's first install - #8
Merged
Merged
Conversation
Lot 14 is done: the changelog, the notes script, the rules, v0.1.0 rewritten, 0.2.0 published with it. Lot 13 shipped in 0.2.0 and closes on the first update from it. Lot 8's chain ran twice; the second machine stays the maintainer's to report. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
A Windows PC out of the box runs no script, and marks anything downloaded; the recipe said .\install-tasks.ps1 and nothing more, which is where a person following it on a fresh machine stops. Unblock-File and a per-command Bypass change nothing on the machine and need no administrator; the elevated half already relaunches itself that way. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Two lines a first-time user was missing on the second machine: the installer is unsigned, so Windows stops it with "Windows protected your PC" and nothing said "More info, Run anyway"; and the recipe's page said to copy its config.toml "over your own", which was read as a merge when the file is the whole configuration and the starter has nothing to keep. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Lot 8's last field box: 0.2.0 installed on the second machine on 2026-09-18, the log showing the three setup lines, the watcher starting, and two sessions. The record keeps the five frictions a first-time user met around the package, with what was taken at once (SmartScreen line, execution policy, replace-not-merge) and what is only proposed (a recipes artefact on the release, a Start menu shortcut). Lot 9 gets the third refinement observation: a session named chrome.exe by Windows' own list, renamed Overwatch.exe at 3 % on its loading screen. 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
1 participant
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.
Documentation only. Four commits, each readable on its own.
What changed
08-distribution.md: the log's facts (the threesetuplines in 300 ms, two sessions), then the five frictions a first-time user met around the package — SmartScreen, the execution policy, no way to download one folder from GitHub, the recipe's file merged rather than replaced, no obvious way to start the watcher again after Quit — with what was taken at once and what is only proposed (a recipes artefact on the release, a Start menu shortcut,.cmdlaunchers). Proposed, not decided.Unblock-File, then-ExecutionPolicy Bypassfor the one command), and says to replaceconfig.tomlwhole rather than merge.chrome.exe, renamedOverwatch.exeat 3 % on its loading screen at T+21 s.Why
The 0.2.0 release and the second machine's install were the two things the lot pages were waiting on. The frictions are recorded where the next lots will weigh them, none needed an action that night.
For the reviewer
build.ps1 testgreen, 26 pages, every link resolves.🤖 Generated with Claude Code