Repository navigation
Make uv base installation the clear first-user path - #265
Merged
Patrick Roebuck (silversurfer562) merged 5 commits intoOct 12, 2026
Merged
Conversation
Explain the base profile, optional integrations, executable checks and separate host-plugin setup with observed release-install limits. Co-Authored-By: GPT-6 <noreply@openai.com>
Point onboarding and CLI links at the existing reviewed installation-guide source; keep optional integrations explicit. Co-Authored-By: GPT-6 <noreply@openai.com>
Close the independent P2 onboarding finding by selecting the actual uv tool Python for fixture, API and GUI examples, with platform-specific paths and version verification. Co-Authored-By: GPT-6 <noreply@openai.com>
Keep README destinations bound to an existing guide revision that includes the reviewed managed-Python selection. Co-Authored-By: GPT-6 <noreply@openai.com>
Preserve the existing immutable documentation revisions while adopting the verified marketplace-only main update. Co-Authored-By: GPT-6 <noreply@openai.com>
Patrick Roebuck (silversurfer562)
marked this pull request as ready for review
October 12, 2026 14:58
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Patrick Roebuck (silversurfer562)
deleted the
docs/uv-first-onboarding
branch
October 12, 2026 15:01
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.
Why
The published 1.4.0 instructions recommend the larger
[all]profile before users need Redis or Voyage, and Python module examples can select a different interpreter from a managed tool. This change gives future users one tested base installation path and binds later examples to that same runtime.What changes
Recommend
uv tool install 'attune-harness==1.4.0'in README and the CLI guide. Add an indexed installation guide covering executable/version checks, optional profiles, managed-Python selection and separate Codex/Claude plugin setup. Preserve pipx and dedicated-venv alternatives. README links pin existing corrected guide revision69f645bd4f471926554d1919c92b8cad2b06274drather than a prospective tag.Only four documentation paths change. Runtime, dependency pins, plugin code, tests, workflows, release tag and published 1.4.0 archives remain unchanged.
Verified
[all]and uv 0.11.28 base installations each passed the existing 29 offline CLI cases and plan/accept/build/review/status journey with zero model calls; all 105 module identities match. Base resolved 48 distributions versus 93 for[all], excluding installer packages. This is an observed package count, not a speed or feature-parity claim.ba589090e9f570320a0365c3b6b72199d8b1e07c(tree603b490169d186bab5bc12d06ddf802186a47f5f). Its P2 interpreter-binding finding was corrected and re-reviewed; all 24 README targets/anchors resolve locally and pinned guides match.Not verified
Fresh uv installation on Windows/Linux, the PowerShell example, normal-tool upgrade and stable saved-work migration were not observed. Cross-platform installed-wheel qualification is separate from the Mac uv experiment. No independent non-programmer first-use, native browser/accessibility trial, live Redis or paid provider execution is claimed.
Left open
Patrick requested reusable installation improvements for future users. Patrick explicitly authorized “re pr 265 shepherd it” on October 12 at 14:55 UTC. All 17 exact-head checks have settled successfully; protected squash integration and exact-main verification are authorized. The existing ordinary Mac uv 1.3.0 tool and all retained evidence environments/practices remain preserved. Already-published PyPI 1.4.0 metadata is immutable; approved guidance can reach GitHub on merge and a future package release without reusing the version. Help hosting and existing S3/S6/S9 deferrals are unchanged.