internationalcolorconsortium/iccdev/upstream-pr-readiness

Upstream PR Readiness

Hard Stop

Find an exact user quotation authorizing PR creation or reopening. Requests to push, trigger CI, prepare a description, request review, or monitor checks do not qualify.

If explicit authorization is absent, return:

readiness: FAIL
reason: PR creation is not explicitly authorized

Do not call gh pr create, gh pr reopen, or an equivalent API.

Workflow

1. Work in a clean clone or worktree. For maintainer branch grooming, apply

../../../docs/linear-stack-workflow.md local Git defaults first.

1. Fetch the target branch and current base.
2. Rebase onto the current base before PR creation or review.
3. Verify linear history and review the rewrite:

``bash git config --get pull.rebase git config --get merge.ff git diff --check origin/master..HEAD test -z "$(git rev-list --merges origin/master..HEAD)" git range-diff origin/master origin/BRANCH HEAD ``

1. Review every changed file and confirm the PR description covers the entire

feature surface.

1. Build normal targets and excluded regression helpers:

``bash cmake -S Build/Cmake -B /tmp/iccdev-pr-ready \ -DCMAKE_BUILD_TYPE=Debug -DENABLE_TOOLS=ON cmake --build /tmp/iccdev-pr-ready -j"$(nproc)" cmake --build /tmp/iccdev-pr-ready \ --target build-test-binaries -j"$(nproc)" ctest --test-dir /tmp/iccdev-pr-ready --output-on-failure ``

1. Record a base...HEAD contract matrix for every changed cross-cutting

surface: producer, consumer, build/runtime behavior, platform or toolchain boundary, CI trigger, dependency owner, and local evidence.

1. Run task-specific Release, compiler, sanitizer, diagnostics, runtime-dispatch,

fallback, malformed-input, and other negative tests.

1. Remove generated artifacts and verify a clean worktree.
2. Inspect all active and suppressed findings from review threads and review

summaries.

1. Produce the evidence record from

docs/governance/UPSTREAM_PR_READINESS.md.

Result

Only readiness: PASS plus explicit authorization permits PR creation.

If a re-review finds any new blocker, including one in the repair, change the result to FAIL and return to branch-only grooming.

References

• ../../../docs/linear-stack-workflow.md