Repository navigation
Conversation
|
|
I read this against The classification is not settled, so no label went on and nothing was run yet. Every item here is classified by two models separately, and the second (Codex Medium) did not run this time because its daily review budget was already used up. Without its answer this pull request has not been reproduced on a worker or given a second review, and none of the above is a verdict on whether it works. It waits on that second classification. Once it agrees, the next pass reproduces the split-transaction file loss on a disposable worker against |
omarchy dev pkg-testinstalls settings-dev before building and installing omarchy-dev. When files move between the packages, the second upgrade removes paths installed by the first, leaving required helpers missing. This was reproduced in omacom/omarchy-pkgs#645 (comment).Build all requested packages first, then pass their archives to one
pacman -Utransaction. A failed build installs nothing; an explicit single-package invocation retains its existing behavior.Validation: command-level stubbed regressions check one transaction after both builds, no installation after a failed second build, and explicit package alias behavior. The tests reject the original implementation. The full CLI suite, bin style check, and
git diff --checkpass. No real package transaction was run on the development machine.