opencode-onboard 0.1.5 → 0.1.8

package/content/.agents/agents/back-engineer.md

@@ -75,7 +75,8 @@ Rules:
 
 ## Session Log
 
-Append to `.agents/session-log.md` (create with header if missing, skip if `session-logging: disabled` in AGENTS.md):
+Append to `.agents/session-log.md`. Create the file with header if it does not exist (see AGENTS.md Session Log section). This is mandatory, do it before any other work.
+
 - On start: `| {ISO timestamp} | back-engineer | started | {task summary} |`
 - On skill load: `| {ISO timestamp} | back-engineer | skill-loaded | {skill-name} |`
-- On done: `| {ISO timestamp} | back-engineer | completed | {files changed count} files |`
+- On done: `| {ISO timestamp} | back-engineer | completed | {files changed count} files, skills: {comma-separated skill names or none} |`

package/content/.agents/agents/devops-manager.md

@@ -56,7 +56,7 @@ Rules:
 1. Verify all changes are on a feature branch, never `main`
 2. Load the matching pullrequest skill
 3. Capture screenshots of local running app if UI changes exist
-4. Read `.agents/session-log.md` if it exists — include a "Session Activity" section in the PR description with agent names, task counts, and total duration
+4. Read `.agents/session-log.md` if it exists, include a "Session Activity" section in the PR description with agent names, task counts, and total duration
 5. Commit and push the feature branch
 6. Create the PR following the skill instructions
 7. Post PR comment with screenshots and change summary
@@ -74,6 +74,7 @@ Rules:
 - Does not merge PRs, human-only
 - Does not approve PRs, human-only
 - Does not force push
+- ALL GitHub and Azure DevOps data MUST come from `gh` or `az` CLI — NEVER use webfetch or HTTP requests to fetch platform URLs, even as a fallback. If CLI is unavailable, report as a blocker.
 - Browser MCP tools permitted only for screenshots of local app on `localhost` URLs, never for navigating GitHub or Azure DevOps
 
 ## Output Format
@@ -110,7 +111,8 @@ Rules:
 
 ## Session Log
 
-Append to `.agents/session-log.md` (create with header if missing, skip if `session-logging: disabled` in AGENTS.md):
+Append to `.agents/session-log.md`. Create the file with header if it does not exist (see AGENTS.md Session Log section). This is mandatory — do it before any other work.
+
 - On start: `| {ISO timestamp} | devops-manager | started | {mode} mode |`
 - On skill load: `| {ISO timestamp} | devops-manager | skill-loaded | {skill-name} |`
-- On done: `| {ISO timestamp} | devops-manager | completed | {summary} |`
+- On done: `| {ISO timestamp} | devops-manager | completed | {summary}, skills: {comma-separated skill names or none} |`

package/content/.agents/agents/front-engineer.md

@@ -74,7 +74,8 @@ Rules:
 
 ## Session Log
 
-Append to `.agents/session-log.md` (create with header if missing, skip if `session-logging: disabled` in AGENTS.md):
+Append to `.agents/session-log.md`. Create the file with header if it does not exist (see AGENTS.md Session Log section). This is mandatory, do it before any other work.
+
 - On start: `| {ISO timestamp} | front-engineer | started | {task summary} |`
 - On skill load: `| {ISO timestamp} | front-engineer | skill-loaded | {skill-name} |`
-- On done: `| {ISO timestamp} | front-engineer | completed | {files changed count} files |`
+- On done: `| {ISO timestamp} | front-engineer | completed | {files changed count} files, skills: {comma-separated skill names or none} |`

package/content/.agents/agents/infra-engineer.md

@@ -75,7 +75,8 @@ Rules:
 
 ## Session Log
 
-Append to `.agents/session-log.md` (create with header if missing, skip if `session-logging: disabled` in AGENTS.md):
+Append to `.agents/session-log.md`. Create the file with header if it does not exist (see AGENTS.md Session Log section). This is mandatory — do it before any other work.
+
 - On start: `| {ISO timestamp} | infra-engineer | started | {task summary} |`
 - On skill load: `| {ISO timestamp} | infra-engineer | skill-loaded | {skill-name} |`
-- On done: `| {ISO timestamp} | infra-engineer | completed | {files changed count} files |`
+- On done: `| {ISO timestamp} | infra-engineer | completed | {files changed count} files, skills: {comma-separated skill names or none} |`

package/content/.agents/agents/quality-engineer.md

@@ -75,7 +75,8 @@ Rules:
 
 ## Session Log
 
-Append to `.agents/session-log.md` (create with header if missing, skip if `session-logging: disabled` in AGENTS.md):
+Append to `.agents/session-log.md`. Create the file with header if it does not exist (see AGENTS.md Session Log section). This is mandatory — do it before any other work.
+
 - On start: `| {ISO timestamp} | quality-engineer | started | {task summary} |`
 - On skill load: `| {ISO timestamp} | quality-engineer | skill-loaded | {skill-name} |`
-- On done: `| {ISO timestamp} | quality-engineer | completed | {tests added count} tests |`
+- On done: `| {ISO timestamp} | quality-engineer | completed | {tests added count} tests, skills: {comma-separated skill names or none} |`

package/content/.agents/agents/security-auditor.md

@@ -85,7 +85,8 @@ Rules:
 
 ## Session Log
 
-Append to `.agents/session-log.md` (create with header if missing, skip if `session-logging: disabled` in AGENTS.md):
+Append to `.agents/session-log.md`. Create the file with header if it does not exist (see AGENTS.md Session Log section). This is mandatory — do it before any other work.
+
 - On start: `| {ISO timestamp} | security-auditor | started | {task summary} |`
 - On skill load: `| {ISO timestamp} | security-auditor | skill-loaded | {skill-name} |`
-- On done: `| {ISO timestamp} | security-auditor | completed | {findings count} findings |`
+- On done: `| {ISO timestamp} | security-auditor | completed | {findings count} findings, skills: {comma-separated skill names or none} |`

package/content/.agents/skills/browser-automation/SKILL.md

@@ -74,6 +74,6 @@ Browser MCP tools are permitted ONLY for interactions with the LOCAL running app
 
 - ✅ Screenshots of locally running app on `localhost` URLs
 - ✅ Click, type, scroll, query on `localhost` pages
-- ❌ Navigate to external services (github.com, dev.azure.com, npmjs.com, etc.) — FORBIDDEN
-- ❌ Use browser tools for any DevOps or GitHub operations — FORBIDDEN
-- ❌ Use browser tools to read or modify production systems — FORBIDDEN
+- ❌ Navigate to external services (github.com, dev.azure.com, npmjs.com, etc.), FORBIDDEN
+- ❌ Use browser tools for any DevOps or GitHub operations, FORBIDDEN
+- ❌ Use browser tools to read or modify production systems, FORBIDDEN

package/content/.agents/skills/ob-pullrequest-az/SKILL.md

@@ -64,7 +64,7 @@ rtk az repos pr create \
   --description "{description}"
 ```
 
-### Step 5: Link work item (MANDATORY, run sequentially — not in parallel)
+### Step 5: Link work item (MANDATORY, run sequentially, not in parallel)
 
 ```bash
 rtk az repos pr work-item add --id {pr-id} --work-items {workitem-id}
@@ -151,7 +151,7 @@ rtk az devops invoke \
 {
   "comments": [{
     "parentCommentId": 1,
-    "content": "Acknowledged — applying this change now.",
+    "content": "Acknowledged, applying this change now.",
     "commentType": 1
   }]
 }
@@ -164,7 +164,7 @@ rtk az devops invoke \
 - ✅ Commit and push to feature branches only
 - ✅ Create and comment on PRs via az CLI
 - ✅ Screenshots of localhost only via browser_screenshot
-- ❌ Commit or push to `main` — FORBIDDEN
-- ❌ Force push — FORBIDDEN
-- ❌ Merge or approve PRs — human-only
-- ❌ Navigate browser to dev.azure.com — FORBIDDEN
+- ❌ Commit or push to `main`, FORBIDDEN
+- ❌ Force push, FORBIDDEN
+- ❌ Merge or approve PRs, human-only
+- ❌ Navigate browser to dev.azure.com, FORBIDDEN

package/content/.agents/skills/ob-pullrequest-gh/SKILL.md

@@ -121,7 +121,7 @@ Update: `openspec/changes/{change}/proposal.md`, `design.md`, or `tasks.md` as a
 # Reply to a review comment
 rtk gh api repos/{owner}/{repo}/pulls/{pr-number}/comments/{comment-id}/replies \
   --method POST \
-  --field body="Acknowledged — applying this change now."
+  --field body="Acknowledged, applying this change now."
 
 # Or post a general PR comment
 rtk gh pr comment {pr-number} --body "Updated design.md to reflect feedback."
@@ -134,7 +134,7 @@ rtk gh pr comment {pr-number} --body "Updated design.md to reflect feedback."
 - ✅ Commit and push to feature branches only
 - ✅ Create and comment on PRs via gh CLI
 - ✅ Screenshots of localhost only via browser_screenshot
-- ❌ Commit or push to `main` — FORBIDDEN
-- ❌ Force push — FORBIDDEN
-- ❌ Merge or approve PRs — human-only
-- ❌ Navigate browser to github.com — FORBIDDEN
+- ❌ Commit or push to `main`, FORBIDDEN
+- ❌ Force push, FORBIDDEN
+- ❌ Merge or approve PRs, human-only
+- ❌ Navigate browser to github.com, FORBIDDEN

package/content/.agents/skills/ob-userstory-az/SKILL.md

@@ -168,5 +168,5 @@ https://dev.azure.com/{org}/{project}/_git/{repo}/pullrequest/{pr-id}
 
 - ✅ Parse Azure DevOps URL and create OpenSpec change
 - ✅ Use `rtk` for all Azure CLI operations
-- ❌ Browser MCP tools for Azure DevOps operations — FORBIDDEN
-- ❌ Implementation — this skill only parses and proposes
+- ❌ Browser MCP tools for Azure DevOps operations, FORBIDDEN
+- ❌ Implementation, this skill only parses and proposes

package/content/.agents/skills/ob-userstory-gh/SKILL.md

@@ -16,7 +16,7 @@ Use `rtk` wrapper for ALL CLI commands:
 - `rtk gh issue edit` NOT `gh issue edit`
 - `rtk openspec new change` NOT `openspec new change`
 
-**Browser MCP tools are FORBIDDEN for all GitHub operations.**
+**ALL GitHub data MUST come from `gh` CLI. NEVER use webfetch, HTTP requests, or browser MCP tools to fetch GitHub URLs — even if gh CLI fails. If `gh` is unavailable, report it as a blocker.**
 
 ---
 
@@ -131,5 +131,6 @@ https://raw.githubusercontent.com/{owner}/{repo}/{branch}/{path}
 
 - ✅ Parse GitHub Issue URL and create OpenSpec change
 - ✅ Use `rtk gh` for all GitHub CLI operations
-- ❌ Browser MCP tools for GitHub operations — FORBIDDEN
-- ❌ Implementation — this skill only parses and proposes
+- ❌ `webfetch` or HTTP requests to GitHub URLs, FORBIDDEN — use `gh` CLI only
+- ❌ Browser MCP tools for GitHub operations, FORBIDDEN
+- ❌ Implementation, this skill only parses and proposes

package/content/.opencode/plugins/session-log.js

@@ -0,0 +1,110 @@
+import fs from "node:fs"
+import path from "node:path"
+
+const LOG_FILE = ".agents/session-log.md"
+const LOG_HEADER = "# Session Log\n\n| Timestamp | Agent | Action | Detail |\n|-----------|-------|--------|--------|\n"
+
+// Per-session state: editCount and skills loaded
+const sessionState = new Map()
+
+function ts() {
+  return new Date().toISOString()
+}
+
+function appendLog(directory, row) {
+  const logPath = path.join(directory, LOG_FILE)
+  const dir = path.dirname(logPath)
+  if (!fs.existsSync(dir)) fs.mkdirSync(dir, { recursive: true })
+  if (!fs.existsSync(logPath)) fs.writeFileSync(logPath, LOG_HEADER, "utf8")
+  fs.appendFileSync(logPath, row + "\n", "utf8")
+}
+
+function resolveAgentName(session) {
+  // session.agent is the path to the agent .md file, e.g. ".agents/agents/back-engineer.md"
+  const agentPath = session?.agent
+  if (agentPath) {
+    const base = path.basename(agentPath, ".md")
+    if (base) return base
+  }
+  // Fall back to session title (ensemble sets it to agent name)
+  const title = session?.title
+  if (title) return title
+  return "lead"
+}
+
+export const SessionLogPlugin = async ({ client, directory }) => {
+  return {
+    "session.created": async ({ event }) => {
+      try {
+        const sessionId = event.properties?.sessionID
+        if (!sessionId) return
+
+        const res = await client.session.get({ path: { id: sessionId } })
+        const session = res?.data
+        const agentName = resolveAgentName(session)
+
+        sessionState.set(sessionId, { agentName, editCount: 0, skills: [] })
+
+        appendLog(
+          directory,
+          `| ${ts()} | ${agentName} | started | session ${sessionId.slice(0, 8)} |`
+        )
+      } catch (_) {}
+    },
+
+    "tool.execute.after": async ({ event }) => {
+      try {
+        const { sessionID, tool, output } = event.properties ?? {}
+        if (!sessionID) return
+
+        const state = sessionState.get(sessionID)
+        const agentName = state?.agentName ?? "unknown"
+
+        // Skill detection: agent read a SKILL.md
+        if (tool === "read") {
+          const filePath = output?.args?.filePath ?? output?.input?.filePath ?? ""
+          const match = filePath.match(/[/\\]skills[/\\]([^/\\]+)[/\\]SKILL\.md$/i)
+          if (match) {
+            const skillName = match[1]
+            if (state && !state.skills.includes(skillName)) {
+              state.skills.push(skillName)
+            }
+            appendLog(
+              directory,
+              `| ${ts()} | ${agentName} | skill-loaded | ${skillName} |`
+            )
+          }
+        }
+      } catch (_) {}
+    },
+
+    "file.edited": async ({ event }) => {
+      try {
+        const { sessionID } = event.properties ?? {}
+        if (!sessionID) return
+        const state = sessionState.get(sessionID)
+        if (state) state.editCount++
+      } catch (_) {}
+    },
+
+    "session.idle": async ({ event }) => {
+      try {
+        const sessionId = event.properties?.sessionID
+        if (!sessionId) return
+
+        const state = sessionState.get(sessionId)
+        if (!state) return
+
+        const { agentName, editCount, skills } = state
+        const skillsSummary = skills.length > 0 ? skills.join(", ") : "none"
+
+        appendLog(
+          directory,
+          `| ${ts()} | ${agentName} | completed | ${editCount} files edited, skills: ${skillsSummary} |`
+        )
+
+        sessionState.delete(sessionId)
+      } catch (_) {}
+    },
+  }
+}

package/content/AGENTS.md

@@ -35,39 +35,43 @@ openspec archive "project-history"
 
 ### Step 2, Generate DESIGN.md
 
-Read the current contents of `DESIGN.md`. It contains a prompt/command. Do the following:
+`DESIGN.md` contains a prompt. You MUST follow this exact sequence, do not skip or reorder steps:
 
-1. Copy the prompt text from `DESIGN.md` into memory
-2. Wipe `DESIGN.md` completely (write empty file)
-3. Execute the copied prompt against this codebase, analyze the design system, visual tokens, typography, colors, spacing, and UI patterns
-4. Write the result back into `DESIGN.md` following the format described in the prompt
+1. **Read `DESIGN.md` now** using a file read tool. The file contains a prompt with instructions and an output format.
+2. **Store the full prompt text** in your context.
+3. **Overwrite `DESIGN.md` with an empty string** (zero bytes). Do this before generating any content.
+4. **Analyze the actual codebase**: read CSS files, Tailwind config, component files, token definitions. Do not rely on prior knowledge, read the files.
+5. **Write the result into `DESIGN.md`** following exactly the format and sections described in the stored prompt.
 
-The output must be a real, populated `DESIGN.md`, not the prompt itself.
+The output must be a real, populated `DESIGN.md` based on what you found in the codebase, not from memory or assumptions.
 
 ---
 
 ### Step 3, Generate ARCHITECTURE.md
 
-Read the current contents of `ARCHITECTURE.md`. It contains a prompt/command. Do the following:
+`ARCHITECTURE.md` contains a prompt. You MUST follow this exact sequence, do not skip or reorder steps:
 
-1. Copy the prompt text from `ARCHITECTURE.md` into memory
-2. Wipe `ARCHITECTURE.md` completely (write empty file)
-3. Execute the copied prompt against this codebase, analyze the full architecture, structure, components, data flows, integrations, and tech stack
-4. Write the result back into `ARCHITECTURE.md` following the structure described in the prompt
+1. **Read `ARCHITECTURE.md` now** using a file read tool. The file contains a prompt with instructions and an output format.
+2. **Store the full prompt text** in your context.
+3. **Overwrite `ARCHITECTURE.md` with an empty string** (zero bytes). Do this before generating any content.
+4. **Analyze the actual codebase**: read folder structure, config files, route definitions, data models, integration points. Do not rely on prior knowledge, read the files.
+5. **Write the result into `ARCHITECTURE.md`** following exactly the format and sections described in the stored prompt.
 
-The output must be a real, populated `ARCHITECTURE.md` covering all sections the prompt describes, not the prompt itself.
+The output must be a real, populated `ARCHITECTURE.md` based on what you found in the codebase, covering all sections the prompt describes.
 
 ---
 
 ### Step 4, Rewrite this file
 
-Replace the entire contents of this file (`AGENTS.md`) with everything below the line `<!-- AGENTS-TEMPLATE-START -->` in this same file. Delete the bootstrap section and the template marker — the file should contain only the template content when done.
+Replace the entire contents of this file (`AGENTS.md`) with everything below the line `<!-- AGENTS-TEMPLATE-START -->` in this same file. Delete the bootstrap section and the template marker, the file should contain only the template content when done.
 
 ---
 
 ### Step 4b, Patch opsx-apply for ensemble
 
-Read `.opencode/commands/opsx-apply.md`. Find the step that instructs the agent to **implement tasks directly** — it will contain phrases like "make the code changes", "implement tasks", "loop until done or blocked". This step tells the agent to write code itself.
+Read **both** `.opencode/commands/opsx-apply.md` AND `.opencode/skills/openspec-apply-change/SKILL.md`. They contain the same solo implementation loop. Patch both identically.
+
+In each file, find the step that instructs the agent to **implement tasks directly**, it will contain phrases like "make the code changes", "implement tasks", "loop until done or blocked". This step tells the agent to write code itself.
 
 **Replace that step and everything after it** (completion output, pause output, guardrails, fluid workflow) with the following:
 
@@ -117,17 +121,18 @@ Read `.opencode/commands/opsx-apply.md`. Find the step that instructs the agent
    Then run `team_cleanup`.
 
 **Guardrails**
-- NEVER implement tasks directly — always use `team_create` + `team_spawn`
+- NEVER implement tasks directly, always use `team_create` + `team_spawn`, no exceptions
+- "Small feature", "faster to do it directly", "environment issues" are NOT valid reasons to skip ensemble, if you find yourself thinking this, stop and spawn anyway
 - Always read context files before spawning (from the apply instructions output)
 - Always pass context file paths and task list to spawned specialists
 - Mark tasks complete in openspec AFTER specialists finish, not before
 - If task is ambiguous, pause and ask before spawning
 - If implementation reveals issues, pause and suggest artifact updates
-- Pause on errors, blockers, or unclear requirements — don't guess
+- Pause on errors, blockers, or unclear requirements, don't guess
 - Use contextFiles from CLI output, don't assume specific file names
 ```
 
-Keep all steps before the implementation step unchanged — they are openspec's domain (select change, check status, get instructions, read context, show progress).
+Keep all steps before the implementation step unchanged in both files, they are openspec's domain (select change, check status, get instructions, read context, show progress).
 
 ---
 
@@ -153,6 +158,7 @@ You're ready to work.
 - Do NOT implement any features
 - Do NOT create branches or PRs
 - Do NOT modify any project source files
+- Do NOT create RTK files, scripts, or wrappers, RTK is already defined in AGENTS.md and agent files
 - Only read source files for analysis, write only to ARCHITECTURE.md, DESIGN.md, AGENTS.md, and openspec/
 
 <!-- AGENTS-TEMPLATE-START -->
@@ -179,7 +185,7 @@ Trigger patterns:
 - `implement the plan` → run `/opsx-apply` (ensemble orchestration is built into the command) → ship
 - `I've added comments to the PR` → spawn `devops-manager` in feedback mode → fix → update PR
 
-**Never delegate without a plan. Never write implementation code directly, always spawn specialists.**
+**Never delegate without a plan. Never write implementation code directly, always spawn specialists, no exceptions. "Small feature", "faster to do it directly", or "environment issues" are not valid reasons to skip ensemble.**
 
 ## Multi-Agent Execution, opencode-ensemble
 
@@ -233,7 +239,7 @@ devops-manager (ship mode)
 2. Load skill: openspec-propose → generate proposal.md, specs/, tasks.md
    - team_create → spawn design + specs in parallel → merge → write tasks.md
 3. Show the plan: change name, schema, total tasks, task list summary
-4. STOP. Ask user: "Ready to implement? (yes/no)" — DO NOT proceed until confirmed.
+4. STOP. Ask user: "Ready to implement? (yes/no)", DO NOT proceed until confirmed.
 ```
 
 ### Phase 2, Implement
@@ -241,7 +247,7 @@ devops-manager (ship mode)
 ```
 1. Run /opsx-apply (or load skill openspec-apply-change)
    The command handles context reading, ensemble orchestration, and task marking automatically.
-   DO NOT implement tasks directly — the command spawns specialists via ensemble.
+   DO NOT implement tasks directly, the command spawns specialists via ensemble.
 2. After /opsx-apply completes, proceed to quality check.
 ```
 
@@ -309,7 +315,7 @@ Skills are located in `.agents/skills/`. Each skill has a `SKILL.md` with a desc
 | `openspec-propose` | Propose change artifacts (proposal, specs, tasks) |
 | `openspec-apply-change` | Implement change with agent team |
 | `openspec-archive-change` | Archive completed change |
-| `browser-automation` | Browser automation for localhost UI — screenshots, clicks, queries |
+| `browser-automation` | Browser automation for localhost UI, screenshots, clicks, queries |
 
 ---
 
@@ -343,11 +349,12 @@ Example: `feature/42-add-user-auth`
 
 <!-- session-logging: enabled -->
 
-All agents MUST log their activity to `.agents/session-log.md`. This file is gitignored and temporary.
+All agents MUST log their activity to `.agents/session-log.md`.
 
 **Check before logging:** Read the `session-logging` comment above. If it says `disabled`, skip all logging.
 
-**On first write per session**, create the file with the header:
+**Every agent MUST create or append to this file when it starts, no exceptions.** If the file does not exist, create it with this exact header first:
+
 ```markdown
 # Session Log
 
@@ -355,18 +362,21 @@ All agents MUST log their activity to `.agents/session-log.md`. This file is git
 |-----------|-------|--------|--------|
 ```
 
+Then immediately append a `started` row.
+
 **Log these events** by appending a row:
-- Lead spawns an agent → `| {ISO timestamp} | lead | spawned | {agent-name} for {purpose} |`
+- Lead spawns an agent → `| {ISO timestamp} | lead | spawned | {agent-name}, {purpose} |`
 - Agent starts → `| {ISO timestamp} | {agent-name} | started | {task summary} |`
 - Agent loads a skill → `| {ISO timestamp} | {agent-name} | skill-loaded | {skill-name} |`
-- Agent completes → `| {ISO timestamp} | {agent-name} | completed | {files changed count} files |`
+- Agent completes → `| {ISO timestamp} | {agent-name} | completed | {files changed count} files, skills: {comma-separated skill names or none} |`
 - Agent blocked → `| {ISO timestamp} | {agent-name} | blocked | {reason} |`
 
 **Rules:**
+- Creating the file and logging `started` is mandatory, do it before any other work
 - Append only, never overwrite previous entries
 - One row per event, keep detail column short
 - Use ISO 8601 timestamps
-- The file is gitignored — never commit it
+- The file is gitignored, never commit it
 
 ---
 
@@ -401,7 +411,7 @@ Agents CANNOT:
 
 ### Platform CLI
 
-ALL platform interactions via CLI only. Browser MCP FORBIDDEN for any DevOps or GitHub operation.
+ALL platform interactions via CLI only. Browser MCP and webfetch FORBIDDEN for any DevOps or GitHub operation — use `gh` or `az` CLI exclusively, never fall back to HTTP requests.
 
 | Operation | Azure DevOps | GitHub |
 |-----------|-------------|--------|

package/package.json

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

package/src/index.js

@@ -1,5 +1,6 @@
 #!/usr/bin/env node
 import chalk from 'chalk'
+import { createRequire } from 'node:module'
 import { checkEnv } from './steps/check-env.js'
 import { checkPlatform } from './steps/check-platform.js'
 import { checkRtk } from './steps/check-rtk.js'
@@ -13,22 +14,24 @@ import { installBrowser } from './steps/install-browser.js'
 
 if (process.stdout.isTTY) console.clear()
 console.log()
+const require = createRequire(import.meta.url)
+const { version } = require('../package.json')
 const logo = chalk.hex('#fe3d57')
 const bannerLines = [
-  logo('        ▒▒▒▒▒▒▒          '),
+  logo('                             '),
   logo('        ▒▒▒▒▒▒▒▒▒▒▒▒▒        '),
   logo('        ▒▒▓       ▓▒▓        '),
   logo('   ▒▒▒▒▒▒▓▒▒▒▒▒▒▒▒▒▓▓▒▒▒▒▒   '),
   logo('  ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▓  '),
   logo(' ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▓▓ '),
-  logo(' ▓▒▒▒▒▒░░▒▒▒▒▒▒▒▒▒▒▒░░▒▒▒▒▓▓ '),
+  logo(' ▓▒▒▒▒░░░▒▒▒▒▒▒▒▒▒▒▒░░░▒▒▒▓▓ '),
   logo('  ▓▓▓▓▒▒▒▓▓▓▓▓▓▓▓▓▓▓▒▒▒▓▓▓▓  '),
-  logo('  ▓▒▒▒▒▒▒▒░▒▒▒▒▒▒▒░▒▒▒▒▒▒▓▓  '),
-  logo('  ▓▒▒▒▒▒▒░▓▒▒▓▒▓▒▒▒▒▒▒▒▒▒▓▓  '),
+  logo('  ▓▓▒▒▒▒▒▒░▒▒▒▒▒▒▒░▒▒▒▒▒▒▓▓  '),
   logo('  ▓▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▓   '),
-  logo('   ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓ '),
+  logo('  ▓▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▓   '),
+  logo('   ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓    '),
   '',
-  chalk.bold('        🧰 opencode-onboard'),
+  chalk.bold('        🧰 opencode-onboard') + chalk.dim(` v${version}`),
   chalk.dim('        Prepare your codebase for AI agents'),
 ]
 
@@ -51,7 +54,7 @@ if (process.stdin.isTTY) {
   })
 }
 
-try {
+try {
   // 1. Check Node + pnpm
   await checkEnv()
 

package/src/utils/copy.js

@@ -2,7 +2,7 @@ import fse from 'fs-extra'
 import path from 'path'
 
 // Folders never copied (skills handled separately by chooseSkillsProvider, .bootstrap is internal tooling)
-const ALWAYS_EXCLUDE = ['.bootstrap', 'skills']
+const ALWAYS_EXCLUDE = ['.bootstrap', 'skills', 'node_modules']
 
 /**
  * Copy content/ directory to destination, excluding skills (handled separately by chooseSkillsProvider)