opencode-onboard 0.5.2 → 0.5.3

package/content/.opencode/commands/opsx-apply.md

@@ -122,9 +122,16 @@ Implement tasks from an OpenSpec change using the ensemble agent team.
        - read each engineer's description and abilities
        - prefer the most specialized custom engineer whose description and abilities match the task
        - use `basic-engineer` only when no custom engineer is a clear fit or as a recovery fallback
-       - never spawn an engineer name that is not present in `.opencode/agents/`
-
-       REQUIRED assignment algorithm (do not skip):
+        - never spawn an engineer name that is not present in `.opencode/agents/`
+
+        **Model resolution for spawned agents (do not skip):**
+        Before each `team_spawn`, resolve the model for that agent using this priority:
+        1. **Agent file frontmatter** — Read `.opencode/agents/<engineer-file>` and check for a `model:` field in the YAML frontmatter. This is the user's explicit choice for this specific agent.
+        2. **`ensemble.json` `modelsByAgent`** — Read `.opencode/ensemble.json`. If `modelsByAgent` contains a key matching this agent's role (build agents → `build`, devops-manager → `explore`), use that value.
+        3. **Active chat model** — Fall back to the model currently running this conversation (your own model).
+        Never hardcode a model ID. Never skip this resolution. Log the result: `[model: <id> ← <source: agent frontmatter / ensemble.json modelsByAgent / active chat>]`
+
+        REQUIRED assignment algorithm (do not skip):
        1. Build candidate list from `.opencode/agents/*.md` excluding `devops-manager`.
        2. Classify each task by domain using task text (api/backend, ui/frontend, infra/devops, testing/qa).
        3. For each task, score every candidate agent:
@@ -174,13 +181,13 @@ Implement tasks from an OpenSpec change using the ensemble agent team.
        ALWAYS set `claim_task` to the first unblocked task in that agent's initial batch.
        Only spawn agents whose tasks are actually needed by this change. Skip agents with no tasks.
 
-       Spawn sequentially, waiting for each result:
-       ```
-       team_spawn name:"ui1" agent:"frontend-engineer" prompt:"..."
-       (wait for result)
-       team_spawn name:"api1" agent:"backend-engineer" prompt:"..."
-       (wait for result)
-       ```
+        Spawn sequentially, waiting for each result:
+        ```
+        team_spawn name:"ui1" agent:"frontend-engineer" model:"<resolved-model>" prompt:"..."
+        (wait for result)
+        team_spawn name:"api1" agent:"backend-engineer" model:"<resolved-model>" prompt:"..."
+        (wait for result)
+        ```
        Replace example agent names with REAL engineers that exist in this project.
 
        Then send each spawned worker a short start message that repeats their exact task IDs if needed:
@@ -226,7 +233,7 @@ Implement tasks from an OpenSpec change using the ensemble agent team.
 
    Spawn the best available verification-capable engineer with `worktree:false` (for example, a testing-focused custom engineer or `basic-engineer` if no better verifier exists):
    ```
-   team_spawn name:"verify" agent:"<real-verifier-engineer>" worktree:false prompt:"<verification scope, context summary, run tests + build + lint + verify acceptance criteria, no task claiming required in this phase, send results to lead when done>"
+   team_spawn name:"verify" agent:"<real-verifier-engineer>" worktree:false model:"<resolved-model>" prompt:"<verification scope, context summary, run tests + build + lint + verify acceptance criteria, no task claiming required in this phase, send results to lead when done>"
    ```
    Wait for message -> team_results -> fix blockers -> team_shutdown (no team_merge needed, worktree:false)
 
@@ -253,9 +260,10 @@ Implement tasks from an OpenSpec change using the ensemble agent team.
 - NEVER implement tasks directly. Always use team_create + team_spawn, no exceptions
 - NEVER touch source files before team_create is called, not even one edit
 - NEVER call team_spawn without the agent field, it is required and will fail without it
-- NEVER call team_spawn before all tasks are on the board; use multiple `team_tasks_add` calls when dependencies require real IDs from earlier calls
-- NEVER poll team_results or team_status in a loop, wait for teammates to message you
-- NEVER call team_claim or team_tasks_complete as lead, only agents call these tools
+- NEVER call team_spawn without a resolved `model:` field; always pass the model resolved from the priority chain
+- NEVER call team_spawn before all tasks are on the board; use multiple `team_tasks_add` calls when dependencies require real IDs from earlier calls
+- NEVER poll team_results or team_status in a loop, wait for teammates to message you
+- NEVER call team_claim or team_tasks_complete as lead, only agents call these tools
 - NEVER edit files between team_spawn and team_merge, team_merge blocks on overlapping local changes
 - NEVER leave pending tasks orphaned, always verify board is empty before proceeding to step 7
 - ALWAYS pass the LITERAL task IDs returned by team_tasks_add into each agent's spawn prompt, copy the exact IDs, never paraphrase

package/content/.opencode/skills/openspec-apply-change/SKILL.md

@@ -128,9 +128,16 @@ Implement tasks from an OpenSpec change using the ensemble agent team.
        - read each engineer's description and abilities
        - prefer the most specialized custom engineer whose description and abilities match the task
        - use `basic-engineer` only when no custom engineer is a clear fit or as a recovery fallback
-       - never spawn an engineer name that is not present in `.opencode/agents/`
+        - never spawn an engineer name that is not present in `.opencode/agents/`
 
-       REQUIRED assignment algorithm (do not skip):
+        **Model resolution for spawned agents (do not skip):**
+        Before each `team_spawn`, resolve the model for that agent using this priority:
+        1. **Agent file frontmatter** — Read `.opencode/agents/<engineer-file>` and check for a `model:` field in the YAML frontmatter. This is the user's explicit choice for this specific agent.
+        2. **`ensemble.json` `modelsByAgent`** — Read `.opencode/ensemble.json`. If `modelsByAgent` contains a key matching this agent's role (build agents → `build`, devops-manager → `explore`), use that value.
+        3. **Active chat model** — Fall back to the model currently running this conversation (your own model).
+        Never hardcode a model ID. Never skip this resolution. Log the result: `[model: <id> ← <source: agent frontmatter / ensemble.json modelsByAgent / active chat>]`
+
+        REQUIRED assignment algorithm (do not skip):
        1. Build candidate list from `.opencode/agents/*.md` excluding `devops-manager`.
        2. Classify each task by domain using task text (api/backend, ui/frontend, infra/devops, testing/qa).
        3. For each task, score every candidate agent:
@@ -181,13 +188,13 @@ Implement tasks from an OpenSpec change using the ensemble agent team.
        5. Send a short team_message with files changed and checks run
        ```
 
-       Spawn sequentially, waiting for each result:
-       ```
-       team_spawn name:"ui1" agent:"frontend-engineer" prompt:"..."
-       (wait for result)
-       team_spawn name:"api1" agent:"backend-engineer" prompt:"..."
-       (wait for result)
-       ```
+        Spawn sequentially, waiting for each result:
+        ```
+        team_spawn name:"ui1" agent:"frontend-engineer" model:"<resolved-model>" prompt:"..."
+        (wait for result)
+        team_spawn name:"api1" agent:"backend-engineer" model:"<resolved-model>" prompt:"..."
+        (wait for result)
+        ```
        Replace example agent names with REAL engineers that exist in this project.
 
        Then send each spawned worker a short start message that repeats their exact task IDs if needed:
@@ -232,7 +239,7 @@ Implement tasks from an OpenSpec change using the ensemble agent team.
 
    Spawn the best available verification-capable engineer with `worktree:false` (for example, a testing-focused custom engineer or `basic-engineer` if no better verifier exists):
    ```
-   team_spawn name:"verify" agent:"<real-verifier-engineer>" worktree:false prompt:"<verification scope, context summary, run tests + build + lint + verify acceptance criteria, no task claiming required in this phase, send results to lead when done>"
+   team_spawn name:"verify" agent:"<real-verifier-engineer>" worktree:false model:"<resolved-model>" prompt:"<verification scope, context summary, run tests + build + lint + verify acceptance criteria, no task claiming required in this phase, send results to lead when done>"
    ```
    Wait for message -> team_results -> fix blockers -> team_shutdown (no team_merge needed, worktree:false)
 
@@ -259,6 +266,7 @@ Implement tasks from an OpenSpec change using the ensemble agent team.
 - NEVER implement tasks directly. Always use team_create + team_spawn, no exceptions
 - NEVER touch source files before team_create is called, not even one edit
 - NEVER call team_spawn without the agent field, it is required and will fail without it
+- NEVER call team_spawn without a resolved `model:` field; always pass the model resolved from the priority chain
 - NEVER call team_spawn before all tasks are on the board; use multiple `team_tasks_add` calls when dependencies require real IDs from earlier calls
 - NEVER poll team_results or team_status in a loop, wait for teammates to message you
 - NEVER call team_claim or team_tasks_complete as lead, only agents call these tools

package/content/AGENTS.md

@@ -248,8 +248,9 @@ Core tools used in this workflow:
 
 If a teammate stalls due to model quota/rate-limit exhaustion:
 1. `team_shutdown name:"<stuck-member>" force:true`
-2. `team_spawn` same member/task with an available model
-3. `team_message` start instruction with the exact next task ID
+2. Resolve a new model using the model resolution priority (agent file frontmatter → `ensemble.json` `modelsByAgent` → active chat model). Avoid the model that hit the rate limit.
+3. `team_spawn` same member/task with the resolved model
+4. `team_message` start instruction with the exact next task ID
 
 ---
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode-onboard",
-  "version": "0.5.2",
+  "version": "0.5.3",
   "description": "Prepare any codebase for AI agent workflows using OpenCode, OpenSpec, and ensemble orchestration.",
   "keywords": [
     "opencode",

package/src/commands/shared.js

@@ -1,3 +1,4 @@
+import { execa } from 'execa'
 import fse from 'fs-extra'
 import path from 'node:path'
 
@@ -10,3 +11,15 @@ export async function readOnboardConfig() {
     return null
   }
 }
+
+export async function ensureGitLongpaths(cwd = process.cwd()) {
+  try {
+    const repoCheck = await execa('git', ['rev-parse', '--is-inside-work-tree'], { cwd, reject: false })
+    if (repoCheck.exitCode !== 0 || repoCheck.stdout.trim() !== 'true') return false
+
+    const configResult = await execa('git', ['config', 'core.longpaths', 'true'], { cwd, reject: false })
+    return configResult.exitCode === 0
+  } catch {
+    return false
+  }
+}

package/src/commands/shared.test.js

@@ -1,13 +1,20 @@
-import { describe, it, expect, beforeEach, afterEach } from 'vitest'
+import { describe, it, expect, beforeEach, afterEach, vi } from 'vitest'
 import fs from 'node:fs'
 import path from 'node:path'
 import os from 'node:os'
-import { readOnboardConfig } from './shared.js'
+
+vi.mock('execa', () => ({
+  execa: vi.fn(),
+}))
+
+import { execa } from 'execa'
+import { ensureGitLongpaths, readOnboardConfig } from './shared.js'
 
 describe('readOnboardConfig()', () => {
   let tmpDir, originalCwd
 
   beforeEach(() => {
+    vi.clearAllMocks()
     tmpDir = fs.mkdtempSync(path.join(os.tmpdir(), 'shared-test-'))
     originalCwd = process.cwd()
     process.chdir(tmpDir)
@@ -54,3 +61,36 @@ describe('readOnboardConfig()', () => {
     expect(result).toBeNull()
   })
 })
+
+describe('ensureGitLongpaths()', () => {
+  beforeEach(() => {
+    vi.clearAllMocks()
+  })
+
+  it('configures core.longpaths in a git repository', async () => {
+    execa
+      .mockResolvedValueOnce({ exitCode: 0, stdout: 'true' })
+      .mockResolvedValueOnce({ exitCode: 0, stdout: '', stderr: '' })
+
+    const result = await ensureGitLongpaths('C:/repo')
+
+    expect(result).toBe(true)
+    expect(execa).toHaveBeenNthCalledWith(1, 'git', ['rev-parse', '--is-inside-work-tree'], {
+      cwd: 'C:/repo',
+      reject: false,
+    })
+    expect(execa).toHaveBeenNthCalledWith(2, 'git', ['config', 'core.longpaths', 'true'], {
+      cwd: 'C:/repo',
+      reject: false,
+    })
+  })
+
+  it('skips configuration outside a git repository', async () => {
+    execa.mockResolvedValueOnce({ exitCode: 1, stdout: '', stderr: '' })
+
+    const result = await ensureGitLongpaths('C:/not-a-repo')
+
+    expect(result).toBe(false)
+    expect(execa).toHaveBeenCalledTimes(1)
+  })
+})

package/src/commands/wizard.js

@@ -1,7 +1,8 @@
 import { select as wizardSelect } from '@inquirer/prompts'
-import chalk from 'chalk'
-import { chooseSourceScope } from '../steps/source/index.js'
-import { cleanAiFiles } from '../steps/clean/index.js'
+import chalk from 'chalk'
+import { ensureGitLongpaths } from './shared.js'
+import { chooseSourceScope } from '../steps/source/index.js'
+import { cleanAiFiles } from '../steps/clean/index.js'
 import { choosePlatform } from '../steps/platform/index.js'
 import { copyContentStep } from '../steps/copy/index.js'
 import { initOpenspec } from '../steps/openspec/index.js'
@@ -37,7 +38,7 @@ export async function runWizard(version) {
   console.log()
 
   // Only wait for Enter in a real interactive TTY
-  if (process.stdin.isTTY) {
+  if (process.stdin.isTTY) {
     console.log(chalk.bold('  Press Enter to begin...'))
     console.log()
     await new Promise(resolve => {
@@ -46,10 +47,13 @@ export async function runWizard(version) {
         process.stdin.pause()
         resolve()
       })
-    })
-  }
-
-  const scope = await chooseSourceScope()
+    })
+  }
+
+  const longpathsConfigured = await ensureGitLongpaths()
+  if (longpathsConfigured) console.log(chalk.dim('  Git long paths enabled for this repository.'))
+
+  const scope = await chooseSourceScope()
 
   const maxConcurrentAgents = await wizardSelect({
     message: 'Max concurrent agents:',

package/src/steps/openspec/ensemble.js

@@ -58,6 +58,13 @@ export const ENSEMBLE_SECTION = `6. **Implement via ensemble team**
       - use \`basic-engineer\` only when no custom engineer is a clear fit or as a recovery fallback
       - never spawn an engineer name that is not present in \`.opencode/agents/\`
 
+      **Model resolution for spawned agents (do not skip):**
+      Before each \`team_spawn\`, resolve the model for that agent using this priority:
+      1. **Agent file frontmatter** — Read \`.opencode/agents/<engineer-file>\` and check for a \`model:\` field in the YAML frontmatter. This is the user's explicit choice for this specific agent.
+      2. **\`ensemble.json\` \`modelsByAgent\`** — Read \`.opencode/ensemble.json\`. If \`modelsByAgent\` contains a key matching this agent's role (build agents → \`build\`, devops-manager → \`explore\`), use that value.
+      3. **Active chat model** — Fall back to the model currently running this conversation (your own model).
+      Never hardcode a model ID. Never skip this resolution. Log the result: \`[model: <id> ← <source: agent frontmatter / ensemble.json modelsByAgent / active chat>]\`
+
       Each \`team_spawn\` MUST include the agent field (required, causes NOT NULL error if omitted).
 
       The spawn prompt must be short and operational. It must contain:
@@ -91,9 +98,9 @@ export const ENSEMBLE_SECTION = `6. **Implement via ensemble team**
 
       Spawn sequentially, waiting for each result:
       \`\`\`
-      team_spawn name:"ui1" agent:"frontend-engineer" prompt:"..."
+      team_spawn name:"ui1" agent:"frontend-engineer" model:"<resolved-model>" prompt:"..."
       (wait for result)
-      team_spawn name:"api1" agent:"backend-engineer" prompt:"..."
+      team_spawn name:"api1" agent:"backend-engineer" model:"<resolved-model>" prompt:"..."
       (wait for result)
       \`\`\`
       Replace example agent names with REAL engineers that exist in this project.
@@ -133,7 +140,7 @@ export const ENSEMBLE_SECTION = `6. **Implement via ensemble team**
       6. **If ALL agents are shut down and tasks remain unassigned** (new domain, dependencies unblocked):
           - Discover the remaining matching engineers from \`.opencode/agents/\` and spawn a new wave (back to step 6d).
       7. **If ALL tasks are done:** proceed to step 7.
-      If a teammate reports rate-limit/quota/token exhaustion, immediately shutdown that teammate and respawn with an available model.
+      If a teammate reports rate-limit/quota/token exhaustion, immediately shutdown that teammate and respawn with a different model using the model resolution priority above.
 
       **ZERO PENDING TASKS GUARANTEE:** Before proceeding to step 7, call \`team_tasks_list\` and verify EVERY task is either \`done\` or \`blocked\`. If any task is \`pending\` and unassigned, assign it to an agent or spawn a new one. Never leave pending tasks orphaned.
 
@@ -141,7 +148,7 @@ export const ENSEMBLE_SECTION = `6. **Implement via ensemble team**
 
    Spawn the best available verification-capable engineer with \`worktree:false\` (for example, a testing-focused custom engineer or \`basic-engineer\` if no better verifier exists):
    \`\`\`
-   team_spawn name:"verify" agent:"<real-verifier-engineer>" worktree:false prompt:"<verification scope, context summary, run tests + build + lint + verify acceptance criteria, no task claiming required in this phase, send results to lead when done>"
+   team_spawn name:"verify" agent:"<real-verifier-engineer>" worktree:false model:"<resolved-model>" prompt:"<verification scope, context summary, run tests + build + lint + verify acceptance criteria, no task claiming required in this phase, send results to lead when done>"
    \`\`\`
    Wait for message -> team_results -> fix blockers -> team_shutdown (no team_merge needed, worktree:false)
 
@@ -165,6 +172,7 @@ export const ENSEMBLE_SECTION = `6. **Implement via ensemble team**
 - NEVER implement tasks directly. Always use team_create + team_spawn, no exceptions
 - NEVER touch source files before team_create is called, not even one edit
 - NEVER call team_spawn without the agent field, it is required and will fail without it
+- NEVER call team_spawn without a resolved \`model:\` field; always pass the model resolved from the priority chain
 - NEVER call team_spawn before all tasks are on the board; use multiple \`team_tasks_add\` calls when dependencies require real IDs from earlier calls
 - NEVER poll team_results or team_status in a loop, wait for teammates to message you
 - NEVER call team_claim or team_tasks_complete as lead, only agents call these tools