[systemfsoftware-maker]

Part of SYS-1245.

Cause

This repo's .mergify.yml is a standalone config that does not extend the org policy, so the org's commands_restrictions — which allow @Mergifyio queue from kiro-systemf[bot], a GitHub App that can never meet sender-permission >= write — do not apply here. On #20 the bot's queue command was refused on exactly that restriction (2026-11-09 14:56 UTC), and the org's queue/merge protections, batch defaults, and approval gates are all absent.

Change

Replaces the standalone config with extends: .github and a queue rule naming this repo's real check: CI reports exactly one check, check (commit lint and the changeset intent run as steps inside that job). Nothing is loosened — approval, draft, hold, and changes-requested gating now comes from the org policy's approved-PR queue rule and merge protections, which enforce the same conditions org-wide, and @Mergifyio queue from kiro-systemf[bot] becomes allowed by the org's command restrictions. The SYS-440 bootstrap note is obsolete: the queue takes over from the next PR.

Verification and pending evidence

• ./bin/dprint check .mergify.yml passes; the rule names the only check CI reports.
• check is red on this PR for a reason unrelated to this diff. The Nix pnpm-store build fails fetching https://pkg.alchemy.run/@alchemy.run/cloudflare/-/d48c0fa9….tgz, a content-hash tarball pinned by main's pnpm-workspace.yaml catalog (with alchemy, @alchemy.run/github, and their closure in pnpm-lock.yaml). The host returns HTTP 404 for that tarball and for the package index https://pkg.alchemy.run/@alchemy.run/cloudflare (probed 2026-11-09). This diff touches only .mergify.yml, and fix(deps): update xstate tarball integrity #20's own check was green earlier the same day, so the artifact expired between the two runs. Every frontend PR pushed from here on will hit this until the catalog stops pinning that artifact; that dependency change is outside SYS-1245's rename-only scope and is not made here.
• Until that is fixed this PR cannot satisfy its own queue rule; merge it manually (branch protection is off) or queue it by command.
• Full pnpm check:ci and pnpm journeys remain pending off-host acceptance (source: fix(deps): update xstate tarball integrity #20's verification notes).

[systemfsoftware-maker]

Duplicate of #8; the fix moves onto the original PR.