[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A0BDG6EZP7GTVVT0Z8FFS0":3,"skill-same:01M7A0BDG6EZP7GTVVT0Z8FFS0":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7A0BDG6EZP7GTVVT0Z8FFS0","release",null,"Cut a Sideboard version. Default: bump, README\u002Fchangelog, commit, merge, then push\u002Fretarget the `v*` tag so `.github\u002Fworkflows\u002Frelease.yml` publishes npm (OIDC) and the signed Mac desktop. No workflow_dispatch. Do not pack Electron in a worktree turn. Use for electron release, desktop release, pnpm release, or “I’ll publish npms.”","mattlevine\u002Fsideboard","mattlevine","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F836225?v=4","01M7A0A4TN8FJQD7Q6MB7K1HK1","Matt Levine","01M7A0A4V7C06D7JKTFA89TEM7",4,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmattlevine\u002Fsideboard\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frelease\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: release\ndescription: >-\n  Cut a Sideboard version. Default: bump, README\u002Fchangelog, commit, merge,\n  then push\u002Fretarget the `v*` tag so `.github\u002Fworkflows\u002Frelease.yml` publishes\n  npm (OIDC) and the signed Mac desktop. No workflow_dispatch. Do not pack\n  Electron in a worktree turn. Use for electron release, desktop release,\n  pnpm release, or “I’ll publish npms.”\n---\n\n# Release\n\nShared version lives in four `package.json` files (root, `apps\u002Fdesktop`, `packages\u002Fcli`, `packages\u002Fcore`).\n\n**The Release Action runs when a `v*` tag is pushed to origin.** That is the default path. Do not pack Electron in a worktree turn. A human at a real terminal may still run `pnpm release patch mac` locally.\n\nLong waits (Actions watch, Fly deploy, optional local pack) use [`.claude\u002Fskills\u002Flong-running\u002FSKILL.md`](..\u002Flong-running\u002FSKILL.md) (`\u002Flong-running`). Do not ask the human to poll.\n\n## What “create a new release” means\n\nThese phrases are the **same default** — do not ask which one they meant:\n\n- create a new release\n- create an electron release \u002F desktop release\n- I’ll publish npms\n\nDo **all** of the following:\n\n1. **Electron** — bump, then let `.github\u002Fworkflows\u002Frelease.yml` pack\u002Fsign\u002Fpublish the Apple Silicon dmg+zip (`electron-updater` `latest-mac.yml`) when the `v*` tag is pushed.\n2. **npm** — the same tag job publishes `@sideboard-ai\u002Fcore` + `@sideboard-ai\u002Fcli` via OIDC. It skips versions already on npm. Do not run `node scripts\u002Fpublish-npm.js` from the worktree unless they explicitly asked.\n3. **README** — Desktop download URL for `vX.Y.Z`.\n4. **Marketing** — update `site\u002F` (and `site\u002Fdocs\u002F`) when the public story changed (install, Slack, features). Homepage download buttons already point at `\u002Freleases\u002Flatest`; still refresh copy\u002Fscreenshots if this cut warrants it.\n5. **Changelog** — move `[Unreleased]` into `## [X.Y.Z] - YYYY-MM-DD`.\n6. **Commit + push** — Release commit, retarget `vX.Y.Z`, open or update the thread PR against **origin**.\n7. **Deploy if needed** — if this cut changed `site\u002F` or `apps\u002Frelay\u002F`, Fly-deploy the relay+site (below). Skip Fly when those trees are untouched.\n\nMerge the PR only when asked. Do not publish npm unless they explicitly said **publish npm** or **full release including npm**.\n\n## Worktree agents\n\nThe Action starts when the **`v*` tag is pushed** (or moved) to origin. Do not start a local Mac pack. Do not run foreground `pnpm release`.\n\n1. Merge `origin\u002Fmain`.\n2. Land feature work. Write `CHANGELOG.md` `[Unreleased]` for what is shipping.\n3. Bump versions **only** (skip if `package.json` is already the new version):\n\n   ```bash\n   node apps\u002Fdesktop\u002Fscripts\u002Frelease.js patch mac bump-only\n   ```\n\n   Signing env (`apps\u002Fdesktop\u002F.env`) is not required for this path.\n4. Point README Desktop download at:\n\n   `https:\u002F\u002Fsideboard-downloads.t3.tigrisfiles.io\u002FSideboard-latest-arm64.dmg`\n\n5. Update `site\u002F` if the public story changed. Move `[Unreleased]` notes into `## [X.Y.Z] - YYYY-MM-DD`.\n6. Commit (`Release vX.Y.Z`).\n7. Open or update the thread PR against **origin**. Merge when asked (or when this turn is a Merge PR \u002F “commit push and merge”).\n8. After the Release commit is on `origin\u002Fmain`, **retarget** the version tag onto that commit. A tag left on an older SHA packs the old tree. Force-push **only** that version tag — never `main` \u002F `master`.\n\n   ```bash\n   git fetch origin\n   git tag -a \"vX.Y.Z\" -m \"Sideboard vX.Y.Z\" origin\u002Fmain -f\n   git push origin \"refs\u002Ftags\u002FvX.Y.Z\" --force\n   ```\n\n   That push is what starts `.github\u002Fworkflows\u002Frelease.yml`. There is no **Run workflow** button.\n9. **Watch Actions yourself** (`\u002Flong-running`). Do not ask the human to poll.\n\n   ```bash\n   RUN=$(gh run list --workflow=release.yml --limit 1 --json databaseId,headBranch --jq '.[0].databaseId')\n   node scripts\u002Fdetached-job.cjs start gha-release -- node scripts\u002Fwatch-gha-run.cjs \"$RUN\"\n   ```\n\n   Do **not** `gh run watch`. It reprints the full TTY every 3 seconds and stalls the log pane. `watch-gha-run.cjs` polls `gh run view` and prints only when jobs\u002Fsteps change.\n\n   `present_artifact` `type=log` `artifact_id=gha-release` with `content=delta` only. CI on the same commit title is **not** a second Release — only the tag workflow publishes.\n10. On desktop job **heap OOM** or **`SecKeychainUnlock` \u002F `set-key-partition-list`**: fix `release.yml` (heap → `NODE_OPTIONS`; keychain → import-cert step, do not pass `CSC_LINK` into electron-builder), land that on main, retarget the **same** `vX.Y.Z` (do not bump). `publish-npm.js` skips versions already on npm. This is not the Apple Developer agreement prompt (that fails at notarization).\n11. **Deploy if needed.** When `site\u002F` or `apps\u002Frelay\u002F` changed in this cut:\n\n    ```bash\n    node scripts\u002Fdetached-job.cjs start fly-deploy -- fly deploy --config apps\u002Frelay\u002Ffly.toml --dockerfile apps\u002Frelay\u002FDockerfile .\n    node scripts\u002Fdetached-job.cjs wait fly-deploy\n    ```\n\n    From the monorepo root (Docker context is `.`). `present_artifact` `type=log` `artifact_id=fly-deploy` with `delta`. Details: [docs\u002Fsystem\u002Fdeploy.md](..\u002F..\u002F..\u002Fdocs\u002Fsystem\u002Fdeploy.md).\n\n    The Fly app id is `sideboard-slack-relay`. Fly cannot rename apps, and `fly apps rename` is not a command. That id is the Sideboard relay (phone, marketing site, and Slack collaboration), not a Slack-only service. Do not create `sideboard-relay` or change `app` in `apps\u002Frelay\u002Ffly.toml` to a name that does not exist.\n\nHuman at a real terminal: `pnpm release patch mac` is still fine for the Electron half; they still publish npm themselves unless they asked otherwise.\n\n## Phone (when they asked for a phone release)\n\nThe iOS app is `apps\u002Fmobile` (Expo). A desktop `v*` tag does not build it. After the release commit is the tree you want in the binary, start one production build and let EAS submit it to App Store Connect. Detach it (`\u002Flong-running`); a cloud build plus submit takes longer than a turn.\n\n```bash\nnode scripts\u002Fdetached-job.cjs start eas-ios -- bash -lc 'cd apps\u002Fmobile && npx eas-cli build --platform ios --profile production --non-interactive --auto-submit --wait'\n```\n\nRun that from the repo root so the job id is visible to `wait_for_job`. `eas.json` `production` auto-increments the iOS build number (`appVersionSource: remote`) and submits with App Store Connect app `6820766038`. Do not start a second build for the same cut. `eas whoami` must already be `matthewklevine`.\n\n## `@cursor\u002Fsdk` (user-installed)\n\nSideboard does not pack `@cursor\u002Fsdk`. Users install it with Settings → Agents → Cursor → Install (`npm i -g @cursor\u002Fsdk`) so agents can update it without a new Sideboard build.\n\n`stage-cursor-runtime.js` copies the runner plus `execa` \u002F `smol-toml` from `packages\u002Fcore\u002Fpackage.json` (same as `stage-sideboard-mcp.js`). Do not add `@cursor\u002Fsdk` to the root package or to core production dependencies. See `docs\u002Fsystem\u002Fconventions.md` (Desktop pack in a Sideboard worktree).\n\nSigning\u002Fnotarization for the **local** pack reads `apps\u002Fdesktop\u002F.env` (`CSC_*`, `APPLE_*`). `GH_TOKEN` comes from that file or `gh auth token`.\n\n## GitHub Actions (`release.yml`)\n\nThere is no **Run workflow** \u002F `workflow_dispatch`. The workflow runs only when a **`v*` tag is pushed** to **origin** (`mattlevine\u002Fsideboard`):\n\n```yaml\non:\n  push:\n    tags:\n      - 'v*'\n```\n\nThat is why step 8 retargets `vX.Y.Z` onto the Release commit on `origin\u002Fmain`. A tag that still points at an old SHA will run Actions against that old tree.\n\nThree jobs, all on the same tag push:\n\n| Job | Runner | What it does |\n|---|---|---|\n| `release-cli` | `ubuntu-latest` | Builds\u002Ftests, then publishes `@sideboard-ai\u002Fcore` + `@sideboard-ai\u002Fcli` via **npm trusted publishing (OIDC)**. |\n| `release-desktop-mac` | `macos-latest` | Import Developer ID into a runner keychain, Vite + stage Node\u002FMCP\u002FCursor runtime and `speech-dictate.app`, then `electron-builder --mac --publish always` without `CSC_LINK` (GitHub Release + `latest-mac.yml`). If the ~250MB zip 500s on `uploads.github.com` (`Error saving asset`), the same step retries that file (and `latest-mac.yml`) with `gh release upload`. Job `timeout-minutes: 50` (signed step 45) so a wedged notarize\u002Fdmg does not sit for the 6h default. |\n| `publish-downloads` | `ubuntu-latest` | After the Mac job, copies those assets to the public Tigris bucket (`download.sideboard.cloud`) via `scripts\u002Fpublish-tigris.sh`. Needs repo secrets `TIGRIS_ACCESS_KEY_ID` and `TIGRIS_SECRET_ACCESS_KEY`. Also writes `Sideboard-latest-arm64.dmg` and removes older versioned objects. New builds check `https:\u002F\u002Fdownload.sideboard.build` (generic, first `build.publish` entry). GitHub Releases stay in `build.publish` so copies that shipped with the GitHub feed can still update. |\n\n`release-cli` uses `permissions: id-token: write`. Do **not** gate it on `if: secrets.NPM_TOKEN` — GitHub rejects the `secrets` context in `if` (`Unrecognized named-value: 'secrets'`). Do **not** set `NODE_AUTH_TOKEN` or `setup-node` `registry-url` on that job; both skip the OIDC exchange. Trusted publisher on npmjs.com: `mattlevine\u002Fsideboard`, workflow file `.github\u002Fworkflows\u002Frelease.yml`, **no Environment name**. The `NPM_TOKEN` repo secret is unused for this job.\n\n`release-desktop-mac` signs\u002Fnotarizes only when repo secrets `MAC_CSC_LINK`, `MAC_CSC_KEY_PASSWORD`, `APPLE_ID`, `APPLE_APP_SPECIFIC_PASSWORD`, and `APPLE_TEAM_ID` are set. The job imports the `.p12` into a runner keychain and **unsets** `CSC_LINK` before `electron-builder` (electron-builder#10066: `set-key-partition-list` uses the p12 password, which macOS 26.6 rejects). If `MAC_CSC_LINK` is empty, it still packs and uploads with `-c.mac.identity=null` (unsigned; no auto-update). The job sets `NODE_OPTIONS=--max-old-space-size=8192` so `electron-vite` does not OOM on the hosted runner.\n\nDo **not** treat a `SecKeychainUnlock: The user name or passphrase you entered is not correct` failure as an Apple Developer Program agreement problem. Agreement \u002F paid-account lapses fail later in **notarization** (`notarytool` \u002F “you must first sign the relevant contracts”). The keychain error is local to the runner and is the #10066 path — keep the import-then-auto-discover workaround until a published `electron-builder` includes the fix.\n\nCI (`ci.yml` on PR \u002F `main` push) only tests. GitHub titles those runs with the commit message, so they look like extra Release jobs — they are not.\n\nTo fire Actions on current `origin\u002Fmain` without a new local pack (human asked to run the workflow):\n\n```bash\ngit fetch origin\ngit tag -a \"vX.Y.Z\" -m \"Sideboard vX.Y.Z\" -f\ngit push origin \"refs\u002Ftags\u002FvX.Y.Z\" --force\n```\n\nUse the version in `package.json`. Force-push **only** that version tag. Watch **Actions → Release**.\n\nPushing `.github\u002Fworkflows\u002F*.yml` needs the GitHub `workflow` OAuth scope (`gh auth refresh -s workflow`). A token without it is rejected (`refusing to allow an OAuth App to create or update workflow`).\n\n## npm publish (only when asked)\n\n```bash\npnpm release patch npm\n# or, versions already bumped:\nnode scripts\u002Fpublish-npm.js\n```\n\n`publish-npm.js --dry-run` builds and pretends to publish — useful to verify, not a substitute for the human’s real publish.\n\n## Full release including npm (only when asked)\n\n```bash\npnpm release          # patch, desktop + npm publish\npnpm release minor\n```\n\nWorktree agents push the `v*` tag and watch Actions. Do not run the combined foreground `pnpm release` from a chat turn.\n\n## Do not\n\n- Treat “create a new release” as docs-only or as “ask whether they also want Electron.”\n- Publish npm on the default release phrase.\n- Use the worktree nickname as the PR or release title.\n- Push to `upstream` or merge locally into the main checkout.\n- Commit `apps\u002Fdesktop\u002F.env` or `apps\u002Fdesktop\u002Frelease\u002F`.\n- Force-push `main` \u002F `master`.\n- Pack Electron locally in a worktree turn, or restart a job because the user asked “status?”.\n- Expect Actions → Release to have a **Run workflow** button. Trigger it by pushing a `v*` tag.\n- Ask the human to poll a long job.\n","# Release\n\nShared version lives in four `package.json` files (root, `apps\u002Fdesktop`, `packages\u002Fcli`, `packages\u002Fcore`).\n\n**The Release Action runs when a `v*` tag is pushed to origin.** That is the default path. Do not pack Electron in a worktree turn. A human at a real terminal may still run `pnpm release patch mac` locally.\n\nLong waits (Actions watch, Fly deploy, optional local pack) use [`.claude\u002Fskills\u002Flong-running\u002FSKILL.md`](..\u002Flong-running\u002FSKILL.md) (`\u002Flong-running`). Do not ask the human to poll.\n\n## What “create a new release” means\n\nThese phrases are the **same default** — do not ask which one they meant:\n\n- create a new release\n- create an electron release \u002F desktop release\n- I’ll publish npms\n\nDo **all** of the following:\n\n1. **Electron** — bump, then let `.github\u002Fworkflows\u002Frelease.yml` pack\u002Fsign\u002Fpublish the Apple Silicon dmg+zip (`electron-updater` `latest-mac.yml`) when the `v*` tag is pushed.\n2. **npm** — the same tag job publishes `@sideboard-ai\u002Fcore` + `@sideboard-ai\u002Fcli` via OIDC. It skips versions already on npm. Do not run `node scripts\u002Fpublish-npm.js` from the worktree unless they explicitly asked.\n3. **README** — Desktop download URL for `vX.Y.Z`.\n4. **Marketing** — update `site\u002F` (and `site\u002Fdocs\u002F`) when the public story changed (install, Slack, features). Homepage download buttons already point at `\u002Freleases\u002Flatest`; still refresh copy\u002Fscreenshots if this cut warrants it.\n5. **Changelog** — move `[Unreleased]` into `## [X.Y.Z] - YYYY-MM-DD`.\n6. **Commit + push** — Release commit, retarget `vX.Y.Z`, open or update the thread PR against **origin**.\n7. **Deploy if needed** — if this cut changed `site\u002F` or `apps\u002Frelay\u002F`, Fly-deploy the relay+site (below). Skip Fly when those trees are untouched.\n\nMerge the PR only when asked. Do not publish npm unless they explicitly said **publish npm** or **full release including npm**.\n\n## Worktree agents\n\nThe Action starts when the **`v*` tag is pushed** (or moved) to origin. Do not start a local Mac pack. Do not run foreground `pnpm release`.\n\n1. Merge `origin\u002Fmain`.\n2. Land feature work. Write `CHANGELOG.md` `[Unreleased]` for what is shipping.\n3. Bump versions **only** (skip if `package.json` is already the new version):\n\n   ```bash\n   node apps\u002Fdesktop\u002Fscripts\u002Frelease.js patch mac bump-only\n   ```\n\n   Signing env (`apps\u002Fdesktop\u002F.env`) is not required for this path.\n4. Point README Desktop download at:\n\n   `https:\u002F\u002Fsideboard-downloads.t3.tigrisfiles.io\u002FSideboard-latest-arm64.dmg`\n\n5. Update `site\u002F` if the public story changed. Move `[Unreleased]` notes into `## [X.Y.Z] - YYYY-MM-DD`.\n6. Commit (`Release vX.Y.Z`).\n7. Open or update the thread PR against **origin**. Merge when asked (or when this turn is a Merge PR \u002F “commit push and merge”).\n8. After the Release commit is on `origin\u002Fmain`, **retarget** the version tag onto that commit. A tag left on an older SHA packs the old tree. Force-push **only** that version tag — never `main` \u002F `master`.\n\n   ```bash\n   git fetch origin\n   git tag -a \"vX.Y.Z\" -m \"Sideboard vX.Y.Z\" origin\u002Fmain -f\n   git push origin \"refs\u002Ftags\u002FvX.Y.Z\" --force\n   ```\n\n   That push is what starts `.github\u002Fworkflows\u002Frelease.yml`. There is no **Run workflow** button.\n9. **Watch Actions yourself** (`\u002Flong-running`). Do not ask the human to poll.\n\n   ```bash\n   RUN=$(gh run list --workflow=release.yml --limit 1 --json databaseId,headBranch --jq '.[0].databaseId')\n   node scripts\u002Fdetached-job.cjs start gha-release -- node scripts\u002Fwatch-gha-run.cjs \"$RUN\"\n   ```\n\n   Do **not** `gh run watch`. It reprints the full TTY every 3 seconds and stalls the log pane. `watch-gha-run.cjs` polls `gh run view` and prints only when jobs\u002Fsteps change.\n\n   `present_artifact` `type=log` `artifact_id=gha-release` with `content=delta` only. CI on the same commit title is **not** a second Release — only the tag workflow publishes.\n10. On desktop job **heap OOM** or **`SecKeychainUnlock` \u002F `set-key-partition-list`**: fix `release.yml` (heap → `NODE_OPTIONS`; keychain → import-cert step, do not pass `CSC_LINK` into electron-builder), land that on main, retarget the **same** `vX.Y.Z` (do not bump). `publish-npm.js` skips versions already on npm. This is not the Apple Developer agreement prompt (that fails at notarization).\n11. **Deploy if needed.** When `site\u002F` or `apps\u002Frelay\u002F` changed in this cut:\n\n    ```bash\n    node scripts\u002Fdetached-job.cjs start fly-deploy -- fly deploy --config apps\u002Frelay\u002Ffly.toml --dockerfile apps\u002Frelay\u002FDockerfile .\n    node scripts\u002Fdetached-job.cjs wait fly-deploy\n    ```\n\n    From the monorepo root (Docker context is `.`). `present_artifact` `type=log` `artifact_id=fly-deploy` with `delta`. Details: [docs\u002Fsystem\u002Fdeploy.md](..\u002F..\u002F..\u002Fdocs\u002Fsystem\u002Fdeploy.md).\n\n    The Fly app id is `sideboard-slack-relay`. Fly cannot rename apps, and `fly apps rename` is not a command. That id is the Sideboard relay (phone, marketing site, and Slack collaboration), not a Slack-only service. Do not create `sideboard-relay` or change `app` in `apps\u002Frelay\u002Ffly.toml` to a name that does not exist.\n\nHuman at a real terminal: `pnpm release patch mac` is still fine for the Electron half; they still publish npm themselves unless they asked otherwise.\n\n## Phone (when they asked for a phone release)\n\nThe iOS app is `apps\u002Fmobile` (Expo). A desktop `v*` tag does not build it. After the release commit is the tree you want in the binary, start one production build and let EAS submit it to App Store Connect. Detach it (`\u002Flong-running`); a cloud build plus submit takes longer than a turn.\n\n```bash\nnode scripts\u002Fdetached-job.cjs start eas-ios -- bash -lc 'cd apps\u002Fmobile && npx eas-cli build --platform ios --profile production --non-interactive --auto-submit --wait'\n```\n\nRun that from the repo root so the job id is visible to `wait_for_job`. `eas.json` `production` auto-increments the iOS build number (`appVersionSource: remote`) and submits with App Store Connect app `6820766038`. Do not start a second build for the same cut. `eas whoami` must already be `matthewklevine`.\n\n## `@cursor\u002Fsdk` (user-installed)\n\nSideboard does not pack `@cursor\u002Fsdk`. Users install it with Settings → Agents → Cursor → Install (`npm i -g @cursor\u002Fsdk`) so agents can update it without a new Sideboard build.\n\n`stage-cursor-runtime.js` copies the runner plus `execa` \u002F `smol-toml` from `packages\u002Fcore\u002Fpackage.json` (same as `stage-sideboard-mcp.js`). Do not add `@cursor\u002Fsdk` to the root package or to core production dependencies. See `docs\u002Fsystem\u002Fconventions.md` (Desktop pack in a Sideboard worktree).\n\nSigning\u002Fnotarization for the **local** pack reads `apps\u002Fdesktop\u002F.env` (`CSC_*`, `APPLE_*`). `GH_TOKEN` comes from that file or `gh auth token`.\n\n## GitHub Actions (`release.yml`)\n\nThere is no **Run workflow** \u002F `workflow_dispatch`. The workflow runs only when a **`v*` tag is pushed** to **origin** (`mattlevine\u002Fsideboard`):\n\n```yaml\non:\n  push:\n    tags:\n      - 'v*'\n```\n\nThat is why step 8 retargets `vX.Y.Z` onto the Release commit on `origin\u002Fmain`. A tag that still points at an old SHA will run Actions against that old tree.\n\nThree jobs, all on the same tag push:\n\n| Job | Runner | What it does |\n|---|---|---|\n| `release-cli` | `ubuntu-latest` | Builds\u002Ftests, then publishes `@sideboard-ai\u002Fcore` + `@sideboard-ai\u002Fcli` via **npm trusted publishing (OIDC)**. |\n| `release-desktop-mac` | `macos-latest` | Import Developer ID into a runner keychain, Vite + stage Node\u002FMCP\u002FCursor runtime and `speech-dictate.app`, then `electron-builder --mac --publish always` without `CSC_LINK` (GitHub Release + `latest-mac.yml`). If the ~250MB zip 500s on `uploads.github.com` (`Error saving asset`), the same step retries that file (and `latest-mac.yml`) with `gh release upload`. Job `timeout-minutes: 50` (signed step 45) so a wedged notarize\u002Fdmg does not sit for the 6h default. |\n| `publish-downloads` | `ubuntu-latest` | After the Mac job, copies those assets to the public Tigris bucket (`download.sideboard.cloud`) via `scripts\u002Fpublish-tigris.sh`. Needs repo secrets `TIGRIS_ACCESS_KEY_ID` and `TIGRIS_SECRET_ACCESS_KEY`. Also writes `Sideboard-latest-arm64.dmg` and removes older versioned objects. New builds check `https:\u002F\u002Fdownload.sideboard.build` (generic, first `build.publish` entry). GitHub Releases stay in `build.publish` so copies that shipped with the GitHub feed can still update. |\n\n`release-cli` uses `permissions: id-token: write`. Do **not** gate it on `if: secrets.NPM_TOKEN` — GitHub rejects the `secrets` context in `if` (`Unrecognized named-value: 'secrets'`). Do **not** set `NODE_AUTH_TOKEN` or `setup-node` `registry-url` on that job; both skip the OIDC exchange. Trusted publisher on npmjs.com: `mattlevine\u002Fsideboard`, workflow file `.github\u002Fworkflows\u002Frelease.yml`, **no Environment name**. The `NPM_TOKEN` repo secret is unused for this job.\n\n`release-desktop-mac` signs\u002Fnotarizes only when repo secrets `MAC_CSC_LINK`, `MAC_CSC_KEY_PASSWORD`, `APPLE_ID`, `APPLE_APP_SPECIFIC_PASSWORD`, and `APPLE_TEAM_ID` are set. The job imports the `.p12` into a runner keychain and **unsets** `CSC_LINK` before `electron-builder` (electron-builder#10066: `set-key-partition-list` uses the p12 password, which macOS 26.6 rejects). If `MAC_CSC_LINK` is empty, it still packs and uploads with `-c.mac.identity=null` (unsigned; no auto-update). The job sets `NODE_OPTIONS=--max-old-space-size=8192` so `electron-vite` does not OOM on the hosted runner.\n\nDo **not** treat a `SecKeychainUnlock: The user name or passphrase you entered is not correct` failure as an Apple Developer Program agreement problem. Agreement \u002F paid-account lapses fail later in **notarization** (`notarytool` \u002F “you must first sign the relevant contracts”). The keychain error is local to the runner and is the #10066 path — keep the import-then-auto-discover workaround until a published `electron-builder` includes the fix.\n\nCI (`ci.yml` on PR \u002F `main` push) only tests. GitHub titles those runs with the commit message, so they look like extra Release jobs — they are not.\n\nTo fire Actions on current `origin\u002Fmain` without a new local pack (human asked to run the workflow):\n\n```bash\ngit fetch origin\ngit tag -a \"vX.Y.Z\" -m \"Sideboard vX.Y.Z\" -f\ngit push origin \"refs\u002Ftags\u002FvX.Y.Z\" --force\n```\n\nUse the version in `package.json`. Force-push **only** that version tag. Watch **Actions → Release**.\n\nPushing `.github\u002Fworkflows\u002F*.yml` needs the GitHub `workflow` OAuth scope (`gh auth refresh -s workflow`). A token without it is rejected (`refusing to allow an OAuth App to create or update workflow`).\n\n## npm publish (only when asked)\n\n```bash\npnpm release patch npm\n# or, versions already bumped:\nnode scripts\u002Fpublish-npm.js\n```\n\n`publish-npm.js --dry-run` builds and pretends to publish — useful to verify, not a substitute for the human’s real publish.\n\n## Full release including npm (only when asked)\n\n```bash\npnpm release          # patch, desktop + npm publish\npnpm release minor\n```\n\nWorktree agents push the `v*` tag and watch Actions. Do not run the combined foreground `pnpm release` from a chat turn.\n\n## Do not\n\n- Treat “create a new release” as docs-only or as “ask whether they also want Electron.”\n- Publish npm on the default release phrase.\n- Use the worktree nickname as the PR or release title.\n- Push to `upstream` or merge locally into the main checkout.\n- Commit `apps\u002Fdesktop\u002F.env` or `apps\u002Fdesktop\u002Frelease\u002F`.\n- Force-push `main` \u002F `master`.\n- Pack Electron locally in a worktree turn, or restart a job because the user asked “status?”.\n- Expect Actions → Release to have a **Run workflow** button. Trigger it by pushing a `v*` tag.\n- Ask the human to poll a long job.\n",{"name":5,"description":7},"main","02fe9a8780abdb3554a042bd4e4d84b774167ee7",".claude\u002Fskills\u002Frelease",0,"https:\u002F\u002Fgithub.com\u002Fmattlevine\u002Fsideboard","https:\u002F\u002Fgithub.com\u002Fmattlevine","2026-11-15 03:17:37",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add mattlevine\u002Fsideboard --skill release",{"tool":37,"command":38},"bunx","bunx skills add mattlevine\u002Fsideboard --skill release",{"tool":40,"command":41},"pnpm","pnpm dlx skills add mattlevine\u002Fsideboard --skill release","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmattlevine\u002Fsideboard\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frelease\u002FSKILL.md",true,[],[46,53,58,64,71,78],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7E0618TWSY135JSVJYDSDB7","skill-improver","When a miss will recur — you made it twice, or a person told you the rule — write the lesson into the skill before the turn ends. One sentence, in the same change. Run in the turn, not on a schedule.","https:\u002F\u002Fgithub.com\u002Fmattlevine\u002Fsideboard\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fskill-improver\u002FSKILL.md",[],[],{"skillNo":54,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7A0C7G870SK6SZTGMATAF26","https:\u002F\u002Fgithub.com\u002Fmattlevine\u002Fsideboard\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Frelease\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7A0C5ABGQBF6Q94FSXH6Y2M","long-running","https:\u002F\u002Fgithub.com\u002Fmattlevine\u002Fsideboard\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Flong-running\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7A0C2YWWYF5PME33KYS13SP","worktree-install","Reinstall dependencies in a Sideboard worktree after merge-from-main or a lockfile change. Use when `pnpm install` hangs, several worktrees install at once, or a native build is outside the permitted directory.","https:\u002F\u002Fgithub.com\u002Fmattlevine\u002Fsideboard\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fworktree-install\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7A0BWTS631GV69KGJW80RDQ","review","Merge-readiness review for this repository. Use when reviewing a PR, worktree diff, or Sideboard Review (Approve \u002F Approve with nits \u002F Request changes).","https:\u002F\u002Fgithub.com\u002Fmattlevine\u002Fsideboard\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Freview\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7A0AX3X2QYRQCTFNNKZGK92","phone-screenshots","Capture Sideboard phone or marketing screenshots from the iOS simulator without the Expo tools button. Use when hiding or restoring that button, retaking site\u002Fphone images, or the Expo overlay is in the way.","https:\u002F\u002Fgithub.com\u002Fmattlevine\u002Fsideboard\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fphone-screenshots\u002FSKILL.md",[],[]]