fix: update remaining stale repo and scope refs to singularity-forge

After fixing forensics.md and error-classifier.ts last fire, swept the
rest of the tree for the same class of stale reference:

- scripts/validate-pack.js: criticalPackages list used \`@sf\` and
  \`@sf-build\` scopes — neither exists in node_modules; this is in CI
  (.github/workflows/ci.yml) + prepublishOnly, so the validation step
  was failing to find anything. Now \`@singularity-forge/pi-coding-agent\`
  and \`@singularity-forge/rpc-client\` (the actual scope).
- src/resources/skills/github-workflows/references/gh/SKILL.md: same
  GraphQL bug as forensics.md — owner:"sf-build" name:"sf-2" — and
  three \`gh project\` commands using owner sf-build. The gh issue
  create command above already used singularity-forge/sf-run, so the
  follow-up calls always failed. Also retitled "sf-2 Backlog" to
  "sf-run Backlog".
- src/resources/extensions/sf/bootstrap/system-context.ts: deprecation
  warning linked to https://github.com/sf-build/SF/issues/1492.
- packages/mcp-server/README.md, packages/rpc-client/README.md: 9 refs
  to \`@sf-build/...\` for installable package names — would mislead
  anyone copy-pasting into npm install.
- docs/user-docs/troubleshooting.md (+ zh-CN): GitHub Issues link
  pointed at github.com/sf-build/SF/issues.
- docs/user-docs/getting-started.md (+ zh-CN): clone URL was correct
  but the next \`cd\` was \`cd sf-2/docker\` — won't exist after a
  fresh clone of sf-run.
- docs/dev/ci-cd-pipeline.md: GHCR org was \`sf-build\`.

Code comments containing "sf-2" / "sf-build" in non-active places
(parsers.ts banner, error message URLs in tests, dev-doc absolute
paths from a contributor's Mac) left alone — they're informational
and not addressed by users or runtime.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

docs/dev/ci-cd-pipeline.md

@@ -147,7 +147,7 @@ For `@dev` or `@next` rollbacks, the next successful merge will overwrite the ta
 | Secret: `ANTHROPIC_API_KEY` | Prod environment only |
 | Secret: `OPENAI_API_KEY` | Prod environment only |
 | Variable: `RUN_LIVE_TESTS` | `false` (set to `true` to enable live LLM tests) |
-| GHCR | Enabled for the `sf-build` org |
+| GHCR | Enabled for the `singularity-forge` org |
 
 ### Docker Images
 

docs/user-docs/getting-started.md

@@ -280,7 +280,7 @@ Run SF in an isolated sandbox without installing Node.js on your host.
 
 ```bash
 git clone https://github.com/singularity-forge/sf-run.git
-cd sf-2/docker
+cd sf-run/docker
 ```
 
 **Step 3 — Create and enter a sandbox:**

docs/user-docs/troubleshooting.md

@@ -307,7 +307,7 @@ Doctor rebuilds `STATE.md` from plan and roadmap files on disk and fixes detecte
 
 ## Getting Help
 
-- **GitHub Issues:** [github.com/sf-build/SF/issues](https://github.com/sf-build/SF/issues)
+- **GitHub Issues:** [github.com/singularity-forge/sf-run/issues](https://github.com/singularity-forge/sf-run/issues)
 - **Dashboard:** `Ctrl+Alt+G` or `/sf status` for real-time diagnostics
 - **Forensics:** `/sf forensics` for structured post-mortem analysis of auto-mode failures
 - **Session logs:** `.sf/activity/` contains JSONL session dumps for crash forensics

docs/zh-CN/user-docs/getting-started.md

@@ -280,7 +280,7 @@ sf --version     # 输出已安装版本
 
 ```bash
 git clone https://github.com/singularity-forge/sf-run.git
-cd sf-2/docker
+cd sf-run/docker
 ```
 
 **第 3 步：创建并进入沙箱：**

docs/zh-CN/user-docs/troubleshooting.md

@@ -324,7 +324,7 @@ Doctor 会从磁盘上的 plan 和 roadmap 文件重建 `STATE.md`，并修复
 
 ## 获取帮助
 
-- **GitHub Issues：** [github.com/sf-build/SF/issues](https://github.com/sf-build/SF/issues)
+- **GitHub Issues：** [github.com/singularity-forge/sf-run/issues](https://github.com/singularity-forge/sf-run/issues)
 - **Dashboard：** `Ctrl+Alt+G` 或 `/sf status`，查看实时诊断信息
 - **Forensics：** `/sf forensics`，用于对自动模式失败做结构化事后分析
 - **Session logs：** `.sf/activity/` 中包含用于崩溃取证的 JSONL 会话转储

packages/mcp-server/README.md

@@ -1,4 +1,4 @@
-# @sf-build/mcp-server
+# @singularity-forge/mcp-server
 
 MCP server exposing SF orchestration tools for Claude Code, Cursor, and other MCP-compatible clients.
 
@@ -13,7 +13,7 @@ This package now exposes two tool surfaces:
 ## Installation
 
 ```bash
-npm install @sf-build/mcp-server
+npm install @singularity-forge/mcp-server
 ```
 
 Or with the monorepo workspace:
@@ -238,12 +238,12 @@ The server also hydrates supported model-provider and tool credentials from `~/.
 
 ```
 ┌─────────────────┐     stdio      ┌──────────────────┐
-│  MCP Client     │ ◄────────────► │  @sf-build/mcp-server │
+│  MCP Client     │ ◄────────────► │  @singularity-forge/mcp-server │
 │  (Claude Code,  │    JSON-RPC    │                  │
 │   Cursor, etc.) │                │  SessionManager  │
 └─────────────────┘                │       │          │
                                    │       ▼          │
-                                   │  @sf-build/rpc-client │
+                                   │  @singularity-forge/rpc-client │
                                    │       │          │
                                    │       ▼          │
                                    │  SF CLI (child  │
@@ -251,9 +251,9 @@ The server also hydrates supported model-provider and tool credentials from `~/.
                                    └──────────────────┘
 ```
 
-- **@sf-build/mcp-server** — MCP protocol adapter. Translates MCP tool calls into SessionManager operations.
+- **@singularity-forge/mcp-server** — MCP protocol adapter. Translates MCP tool calls into SessionManager operations.
 - **SessionManager** — Manages RpcClient lifecycle. One session per project directory. Tracks events in a ring buffer (last 50), detects blockers, accumulates cost.
-- **@sf-build/rpc-client** — Low-level RPC client that spawns and communicates with the SF CLI process via JSON-RPC over stdio.
+- **@singularity-forge/rpc-client** — Low-level RPC client that spawns and communicates with the SF CLI process via JSON-RPC over stdio.
 
 ## License
 

packages/rpc-client/README.md

@@ -1,4 +1,4 @@
-# @sf-build/rpc-client
+# @singularity-forge/rpc-client
 
 Standalone RPC client SDK for SF. Spawn the agent process, perform a v2 protocol handshake, send commands, and consume typed events via an async generator — all in a few lines of TypeScript.
 
@@ -7,13 +7,13 @@ Zero internal dependencies. Ships its own inlined types.
 ## Installation
 
 ```bash
-npm install @sf-build/rpc-client
+npm install @singularity-forge/rpc-client
 ```
 
 ## Quick Start
 
 ```typescript
-import { RpcClient } from '@sf-build/rpc-client';
+import { RpcClient } from '@singularity-forge/rpc-client';
 
 const client = new RpcClient({ cwd: process.cwd() });
 await client.start();
@@ -117,7 +117,7 @@ import type {
   SessionStats,
   SdkAgentEvent,
   RpcClientOptions,
-} from '@sf-build/rpc-client';
+} from '@singularity-forge/rpc-client';
 ```
 
 ## License

scripts/validate-pack.js

@@ -149,8 +149,8 @@ try {
   console.log('==> Verifying @singularity-forge/* workspace package resolution...');
   const installedRoot = join(installDir, 'node_modules', 'sf-run');
   const criticalPackages = [
-    { scope: '@sf', name: 'pi-coding-agent' },
-    { scope: '@sf-build', name: 'rpc-client' },
+    { scope: '@singularity-forge', name: 'pi-coding-agent' },
+    { scope: '@singularity-forge', name: 'rpc-client' },
   ];
   let resolutionFailed = false;
   for (const pkg of criticalPackages) {

src/resources/extensions/sf/bootstrap/system-context.ts

@@ -142,7 +142,7 @@ function warnDeprecatedAgentInstructions(): void {
 			console.warn(
 				`[SF] DEPRECATED: ${path} is no longer loaded. ` +
 					`Migrate your instructions to AGENTS.md (or CLAUDE.md) in the same directory. ` +
-					`See https://github.com/sf-build/SF/issues/1492`,
+					`See https://github.com/singularity-forge/sf-run/issues/1492`,
 			);
 		}
 	}

src/resources/skills/github-workflows/references/gh/SKILL.md

@@ -134,8 +134,8 @@ ISSUE_URL=$(gh issue create -R singularity-forge/sf-run \
 
 # Step 2: Set the issue type via GraphQL
 ISSUE_NUM=$(echo "$ISSUE_URL" | grep -oE '[0-9]+$')
-ISSUE_ID=$(gh api graphql -f query='{ repository(owner:"sf-build",name:"sf-2") { issue(number:'"$ISSUE_NUM"') { id } } }' --jq '.data.repository.issue.id')
-TYPE_ID=$(gh api graphql -f query='{ repository(owner:"sf-build",name:"sf-2") { issueTypes(first:20) { nodes { id name } } } }' --jq '.data.repository.issueTypes.nodes[] | select(.name=="Bug") | .id')
+ISSUE_ID=$(gh api graphql -f query='{ repository(owner:"singularity-forge",name:"sf-run") { issue(number:'"$ISSUE_NUM"') { id } } }' --jq '.data.repository.issue.id')
+TYPE_ID=$(gh api graphql -f query='{ repository(owner:"singularity-forge",name:"sf-run") { issueTypes(first:20) { nodes { id name } } } }' --jq '.data.repository.issueTypes.nodes[] | select(.name=="Bug") | .id')
 gh api graphql -f query='mutation { updateIssue(input:{id:"'"$ISSUE_ID"'",issueTypeId:"'"$TYPE_ID"'"}) { issue { number } } }'
 ```
 
@@ -158,13 +158,13 @@ See [labels.md](./references/labels.md) for the full taxonomy and color codes.
 
 ```bash
 # List projects
-gh project list --owner sf-build
+gh project list --owner singularity-forge
 
 # Create project
-gh project create --owner sf-build --title "sf-2 Backlog"
+gh project create --owner singularity-forge --title "sf-run Backlog"
 
 # Add issue to project
-gh project item-add 1 --owner sf-build \
+gh project item-add 1 --owner singularity-forge \
   --url https://github.com/singularity-forge/sf-run/issues/42
 ```