Skip to content

Fix critical Homebrew adoption and CLI onboarding regressions#565

Merged
cooper (czxtm) merged 1 commit into
mainfrom
cm/critical-bug-investigation-70f3
Jul 22, 2026
Merged

Fix critical Homebrew adoption and CLI onboarding regressions#565
cooper (czxtm) merged 1 commit into
mainfrom
cm/critical-bug-investigation-70f3

Conversation

@cursor

@cursor cursor Bot commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

Summary

Rebased onto main and folded the remaining unique fixes from #490 (now closed):

  • Homebrew nix-eval attr quotingserde_json::to_string already quotes the hostname; the old template added a second pair and produced .#darwinConfigurations.""host"".config.homebrew.
  • GitHub import path rejection — URLs like https://github.com/owner/repo/tree/main no longer mis-parse as owner/repo via rsplit.
  • Shell-safe canonical dir ownership — privileged mkdir/chown for /etc/nix-darwin shell-escapes the username.

CLI empty-model onboarding and Homebrew write-target inference already exist on main (isInferenceConfigured / attach_existing_homebrew_write_target), so those parts of the original drafts are not duplicated here.

Test plan

  • cargo test nix_eval_homebrew_attr_quotes
  • cargo test rejects_github_urls_with_extra
  • cargo test shell_literal_escapes
  • CI green on main

Rebase the critical Cursor-bot fixes onto main: quote flake hostnames
once for nix-eval Homebrew adoption, reject GitHub URLs with extra
path segments before token minting, and shell-escape the privileged
canonical-dir ownership script.
@czxtm
cooper (czxtm) force-pushed the cm/critical-bug-investigation-70f3 branch from cbc5603 to 2071883 Compare July 21, 2026 17:19
@czxtm
cooper (czxtm) changed the base branch from develop to main July 21, 2026 17:19
@czxtm
cooper (czxtm) marked this pull request as ready for review July 21, 2026 17:19
@cursor

cursor Bot commented Jul 21, 2026

Copy link
Copy Markdown
Contributor Author

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

@github-actions

Copy link
Copy Markdown
Contributor
Warnings
⚠️

No Linear issue ID found in this PR's title, description, or branch name (expected something like ENG-123). Add one so this work is traceable in Linear, or add #no-linear to the PR description to acknowledge it's intentionally untracked.

📋 PR Overview

Lines changed 101 (+83 / -18)
Files 0 added, 3 modified, 0 deleted
Draft / WIP no
Has Test Plan yes
Linear issue no
No Test Plan Needed no
New UI components no
New Storybook stories no
New Rust modules no
New TS source files no
New tests no
package.json touched no
Cargo.toml touched no
Infra / CI touched no

🔬 Coverage

Report Lines Statements Functions Branches
apps/native/coverage/coverage-summary.json 37.4% 37.1% 32.8% 31.6%

Generated by 🚫 dangerJS against 2071883

@darkmatter

darkmatter Bot commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

🎨 Storybook preview

Open Storybook preview

Updated for 2071883


🧭 Story changes

Compared to develop (snapshot diff at story level):

🆕 New stories (13)

✏️ Changed stories (88)

💡 Update snapshots ↗ to regenerate baselines and open a PR.


⚠️ Detected UI changes (5)

These stories' HTML snapshots changed. I've added screenshots + links to the changed stories below. Review them carefully then accept the changes to regenerate baselines and include them in this PR:

UI/InputGroup › Inline Addons

UI/InputGroup › Inline Addons

UI/InputGroup › Block Addons

UI/InputGroup › Block Addons

UI/Select › Provider

UI/Select › Provider

Flows/Evolve › Playground

Flows/Evolve › Playground

Flows/Evolve › 1. Begin (idle)

Flows/Evolve › 1. Begin (idle)


Accept UI changes

  • Click here to accept these changes

Alternatively, you can run bun run test:update-snapshots locally to re-generate the baselines and then push the changes to this PR.

What does this do?

The screenshots above show UI changes detected by the Storybook
snapshot tests run on this PR. Each image is the rendered output of
a Storybook story from the code in this PR branch; the snapshot
test compared it against the committed baseline in
__snapshots__/ and flagged the difference.

Checking the box tells the darkmatter[bot] to regenerate the
baselines from this PR's current code and commit them directly to
this branch. The new baselines become the source of truth for
future runs — only accept after confirming the visual changes are
intentional.

Comparison baseline: the committed __snapshots__/ files on this
PR branch (carried forward from develop). Accept updates them in
place on this branch.

@czxtm
cooper (czxtm) merged commit bdc72de into main Jul 22, 2026
7 of 13 checks passed
@czxtm
cooper (czxtm) deleted the cm/critical-bug-investigation-70f3 branch July 22, 2026 09:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant