@nextsparkjs/ai-workflow 0.1.0-beta.92 → 0.1.0-beta.95

package/README.md

@@ -71,16 +71,45 @@ claude/
 └── sessions/     # Created on setup (empty)
 ```
 
+## Auto-Sync on Update
+
+When you run `pnpm update` in a consumer project, this package automatically syncs your `.claude/` directory via postinstall. Framework-managed files are updated while your custom files and configs are preserved.
+
+Requirements for auto-sync:
+- `.claude/` must already exist (run `nextspark setup:ai` first)
+- `pnpm.onlyBuiltDependencies` must include `@nextsparkjs/ai-workflow` in your root `package.json`
+
+You can also trigger a manual sync at any time:
+
+```bash
+nextspark sync:ai
+```
+
+## Troubleshooting
+
+Set `NEXTSPARK_DEBUG=1` to enable verbose logging in the postinstall script:
+
+```bash
+NEXTSPARK_DEBUG=1 pnpm update @nextsparkjs/ai-workflow
+```
+
+This prints detection steps (project root, monorepo check, `.claude/` location) to help diagnose sync issues.
+
 ## For Monorepo Contributors
 
-If you're developing the NextSpark framework itself, use the sync script to copy your working `.claude/` directory into this package before publishing:
+The `packages/ai-workflow/claude/` directory is **intentionally gitignored** (except config JSONs). The source of truth is the repo's `.claude/` working directory. Content is synced into the package at two points:
+
+1. **`pnpm pkg:pack`** — `pack.sh` runs `sync.mjs` automatically before creating the tarball
+2. **`prepack` script** — `package.json` runs `sync.mjs` as a safety net before any `npm pack`
+
+This means the published npm package always contains all agents, commands, skills, etc. — even though git does not track them in `packages/ai-workflow/claude/`.
+
+To sync manually (e.g. for local testing):
 
 ```bash
 node packages/ai-workflow/scripts/sync.mjs
 ```
 
-This syncs agents, commands, skills, templates, workflows, docs, and schemas while preserving the consumer config templates (context.json, workspace.json, team.json, github.json).
-
 ## Versioning
 
 This package versions independently from `@nextsparkjs/core`. Agent, command, and skill updates ship here without requiring a core release.

package/claude/agents/api-tester.md

@@ -70,14 +70,12 @@ curl -s http://localhost:5173/api/health || echo "Server not ready"
 ### 2. Read Test Credentials
 
 ```typescript
-// Read API keys from config
-await Read('.claude/config/agents.json')
-
-// Extract test credentials
+// Read test credentials from active theme's dev config
+// Located in: contents/themes/{activeTheme}/config/dev.config.ts → devKeyring
 const testCredentials = {
   superadmin: {
     email: 'superadmin@cypress.com',
-    password: 'configured_password', // From agents.json (testing.superadmin.password)
+    password: 'configured_password', // From theme dev.config → devKeyring
     apiKey: 'sk_test_...'
   },
   admin: {
@@ -264,7 +262,7 @@ await Read(`${sessionPath}/plan.md`)          // For expected endpoints
 await Read(`${sessionPath}/context.md`)       // For backend status
 await Read(`${sessionPath}/progress.md`)      // For current progress
 await Read(`${sessionPath}/tests.md`)         // For existing test documentation
-await Read('.claude/config/agents.json')        // For test credentials
+// Read test credentials from active theme's dev.config.ts → devKeyring
 ```
 
 ### Step 2: Execute Tests

package/claude/agents/architecture-supervisor.md

@@ -368,35 +368,6 @@ See: core/lib/entities/system-fields.ts
 - Phase 14-15: QA (manual + automation)
 - Phase 16-19: Finalization (review + unit tests + docs + demo)
 
-## ClickUp Configuration (MANDATORY REFERENCE)
-
-**BEFORE any ClickUp interaction, you MUST read the pre-configured ClickUp details:**
-
-All ClickUp connection details are pre-configured in `.claude/.claude/config/agents.json`. **NEVER search or fetch these values manually.** Always use the values from the configuration file:
-
-- **Workspace ID**: `tools.clickup.workspaceId`
-- **Space ID**: `tools.clickup.space.id`
-- **List ID**: `tools.clickup.defaultList.id`
-- **User**: `tools.clickup.user.name` / `tools.clickup.user.id`
-
-**Usage Pattern:**
-```typescript
-// ❌ NEVER DO THIS - Don't search for workspace/space/list
-const hierarchy = await clickup.getWorkspaceHierarchy()
-const spaces = await clickup.searchSpaces()
-
-// ✅ ALWAYS DO THIS - Use pre-configured values from .claude/config/agents.json
-// Read `.claude/.claude/config/agents.json` to get:
-// - Workspace ID: tools.clickup.workspaceId
-// - Space ID: tools.clickup.space.id
-// - List ID: tools.clickup.defaultList.id
-
-await clickup.updateTask(taskId, {
-  // Use task ID from notification, workspace pre-configured
-  description: updatedDescription
-})
-```
-
 ## Your Core Mission
 
 You are the guardian and visionary of the project's architectural integrity. Your primary responsibilities are:
@@ -1375,7 +1346,6 @@ Remember: Translate business requirements into actionable technical plans. Maint
 ## Context Files
 
 Always reference:
-- `.claude/.claude/config/agents.json` - For ClickUp configuration (Workspace ID, Space ID, List ID, credentials)
 - `.claude/skills/clickup-integration/templates/task.md` - For task template structure (Implementation Plan + QA Plan)
 - `.claude/skills/clickup-integration/mcp.md` - For ClickUp MCP usage guide
 - `.claude/config/workflow.md` - For complete development workflow and phase responsibilities

package/claude/agents/backend-developer.md

@@ -80,30 +80,6 @@ At the start of task:execute, scope is documented in context.md showing allowed
 
 **If backend-validator or api-tester FAIL:** They will call you back to fix issues before retrying.
 
-## ClickUp Configuration (MANDATORY REFERENCE)
-
-**BEFORE any ClickUp interaction, you MUST read the pre-configured ClickUp details:**
-
-All ClickUp connection details are pre-configured in `.claude/.claude/config/agents.json`. **NEVER search or fetch these values manually.** Always use the values from the configuration file:
-
-- **Workspace ID**: `tools.clickup.workspaceId`
-- **Space ID**: `tools.clickup.space.id`
-- **List ID**: `tools.clickup.defaultList.id`
-- **User**: `tools.clickup.user.name` / `tools.clickup.user.id`
-
-**Usage Pattern:**
-```typescript
-// ❌ NEVER DO THIS - Don't search for workspace/space/list
-const hierarchy = await clickup.getWorkspaceHierarchy()
-
-// ✅ ALWAYS DO THIS - Use pre-configured values from .claude/config/agents.json
-// Read .claude/config/agents.json to get Workspace ID, Space ID, List ID
-// Then interact with tasks directly
-
-await clickup.updateTaskStatus(taskId, "in progress")
-await clickup.addComment(taskId, "🚀 Starting backend development")
-```
-
 ## Entity Presets (USE AS REFERENCE)
 
 **When creating or modifying entities, use presets as reference:**
@@ -255,7 +231,8 @@ await Read('.rules/testing.md')     // For testing requirements
 await Read('.rules/planning.md')    // For complex tasks (3+ steps)
 
 // 2. Determine project context
-const isCore = await checkProjectContext()
+const context = await Read('.claude/config/context.json')
+const isCore = context.context === 'monorepo'
 
 // 3. Use TodoWrite for complex tasks
 if (task.stepsCount >= 3) {
@@ -720,8 +697,8 @@ ${sessionPath}/progress.md
 **After implementing each endpoint, you MUST test it:**
 
 ```bash
-# Use super admin API key from .claude/.claude/config/agents.json (testing.apiKey)
-API_KEY="<read from .claude/.claude/config/agents.json: testing.apiKey>"
+# Use super admin API key from active theme dev.config → devKeyring
+API_KEY="<from active theme dev.config → devKeyring>"
 
 # Test GET
 curl -X GET http://localhost:5173/api/v1/users/USER_ID \
@@ -1011,7 +988,6 @@ Do you approve this security addition?
 ## Context Files
 
 Always reference:
-- `.claude/.claude/config/agents.json` - For test credentials and API keys
 - `.claude/config/workflow.md` - For complete development workflow v4.0 (19 phases)
 - `${sessionPath}/plan.md` - For technical plan
 - `${sessionPath}/context.md` - For coordination context

package/claude/agents/code-reviewer.md

@@ -75,30 +75,6 @@ grep -rn "@/contents" core/ --include="*.ts" --include="*.tsx"
 **Pre-conditions:** qa-automation (Phase 15) MUST be PASSED
 **Post-conditions:** unit-test-writer (Phase 17) follows after my review
 
-## ClickUp Configuration (MANDATORY REFERENCE)
-
-**BEFORE any ClickUp interaction, you MUST read the pre-configured ClickUp details:**
-
-All ClickUp connection details are pre-configured in `.claude/.claude/config/agents.json`. **NEVER search or fetch these values manually.** Always use the values from the configuration file:
-
-- **Workspace ID**: `tools.clickup.workspaceId`
-- **Space ID**: `tools.clickup.space.id`
-- **List ID**: `tools.clickup.defaultList.id`
-- **User**: `tools.clickup.user.name` / `tools.clickup.user.id`
-
-**Usage Pattern:**
-```typescript
-// ❌ NEVER DO THIS - Don't search for workspace/space/list
-const hierarchy = await clickup.getWorkspaceHierarchy()
-
-// ✅ ALWAYS DO THIS - Use pre-configured values from .claude/config/agents.json
-// Read .claude/config/agents.json to get Workspace ID, Space ID, List ID
-// Then read task and add review comments
-
-const task = await clickup.getTaskById(taskId)
-await clickup.addComment(taskId, reviewMarkdown)
-```
-
 ## Core Responsibilities
 
 ### 1. Project Context Detection (CRITICAL FIRST STEP)
@@ -861,9 +837,7 @@ Structure your review as follows:
 - Performance acceptable
 - Project rules followed
 
-## Session-Based Workflow with ClickUp Integration (MANDATORY)
-
-**CRITICAL: Code Reviewer is one of the 3 agents that DOES write to ClickUp (PM, QA, Code Reviewer) - ONLY for review comments**
+## Session-Based Workflow (MANDATORY)
 
 ### When to Perform Code Review
 
@@ -1452,8 +1426,6 @@ export const ProfileForm = React.memo(({ user }: { user: User }) => {
 ## Context Files
 
 Always reference:
-- `.claude/.claude/config/agents.json` - For ClickUp configuration (Workspace ID, Space ID, List ID)
-- `.claude/skills/clickup-integration/mcp.md` - For ClickUp MCP usage guide (reading tasks, adding comments)
 - `.claude/config/workflow.md` - For complete development workflow (Phase 5: Code Review)
 - `.rules/` directory - For all project rules to validate against
 

package/claude/agents/db-developer.md

@@ -387,7 +387,7 @@ VALUES
 
   -- Super Admin (for Cypress tests) - uses different password
   ('55555555-5555-5555-5555-555555555555', 'Cypress Super Admin', 'superadmin@cypress.com', true,
-   -- This user may have a different password configured in agents.json
+   -- This user may have a different password configured in theme dev.config → devKeyring
    '3db9e98e2b4d3caca97fdf2783791cbc:34b293de615caf277a237773208858e960ea8aa10f1f5c5c309b632f192cac34d52ceafbd338385616f4929e4b1b6c055b67429c6722ffdb80b01d9bf4764866',
    NOW(), NOW())
 ON CONFLICT ("id") DO NOTHING;

package/claude/agents/documentation-writer.md

@@ -97,23 +97,6 @@ This will ensure you follow the correct patterns for:
 
 ---
 
-## ClickUp Configuration
-
-**CRITICAL**: Before starting work, read the ClickUp configuration:
-
-```typescript
-await Read('.claude/config/agents.json')
-```
-
-This file contains:
-- Pre-configured workspace ID
-- Team member IDs and names
-- ClickUp list IDs for different task types
-
-Use these IDs instead of looking them up each time.
-
----
-
 ## Parallel Execution with Task Tool
 
 You have access to the `Task` and `TaskOutput` tools for parallel execution. Use them wisely.
@@ -1099,13 +1082,7 @@ Before starting work, read these configuration files:
 await Read('core/docs/15-documentation-system/01-overview.md')
 await Read('core/docs/15-documentation-system/03-core-vs-theme-docs.md')
 
-// 2. ClickUp configuration (workspace ID, team members, list IDs)
-await Read('.claude/config/agents.json')
-
-// 3. ClickUp MCP tool documentation (how to use ClickUp tools)
-await Read('.claude/skills/clickup-integration/mcp.md')
-
-// 4. Session workflow guide (session file structure and patterns)
+// 2. Session workflow guide (session file structure and patterns)
 await Read('.claude/sessions/README.md')
 ```
 

package/claude/agents/frontend-developer.md

@@ -70,30 +70,6 @@ You are an elite Frontend Developer specializing in Next.js 15, TypeScript, Tail
 
 **If frontend-validator or functional-validator FAIL:** They will call you back to fix issues before retrying.
 
-## ClickUp Configuration (MANDATORY REFERENCE)
-
-**BEFORE any ClickUp interaction, you MUST read the pre-configured ClickUp details:**
-
-All ClickUp connection details are pre-configured in `.claude/.claude/config/agents.json`. **NEVER search or fetch these values manually.** Always use the values from the configuration file:
-
-- **Workspace ID**: `tools.clickup.workspaceId`
-- **Space ID**: `tools.clickup.space.id`
-- **List ID**: `tools.clickup.defaultList.id`
-- **User**: `tools.clickup.user.name` / `tools.clickup.user.id`
-
-**Usage Pattern:**
-```typescript
-// ❌ NEVER DO THIS - Don't search for workspace/space/list
-const hierarchy = await clickup.getWorkspaceHierarchy()
-
-// ✅ ALWAYS DO THIS - Use pre-configured values from .claude/config/agents.json
-// Read .claude/config/agents.json to get Workspace ID, Space ID, List ID
-// Then update task status and add comments directly with task ID
-
-await clickup.updateTaskStatus(taskId, "in progress")
-await clickup.addComment(taskId, "🚀 Starting frontend development")
-```
-
 ## Context Awareness
 
 **CRITICAL:** Before creating any components or files, read `.claude/config/context.json` to understand the environment.
@@ -1249,7 +1225,6 @@ Do you approve this addition or prefer I remove it?
 ## Context Files
 
 Always reference:
-- `.claude/.claude/config/agents.json` - For test credentials and configuration
 - `.claude/config/workflow.md` - For complete development workflow v4.0 (19 phases)
 - `${sessionPath}/plan.md` - For technical plan
 - `${sessionPath}/context.md` - For coordination context

package/claude/agents/product-manager.md

@@ -145,36 +145,26 @@ await Read('core/docs/13-plugins/01-plugin-overview.md')
 | Page customization | `core/docs/18-page-builder/` |
 | Development phases | `.rules/planning.md` |
 
-## ClickUp Configuration (MANDATORY REFERENCE)
+## Task Manager Configuration (MANDATORY REFERENCE)
 
-**BEFORE any ClickUp interaction, you MUST read the pre-configured ClickUp details:**
+**BEFORE any task manager interaction, you MUST read the workspace configuration:**
 
-All ClickUp connection details are pre-configured in `.claude/.claude/config/agents.json`. **NEVER search or fetch these values manually.** Always use the values from the configuration file:
+```typescript
+// 1. Read workspace config for task manager settings
+const workspace = await Read('.claude/config/workspace.json')
+// → workspace.taskManager.provider (e.g., "clickup", "jira", "asana")
+// → workspace.taskManager.config (provider-specific settings: workspaceId, defaultList, etc.)
 
-- **Workspace ID**: `tools.clickup.workspaceId`
-- **Space ID**: `tools.clickup.space.id`
-- **List ID**: `tools.clickup.defaultList.id`
-- **User**: `tools.clickup.user.name` / `tools.clickup.user.id`
+// 2. Read team config for user mapping
+const team = await Read('.claude/config/team.json')
+// → Find active user via workspace.activeUser → team.members[].ids.taskManager
 
-**Usage Pattern:**
-```typescript
-// ❌ NEVER DO THIS - Don't search for workspace/space/list
-const hierarchy = await clickup.getWorkspaceHierarchy()
-const spaces = await clickup.searchSpaces()
-
-// ✅ ALWAYS DO THIS - Use pre-configured values from .claude/config/agents.json
-// Read `.claude/.claude/config/agents.json` to get:
-// - Workspace ID: tools.clickup.workspaceId
-// - Space ID: tools.clickup.space.id
-// - List ID: tools.clickup.defaultList.id
-
-await clickup.createTask({
-  list_id: "<read from agents.json: tools.clickup.defaultList.id>", // From .claude/config/agents.json
-  name: "Task name",
-  // ... rest of task config
-})
+// 3. Load the integration skill matching the provider
+// e.g., .claude/skills/clickup-integration/SKILL.md
 ```
 
+**NEVER hardcode provider-specific IDs.** Always read from `workspace.json → taskManager.config`.
+
 ## Core Responsibilities
 
 You are responsible for:
@@ -262,10 +252,11 @@ If a consumer project identifies a core improvement:
 ## Task Creation Guidelines
 
 Before creating any task, you MUST:
-1. Read and understand `.claude/.claude/config/agents.json` for ClickUp configuration (IDs, credentials)
-2. Read the task template from `.claude/skills/clickup-integration/templates/task.md`
-3. Determine the correct ClickUp board based on project context
-4. Follow the task template structure specified in the template file
+1. Read `.claude/config/workspace.json` for task manager configuration (`taskManager.provider`, `taskManager.config`)
+2. Read `.claude/config/team.json` to resolve user IDs from `activeUser`
+3. Read the task template from the matching integration skill (e.g., `.claude/skills/clickup-integration/templates/task.md`)
+4. Determine the correct board/list based on `workspace.json → taskManager.config`
+5. Follow the task template structure specified in the template file
 
 ### Task Template Structure
 
@@ -366,8 +357,9 @@ Before finalizing any task, verify:
 ## Context Files
 
 Always reference:
-- `.claude/.claude/config/agents.json` - For ClickUp configuration (Workspace ID, Space ID, List ID, credentials)
-- `.claude/skills/clickup-integration/templates/task.md` - For task template structure
+- `.claude/config/workspace.json` - For task manager configuration (`taskManager.provider`, `taskManager.config`)
+- `.claude/config/team.json` - For user mapping (`activeUser` → `members[].ids.taskManager`)
+- `.claude/skills/clickup-integration/templates/task.md` - For task template structure (when using ClickUp)
 - `.claude/skills/clickup-integration/mcp.md` - For ClickUp MCP usage guide
 - `.claude/config/workflow.md` - For complete development workflow
 - Project-specific CLAUDE.md files - For understanding the codebase architecture and existing patterns (to ensure requirements align with technical capabilities)
@@ -375,10 +367,10 @@ Always reference:
 ## ClickUp Task Creation Workflow
 
 ### Step 1: Read Configuration
-1. Load `.claude/.claude/config/agents.json` to get ClickUp IDs
-2. Load `.claude/skills/clickup-integration/templates/task.md` to get task template
-3. Determine project context (core vs client)
-4. Identify correct ClickUp board (Boilerplate for core)
+1. Load `.claude/config/workspace.json` to get task manager settings (`taskManager.provider`, `taskManager.config`)
+2. Load `.claude/config/team.json` to resolve active user's task manager ID
+3. Load the task template from the matching integration skill
+4. Determine project context (core vs client) from `.claude/config/context.json`
 
 ### Step 2: Create Task in ClickUp (IN SPANISH)
 1. Use ClickUp MCP `createTask`
@@ -387,7 +379,7 @@ Always reference:
    - **Initial Status:** **backlog**
    - **Priority:** High/Medium/Low based on business impact
    - **Tags:** feature/bug/enhancement/refactor
-   - **Assign to:** User from `tools.clickup.user.name` (ID: `tools.clickup.user.id`)
+   - **Assign to:** Active user (from `workspace.json → activeUser` → `team.json → members[].ids.taskManager`)
    - **Context:** Why, Impact, Benefits, User Story
    - **Acceptance Criteria:** NUMBERED LIST focused on business (NOT technical, NOT checkboxes)
 3. Leave **Implementation Plan** and **QA Plan** EMPTY (for architecture-supervisor)
@@ -548,7 +540,7 @@ cp .claude/templates/clickup_task.md \
 **Created By:** product-manager
 **Task ID:** 86abc123
 **Task URL:** https://app.clickup.com/t/86abc123
-**Assigned To:** <read from agents.json: tools.clickup.user.name> (ID: <read from agents.json: tools.clickup.user.id>)
+**Assigned To:** <from workspace.json activeUser + team.json taskManager ID>
 **Status:** backlog
 **Priority:** normal
 
@@ -839,7 +831,7 @@ cp .claude/templates/scope.json \
 - Task ID: 86abc123
 - URL: https://app.clickup.com/t/86abc123
 - Status: backlog
-- Assigned: <read from agents.json: tools.clickup.user.name>
+- Assigned: <from workspace.json activeUser>
 
 **Session:**
 - Folder: .claude/sessions/2025-01-19-user-profile-edit-v1/
@@ -922,7 +914,7 @@ await clickup.addComment(taskId, `
 Task ID: 86abc123
 URL: https://app.clickup.com/t/86abc123
 Status: backlog
-Assigned: <read from agents.json: tools.clickup.user.name>
+Assigned: <from workspace.json activeUser>
 File: \`clickup_task_feature.md\`
 
 Next step: Architecture-supervisor will create the technical plan
@@ -934,9 +926,9 @@ When using ClickUp MCP to create tasks:
 ```typescript
 // Example task creation
 const task = await clickup.createTask({
-  list_id: "<read from agents.json: tools.clickup.defaultList.id>", // From .claude/config/agents.json
+  list_id: "<from workspace.json → taskManager.config.defaultList>",
   name: "Implementar edición de perfil de usuario",
-  assignees: ["<read from agents.json: tools.clickup.user.id>"], // From .claude/config/agents.json
+  assignees: ["<from team.json → members[activeUser].ids.taskManager>"],
   markdown_description: `  // ⚠️ CRITICAL: Use markdown_description, NOT description
 ## 📋 Contexto
 

package/claude/agents/workflow-maintainer.md

@@ -67,8 +67,6 @@ Use thorough analysis before implementing ANY change.
 ├── agents/                                 # 22+ agent definitions
 ├── commands/                               # Slash commands
 ├── config/
-│   ├── agents.json                         # Credentials & IDs (NEVER commit)
-│   ├── agents.example.json                 # Template for new developers
 │   ├── workflow.md                         # Workflow documentation
 │   └── workflow.example.md                 # Template
 ├── sessions/                               # Session data (gitignored)
@@ -94,8 +92,6 @@ packages/ai-workflow/claude/                # PUBLISHABLE PACKAGE (synced from .
 |----------|---------|------------|
 | `.claude/` | Developer's working directory | **gitignored** |
 | `packages/ai-workflow/claude/` | Publishable package (synced from `.claude/`) | **committed** |
-| `.claude/config/agents.json` | Real credentials | **gitignored** |
-| `.claude/config/agents.example.json` | Placeholder template | can be committed |
 
 ---
 
@@ -105,14 +101,14 @@ packages/ai-workflow/claude/                # PUBLISHABLE PACKAGE (synced from .
 
 ```typescript
 // Step 1: Check if this is the core framework
-await Read('.claude/config/agents.json')
-// Look for: "isCore": true in project section
+await Read('.claude/config/context.json')
+// Look for: "context": "monorepo" (core) or "consumer" (derived)
 
 // Step 2: Verify ai-workflow package exists
 await Glob('packages/ai-workflow/claude/**/*')
 
 // Step 3: Determine action
-if (projectIsCore && aiWorkflowExists) {
+if (context === 'monorepo' && aiWorkflowExists) {
   // This is the CORE FRAMEWORK - remind to run sync before publishing
   // After modifying .claude/, run: node packages/ai-workflow/scripts/sync.mjs
 } else {
@@ -127,31 +123,15 @@ if (projectIsCore && aiWorkflowExists) {
 
 **Agents must NEVER contain hardcoded configuration data.**
 
-### Configuration Structure (`agents.json`)
-
-```json
-{
-  "project": {
-    "name": "Project Name",
-    "isCore": true|false
-  },
-  "testing": {
-    "superadmin": {
-      "email": "superadmin@cypress.com",
-      "password": "..."
-    },
-    "apiKey": "sk_test_..."
-  },
-  "tools": {
-    "clickup": {
-      "workspaceId": "...",
-      "space": { "name": "...", "id": "..." },
-      "defaultList": { "name": "...", "id": "..." },
-      "user": { "name": "...", "id": "..." }
-    }
-  }
-}
-```
+### Configuration Sources
+
+| Data | Source |
+|------|--------|
+| Project type (monorepo/consumer) | `.claude/config/context.json` → `context` |
+| Task manager settings | `.claude/config/workspace.json` → `taskManager` |
+| Active user & team members | `.claude/config/workspace.json` → `activeUser` + `.claude/config/team.json` |
+| Test credentials & API keys | Active theme `dev.config.ts` → `devKeyring` |
+| Git workflow conventions | `.claude/config/github.json` |
 
 ### Reference Patterns in Agents
 
@@ -159,12 +139,11 @@ if (projectIsCore && aiWorkflowExists) {
 # ❌ NEVER DO THIS - Hardcoded values
 - Workspace ID: 90132320273
 - User: Pablo Capello (ID: 3020828)
-API_KEY="sk_test_62fc..."
 
 # ✅ ALWAYS DO THIS - JSON path references
-- **Workspace ID**: `tools.clickup.workspaceId`
-- **User**: `tools.clickup.user.name` / `tools.clickup.user.id`
-API_KEY="<read from agents.json: testing.apiKey>"
+- **Task Manager Config**: `workspace.json → taskManager.config`
+- **Active User**: `workspace.json → activeUser` + `team.json → members[].ids`
+- **Test Credentials**: Active theme `dev.config.ts` → `devKeyring`
 ```
 
 ---
@@ -307,8 +286,8 @@ await Write({
 ### 4. Modifying Configuration
 
 ```typescript
-// Step 1: ONLY modify .claude/config/agents.json for real values
-// Step 2: Update .claude/config/agents.example.json with structure changes
+// Step 1: Modify .claude/config/workspace.json for task manager settings
+// Step 2: Update .claude/config/team.json for team member changes
 // Step 3: If core project, run sync to update ai-workflow package
 
 // NEVER put real credentials in: