Skip to content

DO NOT MERGE — MX-222 negative control, proving the new gate can go red - #9

Closed
MGrin wants to merge 2 commits into
mainfrom
mx-222-negative-control
Closed

DO NOT MERGE — MX-222 negative control, proving the new gate can go red#9
MGrin wants to merge 2 commits into
mainfrom
mx-222-negative-control

Conversation

@MGrin

@MGrin MGrin commented Aug 21, 2026

Copy link
Copy Markdown
Owner

Throwaway. A gate that has never failed is not known to be a gate — MX-222 exists because a green check proved less than it looked like it did. This branch breaks something on purpose so the new job is observed failing, and will be closed and deleted as soon as the red is read.

… (MX-222)

`npm install` may resolve a version the lockfile does not pin and will happily
run against a package.json the lockfile no longer matches. `npm ci` fails on
that disagreement, which is the one extra thing this job can check for free.

Swept from MX-222 (bb-plugin-accounts). This repo already had the Test job —
MX-228 added it — so this is the only difference between the three plugins'
gates. Verified locally: `npm ci` + typecheck + `npm test` all exit 0.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@MGrin
MGrin force-pushed the mx-222-negative-control branch from b63e901 to d0ff06e Compare August 21, 2026 03:16
@MGrin

MGrin commented Aug 21, 2026

Copy link
Copy Markdown
Owner Author

Read: npm ci refused the lockfile drift that npm install accepted, on the same commit (MX-222). Evidence copied to #8.

@MGrin MGrin closed this Aug 21, 2026
@MGrin
MGrin deleted the mx-222-negative-control branch August 21, 2026 03:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant