docs: add HOW_TO_PR_UPSTREAM.md and a pr-upstream skill - #50
Merged
Merged
Conversation
…r upstream PRs HOW_TO_PR_UPSTREAM.md records the full procedure behind the numbers in wild-linker#2634: how the binaries are built, the captures, capture_ab.py settings (budgets, ABBA pairs, tmpfs output, discarding contaminated runs), correctness evidence and the fork CI A/B. It also covers the verification steps, the PR description format (italic AI-disclosure header, then Summary, Benchmarks, Design), the approval rule, and the lessons previously in AGENTS.md. The pr-upstream repo skill walks through it, and AGENTS.md makes reading it mandatory before authoring an upstream PR. make_small_captures.sh regenerates the tinyc and cxxdbg small-link captures.
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.
Makes the upstream PR process explicit and mandatory.
HOW_TO_PR_UPSTREAM.mdis the full procedure behind the upstream debug-relocation PR's numbers: identical builds, captures,capture_ab.pysettings (600 s / 300 s budgets, ABBA pairs,--no-fork, tmpfs output, discarding contaminated runs), correctness evidence (both build-id modes, forced fallback, cross-arch threshold test) and the fork CI A/B via a draft[bench]PR. It also covers verification (tests, clippy, nightly fmt, wasip1), the description format (italic AI-disclosure header, then Summary, Benchmarks, Design), the approval rule, review etiquette, and the lessons previously in AGENTS.md..claude/skills/pr-upstream/SKILL.mdwalks through the guide step by step and requires approval before anything is posted upstream.AGENTS.mdnow makes reading the guide and using the skill mandatory before authoring an upstream PR. The long lessons section moved into the guide, so there's one source of truth.benchmarks/performance_guard/make_small_captures.shregenerates thetinyc(5,000 C files) andcxxdbg(1,500 C++ files) small-link captures. Verified locally: both capture, relink and run.REUSE.tomlcovers the new files.