• Canonical ownership: generated

Functional Spec

• Story: story-vibepro-release-exact-sha-fast-path
• Status: -
• Clauses: 8

C-001

The workflow summary evaluates whether merge-to-npm publication completed within the 120000 millisecond target and reports the measured result.

Origin refs

INV-001

The merge commit is eligible for CI reuse only when its ordered parents are the pull request base and reviewed head and its tree equals a freshly reconstructed merge tree.

Origin refs

INV-003

Both validation modes retain the existing npm gitHead, dist-tag, git tag, and GitHub Release convergence checks.

Origin refs

INV-004

Unit and end-to-end tests cover fast reuse, full fallback, stale evidence, SHA mismatch, current-base mismatch, workflow mismatch, parent mismatch, tree mismatch, pagination, rerun pending state, foreign provenance, and Checks API failure.

Origin refs

INV-005

Release timing records merge, publish start, npm publication, and workflow final-step timestamps and derives pre-publish, npm, post-publish, merge-to-npm, and total durations without fabricating rerun stages.

Origin refs

INV-006

Fast validation requires successful, completed, fresh test (20), test (22), and analyze check runs from the expected GitHub Actions workflow paths, signed with the current pull request number, base SHA, and exact reviewed head SHA.

Origin refs

S-001

When every binding and evidence condition passes, the release workflow runs version checks, typecheck, release-focused tests, and npm pack without rerunning the full test suite.

Origin refs

S-003

When CI evidence, current-base/workflow provenance, or source binding is absent, failed, pending, stale, mismatched, or untrusted, the read-only immutable-base selector records explicit reasons and the separate release job executes the full test suite.

Origin refs

Diagrams

• none