Repository navigation
README for the release, and ADR-0003 - #50
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.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
Closes #36
README brought up to date for the 0.1.0 release, plus ADR-0003 recording the release decision.
README.md What a Run does Status - walking skeleton … (except marking a draft ready) … + designed behaviour implemented; gaps in open issues Install + curl … thirdshift-installer.sh | sh → ~/.local/bin, no Rust + cargo install thirdshift (alternative for Rust users) Updating (thirdshift update; lists the other kinds of install) + Supported platforms (Rocky 9.8+, Ubuntu 24.04.3+, WSL2 + Ubuntu 24.04+, macOS Tahoe 26.5.2+ Apple Silicon) Prerequisites (claude, gh, git only) - The Rust toolchain Usage + update / version / help (bare words only) + Building from source (Rust, cargo install --path ., system-wide install, python3 for tests) + Releasing (bump in a PR → merge → push v<version> tag) docs/adr/ + 0003-static-binaries-through-github-releases.mdADR-0003 gives three reasons for choosing static musl binaries through
distGitHub Releases, mirrored to crates.io, over crates.io alone: installing needs no Rust, a glibc build won't run on Rocky 9, and the crate name is permanent once claimed.CONTEXT.mdis unchanged.Evidence
Docs only, with no code changes.
cargo install --path ., and Rust was a prerequisite.After: every acceptance criterion in README for the release, and ADR-0003 #36 is covered. The claims were checked against
dist-workspace.toml,.github/workflows/release-smoke.yml,publish-crates.yml,src/main.rs(help text) andsrc/update.rs(refusal hints).cargo testpasses in full.Merge Danger
Door: two-way
Blast Radius: documentation
Only readers are affected. The Install section points at
releases/latest/download/thirdshift-installer.sh, which only works afterv0.1.0is tagged (#38).Unaddressed findings
Standards
git checkout main && git pull, butupdate.rsprintsgit pull: the README version is the more explicit form of the same step, and not worth changing the binary's output for.src/update.rs: user docs and CLI output naturally both show the command, and a docs change shouldn't pull in a shared source.Spec
🤖 Generated with Claude Code