feat: add status page CLI commands and YAML workflow #32

AssertionError: YAML section "statusPages" has no corresponding CLI resource mapping: expected false to be true // Object.is equality - Expected + Received - true + false ❯ test/yaml/parity.test.ts:43:9

test/yaml/handlers.test.ts > handler registry > allHandlers returns all 9 handlers: test/yaml/handlers.test.ts#L36

AssertionError: expected [ …(10) ] to have a length of 9 but got 10 - Expected + Received - 9 + 10 ❯ test/yaml/handlers.test.ts:36:22

test/yaml/applier.test.ts > applier > updates > updates an environment via PUT using environment id in path: test/yaml/applier.test.ts#L258

AssertionError: expected "vi.fn()" to be called with arguments: [ '/api/v1/environments/{slug}', …(1) ] Received: 1st vi.fn() call: @@ -1,10 +1,10 @@ [ "/api/v1/environments/{slug}", { "body": { - "isDefault": undefined, + "isDefault": null, "name": "Prod", "variables": { "KEY": "val", }, }, Number of calls: 1 ❯ test/yaml/applier.test.ts:258:23

lint

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

lint: src/commands/status-pages/groups/list.ts#L16