opencastle 0.6.0 → 0.8.0

package/src/cli/update.ts

@@ -1,18 +1,29 @@
 import { resolve } from 'node:path'
 import { readFile } from 'node:fs/promises'
 import { readManifest, writeManifest } from './manifest.js'
-import { confirm, closePrompts } from './prompt.js'
-import type { CliContext, IdeAdapter } from './types.js'
+import { confirm, closePrompts, c } from './prompt.js'
+import { isLegacyStack, migrateStackConfig } from './types.js'
+import type { CliContext, IdeAdapter, IdeChoice } from './types.js'
 
 const ADAPTERS: Record<string, () => Promise<IdeAdapter>> = {
   vscode: () => import('./adapters/vscode.js') as Promise<IdeAdapter>,
   cursor: () => import('./adapters/cursor.js') as Promise<IdeAdapter>,
   'claude-code': () =>
     import('./adapters/claude-code.js') as Promise<IdeAdapter>,
+  opencode: () =>
+    import('./adapters/opencode.js') as Promise<IdeAdapter>,
 }
 
 const VALID_IDES = Object.keys(ADAPTERS)
 
+/** IDE display labels */
+const IDE_DISPLAY: Record<IdeChoice, string> = {
+  vscode: 'VS Code',
+  cursor: 'Cursor',
+  'claude-code': 'Claude Code',
+  opencode: 'OpenCode',
+}
+
 export default async function update({
   pkgRoot,
   args,
@@ -22,18 +33,27 @@ export default async function update({
   const manifest = await readManifest(projectRoot)
   if (!manifest) {
     console.error(
-      '  ✗ No OpenCastle installation found. Run "npx opencastle init" first.'
+      `  ${c.red('✗')} No OpenCastle installation found. Run "npx opencastle init" first.`
     )
     process.exit(1)
   }
 
-  if (!manifest.ide || !VALID_IDES.includes(manifest.ide)) {
+  // Determine list of IDEs to update (support legacy single-IDE manifests)
+  const ides = manifest.ides?.length ? manifest.ides : [manifest.ide]
+  const invalidIdes = ides.filter((id) => !VALID_IDES.includes(id))
+  if (invalidIdes.length > 0) {
     console.error(
-      `  ✗ Invalid IDE "${manifest.ide}" in .opencastle.json. Valid options: ${VALID_IDES.join(', ')}`
+      `  ${c.red('✗')} Invalid IDE(s) "${invalidIdes.join(', ')}" in .opencastle.json. Valid: ${VALID_IDES.join(', ')}`
     )
     process.exit(1)
   }
 
+  // Migrate legacy stack config if needed
+  if (manifest.stack && isLegacyStack(manifest.stack)) {
+    manifest.stack = migrateStackConfig(manifest.stack, manifest.ide)
+    manifest.stack.ides = ides as IdeChoice[]
+  }
+
   const pkg = JSON.parse(
     await readFile(resolve(pkgRoot, 'package.json'), 'utf8')
   ) as { version: string }
@@ -45,23 +65,24 @@ export default async function update({
     return
   }
 
+  const ideNames = ides.map((id) => IDE_DISPLAY[id as IdeChoice] ?? id).join(', ')
   console.log(
-    `\n  🏰 OpenCastle ${dryRun ? 'dry-run' : 'update'}: v${manifest.version} → v${pkg.version}\n`
+    `\n  🏰 ${c.bold('OpenCastle')} ${dryRun ? 'dry-run' : 'update'}: ${c.dim(`v${manifest.version}`)} → ${c.green(`v${pkg.version}`)}\n`
   )
-  console.log(`  IDE: ${manifest.ide}`)
-  console.log('  Framework files will be overwritten.')
-  console.log('  Customization files will be preserved.\n')
+  console.log(`  IDEs: ${c.cyan(ideNames)}`)
+  console.log(`  ${c.dim('Framework files will be overwritten.')}`)
+  console.log(`  ${c.dim('Customization files will be preserved.')}\n`)
 
   if (dryRun) {
-    console.log('  [dry-run] Framework files that would be updated:\n')
+    console.log(`  ${c.dim('[dry-run]')} Framework files that would be updated:\n`)
     for (const p of manifest.managedPaths?.framework ?? []) {
-      console.log(`    ↻ ${p}`)
+      console.log(`    ${c.yellow('↻')} ${p}`)
     }
-    console.log('\n  Customization files that would be preserved:\n')
+    console.log(`\n  ${c.dim('[dry-run]')} Customization files that would be preserved:\n`)
     for (const p of manifest.managedPaths?.customizable ?? []) {
-      console.log(`    ✓ ${p}`)
+      console.log(`    ${c.green('✓')} ${p}`)
     }
-    console.log('\n  No files were written.\n')
+    console.log(`\n  ${c.dim('No files were written.')}\n`)
     return
   }
 
@@ -71,8 +92,21 @@ export default async function update({
     return
   }
 
-  const adapter = await ADAPTERS[manifest.ide]()
-  const results = await adapter.update(pkgRoot, projectRoot, manifest.stack)
+  // Update each IDE
+  let totalCopied = 0
+  let totalCreated = 0
+  const allManagedPaths = { framework: [] as string[], customizable: [] as string[] }
+
+  for (const ide of ides) {
+    const adapter = await ADAPTERS[ide]()
+    const results = await adapter.update(pkgRoot, projectRoot, manifest.stack)
+    totalCopied += results.copied.length
+    totalCreated += results.created.length
+
+    const managed = adapter.getManagedPaths()
+    allManagedPaths.framework.push(...managed.framework)
+    allManagedPaths.customizable.push(...managed.customizable)
+  }
 
   // Refresh repo research on update
   const { detectRepoInfo, mergeStackIntoRepoInfo } = await import('./detect.js')
@@ -80,16 +114,33 @@ export default async function update({
 
   // Update manifest
   manifest.version = pkg.version
+  manifest.ides = ides
   manifest.updatedAt = new Date().toISOString()
-  manifest.managedPaths = adapter.getManagedPaths()
+  manifest.managedPaths = allManagedPaths
   manifest.repoInfo = manifest.stack
     ? mergeStackIntoRepoInfo(repoInfo, manifest.stack)
     : repoInfo
   await writeManifest(projectRoot, manifest)
 
-  console.log(`\n  ✓ Updated ${results.copied.length} framework files`)
-  if (results.created.length > 0) {
-    console.log(`  + Created ${results.created.length} new files`)
+  console.log(`\n  ${c.green('✓')} Updated ${c.bold(String(totalCopied))} framework files`)
+  if (totalCreated > 0) {
+    console.log(`  ${c.green('+')} Created ${c.bold(String(totalCreated))} new files`)
+  }
+
+  // ── Reload window message ─────────────────────────────────────
+  const needsReload = ides.filter((id) => ['vscode', 'cursor'].includes(id))
+  if (needsReload.length > 0) {
+    console.log()
+    if (needsReload.includes('vscode')) {
+      console.log(
+        `  ${c.yellow('⟳')} Reload VS Code window (Cmd+Shift+P → "Developer: Reload Window") to pick up changes`
+      )
+    }
+    if (needsReload.includes('cursor')) {
+      console.log(
+        `  ${c.yellow('⟳')} Reload Cursor window to pick up the updated rule files`
+      )
+    }
   }
   console.log()
 

package/src/dashboard/node_modules/.vite/deps/_metadata.json

@@ -1,25 +1,25 @@
 {
-  "hash": "b74383b1",
+  "hash": "ef84f2a1",
   "configHash": "30f8ea04",
-  "lockfileHash": "280174fa",
-  "browserHash": "2ec9de9d",
+  "lockfileHash": "fc571d9a",
+  "browserHash": "822a1467",
   "optimized": {
     "astro > cssesc": {
       "src": "../../../../../node_modules/cssesc/cssesc.js",
       "file": "astro___cssesc.js",
-      "fileHash": "bb46d6fb",
+      "fileHash": "d234c1d0",
       "needsInterop": true
     },
     "astro > aria-query": {
       "src": "../../../../../node_modules/aria-query/lib/index.js",
       "file": "astro___aria-query.js",
-      "fileHash": "8270e9c7",
+      "fileHash": "bcc57b41",
       "needsInterop": true
     },
     "astro > axobject-query": {
       "src": "../../../../../node_modules/axobject-query/lib/index.js",
       "file": "astro___axobject-query.js",
-      "fileHash": "1cfcd59d",
+      "fileHash": "196f4f3c",
       "needsInterop": true
     }
   },

package/src/orchestrator/agent-workflows/README.md

@@ -1,4 +1,4 @@
-<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .github/customizations/ directory instead. -->
 
 # Workflow Templates
 

package/src/orchestrator/agent-workflows/bug-fix.md

@@ -1,4 +1,4 @@
-<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .github/customizations/ directory instead. -->
 
 # Workflow: Bug Fix
 
@@ -29,23 +29,23 @@ Follow the **Delivery Outcome** in `general.instructions.md` and the **Branch Ow
 
 ### Steps
 
-1. Check `docs/KNOWN-ISSUES.md` for existing entry
-2. Check Linear for existing bug ticket
+1. Check `.github/customizations/KNOWN-ISSUES.md` for existing entry
+2. Check tracker for existing bug ticket
 3. Read `.github/customizations/LESSONS-LEARNED.md` for related pitfalls
 4. **Reproduce the bug** — this is mandatory before any fix attempt:
-   a. Start the dev server: `yarn nx run <app>:serve`
+   a. Start the dev server (see the **codebase-tool** skill for the serve command)
    b. Navigate to the affected page in Chrome
    c. Follow the reproduction steps from the bug report
    d. **Confirm the failure** — screenshot the broken state as evidence
    e. If the bug **cannot be reproduced**, document what was tried and ask the reporter for more detail. Do NOT proceed to Phase 2 without reproduction
 5. Assess severity (Critical/High/Medium/Low)
-6. Create Linear issue with `[Bug]` prefix and `bug` label, including reproduction steps and screenshot
+6. Create tracker issue with `[Bug]` prefix and `bug` label, including reproduction steps and screenshot
 
 ### Exit Criteria
 
 - [ ] Bug **confirmed reproduced** with screenshot evidence (or documented as non-reproducible with investigation notes)
 - [ ] Severity assessed
-- [ ] Linear issue created with reproduction steps and screenshot
+- [ ] Tracker issue created with reproduction steps and screenshot
 - [ ] Affected apps identified (see `project.instructions.md` for inventory)
 
 ---
@@ -66,7 +66,7 @@ Follow the **Delivery Outcome** in `general.instructions.md` and the **Branch Ow
    - Race condition (timing, hydration mismatch)
    - CSS/Layout (specificity, overflow, responsive)
    - Integration (API contract mismatch, schema drift)
-5. Update Linear issue with root cause and affected files
+5. Update tracker issue with root cause and affected files
 
 ### Exit Criteria
 
@@ -109,17 +109,17 @@ Follow the **Delivery Outcome** in `general.instructions.md` and the **Branch Ow
 3. Verify the bug is fixed in Chrome (screenshot the working state)
 4. Test adjacent features for regressions
 5. If security-related: schedule panel review
-6. Move Linear issue to Done
-7. Update `docs/KNOWN-ISSUES.md` if the bug was listed there
+6. Move tracker issue to Done
+7. Update `.github/customizations/KNOWN-ISSUES.md` if the bug was listed there
 8. Commit and push
 
 ### Exit Criteria
 
 - [ ] Bug confirmed fixed with screenshot
 - [ ] No regressions introduced
-- [ ] Linear issue moved to Done
+- [ ] Tracker issue moved to Done
 - [ ] Known issues updated (if applicable)
-- [ ] Delivery Outcome completed (see `general.instructions.md`) — branch pushed, PR opened (not merged), Linear linked
+- [ ] Delivery Outcome completed (see `general.instructions.md`) — branch pushed, PR opened (not merged), tracker linked
 
 ---
 
@@ -127,4 +127,4 @@ Follow the **Delivery Outcome** in `general.instructions.md` and the **Branch Ow
 
 > **See [shared-delivery-phase.md](shared-delivery-phase.md) for the standard delivery steps.**
 >
-> Commit → Push → PR → Linear linkage. Team Lead owns delivery.
+> Commit → Push → PR → tracker linkage. Team Lead owns delivery.

package/src/orchestrator/agent-workflows/data-pipeline.md

@@ -1,8 +1,8 @@
-<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .github/customizations/ directory instead. -->
 
 # Workflow: Data Pipeline
 
-Standard execution plan for scraping, processing, and importing data.
+Standard execution plan for crowling, processing, and importing data.
 
 > **Project config:** For project-specific paths, data schema, CLI commands, and processing rules, see `data-pipeline-config.md`. For data model docs, see `docs-structure.md`.
 
@@ -10,7 +10,7 @@ Standard execution plan for scraping, processing, and importing data.
 
 ```
 Phase 1: Source Analysis    (sub-agent, inline)
-Phase 2: Scraping           (background agent)
+Phase 2: Crowling           (background agent)
 Phase 3: Processing         (sub-agent, sequential)
 Phase 4: Validation         (sub-agent, inline)
 Phase 5: Import             (sub-agent, inline)
@@ -37,34 +37,34 @@ Follow the **Delivery Outcome** in `general.instructions.md` and the **Branch Ow
 3. Check the data model documentation (see `docs-structure.md`) for required fields
 4. Estimate record count
 5. Check for existing scraper patterns (see **data-engineering** skill)
-6. Create Linear issue with data source details
+6. Create tracker issue with data source details
 
 ### Exit Criteria
 
 - [ ] Source structure documented
 - [ ] Field mapping defined (source field → target field)
 - [ ] Estimated record count
-- [ ] Linear issue created
-- [ ] Scraper approach decided (Puppeteer, fetch, API)
+- [ ] Tracker issue created
+- [ ] Scraper approach decided (browser-based, fetch, API)
 
 ---
 
-## Phase 2: Scraping
+## Phase 2: Crowling
 
 **Agent:** Data Expert
 **Type:** Background agent (may be long-running)
 
 ### Steps
 
-1. Implement scraper following existing patterns (see `data-pipeline-config.md`)
+1. Implement crowler following existing patterns (see `data-pipeline-config.md`)
 2. Output raw data as NDJSON
 3. Handle pagination, rate limiting, and error recovery
-4. Log scraping statistics (pages visited, records extracted, errors)
+4. Log crowling statistics (pages visited, records extracted, errors)
 
 ### Exit Criteria
 
 - [ ] Raw NDJSON file produced
-- [ ] Scraping statistics logged
+- [ ] Crowling statistics logged
 - [ ] No duplicate records
 - [ ] Output contract returned
 
@@ -78,18 +78,19 @@ Follow the **Delivery Outcome** in `general.instructions.md` and the **Branch Ow
 ### Steps
 
 1. Convert raw data to the target schema format
-2. Enrich with geocoding, slug generation, image optimization
-3. Normalize text fields (see data-pipeline-config.md for rules)
-4. Validate against place schema
-5. Output processed NDJSON
+2. Enrich with appropriate metadata (geocoding, slug generation)
+3. Images optimization
+4. Normalize text fields (see data-pipeline-config.md for rules)
+5. Validate against schema
+6. Output processed NDJSON
 
 ### Exit Criteria
 
-- [ ] Processed NDJSON matches place schema
+- [ ] Processed NDJSON matches schema
 - [ ] All required fields present
 - [ ] Slugs are unique
-- [ ] Geocoding complete
-- [ ] Pipeline tests pass: `yarn nx run data-pipeline:test`
+- [ ] Metadata complete
+- [ ] Pipeline tests pass (run the project's test command — see **codebase-tool** skill)
 - [ ] Output contract returned with quality metrics
 
 ---
@@ -127,7 +128,7 @@ Follow the **Delivery Outcome** in `general.instructions.md` and the **Branch Ow
 2. Verify in CMS
 3. Import full dataset
 4. Log import statistics (created, updated, skipped, failed)
-5. Update Linear issue and roadmap
+5. Update tracker issue and roadmap
 
 ### Exit Criteria
 
@@ -136,7 +137,7 @@ Follow the **Delivery Outcome** in `general.instructions.md` and the **Branch Ow
 - [ ] Import statistics logged
 - [ ] <0.1% failure rate
 - [ ] Output contract returned
-- [ ] Delivery Outcome completed (see `general.instructions.md`) — branch pushed, PR opened (not merged), Linear linked
+- [ ] Delivery Outcome completed (see `general.instructions.md`) — branch pushed, PR opened (not merged), tracker linked
 
 ---
 
@@ -144,4 +145,4 @@ Follow the **Delivery Outcome** in `general.instructions.md` and the **Branch Ow
 
 > **See [shared-delivery-phase.md](shared-delivery-phase.md) for the standard delivery steps.**
 >
-> Commit → Push → PR → Linear linkage. Team Lead owns delivery.
+> Commit → Push → PR → tracker linkage. Team Lead owns delivery.

package/src/orchestrator/agent-workflows/database-migration.md

@@ -1,10 +1,10 @@
-<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .github/customizations/ directory instead. -->
 
 # Workflow: Database Migration
 
 Structured workflow for database schema changes, RLS policies, and data migrations.
 
-> **Project config:** For database-specific paths, schema details, and migration conventions, see the relevant database customization file (e.g., `supabase-config.md`).
+> **Project config:** For database-specific paths, schema details, and migration conventions, see the relevant database customization file in `customizations/stack/`.
 
 ## Phases
 
@@ -34,11 +34,11 @@ Follow the **Delivery Outcome** in `general.instructions.md` and the **Branch Ow
 
 1. Read current schema in the migrations directory (see database customization) to understand existing tables
 2. Check existing RLS policies using the database query tool
-3. Read `docs/PROJECT.md` for database architecture
-4. Check `docs/KNOWN-ISSUES.md` for database-related limitations
+3. Read `.github/customizations/project.instructions.md` for database architecture
+4. Check `.github/customizations/KNOWN-ISSUES.md` for database-related limitations
 5. Document the migration plan: tables affected, columns added/removed, RLS changes
 6. Write rollback strategy (how to reverse the migration)
-7. Create Linear issue with migration details and rollback plan
+7. Create tracker issue with migration details and rollback plan
 
 ### Exit Criteria
 
@@ -46,7 +46,7 @@ Follow the **Delivery Outcome** in `general.instructions.md` and the **Branch Ow
 - [ ] Migration plan documented
 - [ ] Rollback strategy defined
 - [ ] Impact on existing data assessed
-- [ ] Linear issue created with rollback plan
+- [ ] Tracker issue created with rollback plan
 
 ---
 
@@ -139,8 +139,8 @@ Follow the **Delivery Outcome** in `general.instructions.md` and the **Branch Ow
 3. Spot-check data using the database query tool
 4. Start dev server and verify end-to-end functionality
 5. **Security check:** If the migration touches auth or RLS, schedule panel review
-6. Document rollback procedure in Linear issue
-7. Move Linear issue to Done
+6. Document rollback procedure in tracker issue
+7. Move tracker issue to Done
 
 ### Exit Criteria
 
@@ -149,8 +149,8 @@ Follow the **Delivery Outcome** in `general.instructions.md` and the **Branch Ow
 - [ ] End-to-end flow works in browser
 - [ ] Panel review passed (if auth/RLS changes)
 - [ ] Rollback procedure documented
-- [ ] Linear issue moved to Done
-- [ ] Delivery Outcome completed (see `general.instructions.md`) — branch pushed, PR opened (not merged), Linear linked
+- [ ] Tracker issue moved to Done
+- [ ] Delivery Outcome completed (see `general.instructions.md`) — branch pushed, PR opened (not merged), tracker linked
 
 ---
 
@@ -158,4 +158,4 @@ Follow the **Delivery Outcome** in `general.instructions.md` and the **Branch Ow
 
 > **See [shared-delivery-phase.md](shared-delivery-phase.md) for the standard delivery steps.**
 >
-> Commit → Push → PR → Linear linkage. Team Lead owns delivery.
+> Commit → Push → PR → tracker linkage. Team Lead owns delivery.

package/src/orchestrator/agent-workflows/feature-implementation.md

@@ -1,4 +1,4 @@
-<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .github/customizations/ directory instead. -->
 
 # Workflow: Feature Implementation
 
@@ -77,7 +77,7 @@ Run the `brainstorm` prompt when the task has ambiguity, multiple valid approach
 
 ### Steps
 
-1. Read `docs/PROJECT.md`, `docs/KNOWN-ISSUES.md`, `.github/customizations/LESSONS-LEARNED.md`
+1. Read `.github/customizations/project.instructions.md`, `.github/customizations/KNOWN-ISSUES.md`, `.github/customizations/LESSONS-LEARNED.md`
 2. Search codebase for existing implementations
 3. Identify affected apps, libs, and layers
 4. **Spec flow analysis** — Trace the complete user flow end-to-end and identify:
@@ -86,8 +86,8 @@ Run the `brainstorm` prompt when the task has ambiguity, multiple valid approach
    - Edge cases (network failure, invalid data, concurrent access, empty collections)
    - Missing paths in the spec ("what happens when X?")
    - Accessibility flows (keyboard navigation, screen reader announcements)
-   - Document findings as acceptance criteria on the Linear issues
-5. Decompose into Linear issues with file partitions
+   - Document findings as acceptance criteria on the tracker issues
+5. Decompose into tracker issues with file partitions
 6. **Surface Open Questions** — Collect ambiguities, design choices, and assumptions that need user input. Present as a structured list for approval before proceeding.
 7. Create session checkpoint
 
@@ -112,7 +112,7 @@ If there are no open questions, explicitly state: "No open questions — plan is
 
 - [ ] All relevant docs read
 - [ ] **User flow traced** — all states, transitions, and edge cases documented
-- [ ] Linear issues created for every subtask (including edge case coverage)
+- [ ] Tracker issues created for every subtask (including edge case coverage)
 - [ ] File partitions mapped (no overlaps)
 - [ ] Dependencies identified
 - [ ] **Open questions answered** by user (or none identified)
@@ -202,19 +202,26 @@ If there are no open questions, explicitly state: "No open questions — plan is
 1. Review all output contracts from Phases 2-4
 2. Run full lint + test + build across all affected projects
 3. Verify no files outside partitions were modified
-4. Check all Linear issue acceptance criteria
+4. Check all tracker issue acceptance criteria
 5. Run panel review if high-stakes (security, DB, architecture)
-6. Move all issues to Done
-7. Update session checkpoint → delete checkpoint
-8. Update `docs/ROADMAP-POST-MVP.md`
+6. **Final Smoke Test (Gate 10)** — verify the complete feature end-to-end:
+   - Full clean build of all affected projects (not incremental)
+   - End-to-end browser walkthrough of the complete user flow
+   - Verify all states: loading, empty, populated, error, partial
+   - Cross-task integration check (e.g., migration + component + page compose correctly)
+   - Final responsive sweep at all breakpoints (if UI changes)
+7. Move all issues to Done
+8. Update session checkpoint → delete checkpoint
+9. Update `.github/customizations/project/roadmap.md`
 
 ### Exit Criteria
 
 - [ ] All phases verified
-- [ ] All Linear issues Done
+- [ ] All tracker issues Done
 - [ ] Full build passes
+- [ ] **Final smoke test passed** — complete user flow verified end-to-end
 - [ ] Roadmap updated
-- [ ] Delivery Outcome completed (see `general.instructions.md`) — branch pushed, PR opened (not merged), Linear linked
+- [ ] Delivery Outcome completed (see `general.instructions.md`) — branch pushed, PR opened (not merged), tracker linked
 
 ---
 
@@ -222,4 +229,4 @@ If there are no open questions, explicitly state: "No open questions — plan is
 
 > **See [shared-delivery-phase.md](shared-delivery-phase.md) for the standard delivery steps.**
 >
-> Commit → Push → PR → Linear linkage. Team Lead owns delivery.
+> Commit → Push → PR → tracker linkage. Team Lead owns delivery.

package/src/orchestrator/agent-workflows/performance-optimization.md

@@ -1,4 +1,4 @@
-<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .github/customizations/ directory instead. -->
 
 # Workflow: Performance Optimization
 
@@ -31,7 +31,7 @@ Follow the **Delivery Outcome** in `general.instructions.md` and the **Branch Ow
 
 1. Build the affected app(s) with production config
 2. Run Lighthouse audit on key pages
-3. Measure bundle size (`yarn nx run <app>:build` output)
+3. Measure bundle size (production build output — see the **codebase-tool** skill for the build command)
 4. Record Core Web Vitals: LCP, FID/INP, CLS, TTFB
 5. Profile server-side rendering time
 6. Document baseline metrics
@@ -45,7 +45,7 @@ Follow the **Delivery Outcome** in `general.instructions.md` and the **Branch Ow
 - [ ] Baseline metrics recorded for all key pages
 - [ ] Bundle size documented
 - [ ] Lighthouse scores saved
-- [ ] Linear issue created with targets
+- [ ] Tracker issue created with targets
 
 ---
 
@@ -114,9 +114,9 @@ Follow the **Delivery Outcome** in `general.instructions.md` and the **Branch Ow
 - [ ] Metrics improved (or justified why not)
 - [ ] No visual regressions
 - [ ] No functional regressions
-- [ ] Results documented in Linear issue
+- [ ] Results documented in tracker issue
 - [ ] Roadmap updated
-- [ ] Delivery Outcome completed (see `general.instructions.md`) — branch pushed, PR opened (not merged), Linear linked
+- [ ] Delivery Outcome completed (see `general.instructions.md`) — branch pushed, PR opened (not merged), tracker linked
 
 ---
 
@@ -124,4 +124,4 @@ Follow the **Delivery Outcome** in `general.instructions.md` and the **Branch Ow
 
 > **See [shared-delivery-phase.md](shared-delivery-phase.md) for the standard delivery steps.**
 >
-> Commit → Push → PR → Linear linkage. Team Lead owns delivery.
+> Commit → Push → PR → tracker linkage. Team Lead owns delivery.

package/src/orchestrator/agent-workflows/refactoring.md

@@ -1,4 +1,4 @@
-<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .github/customizations/ directory instead. -->
 
 # Workflow: Code Refactoring
 
@@ -32,16 +32,16 @@ Follow the **Delivery Outcome** in `general.instructions.md` and the **Branch Ow
 
 1. Identify all files and modules in scope for refactoring
 2. Document current behavior (screenshots, test outputs, API responses)
-3. Run baseline tests: `yarn nx run <project>:test --coverage`
-4. Run baseline lint: `yarn nx run <project>:lint`
+3. Run baseline tests (with coverage) for the project — see the **codebase-tool** skill for commands
+4. Run baseline lint for the project
 5. Record baseline metrics (test count, coverage %, lint errors, bundle size)
-6. Create Linear issues for the refactoring scope
+6. Create tracker issues for the refactoring scope
 
 ### Exit Criteria
 
 - [ ] Scope documented with file list
 - [ ] Baseline metrics recorded
-- [ ] Linear issues created
+- [ ] Tracker issues created
 
 ---
 
@@ -96,9 +96,9 @@ The refactoring agent owns only the scoped files. No changes outside the partiti
 
 ### Steps
 
-1. Run full test suite: `yarn nx run <project>:test`
-2. Run lint: `yarn nx run <project>:lint`
-3. Run build: `yarn nx run <project>:build`
+1. Run full test suite for the project
+2. Run lint for the project
+3. Run build for the project
 4. Compare metrics against Phase 1 baseline (test count, coverage, bundle size)
 5. For UI refactors: start dev server and visually verify at all breakpoints
 6. Verify no regressions in dependent code
@@ -133,7 +133,7 @@ The refactoring agent owns only the scoped files. No changes outside the partiti
 ### Exit Criteria
 
 - [ ] Panel PASS (2/3 majority)
-- [ ] Delivery Outcome completed (see `general.instructions.md`) — branch pushed, PR opened (not merged), Linear linked
+- [ ] Delivery Outcome completed (see `general.instructions.md`) — branch pushed, PR opened (not merged), tracker linked
 
 ---
 
@@ -141,4 +141,4 @@ The refactoring agent owns only the scoped files. No changes outside the partiti
 
 > **See [shared-delivery-phase.md](shared-delivery-phase.md) for the standard delivery steps.**
 >
-> Commit → Push → PR → Linear linkage. Team Lead owns delivery.
+> Commit → Push → PR → tracker linkage. Team Lead owns delivery.