chore: rename socket-repo-template to socket-wheelhouse

jdalton · jdalton · commit e74da4d0bdbc · 2026-05-10T20:06:33.000-04:00
diff --git a/.claude/hooks/auth-rotation-reminder/README.md b/.claude/hooks/auth-rotation-reminder/README.md
@@ -142,6 +142,6 @@ Other hooks can adopt the same `.snooze` pattern. The convention:
 ## Cross-fleet sync
 
 This README and the hook itself live in
-[`socket-repo-template`](https://github.com/SocketDev/socket-repo-template/tree/main/template/.claude/hooks/auth-rotation-reminder)
+[`socket-wheelhouse`](https://github.com/SocketDev/socket-wheelhouse/tree/main/template/.claude/hooks/auth-rotation-reminder)
 and are required to be byte-identical across every fleet repo.
 `scripts/sync-scaffolding.mts` flags drift; `--fix` rewrites it.
diff --git a/.claude/hooks/check-new-deps/README.md b/.claude/hooks/check-new-deps/README.md
@@ -129,6 +129,6 @@ All dependencies use `catalog:` references from the workspace root
 ## Cross-fleet sync
 
 This README and the hook itself live in
-[`socket-repo-template`](https://github.com/SocketDev/socket-repo-template/tree/main/template/.claude/hooks/check-new-deps)
+[`socket-wheelhouse`](https://github.com/SocketDev/socket-wheelhouse/tree/main/template/.claude/hooks/check-new-deps)
 and are required to be byte-identical across every fleet repo.
 `scripts/sync-scaffolding.mts` flags drift; `--fix` rewrites it.
diff --git a/.claude/hooks/cross-repo-guard/README.md b/.claude/hooks/cross-repo-guard/README.md
@@ -62,7 +62,7 @@ socket-cli
 socket-lib
 socket-packageurl-js
 socket-registry
-socket-repo-template
+socket-wheelhouse
 socket-sdk-js
 socket-sdxgen
 socket-stuie
@@ -98,6 +98,6 @@ companion git-side scanner in `.git-hooks/_helpers.mts` (`FLEET_REPO_NAMES`)
 ## Cross-fleet sync
 
 This README and the hook itself live in
-[`socket-repo-template`](https://github.com/SocketDev/socket-repo-template/tree/main/template/.claude/hooks/cross-repo-guard)
+[`socket-wheelhouse`](https://github.com/SocketDev/socket-wheelhouse/tree/main/template/.claude/hooks/cross-repo-guard)
 and are required to be byte-identical across every fleet repo.
 `scripts/sync-scaffolding.mts` flags drift; `--fix` rewrites it.
diff --git a/.claude/hooks/cross-repo-guard/index.mts b/.claude/hooks/cross-repo-guard/index.mts
@@ -53,7 +53,7 @@ const FLEET_REPO_NAMES = [
   'socket-lib',
   'socket-packageurl-js',
   'socket-registry',
-  'socket-repo-template',
+  'socket-wheelhouse',
   'socket-sdk-js',
   'socket-sdxgen',
   'socket-stuie',
diff --git a/.claude/hooks/gitmodules-comment-guard/README.md b/.claude/hooks/gitmodules-comment-guard/README.md
@@ -74,6 +74,6 @@ In `.claude/settings.json`:
 ## Cross-fleet sync
 
 This hook lives in
-[`socket-repo-template`](https://github.com/SocketDev/socket-repo-template/tree/main/template/.claude/hooks/gitmodules-comment-guard)
+[`socket-wheelhouse`](https://github.com/SocketDev/socket-wheelhouse/tree/main/template/.claude/hooks/gitmodules-comment-guard)
 and is required to be byte-identical across every fleet repo.
 `scripts/sync-scaffolding.mts` flags drift; `--fix` rewrites it.
diff --git a/.claude/hooks/logger-guard/README.md b/.claude/hooks/logger-guard/README.md
@@ -99,6 +99,6 @@ node --test test/*.test.mts
 ## Cross-fleet sync
 
 This README and the hook itself live in
-[`socket-repo-template`](https://github.com/SocketDev/socket-repo-template/tree/main/template/.claude/hooks/logger-guard)
+[`socket-wheelhouse`](https://github.com/SocketDev/socket-wheelhouse/tree/main/template/.claude/hooks/logger-guard)
 and are required to be byte-identical across every fleet repo.
 `scripts/sync-scaffolding.mts` flags drift; `--fix` rewrites it.
diff --git a/.claude/hooks/path-guard/README.md b/.claude/hooks/path-guard/README.md
@@ -103,7 +103,7 @@ negative test in `test/path-guard.test.mts`.
 ## Cross-fleet sync
 
 This README and the hook itself live in
-[`socket-repo-template`](https://github.com/SocketDev/socket-repo-template/tree/main/template/.claude/hooks/path-guard)
+[`socket-wheelhouse`](https://github.com/SocketDev/socket-wheelhouse/tree/main/template/.claude/hooks/path-guard)
 and are required to be byte-identical across every fleet repo.
 `scripts/sync-scaffolding.mts` flags drift; `--fix` rewrites it.
 
diff --git a/.claude/hooks/path-guard/segments.mts b/.claude/hooks/path-guard/segments.mts
@@ -6,7 +6,7 @@
 // consumers import from here so they can never drift apart.
 //
 // Synced byte-identically across the Socket fleet via
-// socket-repo-template/scripts/sync-scaffolding.mts (IDENTICAL_FILES).
+// socket-wheelhouse/scripts/sync-scaffolding.mts (IDENTICAL_FILES).
 // When adding a new stage/build-root/mode/sibling, edit this file in
 // the template and re-sync.
 
@@ -42,7 +42,7 @@ export const MODE_SEGMENTS = new Set(['dev', 'prod', 'shared'])
 // listing every fleet package keeps Rule B firing in any repo. When a
 // new package joins the workspace, add it here and propagate via
 // `node scripts/sync-scaffolding.mts --all --fix` from
-// socket-repo-template.
+// socket-wheelhouse.
 export const KNOWN_SIBLING_PACKAGES = new Set([
   // socket-btm
   'bin-infra',
diff --git a/.claude/hooks/private-name-guard/README.md b/.claude/hooks/private-name-guard/README.md
@@ -72,6 +72,6 @@ Always `0`. The hook never blocks; it only prints to stderr.
 ## Cross-fleet sync
 
 This README and the hook itself live in
-[`socket-repo-template`](https://github.com/SocketDev/socket-repo-template/tree/main/template/.claude/hooks/private-name-guard)
+[`socket-wheelhouse`](https://github.com/SocketDev/socket-wheelhouse/tree/main/template/.claude/hooks/private-name-guard)
 and are required to be byte-identical across every fleet repo.
 `scripts/sync-scaffolding.mts` flags drift; `--fix` rewrites it.
diff --git a/.claude/hooks/public-surface-reminder/README.md b/.claude/hooks/public-surface-reminder/README.md
@@ -81,6 +81,6 @@ Always `0`. The hook prints a reminder and steps aside.
 ## Cross-fleet sync
 
 This README and the hook itself live in
-[`socket-repo-template`](https://github.com/SocketDev/socket-repo-template/tree/main/template/.claude/hooks/public-surface-reminder)
+[`socket-wheelhouse`](https://github.com/SocketDev/socket-wheelhouse/tree/main/template/.claude/hooks/public-surface-reminder)
 and are required to be byte-identical across every fleet repo.
 `scripts/sync-scaffolding.mts` flags drift; `--fix` rewrites it.
diff --git a/.claude/hooks/release-workflow-guard/README.md b/.claude/hooks/release-workflow-guard/README.md
@@ -102,6 +102,6 @@ a wrong fire is irreversible; prime when it's recoverable.
 ## Cross-fleet sync
 
 This README and the hook itself live in
-[`socket-repo-template`](https://github.com/SocketDev/socket-repo-template/tree/main/template/.claude/hooks/release-workflow-guard)
+[`socket-wheelhouse`](https://github.com/SocketDev/socket-wheelhouse/tree/main/template/.claude/hooks/release-workflow-guard)
 and are required to be byte-identical across every fleet repo.
 `scripts/sync-scaffolding.mts` flags drift; `--fix` rewrites it.
diff --git a/.claude/hooks/setup-security-tools/README.md b/.claude/hooks/setup-security-tools/README.md
@@ -142,6 +142,6 @@ the shim under `~/.socket/sfw/shims/`, not the real binary.
 ## Cross-fleet sync
 
 This README and the hook itself live in
-[`socket-repo-template`](https://github.com/SocketDev/socket-repo-template/tree/main/template/.claude/hooks/setup-security-tools)
+[`socket-wheelhouse`](https://github.com/SocketDev/socket-wheelhouse/tree/main/template/.claude/hooks/setup-security-tools)
 and are required to be byte-identical across every fleet repo.
 `scripts/sync-scaffolding.mts` flags drift; `--fix` rewrites it.
diff --git a/.claude/hooks/stale-process-sweeper/README.md b/.claude/hooks/stale-process-sweeper/README.md
@@ -89,6 +89,6 @@ node --test test/*.test.mts
 ## Cross-fleet sync
 
 This README and the hook itself live in
-[`socket-repo-template`](https://github.com/SocketDev/socket-repo-template/tree/main/template/.claude/hooks/stale-process-sweeper)
+[`socket-wheelhouse`](https://github.com/SocketDev/socket-wheelhouse/tree/main/template/.claude/hooks/stale-process-sweeper)
 and are required to be byte-identical across every fleet repo.
 `scripts/sync-scaffolding.mts` flags drift; `--fix` rewrites it.
diff --git a/.claude/hooks/token-guard/README.md b/.claude/hooks/token-guard/README.md
@@ -79,7 +79,7 @@ negative test in `test/token-guard.test.mts`.
 ## Cross-fleet sync
 
 This README and the hook itself live in
-[`socket-repo-template`](https://github.com/SocketDev/socket-repo-template/tree/main/template/.claude/hooks/token-guard)
+[`socket-wheelhouse`](https://github.com/SocketDev/socket-wheelhouse/tree/main/template/.claude/hooks/token-guard)
 and are required to be byte-identical across every fleet repo.
 `scripts/sync-scaffolding.mts` flags drift; `--fix` rewrites it.
 
diff --git a/.claude/hooks/token-hygiene/README.md b/.claude/hooks/token-hygiene/README.md
@@ -48,7 +48,7 @@ Adding new token-shape detections: update `LITERAL_TOKEN_PATTERNS` in `index.mts
 
 ## Updating across the fleet
 
-This file is in `IDENTICAL_FILES` in `scripts/sync-scaffolding.mjs`. After editing, run from `socket-repo-template`:
+This file is in `IDENTICAL_FILES` in `scripts/sync-scaffolding.mjs`. After editing, run from `socket-wheelhouse`:
 
 ```bash
 node scripts/sync-scaffolding.mjs --all --fix
diff --git a/.claude/skills/_shared/path-guard-rule.md b/.claude/skills/_shared/path-guard-rule.md
@@ -1,6 +1,6 @@
 <!--
 Shared snippet — the canonical "1 path, 1 reference" rule text.
-Synced byte-identical across the Socket fleet via socket-repo-template's
+Synced byte-identical across the Socket fleet via socket-wheelhouse's
 sync-scaffolding.mts (SHARED_SKILL_FILES).
 
 This file is the source of truth for the rule's wording. Three artifacts
@@ -11,7 +11,7 @@ embed (or paraphrase) it:
   3. .claude/skills/guarding-paths/SKILL.md — what the skill enforces.
 
 If the wording changes here, re-run `node scripts/sync-scaffolding.mts
---all --fix` from socket-repo-template to propagate.
+--all --fix` from socket-wheelhouse to propagate.
 -->
 
 ## 1 path, 1 reference
diff --git a/.claude/skills/_shared/skill-authoring.md b/.claude/skills/_shared/skill-authoring.md
@@ -89,7 +89,7 @@ The Anthropic docs codify several rules; honor them:
 
 ## Fleet repo references
 
-When scaffolding a new fleet repo, or when a sync question arises ("how does the fleet do X?"), mimic the reference that matches both axes (`layout` + `native`) in `.config/socket-repo-template.json`:
+When scaffolding a new fleet repo, or when a sync question arises ("how does the fleet do X?"), mimic the reference that matches both axes (`layout` + `native`) in `.config/socket-wheelhouse.json`:
 
 | layout × native | Best reference | Notes |
 |---|---|---|
diff --git a/.claude/skills/driving-cursor-bugbot/SKILL.md b/.claude/skills/driving-cursor-bugbot/SKILL.md
@@ -36,7 +36,7 @@ This skill makes all of the above mechanical.
 |---|---|---|
 | 1 | Inventory | List Bugbot findings via `gh api .../pulls/<PR#>/comments`. Capture `id`, `path`, `line`, body. |
 | 2 | Classify | Sort each finding into `real` / `already-fixed` / `false-positive` / `wont-fix`. |
-| 3 | Fix | Implement fixes for `real` findings. Propagate to canonical (`socket-repo-template/template/`) when the file is fleet-shared. One commit per finding. |
+| 3 | Fix | Implement fixes for `real` findings. Propagate to canonical (`socket-wheelhouse/template/`) when the file is fleet-shared. One commit per finding. |
 | 4 | Reply + resolve | Reply on each inline thread (NOT detached); resolve on `fixed` / `already-fixed` / `false-positive`; leave `wont-fix` open. |
 | 5 | Title + body realignment | Per CLAUDE.md, update PR title / body when scope shifted. Use `gh pr edit`. |
 | 6 | Push | `git push`. Bugbot re-reviews; loop back to phase 1 if new findings. |
@@ -60,7 +60,7 @@ To check `already-fixed`: read `git log` on the PR branch since the comment's `c
 - **Reply first, resolve second.** Resolving without a written reply leaves future readers blind.
 - **One commit per `real` finding.** Don't bundle. Conventional Commits: `fix(<scope>): address Bugbot finding on <file>:<line>`.
 - **Push after each fix; reply with the new commit SHA.** The reply cites the SHA, so the SHA must already be pushed.
-- **Propagate canonical fixes.** When the file lives under `.claude/hooks/`, `.claude/skills/`, or `.git-hooks/`, fix at `socket-repo-template/template/` first, then sync to consumers — drifting fleet copies is the larger bug.
+- **Propagate canonical fixes.** When the file lives under `.claude/hooks/`, `.claude/skills/`, or `.git-hooks/`, fix at `socket-wheelhouse/template/` first, then sync to consumers — drifting fleet copies is the larger bug.
 
 ## When to use
 
diff --git a/.claude/skills/driving-cursor-bugbot/reference.md b/.claude/skills/driving-cursor-bugbot/reference.md
@@ -76,7 +76,7 @@ mutation($threadId: ID!) {
 Keep replies short. Bugbot doesn't read them, but the human reviewer does.
 
 - **Real, fixed**: `Fixed in <commit-sha>. <one-sentence what changed>. <propagation note if any>.`
-  - Example: `Fixed in a63d29105. Restored the Linear team-key + linear.app URL blocking from the deleted .sh hook as scanLinearRefs() in _helpers.mts. Synced from canonical socket-repo-template.`
+  - Example: `Fixed in a63d29105. Restored the Linear team-key + linear.app URL blocking from the deleted .sh hook as scanLinearRefs() in _helpers.mts. Synced from canonical socket-wheelhouse.`
 
 - **Already fixed**: `Already fixed in <commit-sha> (current PR HEAD). <one-sentence what changed>.`
 
diff --git a/.config/rolldown/lib-stub.mts b/.config/rolldown/lib-stub.mts
@@ -16,7 +16,7 @@
  *
  * Source: lifted from socket-packageurl-js's inline plugin
  * (.config/rolldown.config.mts), generalized so the stub-pattern is
- * caller-provided. Fleet-canonical via socket-repo-template.
+ * caller-provided. Fleet-canonical via socket-wheelhouse.
  */
 
 import type { Plugin } from 'rolldown'
diff --git a/.config/socket-wheelhouse-schema.json b/.config/socket-wheelhouse-schema.json
@@ -1,13 +1,13 @@
 {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "$id": "https://github.com/SocketDev/socket-repo-template-schema.json",
-  "title": "socket-repo-template per-repo config",
-  "description": "Per-repo socket-repo-template config. Two valid locations: `.config/socket-repo-template.json` (primary) or `.socket-repo-template.json` at the repo root (alternative). Both are first-class — pick the location that fits your repo's convention.",
+  "$id": "https://github.com/SocketDev/socket-wheelhouse-schema.json",
+  "title": "socket-wheelhouse per-repo config",
+  "description": "Per-repo socket-wheelhouse config. Two valid locations: `.config/socket-wheelhouse.json` (primary) or `.socket-wheelhouse.json` at the repo root (alternative). Both are first-class — pick the location that fits your repo's convention.",
   "type": "object",
   "required": ["schemaVersion", "repoName", "layout", "native"],
   "properties": {
     "$schema": {
-      "description": "JSON Schema reference for editor autocompletion. Conventionally `./socket-repo-template-schema.json` — both the config and its schema live side-by-side in `.config/`.",
+      "description": "JSON Schema reference for editor autocompletion. Conventionally `./socket-wheelhouse-schema.json` — both the config and its schema live side-by-side in `.config/`.",
       "type": "string"
     },
     "schemaVersion": {
diff --git a/.config/socket-wheelhouse.json b/.config/socket-wheelhouse.json
@@ -1,5 +1,5 @@
 {
-  "$schema": "./socket-repo-template-schema.json",
+  "$schema": "./socket-wheelhouse-schema.json",
   "schemaVersion": 1,
   "repoName": "socket-cli",
   "layout": "monorepo",
diff --git a/.git-hooks/_helpers.mts b/.git-hooks/_helpers.mts
@@ -506,7 +506,7 @@ const FLEET_REPO_NAMES = [
   'socket-lib',
   'socket-packageurl-js',
   'socket-registry',
-  'socket-repo-template',
+  'socket-wheelhouse',
   'socket-sdk-js',
   'socket-sdxgen',
   'socket-stuie',
diff --git a/CLAUDE.md b/CLAUDE.md
@@ -2,7 +2,7 @@
 
 **MANDATORY**: Act as principal-level engineer. Follow these guidelines exactly.
 
-<!-- BEGIN FLEET-CANONICAL — sync via socket-repo-template/scripts/sync-scaffolding.mts. Do not edit downstream. -->
+<!-- BEGIN FLEET-CANONICAL — sync via socket-wheelhouse/scripts/sync-scaffolding.mts. Do not edit downstream. -->
 
 ## 📚 Fleet Standards
 
@@ -171,7 +171,7 @@ How to check:
 
 1. If you're editing one of these in repo A, grep the same thing in repos B/C/D. If A is older, bump A first; if A is newer, plan a sync to B/C/D.
 2. `socket-registry`'s `setup-and-install` action is the canonical source for tool SHAs. Diverging from it is drift.
-3. `socket-repo-template`'s `template/` tree is the canonical source for `.claude/`, CLAUDE.md fleet block, and hook code. Diverging is drift.
+3. `socket-wheelhouse`'s `template/` tree is the canonical source for `.claude/`, CLAUDE.md fleet block, and hook code. Diverging is drift.
 4. Run `pnpm run sync-scaffolding` (in repos that have it) to surface drift programmatically.
 
 Never silently let drift sit. Either reconcile in the same PR or open a follow-up PR titled `chore(sync): cascade <thing> from <newer-repo>` and link it.
@@ -287,19 +287,19 @@ Full hook spec in [`.claude/hooks/token-guard/README.md`](.claude/hooks/token-gu
 
 Every skill under `.claude/skills/` falls into one of three tiers — surface this distinction when adding a new skill so it lands in the right place:
 
-- **Fleet skill** — present in every fleet repo, identical contract everywhere. Examples: `guarding-paths`, `scanning-quality`, `scanning-security`, `updating`, `locking-down-programmatic-claude`, `plug-leaking-promise-race`. New fleet skills land in `socket-repo-template/template/.claude/skills/<name>/` and cascade via `node socket-repo-template/scripts/sync-scaffolding.mts --all --fix`. Track them in `SHARED_SKILL_FILES` in the sync manifest.
+- **Fleet skill** — present in every fleet repo, identical contract everywhere. Examples: `guarding-paths`, `scanning-quality`, `scanning-security`, `updating`, `locking-down-programmatic-claude`, `plug-leaking-promise-race`. New fleet skills land in `socket-wheelhouse/template/.claude/skills/<name>/` and cascade via `node socket-wheelhouse/scripts/sync-scaffolding.mts --all --fix`. Track them in `SHARED_SKILL_FILES` in the sync manifest.
 - **Partial skill** — present in the subset of repos that need it, identical contract within that subset. Examples: `driving-cursor-bugbot` (every repo with PR review), `updating-lockstep` (every repo with `lockstep.json`), `squashing-history` (repos with the squash workflow). Live in each adopting repo's `.claude/skills/<name>/`. When you change one, propagate to the others.
 - **Unique skill** — one repo only, bespoke to that repo's domain. Examples: `updating-cdxgen` (sdxgen), `updating-yoga` (socket-btm), `release` (socket-registry). Never canonical-tracked; the host repo owns it end-to-end.
 
-Audit the current classification with `node socket-repo-template/scripts/run-skill-fleet.mts --list-skills`.
+Audit the current classification with `node socket-wheelhouse/scripts/run-skill-fleet.mts --list-skills`.
 
 #### `updating` umbrella + `updating-*` siblings
 
 `updating` is the canonical fleet umbrella that runs `pnpm run update` then discovers and runs every `updating-*` sibling skill the host repo registers. The umbrella is fleet-shared; the siblings are per-repo (or partial — e.g. `updating-lockstep` lives in every repo with `lockstep.json`). To add a new repo-specific update step, drop a new `.claude/skills/updating-<domain>/SKILL.md` and the umbrella picks it up automatically — no edits to `updating` itself.
 
 #### Running skills across the fleet
 
-`scripts/run-skill-fleet.mts` (in `socket-repo-template`) spawns one headless `claude --print` agent per fleet repo, in parallel (concurrency 4 by default), with the four lockdown flags set per the _Programmatic Claude calls_ rule above. Per-skill profile table maps known skills to sensible tool/allow/disallow lists; override with `--tools` / `--allow` / `--disallow`. Per-repo logs land in `.cache/fleet-skill/<timestamp>-<skill>/<repo>.log`. Use `Promise.allSettled` semantics — one repo's failure doesn't abort the rest.
+`scripts/run-skill-fleet.mts` (in `socket-wheelhouse`) spawns one headless `claude --print` agent per fleet repo, in parallel (concurrency 4 by default), with the four lockdown flags set per the _Programmatic Claude calls_ rule above. Per-skill profile table maps known skills to sensible tool/allow/disallow lists; override with `--tools` / `--allow` / `--disallow`. Per-repo logs land in `.cache/fleet-skill/<timestamp>-<skill>/<repo>.log`. Use `Promise.allSettled` semantics — one repo's failure doesn't abort the rest.
 
 ```bash
 pnpm run fleet-skill updating                       # update every fleet repo
diff --git a/docs/references/bypass-phrases.md b/docs/references/bypass-phrases.md
@@ -46,4 +46,4 @@ When introducing a new destructive flag or hook bypass:
 1. Add a new entry to the `CHECKS` array in `.claude/hooks/no-revert-guard/index.mts`. Each check is `{ pattern: RegExp, bypassPhrase: string, label: string }`.
 2. Add a row to this reference's table.
 3. Add a test case to `.claude/hooks/no-revert-guard/test/index.test.mts` covering both the blocked-without-phrase and allowed-with-phrase paths.
-4. Cascade via `node socket-repo-template/scripts/sync-scaffolding.mts --all --fix` so every fleet repo picks up the change.
+4. Cascade via `node socket-wheelhouse/scripts/sync-scaffolding.mts --all --fix` so every fleet repo picks up the change.
diff --git a/packages/build-infra/release-assets.schema.json b/packages/build-infra/release-assets.schema.json
@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "$id": "https://raw.githubusercontent.com/SocketDev/socket-repo-template/main/template/packages/build-infra/release-assets.schema.json",
+  "$id": "https://raw.githubusercontent.com/SocketDev/socket-wheelhouse/main/template/packages/build-infra/release-assets.schema.json",
   "title": "Release Assets Manifest",
   "description": "Embedded SHA-256 manifest for release artifacts. One block per tool: identifies the upstream release tag and the SHA-256 of every asset that release published. Consumers verify downloads against these hashes before installing or republishing. Producers (e.g. socket-btm) update this file when cutting a new release.",
   "type": "object",
diff --git a/scripts/lockstep-schema.mts b/scripts/lockstep-schema.mts
diff --git a/scripts/lockstep.mts b/scripts/lockstep.mts
diff --git a/scripts/power-state.mts b/scripts/power-state.mts
diff --git a/scripts/socket-wheelhouse-emit-schema.mts b/scripts/socket-wheelhouse-emit-schema.mts
diff --git a/scripts/socket-wheelhouse-schema.mts b/scripts/socket-wheelhouse-schema.mts
