chore: repoint run402 private-repo references to ~/Developer/run402-private

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

Author: MajorTal

.claude/commands/publish.md

@@ -36,7 +36,7 @@ Stage all three files and commit: `git add package.json cli/package.json package
 2. Create a git tag: `git tag v<new_version> && git push --tags`
 3. Create a GitHub release from the tag. Write a human-readable summary of the actual changes (features, fixes, improvements) — don't just list commit hashes or rely on `--generate-notes`. Use `gh release create v<new_version> --notes "..."` with a clear description.
 4. **Close linked GitHub issues.** If any commit in the release references a GitHub issue (e.g. `Fixes #20`, `Closes #42`), verify the issue is closed. If not, close it with `gh issue close <number> --reason completed`.
-5. **Update `llms-cli.txt` in the run402 repo.** The CLI documentation lives in a separate repo at `~/dev/run402/site/llms-cli.txt`. If any CLI commands, manifest fields, or user-facing behavior changed since the last release, update that file to match, then commit and push the run402 repo.
+5. **Update `llms-cli.txt` in the run402 repo.** The CLI documentation lives in a separate repo at `~/Developer/run402-private/site/llms-cli.txt`. If any CLI commands, manifest fields, or user-facing behavior changed since the last release, update that file to match, then commit and push the run402 repo.
 6. **Install the new version locally** so `run402` on the command line uses the just-published version:
    ```
    npm install -g run402@<new_version>

.claude/commands/upgrade-run402.md

@@ -7,7 +7,7 @@ Read the memory file `project_last_integration.md` to get the last known sync co
 ## Step 2: Gather new commits from run402
 
 ```bash
-cd ~/dev/run402 && git log --oneline --format="%h %ai %s" <last_synced_commit>..HEAD
+cd ~/Developer/run402-private && git log --oneline --format="%h %ai %s" <last_synced_commit>..HEAD
 ```
 
 If the last synced commit is missing (rebased/squashed), use `--since` with the sync date instead.
@@ -35,8 +35,8 @@ Focus on commits that touch `packages/gateway/src/routes/`, `packages/gateway/sr
 For each commit classified as "Yes" or "Maybe":
 
 ```bash
-cd ~/dev/run402 && git show --stat <commit>
-cd ~/dev/run402 && git show <commit> -- <relevant_files>
+cd ~/Developer/run402-private && git show --stat <commit>
+cd ~/Developer/run402-private && git show <commit> -- <relevant_files>
 ```
 
 Determine specifically:

CLAUDE.md

@@ -44,7 +44,7 @@ Tests are excluded from the build (`tsconfig.json` and `core/tsconfig.json` both
 - CLI commands in `cli/lib/*.mjs` match the expected set
 - OpenClaw commands in `openclaw/scripts/*.mjs` match the expected set (follows re-exports to CLI)
 - CLI and OpenClaw have identical command sets (parity)
-- If `~/dev/run402/site/llms.txt` exists: MCP Tools table lists all tools, all endpoints documented
+- If `~/Developer/run402-private/site/llms.txt` exists: MCP Tools table lists all tools, all endpoints documented
 
 When adding a new tool/command, add it to the `SURFACE` array in `sync.test.ts`.
 

cli-integration.test.ts

@@ -78,8 +78,7 @@ before(async () => {
     const { dirname } = await import("node:path");
     const thisDir = dirname(fileURLToPath(import.meta.url));
     const searchPaths = [
-      join(thisDir, "..", "run402", ".env"),       // ~/Developer/run402/.env
-      join(thisDir, "..", "..", "dev", "run402", ".env"), // ~/dev/run402/.env
+      join(thisDir, "..", "run402-private", ".env"), // ~/Developer/run402-private/.env
     ];
     for (const envPath of searchPaths) {
       try {

mcp-integration.test.ts

@@ -15,7 +15,7 @@
  *   - Cleanup: delete function, delete project
  *
  * Prerequisites:
- *   - Set BUYER_PRIVATE_KEY env var (or have it in ../run402/.env or ~/dev/run402/.env).
+ *   - Set BUYER_PRIVATE_KEY env var (or have it in ~/Developer/run402-private/.env).
  *     This is an EVM private key with testnet USDC on Base Sepolia.
  *
  * Run:

openspec/specs/project-email/spec.md

@@ -126,7 +126,7 @@ The CLI `email` module SHALL include a HELP string matching the existing module
 - **THEN** the system prints the full help text and exits with code 0
 
 ### Requirement: llms-cli.txt documentation
-The `~/dev/run402/site/llms-cli.txt` file SHALL include an `### email` section in the Command Reference area documenting all email subcommands with their arguments, matching the existing format.
+The `~/Developer/run402-private/site/llms-cli.txt` file SHALL include an `### email` section in the Command Reference area documenting all email subcommands with their arguments, matching the existing format.
 
 #### Scenario: Email commands documented in llms-cli.txt
 - **WHEN** the llms-cli.txt file is read

sync.test.ts

@@ -437,10 +437,10 @@ describe("SURFACE consistency", () => {
 
 // ─── llms.txt alignment (conditional — only if the main repo is available) ───
 
-const LLMS_TXT_PATH = join(homedir(), "dev/run402/site/llms.txt");
+const LLMS_TXT_PATH = join(homedir(), "Developer/run402-private/site/llms.txt");
 const llmsTxtAvailable = existsSync(LLMS_TXT_PATH);
 
-describe("llms.txt alignment", { skip: !llmsTxtAvailable && "~/dev/run402/site/llms.txt not found" }, () => {
+describe("llms.txt alignment", { skip: !llmsTxtAvailable && "~/Developer/run402-private/site/llms.txt not found" }, () => {
   const llmsTxt = llmsTxtAvailable ? readFileSync(LLMS_TXT_PATH, "utf-8") : "";
 
   it("MCP Tools table lists all actual MCP tools", { skip: !llmsTxt.includes("### MCP Tools") && "llms.txt has no MCP Tools table" }, () => {