YI Yeh I. / Product Engineering Back to capabilities

SELF-OWNED ENGINEERING PROOF · CI / RELEASE

PR Release Gate

A pull request reaches staging only when typecheck, unit, Playwright, and build evidence all pass for the exact candidate commit. Missing, pending, failed, or stale results return an explicit hold decision.

Candidate
8f31c2a
Required checks
typecheck · unit · playwright · build
Decision
RELEASE
Policy verification
4 / 4 policy checks passed

ONE COMMIT · FOUR CHECKS

Green is valid only when every result belongs to the candidate.

  1. 01typecheckSyntax and type boundary
  2. 02unitPolicy and business behavior
  3. 03playwrightDesktop and mobile workflow
  4. 04buildPublic-content gate

FAIL-CLOSED POLICY

The gate explains why it stopped.

Missing

No silent skip

If any required check is absent, the decision records the missing check and remains on hold.

Failed or pending

No premature staging

A failed or unfinished result remains a blocker even when every other check is green.

Stale commit

No borrowed green result

A passed check from an earlier commit cannot approve the current candidate.

Handoff

One release decision

The returned decision includes the verified commit and a concrete blocker list for the reviewer.

EXECUTABLE EVIDENCE

Policy, browser check, and CI configuration are inspectable.

The repository contains the decision function, four policy tests, a responsive Playwright check, and a GitHub Actions workflow.

release-policy.test.mjsPASS
$ node --test release-gate-proof/release-policy.test.mjs

✔ all required checks passed for the candidate commit
✔ missing Playwright check blocks staging
✔ failed and pending checks return explicit blockers
✔ stale commit result cannot approve the candidate

tests 4   pass 4   fail 0

Acceptance conditions

  • Only the four required check names can satisfy the policy.
  • Every result must match the candidate commit.
  • The responsive page is checked in desktop and mobile Chromium.
  • Public copy is checked for required evidence and unsupported claims.
Inspect the policy and tests on GitHub

BUYER HANDOFF

A CI engagement returns the checks, branch gate, failure evidence, and written release path for your repository.

Provide the repository and current deploy path. The first bounded step maps the release boundary, installs the agreed checks, proves one blocked and one passing pull request, and returns the operating notes.

Open Upwork profile