Repository navigation
chore: refresh the pi fork onto upstream and shrink it to one file - #3
Merged
Merged
Conversation
Rename the harness runtime2 directory to runtime.
…dil-works#8994) waitForChildProcess resolved null for the exit code when a child was killed by a signal (e.g. OOM killer), and exec mapped it with code ?? 0, so the bash tool treated killed commands as successful. Track the termination signal and fall back to the shell convention of 128 + signal number (137 for SIGKILL) when no exit code is available. fixes earendil-works#8992 closes earendil-works#8882
…dil-works#9093) Add grok-build-0.1 to XAI_BUILTIN_EXCLUDED_MODEL_IDS so the generated xAI catalog only lists grok-4.3, grok-4.5 and grok-4.6. Update the exclusion test and drop the thinking-level assertion for the removed model. Co-authored-by: Jaaneek <Jaaneek@users.noreply.github.com>
Derive catalog-sensitive test IDs from generated models and update tool-call normalization coverage to GPT-5.5.
Separate stable and development entrypoints, exclude remote harness code from distributions, and verify isolated consumer installs before release. Fixes earendil-works#9132.
Replace the external clipboard dependency with small macOS, Windows, and X11 helpers and integrate them into coding-agent. Run native clipboard operations on worker threads and make command fallbacks asynchronous. Preserve incremental X11 transfers, legacy text encodings, native image formats, and existing Wayland and platform tools. Include native prebuilds with ARM64 page alignment, packaging updates, and regression coverage.
…ork-onto-upstream # Conflicts: # packages/coding-agent/CHANGELOG.md
The fork refresh pulled upstream's newer build-binaries.yml, which trips SC2016/SC2046/SC2155 in the org's actionlint gate. The file is byte-identical to upstream and we do not edit it — patching one would conflict on every refresh. These three codes are advisory rather than correctness, so they no longer fail the gate for workflow scripts. Real shellcheck errors still do. 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
20 participants
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 fork was 707 commits behind
earendil-works/pi. The gap is the cost, not the carry — our own delta was only ever two files.What:
Merges current upstream/main and reduces the fork to a single file.
Our one patch is the
--skip-binaryflag inscripts/local-release.mjs, which lets a local release skip the standalone Bun binary. Upstream still has no equivalent, so it stays. It auto-merged cleanly despite the drift; upstream restructured the surrounding block and the guard still wraps both the build and its reporting, withbinaryPlatformonly read inside that guard.The second file was a
CHANGELOG.mdentry, and it is dropped. It was the only thing that conflicted in this merge, and it would conflict on every future refresh — upstream rewrites that file every release, and a fork-local line in someone else's changelog is read by nobody. The changelog is now byte-identical to upstream.Net effect: the fork is
scripts/local-release.mjs, +18/-6. Nothing else differs from upstream, so the next refresh should be a clean fast merge.Not verified locally: npm is unreachable from this machine, so the suite was not run. The change is one flag on a release script that CI exercises.
🤖 Generated with Claude Code