thevoidforge-methodology 23.5.4 → 23.6.0

package/.claude/agents/silver-surfer-herald.md

@@ -0,0 +1,41 @@
+---
+name: Silver Surfer
+description: Herald pre-scan dispatch — reads codebase context and selects optimal agent roster via Haiku
+model: haiku
+tools:
+  - Read
+  - Grep
+  - Glob
+  - Bash
+tags: [dispatch, herald, roster-selection, pre-scan]
+---
+
+# Silver Surfer — The Herald
+
+**"All that you know is at an end."**
+
+You are the Silver Surfer, Herald of Galactus. You scout ahead — reading the codebase, the command, and the user's intent — then summon the right agents for the mission. You don't fight; you select who fights. Your cosmic speed means you complete your scan in under 2 seconds for less than a fraction of a cent.
+
+You are the bridge between the user's command and the full agent roster. Without you, every command deploys the same generic team. With you, every command gets a team tailored to the codebase.
+
+## How You Work
+
+1. Read the codebase file tree (top 80 files)
+2. Read the PRD frontmatter (if exists)
+3. Read the git diff summary (if uncommitted changes)
+4. Read all 264 agent descriptions from the registry
+5. Select every agent whose expertise is relevant to this codebase + this command
+6. Output a JSON roster: `{ "roster": [...], "reasoning": "...", "estimatedAgents": N }`
+
+## Operating Rules
+
+- **Over-include, never under-include.** A false positive costs one sub-agent launch. A false negative costs a missed finding that requires another user prompt.
+- **Bias toward the user's `--focus` topic** but don't exclude unrelated agents — cross-domain insights are the whole point.
+- **Never remove the command's lead agents.** You add specialists; leads are non-negotiable.
+- **If you can't run (no API key, timeout, error), return empty roster.** The command falls back to its hardcoded manifest. You are additive, never blocking.
+
+## Required Context
+
+- CLI entry: `npx thevoidforge herald --command /<name> --focus "<topic>" --json`
+- Library: `packages/voidforge/wizard/lib/herald.ts`
+- Registry: `packages/voidforge/wizard/lib/agent-registry.ts`

package/.claude/commands/ai.md

@@ -15,20 +15,18 @@ Opus scans `git diff --stat` and matches changed files against the `description`
 
 **Dispatch control:** `--light` skips dynamic dispatch (core only). `--solo` runs lead agent only.
 
-## Herald Pre-Scan (ADR-047)
+## Silver Surfer Pre-Scan (ADR-048)
 
-Before agent deployment, run the Herald to select the optimal roster:
+Before agent deployment, the Silver Surfer selects the optimal roster:
 
-1. Call `gatherHeraldContext('/ai', '$ARGUMENTS', '<focus-if-provided>')` to collect codebase context
-2. Call `loadAgentRegistry()` to get all 263 agent definitions
-3. Call `runHerald(context, registry)` to get the optimal roster
-4. Merge Herald's roster with this command's hardcoded lead agents (Herald adds, never removes leads)
-5. Deploy the merged roster per the command's normal parallel/sequential protocol
+Run: `npx thevoidforge herald --command /ai --json`
+(Add `--focus "<topic>"` if the user provided `--focus`)
 
-**`--focus "topic"`** biases the Herald toward agents matching the topic. Examples: `--focus "security"`, `--focus "financial accuracy"`, `--focus "mobile UX"`.
+Parse the JSON output. The `roster` array contains agent IDs to deploy alongside this command's lead agents. If the command fails or returns an empty roster, use the hardcoded manifest below.
 
-**`--light`** skips the Herald entirely — uses only the command's hardcoded core roster.
-**`--solo`** skips both Herald and all sub-agents — lead agent only.
+**`--focus "topic"`** biases the Surfer toward agents matching the topic.
+**`--light`** skips the Surfer — uses only hardcoded core roster.
+**`--solo`** skips Surfer and all sub-agents — lead only.
 
 ## Phase 0 — AI Surface Map (`subagent_type: Seldon`)
 

package/.claude/commands/architect.md

@@ -10,20 +10,18 @@ Opus scans `git diff --stat` and matches changed files against the `description`
 
 **Promoted agent:** **Riker** `subagent_type: Riker` runs on every ADR written — challenges trade-offs.
 
-## Herald Pre-Scan (ADR-047)
+## Silver Surfer Pre-Scan (ADR-048)
 
-Before agent deployment, run the Herald to select the optimal roster:
+Before agent deployment, the Silver Surfer selects the optimal roster:
 
-1. Call `gatherHeraldContext('/architect', '$ARGUMENTS', '<focus-if-provided>')` to collect codebase context
-2. Call `loadAgentRegistry()` to get all 263 agent definitions
-3. Call `runHerald(context, registry)` to get the optimal roster
-4. Merge Herald's roster with this command's hardcoded lead agents (Herald adds, never removes leads)
-5. Deploy the merged roster per the command's normal parallel/sequential protocol
+Run: `npx thevoidforge herald --command /architect --json`
+(Add `--focus "<topic>"` if the user provided `--focus`)
 
-**`--focus "topic"`** biases the Herald toward agents matching the topic. Examples: `--focus "security"`, `--focus "financial accuracy"`, `--focus "mobile UX"`.
+Parse the JSON output. The `roster` array contains agent IDs to deploy alongside this command's lead agents. If the command fails or returns an empty roster, use the hardcoded manifest below.
 
-**`--light`** skips the Herald entirely — uses only the command's hardcoded core roster.
-**`--solo`** skips both Herald and all sub-agents — lead agent only.
+**`--focus "topic"`** biases the Surfer toward agents matching the topic.
+**`--light`** skips the Surfer — uses only hardcoded core roster.
+**`--solo`** skips Surfer and all sub-agents — lead only.
 
 ## Context Setup
 1. Read `/logs/build-state.md` — understand current project state

package/.claude/commands/assemble.md

@@ -13,20 +13,18 @@ Opus scans `git diff --stat` and matches changed files against the `description`
 
 **Dispatch control:** `--light` skips dynamic dispatch (core only). `--solo` runs lead agent only.
 
-## Herald Pre-Scan (ADR-047)
+## Silver Surfer Pre-Scan (ADR-048)
 
-Before agent deployment, run the Herald to select the optimal roster:
+Before agent deployment, the Silver Surfer selects the optimal roster:
 
-1. Call `gatherHeraldContext('/assemble', '$ARGUMENTS', '<focus-if-provided>')` to collect codebase context
-2. Call `loadAgentRegistry()` to get all 263 agent definitions
-3. Call `runHerald(context, registry)` to get the optimal roster
-4. Merge Herald's roster with this command's hardcoded lead agents (Herald adds, never removes leads)
-5. Deploy the merged roster per the command's normal parallel/sequential protocol
+Run: `npx thevoidforge herald --command /assemble --json`
+(Add `--focus "<topic>"` if the user provided `--focus`)
 
-**`--focus "topic"`** biases the Herald toward agents matching the topic. Examples: `--focus "security"`, `--focus "financial accuracy"`, `--focus "mobile UX"`.
+Parse the JSON output. The `roster` array contains agent IDs to deploy alongside this command's lead agents. If the command fails or returns an empty roster, use the hardcoded manifest below.
 
-**`--light`** skips the Herald entirely — uses only the command's hardcoded core roster.
-**`--solo`** skips both Herald and all sub-agents — lead agent only.
+**`--focus "topic"`** biases the Surfer toward agents matching the topic.
+**`--light`** skips the Surfer — uses only hardcoded core roster.
+**`--solo`** skips Surfer and all sub-agents — lead only.
 
 ## Agent Deployment Manifest — The Full Initiative
 

package/.claude/commands/assess.md

@@ -2,20 +2,18 @@
 
 Evaluate an existing codebase before a rebuild, migration, or VoidForge onboarding. Chains architecture review, assessment-mode Gauntlet, and PRD gap analysis into a unified "State of the Codebase" report.
 
-## Herald Pre-Scan (ADR-047)
+## Silver Surfer Pre-Scan (ADR-048)
 
-Before agent deployment, run the Herald to select the optimal roster:
+Before agent deployment, the Silver Surfer selects the optimal roster:
 
-1. Call `gatherHeraldContext('/assess', '$ARGUMENTS', '<focus-if-provided>')` to collect codebase context
-2. Call `loadAgentRegistry()` to get all 263 agent definitions
-3. Call `runHerald(context, registry)` to get the optimal roster
-4. Merge Herald's roster with this command's hardcoded lead agents (Herald adds, never removes leads)
-5. Deploy the merged roster per the command's normal parallel/sequential protocol
+Run: `npx thevoidforge herald --command /assess --json`
+(Add `--focus "<topic>"` if the user provided `--focus`)
 
-**`--focus "topic"`** biases the Herald toward agents matching the topic. Examples: `--focus "security"`, `--focus "financial accuracy"`, `--focus "mobile UX"`.
+Parse the JSON output. The `roster` array contains agent IDs to deploy alongside this command's lead agents. If the command fails or returns an empty roster, use the hardcoded manifest below.
 
-**`--light`** skips the Herald entirely — uses only the command's hardcoded core roster.
-**`--solo`** skips both Herald and all sub-agents — lead agent only.
+**`--focus "topic"`** biases the Surfer toward agents matching the topic.
+**`--light`** skips the Surfer — uses only hardcoded core roster.
+**`--solo`** skips Surfer and all sub-agents — lead only.
 
 ## Context Setup
 1. Read `/logs/build-state.md` if it exists — understand current project state

package/.claude/commands/build.md

@@ -10,20 +10,18 @@ Opus scans `git diff --stat` and matches changed files against the `description`
 - **Troi** `subagent_type: Troi` runs after every build mission completion — catches PRD drift before it compounds.
 - **Riker** `subagent_type: Riker` runs whenever an ADR is written during the build — prevents rubber-stamped decisions.
 
-## Herald Pre-Scan (ADR-047)
+## Silver Surfer Pre-Scan (ADR-048)
 
-Before agent deployment, run the Herald to select the optimal roster:
+Before agent deployment, the Silver Surfer selects the optimal roster:
 
-1. Call `gatherHeraldContext('/build', '$ARGUMENTS', '<focus-if-provided>')` to collect codebase context
-2. Call `loadAgentRegistry()` to get all 263 agent definitions
-3. Call `runHerald(context, registry)` to get the optimal roster
-4. Merge Herald's roster with this command's hardcoded lead agents (Herald adds, never removes leads)
-5. Deploy the merged roster per the command's normal parallel/sequential protocol
+Run: `npx thevoidforge herald --command /build --json`
+(Add `--focus "<topic>"` if the user provided `--focus`)
 
-**`--focus "topic"`** biases the Herald toward agents matching the topic. Examples: `--focus "security"`, `--focus "financial accuracy"`, `--focus "mobile UX"`.
+Parse the JSON output. The `roster` array contains agent IDs to deploy alongside this command's lead agents. If the command fails or returns an empty roster, use the hardcoded manifest below.
 
-**`--light`** skips the Herald entirely — uses only the command's hardcoded core roster.
-**`--solo`** skips both Herald and all sub-agents — lead agent only.
+**`--focus "topic"`** biases the Surfer toward agents matching the topic.
+**`--light`** skips the Surfer — uses only hardcoded core roster.
+**`--solo`** skips Surfer and all sub-agents — lead only.
 
 ## Context Setup
 1. Read `/logs/build-state.md` — if it exists, resume from current phase

package/.claude/commands/campaign.md

@@ -53,20 +53,18 @@ Opus scans `git diff --stat` and matches changed files against the `description`
 
 **Dispatch control:** `--light` skips dynamic dispatch (core only). `--solo` runs lead agent only.
 
-## Herald Pre-Scan (ADR-047)
+## Silver Surfer Pre-Scan (ADR-048)
 
-Before agent deployment, run the Herald to select the optimal roster:
+Before agent deployment, the Silver Surfer selects the optimal roster:
 
-1. Call `gatherHeraldContext('/campaign', '$ARGUMENTS', '<focus-if-provided>')` to collect codebase context
-2. Call `loadAgentRegistry()` to get all 263 agent definitions
-3. Call `runHerald(context, registry)` to get the optimal roster
-4. Merge Herald's roster with this command's hardcoded lead agents (Herald adds, never removes leads)
-5. Deploy the merged roster per the command's normal parallel/sequential protocol
+Run: `npx thevoidforge herald --command /campaign --json`
+(Add `--focus "<topic>"` if the user provided `--focus`)
 
-**`--focus "topic"`** biases the Herald toward agents matching the topic. Examples: `--focus "security"`, `--focus "financial accuracy"`, `--focus "mobile UX"`.
+Parse the JSON output. The `roster` array contains agent IDs to deploy alongside this command's lead agents. If the command fails or returns an empty roster, use the hardcoded manifest below.
 
-**`--light`** skips the Herald entirely — uses only the command's hardcoded core roster.
-**`--solo`** skips both Herald and all sub-agents — lead agent only.
+**`--focus "topic"`** biases the Surfer toward agents matching the topic.
+**`--light`** skips the Surfer — uses only hardcoded core roster.
+**`--solo`** skips Surfer and all sub-agents — lead only.
 
 ## Execution Mode (default)
 

package/.claude/commands/deploy.md

@@ -4,20 +4,18 @@
 
 Read `/docs/methods/DEVOPS_ENGINEER.md` for operating rules (see "Deploy Automation" section).
 
-## Herald Pre-Scan (ADR-047)
+## Silver Surfer Pre-Scan (ADR-048)
 
-Before agent deployment, run the Herald to select the optimal roster:
+Before agent deployment, the Silver Surfer selects the optimal roster:
 
-1. Call `gatherHeraldContext('/deploy', '$ARGUMENTS', '<focus-if-provided>')` to collect codebase context
-2. Call `loadAgentRegistry()` to get all 263 agent definitions
-3. Call `runHerald(context, registry)` to get the optimal roster
-4. Merge Herald's roster with this command's hardcoded lead agents (Herald adds, never removes leads)
-5. Deploy the merged roster per the command's normal parallel/sequential protocol
+Run: `npx thevoidforge herald --command /deploy --json`
+(Add `--focus "<topic>"` if the user provided `--focus`)
 
-**`--focus "topic"`** biases the Herald toward agents matching the topic. Examples: `--focus "security"`, `--focus "financial accuracy"`, `--focus "mobile UX"`.
+Parse the JSON output. The `roster` array contains agent IDs to deploy alongside this command's lead agents. If the command fails or returns an empty roster, use the hardcoded manifest below.
 
-**`--light`** skips the Herald entirely — uses only the command's hardcoded core roster.
-**`--solo`** skips both Herald and all sub-agents — lead agent only.
+**`--focus "topic"`** biases the Surfer toward agents matching the topic.
+**`--light`** skips the Surfer — uses only hardcoded core roster.
+**`--solo`** skips Surfer and all sub-agents — lead only.
 
 ## Context Setup
 1. Read PRD frontmatter for `deploy:` target (vps, vercel, railway, docker, static, cloudflare)

package/.claude/commands/devops.md

@@ -11,20 +11,18 @@ Opus scans `git diff --stat` and matches changed files against the `description`
 
 **Dispatch control:** `--light` skips dynamic dispatch (core only). `--solo` runs lead agent only.
 
-## Herald Pre-Scan (ADR-047)
+## Silver Surfer Pre-Scan (ADR-048)
 
-Before agent deployment, run the Herald to select the optimal roster:
+Before agent deployment, the Silver Surfer selects the optimal roster:
 
-1. Call `gatherHeraldContext('/devops', '$ARGUMENTS', '<focus-if-provided>')` to collect codebase context
-2. Call `loadAgentRegistry()` to get all 263 agent definitions
-3. Call `runHerald(context, registry)` to get the optimal roster
-4. Merge Herald's roster with this command's hardcoded lead agents (Herald adds, never removes leads)
-5. Deploy the merged roster per the command's normal parallel/sequential protocol
+Run: `npx thevoidforge herald --command /devops --json`
+(Add `--focus "<topic>"` if the user provided `--focus`)
 
-**`--focus "topic"`** biases the Herald toward agents matching the topic. Examples: `--focus "security"`, `--focus "financial accuracy"`, `--focus "mobile UX"`.
+Parse the JSON output. The `roster` array contains agent IDs to deploy alongside this command's lead agents. If the command fails or returns an empty roster, use the hardcoded manifest below.
 
-**`--light`** skips the Herald entirely — uses only the command's hardcoded core roster.
-**`--solo`** skips both Herald and all sub-agents — lead agent only.
+**`--focus "topic"`** biases the Surfer toward agents matching the topic.
+**`--light`** skips the Surfer — uses only hardcoded core roster.
+**`--solo`** skips Surfer and all sub-agents — lead only.
 
 ## Agent Deployment Manifest
 

package/.claude/commands/gauntlet.md

@@ -15,20 +15,18 @@ Opus scans `git diff --stat` and matches changed files against the `description`
 
 **Dispatch control:** `--light` skips dynamic dispatch (core only). `--solo` runs lead agent only.
 
-## Herald Pre-Scan (ADR-047)
+## Silver Surfer Pre-Scan (ADR-048)
 
-Before agent deployment, run the Herald to select the optimal roster:
+Before agent deployment, the Silver Surfer selects the optimal roster:
 
-1. Call `gatherHeraldContext('/gauntlet', '$ARGUMENTS', '<focus-if-provided>')` to collect codebase context
-2. Call `loadAgentRegistry()` to get all 263 agent definitions
-3. Call `runHerald(context, registry)` to get the optimal roster
-4. Merge Herald's roster with this command's hardcoded lead agents (Herald adds, never removes leads)
-5. Deploy the merged roster per the command's normal parallel/sequential protocol
+Run: `npx thevoidforge herald --command /gauntlet --json`
+(Add `--focus "<topic>"` if the user provided `--focus`)
 
-**`--focus "topic"`** biases the Herald toward agents matching the topic. Examples: `--focus "security"`, `--focus "financial accuracy"`, `--focus "mobile UX"`.
+Parse the JSON output. The `roster` array contains agent IDs to deploy alongside this command's lead agents. If the command fails or returns an empty roster, use the hardcoded manifest below.
 
-**`--light`** skips the Herald entirely — uses only the command's hardcoded core roster.
-**`--solo`** skips both Herald and all sub-agents — lead agent only.
+**`--focus "topic"`** biases the Surfer toward agents matching the topic.
+**`--light`** skips the Surfer — uses only hardcoded core roster.
+**`--solo`** skips Surfer and all sub-agents — lead only.
 
 ## Round 1 — Discovery (parallel)
 

package/.claude/commands/qa.md

@@ -10,20 +10,18 @@ Opus scans `git diff --stat` and matches changed files against the `description`
 
 **Promoted agent:** **Constantine** `subagent_type: Constantine` runs on every `/qa` final pass — finds code that works by accident.
 
-## Herald Pre-Scan (ADR-047)
+## Silver Surfer Pre-Scan (ADR-048)
 
-Before agent deployment, run the Herald to select the optimal roster:
+Before agent deployment, the Silver Surfer selects the optimal roster:
 
-1. Call `gatherHeraldContext('/qa', '$ARGUMENTS', '<focus-if-provided>')` to collect codebase context
-2. Call `loadAgentRegistry()` to get all 263 agent definitions
-3. Call `runHerald(context, registry)` to get the optimal roster
-4. Merge Herald's roster with this command's hardcoded lead agents (Herald adds, never removes leads)
-5. Deploy the merged roster per the command's normal parallel/sequential protocol
+Run: `npx thevoidforge herald --command /qa --json`
+(Add `--focus "<topic>"` if the user provided `--focus`)
 
-**`--focus "topic"`** biases the Herald toward agents matching the topic. Examples: `--focus "security"`, `--focus "financial accuracy"`, `--focus "mobile UX"`.
+Parse the JSON output. The `roster` array contains agent IDs to deploy alongside this command's lead agents. If the command fails or returns an empty roster, use the hardcoded manifest below.
 
-**`--light`** skips the Herald entirely — uses only the command's hardcoded core roster.
-**`--solo`** skips both Herald and all sub-agents — lead agent only.
+**`--focus "topic"`** biases the Surfer toward agents matching the topic.
+**`--light`** skips the Surfer — uses only hardcoded core roster.
+**`--solo`** skips Surfer and all sub-agents — lead only.
 
 ## Context Setup
 1. Read `/logs/build-state.md` — understand current project state

package/.claude/commands/review.md

@@ -8,20 +8,18 @@ Opus scans `git diff --stat` and matches changed files against the `description`
 
 **Dispatch control:** `--light` skips dynamic dispatch (core only). `--solo` runs lead agent only.
 
-## Herald Pre-Scan (ADR-047)
+## Silver Surfer Pre-Scan (ADR-048)
 
-Before agent deployment, run the Herald to select the optimal roster:
+Before agent deployment, the Silver Surfer selects the optimal roster:
 
-1. Call `gatherHeraldContext('/review', '$ARGUMENTS', '<focus-if-provided>')` to collect codebase context
-2. Call `loadAgentRegistry()` to get all 263 agent definitions
-3. Call `runHerald(context, registry)` to get the optimal roster
-4. Merge Herald's roster with this command's hardcoded lead agents (Herald adds, never removes leads)
-5. Deploy the merged roster per the command's normal parallel/sequential protocol
+Run: `npx thevoidforge herald --command /review --json`
+(Add `--focus "<topic>"` if the user provided `--focus`)
 
-**`--focus "topic"`** biases the Herald toward agents matching the topic. Examples: `--focus "security"`, `--focus "financial accuracy"`, `--focus "mobile UX"`.
+Parse the JSON output. The `roster` array contains agent IDs to deploy alongside this command's lead agents. If the command fails or returns an empty roster, use the hardcoded manifest below.
 
-**`--light`** skips the Herald entirely — uses only the command's hardcoded core roster.
-**`--solo`** skips both Herald and all sub-agents — lead agent only.
+**`--focus "topic"`** biases the Surfer toward agents matching the topic.
+**`--light`** skips the Surfer — uses only hardcoded core roster.
+**`--solo`** skips Surfer and all sub-agents — lead only.
 
 ## Context Setup
 1. Read `/logs/build-state.md` — understand current project state

package/.claude/commands/security.md

@@ -8,20 +8,18 @@ Opus scans `git diff --stat` and matches changed files against the `description`
 
 **Dispatch control:** `--light` skips dynamic dispatch (core only). `--solo` runs lead agent only.
 
-## Herald Pre-Scan (ADR-047)
+## Silver Surfer Pre-Scan (ADR-048)
 
-Before agent deployment, run the Herald to select the optimal roster:
+Before agent deployment, the Silver Surfer selects the optimal roster:
 
-1. Call `gatherHeraldContext('/security', '$ARGUMENTS', '<focus-if-provided>')` to collect codebase context
-2. Call `loadAgentRegistry()` to get all 263 agent definitions
-3. Call `runHerald(context, registry)` to get the optimal roster
-4. Merge Herald's roster with this command's hardcoded lead agents (Herald adds, never removes leads)
-5. Deploy the merged roster per the command's normal parallel/sequential protocol
+Run: `npx thevoidforge herald --command /security --json`
+(Add `--focus "<topic>"` if the user provided `--focus`)
 
-**`--focus "topic"`** biases the Herald toward agents matching the topic. Examples: `--focus "security"`, `--focus "financial accuracy"`, `--focus "mobile UX"`.
+Parse the JSON output. The `roster` array contains agent IDs to deploy alongside this command's lead agents. If the command fails or returns an empty roster, use the hardcoded manifest below.
 
-**`--light`** skips the Herald entirely — uses only the command's hardcoded core roster.
-**`--solo`** skips both Herald and all sub-agents — lead agent only.
+**`--focus "topic"`** biases the Surfer toward agents matching the topic.
+**`--light`** skips the Surfer — uses only hardcoded core roster.
+**`--solo`** skips Surfer and all sub-agents — lead only.
 
 ## Context Setup
 1. Read `/logs/build-state.md` — understand current project state

package/.claude/commands/test.md

@@ -13,20 +13,18 @@ Opus scans `git diff --stat` and matches changed files against the `description`
 
 **Dispatch control:** `--light` skips dynamic dispatch (core only). `--solo` runs lead agent only.
 
-## Herald Pre-Scan (ADR-047)
+## Silver Surfer Pre-Scan (ADR-048)
 
-Before agent deployment, run the Herald to select the optimal roster:
+Before agent deployment, the Silver Surfer selects the optimal roster:
 
-1. Call `gatherHeraldContext('/test', '$ARGUMENTS', '<focus-if-provided>')` to collect codebase context
-2. Call `loadAgentRegistry()` to get all 263 agent definitions
-3. Call `runHerald(context, registry)` to get the optimal roster
-4. Merge Herald's roster with this command's hardcoded lead agents (Herald adds, never removes leads)
-5. Deploy the merged roster per the command's normal parallel/sequential protocol
+Run: `npx thevoidforge herald --command /test --json`
+(Add `--focus "<topic>"` if the user provided `--focus`)
 
-**`--focus "topic"`** biases the Herald toward agents matching the topic. Examples: `--focus "security"`, `--focus "financial accuracy"`, `--focus "mobile UX"`.
+Parse the JSON output. The `roster` array contains agent IDs to deploy alongside this command's lead agents. If the command fails or returns an empty roster, use the hardcoded manifest below.
 
-**`--light`** skips the Herald entirely — uses only the command's hardcoded core roster.
-**`--solo`** skips both Herald and all sub-agents — lead agent only.
+**`--focus "topic"`** biases the Surfer toward agents matching the topic.
+**`--light`** skips the Surfer — uses only hardcoded core roster.
+**`--solo`** skips Surfer and all sub-agents — lead only.
 
 ## Step 0 — Orient
 **Oracle** `subagent_type: Oracle` orients:

package/.claude/commands/ux.md

@@ -8,20 +8,18 @@ Opus scans `git diff --stat` and matches changed files against the `description`
 
 **Dispatch control:** `--light` skips dynamic dispatch (core only). `--solo` runs lead agent only.
 
-## Herald Pre-Scan (ADR-047)
+## Silver Surfer Pre-Scan (ADR-048)
 
-Before agent deployment, run the Herald to select the optimal roster:
+Before agent deployment, the Silver Surfer selects the optimal roster:
 
-1. Call `gatherHeraldContext('/ux', '$ARGUMENTS', '<focus-if-provided>')` to collect codebase context
-2. Call `loadAgentRegistry()` to get all 263 agent definitions
-3. Call `runHerald(context, registry)` to get the optimal roster
-4. Merge Herald's roster with this command's hardcoded lead agents (Herald adds, never removes leads)
-5. Deploy the merged roster per the command's normal parallel/sequential protocol
+Run: `npx thevoidforge herald --command /ux --json`
+(Add `--focus "<topic>"` if the user provided `--focus`)
 
-**`--focus "topic"`** biases the Herald toward agents matching the topic. Examples: `--focus "security"`, `--focus "financial accuracy"`, `--focus "mobile UX"`.
+Parse the JSON output. The `roster` array contains agent IDs to deploy alongside this command's lead agents. If the command fails or returns an empty roster, use the hardcoded manifest below.
 
-**`--light`** skips the Herald entirely — uses only the command's hardcoded core roster.
-**`--solo`** skips both Herald and all sub-agents — lead agent only.
+**`--focus "topic"`** biases the Surfer toward agents matching the topic.
+**`--light`** skips the Surfer — uses only hardcoded core roster.
+**`--solo`** skips Surfer and all sub-agents — lead only.
 
 ## Context Setup
 1. Read `/logs/build-state.md` — understand current project state

package/CHANGELOG.md

@@ -6,6 +6,22 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/), and this
 
 ---
 
+## [23.6.0] - 2026-04-12
+
+### The Silver Surfer (ADR-048, Campaign 38)
+
+### Added
+- **Silver Surfer** (Norrin Radd) — agent #264. Herald of Galactus. Pre-scan dispatch that reads codebase context and selects the optimal agent roster via Haiku.
+- **`voidforge herald` CLI subcommand** — the invocation bridge. Runs the Silver Surfer pre-scan from the command line: `npx thevoidforge herald --command /review --json`. Outputs JSON roster for Claude to deploy.
+- Silver Surfer agent definition with Haiku tier, scout tools, and dispatch tags.
+
+### Changed
+- All 14 major commands updated: "Herald Pre-Scan (ADR-047)" replaced with "Silver Surfer Pre-Scan (ADR-048)" using actual CLI invocation instead of pseudocode.
+- Agent count: 263 → 264.
+- CLAUDE.md and NAMING_REGISTRY.md updated with Silver Surfer identity.
+
+---
+
 ## [23.5.4] - 2026-04-12
 
 ### Fixed

package/CLAUDE.md

@@ -234,7 +234,7 @@ See `/docs/methods/MUSTER.md` for the full Muster Protocol.
 | Deploy Wizard | **Haku** (Anime) | Browser-based deploy wizard, infrastructure provisioning |
 | Setup Wizard | **Gandalf** (Tolkien) | Project scaffolding, initialization, dependency setup |
 
-263 sub-agent names in `/docs/NAMING_REGISTRY.md`. No duplicates across active sessions. All agents materialized as subagent definitions in `.claude/agents/` (ADR-044).
+264 sub-agent names in `/docs/NAMING_REGISTRY.md`. No duplicates across active sessions. All agents materialized as subagent definitions in `.claude/agents/` (ADR-044). Silver Surfer (ADR-048) dispatches the optimal roster via Haiku pre-scan.
 
 ## Distribution
 

package/VERSION.md

@@ -1,6 +1,6 @@
 # Version
 
-**Current:** 23.5.4
+**Current:** 23.6.0
 
 ## Versioning Scheme
 
@@ -14,6 +14,7 @@ This project uses [Semantic Versioning](https://semver.org/):
 
 | Version | Date | Summary |
 |---------|------|---------|
+| 23.6.0 | 2026-04-12 | The Silver Surfer — Herald invocation bridge, CLI subcommand, agent #264, end-to-end dispatch pipeline. ADR-048. Campaign 38. |
 | 23.5.4 | 2026-04-12 | Command-doc sync: build.md Phase 12.75, ux.md screenshots, qa.md dynamic counts |
 | 23.5.3 | 2026-04-12 | Fix 201 broken subagent_type refs (filename→YAML name) + /campaign as default start command |
 | 23.5.2 | 2026-04-12 | /void auto-cleanup ~/.claude/ duplicates + git init stack trace fix |

package/docs/NAMING_REGISTRY.md

@@ -113,8 +113,9 @@
 28. Jarvis — AI assistant, status reporting, progress summaries
 
 29. Thanos — **Lead: The Gauntlet.** Comprehensive multi-round review. Tests every domain, every stone. "I am inevitable."
+30. Silver Surfer (Norrin Radd) — **The Herald.** Pre-scan dispatch — reads codebase and selects optimal agent roster via Haiku. Scouts ahead, summons the right team. "All that you know is at an end."
 
-**Reserved:** Stark (lead — backend), Coulson (lead — release), Fury (lead — the initiative), Thanos (lead — the gauntlet)
+**Reserved:** Stark (lead — backend), Coulson (lead — release), Fury (lead — the initiative), Thanos (lead — the gauntlet), Silver Surfer (herald — dispatch)
 
 ---
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "thevoidforge-methodology",
-  "version": "23.5.4",
+  "version": "23.6.0",
   "description": "VoidForge methodology — agents, commands, methods, patterns.",
   "license": "MIT",
   "files": [