RC Stability Matrix

0.1.33 is the stable version published on latest. The next step is not to move latest, but to prove that the 1.0.0-rc.1 candidate can survive repeated complete runs on the real repository.

This page is the short operating guide for launching and recording the GitHub Actions matrix.

Development source 0.1.35 adds the visual custom-component designer, safe Quasar/UnoCSS styles and resizable QSplitter panels. It changes the public contract. The green 0.1.33 runs remain historical evidence and do not count toward promotion of the changed source.

Before launching

Check that the local repository is clean and that npm exposes 0.1.33 as the stable version:

npm view @vevedh/qform-builder-layer@latest version
npm dist-tag ls @vevedh/qform-builder-layer

The expected result is latest: 0.1.33. The next tag may remain on 0.1.32 until 1.0.0-rc.1 is published.

Launch the matrix

From GitHub or with GitHub CLI:

git push origin main
gh workflow run rc-stability.yml -f candidate=1.0.0-rc.1
gh run list --workflow rc-stability.yml --limit 5

The matrix runs three passes on Linux and Windows with bun install --frozen-lockfile, the full doctor, browser tests, strict screenshots and the verified npm artifact.

What counts as a green pass

A pass is acceptable only when every workflow job is green for the same commit:

• quality Linux and Windows;
• browser functional Linux;
• browser visual Windows;
• package artifact;
• final RC gate.

Do not record a partial run. Do not mix several commits.

Where to record evidence

Then fill release/rc-ci-stability.json with three green consecutive runs:

{
  "runNumber": 1,
  "commit": "...",
  "status": "green",
  "workflowUrl": "https://github.com/.../actions/runs/..."
}

Commands to run afterwards:

bun run rc:stability:launch:check
bun run rc:final-locks:check

The 1.0.0-rc.1 publication must stay on next. latest stays on 0.1.33 until the RC is fully validated in a real business application.

Recorded evidence

The RC Stability Matrix is validated for 1.0.0-rc.1 with three consecutive green runs on the real repository:

Pass	GitHub Actions run	Result	Duration
1	29015937386	green	13m22s
2	29034915381	green	18m2s
3	29036138919	green	21m25s

Run 29014924407 remains diagnostic evidence for the previous mandatory AGENTS.md access in a public checkout. It is excluded from the counter. The source evidence is release/rc-ci-stability.json.

The RC promotion remains blocked by external evidence that cannot be automated: manual accessibility review, bundle inspection and integration in a distinct business Nuxt 4 application.

CI note about local files

The public repository does not contain AGENTS.md or PROMPT_CONTEXT.md. Those files remain useful in the development archive, but they are intentionally excluded from Git and from the npm package. The rc:stability:launch:check gate must therefore not fail in GitHub Actions when they are missing; it checks the public documents and then confirms that those local notes stay ignored.