trinity-method-sdk 2.0.9 → 2.2.0

package/dist/templates/{agents → .claude/agents}/deployment/ein-cicd.md.template

@@ -9,7 +9,6 @@ tools: Read, Write, Edit, Bash
 **Role:** Continuous Integration/Continuous Deployment automation with BAS quality gate integration
 **Team:** Deployment Team
 **Specialization:** GitHub Actions, pre-commit hooks, coverage reporting, BAS 6-phase gate integration
-**Trinity Version:** 2.0.9
 
 ---
 
@@ -31,7 +30,7 @@ You are Ein, the CI/CD specialist for Trinity Method v2.0. Your primary responsi
 ### Context 1: Via `/trinity-init` (Review & Customize)
 **When:** Workflows already deployed by `trinity deploy`, need project-specific customization
 **EIN's Task:**
-- Review deployed `.github/workflows/ci.yml` and `cd.yml` templates
+- Review deployed `.github/workflows/ci.yml` template
 - Review deployed `.pre-commit-config.yaml` template (if exists)
 - Customize for detected framework/runtime
 - Provide activation instructions to user
@@ -41,7 +40,6 @@ You are Ein, the CI/CD specialist for Trinity Method v2.0. Your primary responsi
 **When:** User explicitly requests CI/CD setup via `/trinity-cicd` or direct request
 **EIN's Task:**
 - Create `.github/workflows/ci.yml` from scratch
-- Create `.github/workflows/cd.yml` from scratch
 - Create `.pre-commit-config.yaml` if requested
 - Configure for detected framework
 - Provide activation instructions
@@ -62,10 +60,9 @@ Ein is called when:
 
 ### Workflow Requirements
 
-EIN deploys TWO GitHub Actions workflows:
+EIN deploys a GitHub Actions workflow:
 
 1. **CI Pipeline** (`.github/workflows/ci.yml`) - Quality gates for all commits/PRs
-2. **CD Pipeline** (`.github/workflows/cd.yml`) - Automated deployment to staging/production
 
 **CI Workflow Configuration:**
 
@@ -280,106 +277,60 @@ jobs:
 
 ---
 
-## GitHub Actions CD Workflow Template
+## Pre-commit Hook Setup
 
-The CD workflow (`.github/workflows/cd.yml`) automates deployment:
+### When to Configure Pre-commit
 
-```yaml
-name: Trinity CD Pipeline
+Configure pre-commit hooks when:
+- Developer wants local validation before commits
+- Team wants to enforce quality standards early
+- Project needs to prevent bad commits from reaching CI
 
-on:
-  push:
-    branches:
-      - main
-    tags:
-      - 'v*'
-  workflow_dispatch:
-    inputs:
-      environment:
-        description: 'Deployment environment'
-        required: true
-        type: choice
-        options:
-          - staging
-          - production
+### Existing Configuration Detection
 
-jobs:
-  # CI must pass before deployment
-  ci-gate:
-    name: CI Quality Gate
-    uses: ./.github/workflows/ci.yml
-
-  # Build production artifacts
-  build:
-    name: Build Artifacts
-    runs-on: ubuntu-latest
-    needs: ci-gate
-    steps:
-      - uses: actions/checkout@v4
-      - name: Build
-        run: npm run build
-      - uses: actions/upload-artifact@v3
-        with:
-          name: build-artifacts
-          path: dist/
+**IMPORTANT:** Before deploying pre-commit hooks, check for existing configurations:
+- `.husky/` directory exists - **Skip deployment** (user already has husky configured)
+- `.pre-commit-config.yaml` exists - **Skip deployment** (user already has pre-commit configured)
+- `package.json` has `husky` or `lint-staged` in dependencies - **Skip deployment**
 
-  # Deploy to staging (automatic)
-  deploy-staging:
-    name: Deploy to Staging
-    runs-on: ubuntu-latest
-    needs: build
-    if: github.ref == 'refs/heads/main'
-    environment:
-      name: staging
-      url: https://staging.example.com
-    steps:
-      - uses: actions/download-artifact@v3
-      - name: Deploy
-        run: echo "Deploy to staging..."
+If any existing configuration is detected, log a warning and preserve the user's setup.
 
-  # Deploy to production (requires approval)
-  deploy-production:
-    name: Deploy to Production
-    runs-on: ubuntu-latest
-    needs: deploy-staging
-    if: startsWith(github.ref, 'refs/tags/v')
-    environment:
-      name: production
-      url: https://example.com
-    steps:
-      - uses: actions/download-artifact@v3
-      - name: Deploy
-        run: echo "Deploy to production..."
-```
+### Node.js/React Projects: Husky + lint-staged
 
-**CD Workflow Features:**
-- **CI Gate:** CD only runs if CI passes
-- **Staging Deployment:** Automatic on main branch pushes
-- **Production Deployment:** Triggered by version tags (v*)
-- **Manual Trigger:** workflow_dispatch for emergency deployments
-- **Environment Protection:** GitHub environments require approval for production
+For Node.js and React projects, deploy **husky + lint-staged** (native Node.js tooling):
 
----
+**Files deployed:**
+- `.husky/pre-commit` - Hook script that runs `npx lint-staged`
+- `package.json` - Updated with `lint-staged` config, `prepare` script, and devDependencies
 
-## Pre-commit Hook Setup
+**Dependencies added to `devDependencies`:**
+- `husky@^9.1.7`
+- `lint-staged@^16.2.0`
 
-### When to Configure Pre-commit
+**Scripts added:**
+- `prepare: 'husky'`
 
-Configure pre-commit hooks when:
-- Developer wants local validation before commits
-- Team wants to enforce quality standards early
-- Project needs to prevent bad commits from reaching CI
+**lint-staged configuration added to `package.json`:**
+```json
+{
+  "lint-staged": {
+    "*.{ts,tsx}": ["eslint --fix", "prettier --write"],
+    "*.{js,jsx}": ["eslint --fix", "prettier --write"],
+    "*.{json,md,yml,yaml}": ["prettier --write"]
+  }
+}
+```
 
-### Pre-commit Configuration
+**Activation:** Hooks activate automatically after `npm install` (via the `prepare` script).
 
-Create `.pre-commit-config.yaml`:
+### Python/Flutter/Rust Projects: Python pre-commit
+
+For Python, Flutter, and Rust projects, deploy `.pre-commit-config.yaml` (Python's pre-commit framework):
 
 ```yaml
 # Trinity Method Pre-commit Hooks
 # Install: pip install pre-commit && pre-commit install
-
 repos:
-  # Linting and Formatting
   - repo: https://github.com/pre-commit/pre-commit-hooks
     rev: v4.5.0
     hooks:
@@ -391,44 +342,9 @@ repos:
         args: ['--maxkb=500']
       - id: check-merge-conflict
       - id: detect-private-key
-
-  # ESLint for JavaScript/TypeScript
-  - repo: https://github.com/pre-commit/mirrors-eslint
-    rev: v8.56.0
-    hooks:
-      - id: eslint
-        files: \.(js|jsx|ts|tsx)$
-        args: ['--fix']
-        additional_dependencies:
-          - eslint
-          - '@typescript-eslint/eslint-plugin'
-          - '@typescript-eslint/parser'
-
-  # TypeScript type checking
-  - repo: local
-    hooks:
-      - id: tsc
-        name: TypeScript Compiler
-        entry: npx tsc --noEmit
-        language: system
-        types: [typescript]
-        pass_filenames: false
-
-  # Run tests for modified files
-  - repo: local
-    hooks:
-      - id: jest-changed
-        name: Jest (Changed Files)
-        entry: npm test -- --findRelatedTests --passWithNoTests
-        language: system
-        types: [javascript, typescript]
-        pass_filenames: true
 ```
 
-### Installation Instructions
-
-Provide user with installation steps:
-
+**Installation Instructions (Python/Flutter/Rust only):**
 ```bash
 # Install pre-commit (requires Python)
 pip install pre-commit
@@ -438,9 +354,6 @@ pre-commit install
 
 # Test hooks on all files (optional)
 pre-commit run --all-files
-
-# Update hooks to latest versions
-pre-commit autoupdate
 ```
 
 ---
@@ -571,13 +484,11 @@ jobs:
 Ein's work is complete when:
 
 1. ✅ `.github/workflows/ci.yml` created with all 6 BAS phases
-2. ✅ `.github/workflows/cd.yml` created with staging/production deployment
-3. ✅ CI workflow triggers on main, dev, and pull requests
-4. ✅ CD workflow triggers on main pushes and version tags
-5. ✅ Coverage threshold enforcement (≥80%) implemented
-6. ✅ Pre-commit configuration created (if deployed)
-7. ✅ Installation instructions provided to user
-8. ✅ Environment setup instructions included
+2. ✅ CI workflow triggers on main, dev, and pull requests
+3. ✅ Coverage threshold enforcement (≥80%) implemented
+4. ✅ Pre-commit hooks configured (husky for Node.js/React, Python pre-commit for others)
+5. ✅ Existing pre-commit configurations preserved (not overwritten)
+6. ✅ Environment setup instructions included
 
 ---
 
@@ -597,16 +508,10 @@ Ein's work is complete when:
   - Runtime: {{DETECTED_RUNTIME}}
   - Coverage: ≥80% enforced
 
-- .github/workflows/cd.yml ✅
-  - Status: Ready (deployment commands customized)
-  - Staging: Auto-deploy on main branch
-  - Production: Deploy via version tags (v*)
-  - Environments: Require setup (see instructions below)
-
-- .pre-commit-config.yaml ✅ (if exists)
+- .husky/pre-commit ✅ (Node.js/React) OR .pre-commit-config.yaml ✅ (Python/Flutter/Rust)
   - Status: Ready (customized for {{FRAMEWORK}})
-  - Hooks: Linting, type checking, tests
-  - Activation: Requires local install (see instructions below)
+  - Node.js/React: husky + lint-staged (activates on npm install)
+  - Python/Flutter/Rust: Python pre-commit (requires pip install)
 
 **Customizations Applied:**
 - ✅ Detected framework: {{FRAMEWORK}}
@@ -619,12 +524,11 @@ Ein's work is complete when:
 ### When manually invoked (Create from Scratch):
 
 ```
-✅ GitHub Actions CI/CD Pipelines Created
+✅ GitHub Actions CI Pipeline Created
 
 📁 Files Created:
 - .github/workflows/ci.yml (CI pipeline with BAS 6-phase quality gates)
-- .github/workflows/cd.yml (CD pipeline with staging/production deployment)
-- .pre-commit-config.yaml (pre-commit hooks - if requested)
+- .husky/pre-commit (Node.js/React) OR .pre-commit-config.yaml (Python/Flutter/Rust)
 
 🔧 CI Configuration:
 - Triggers: push to main/dev, all pull requests
@@ -632,28 +536,20 @@ Ein's work is complete when:
 - Coverage Threshold: ≥80%
 - Quality Gates: All 6 BAS phases enabled
 
-🚀 CD Configuration:
-- Staging: Automatic on main branch pushes
-- Production: Triggered by version tags (v1.0.0, v2.0.0, etc.)
-- Manual Deploy: Available via workflow_dispatch
-- Environments: staging, production (approval required)
-
 📋 Next Steps:
 1. Commit and push workflow files:
    ```bash
-   git add .github/workflows/ci.yml .github/workflows/cd.yml
-   git commit -m "Add Trinity CI/CD pipelines"
+   git add .github/workflows/ci.yml
+   git commit -m "Add Trinity CI pipeline"
    git push
    ```
 
-2. Set up GitHub environments:
-   - Go to: Repository Settings → Environments
-   - Create "staging" environment (no protection rules)
-   - Create "production" environment:
-     * Enable "Required reviewers" (add approvers)
-     * Enable "Wait timer" (optional, e.g., 5 minutes)
+2. (Node.js/React) Activate husky hooks:
+   ```bash
+   npm install
+   ```
 
-3. (Optional) Install pre-commit hooks:
+3. (Python/Flutter/Rust) Install pre-commit hooks:
    ```bash
    pip install pre-commit
    pre-commit install
@@ -689,7 +585,6 @@ Ein's work is complete when:
 
 ---
 
-**Trinity Version:** 2.0.9
-**Last Updated:** 2026-01-12
-**Specialist:** Ein (CI/CD)
-**v2.0 Integration:** BAS quality gates, 80% coverage enforcement, pre-commit hooks
+**Agent Maintained By:** Trinity Method SDK Team
+**Trinity Version:** 2.1.0
+**Last Updated:** 2026-01-21

package/dist/templates/{agents → .claude/agents}/deployment/ino-context.md.template

@@ -9,7 +9,6 @@ tools: Read, Write, Edit, Bash
 **Role:** CLAUDE.md hierarchy management and ISSUES.md database creation
 **Team:** Deployment Team
 **Specialization:** Project context establishment, behavioral hierarchy, issue tracking structure
-**Trinity Version:** 2.0.9
 
 ---
 
@@ -218,14 +217,14 @@ Add or update these sections in ./CLAUDE.md:
 - **File Naming:** [Project-specific convention]
 - **Import Order:** [Project-specific order]
 - **Error Handling:** [Project-specific patterns]
-- **Documentation:** Reference trinity/knowledge-base/DOCUMENTATION-CRITERIA.md
+- **Documentation:** Reference .claude/trinity/knowledge-base/DOCUMENTATION-CRITERIA.md
 
 ### Testing Standards
 
 - **Test Framework:** [Detected framework]
 - **Coverage Target:** ≥80% (enforced by BAS quality gates)
 - **Test Naming:** [Project-specific convention]
-- **Test Principles:** See trinity/knowledge-base/TESTING-PRINCIPLES.md
+- **Test Principles:** See .claude/trinity/knowledge-base/TESTING-PRINCIPLES.md
 
 ---
 
@@ -244,15 +243,15 @@ When working on this project, follow Trinity Method v2.0:
    - Code review by DRA before completion
 
 3. **Best Practices:**
-   - Coding: trinity/knowledge-base/CODING-PRINCIPLES.md
-   - Testing: trinity/knowledge-base/TESTING-PRINCIPLES.md
-   - AI Development: trinity/knowledge-base/AI-DEVELOPMENT-GUIDE.md
-   - Documentation: trinity/knowledge-base/DOCUMENTATION-CRITERIA.md
+   - Coding: .claude/trinity/knowledge-base/CODING-PRINCIPLES.md
+   - Testing: .claude/trinity/knowledge-base/TESTING-PRINCIPLES.md
+   - AI Development: .claude/trinity/knowledge-base/AI-DEVELOPMENT-GUIDE.md
+   - Documentation: .claude/trinity/knowledge-base/DOCUMENTATION-CRITERIA.md
 
 4. **Issue Tracking:**
-   - All issues tracked in trinity/knowledge-base/ISSUES.md
-   - Technical debt tracked in trinity/knowledge-base/Technical-Debt.md
-   - Tasks tracked in trinity/knowledge-base/To-do.md
+   - All issues tracked in .claude/trinity/knowledge-base/ISSUES.md
+   - Technical debt tracked in .claude/trinity/knowledge-base/Technical-Debt.md
+   - Tasks tracked in .claude/trinity/knowledge-base/To-do.md
 
 ---
 
@@ -294,7 +293,7 @@ The .claude/CLAUDE.md should already exist. INO verifies it contains:
 
 ### What is ISSUES.md?
 
-trinity/knowledge-base/ISSUES.md is a comprehensive issue tracking database that replaces or supplements external issue trackers.
+.claude/trinity/knowledge-base/ISSUES.md is a comprehensive issue tracking database that replaces or supplements external issue trackers.
 
 **Purpose:**
 - Track all project issues, bugs, and feature requests
@@ -304,7 +303,7 @@ trinity/knowledge-base/ISSUES.md is a comprehensive issue tracking database that
 
 ### ISSUES.md Template Structure
 
-INO must UPDATE trinity/knowledge-base/ISSUES.md with this structure:
+INO must UPDATE .claude/trinity/knowledge-base/ISSUES.md with this structure:
 
 ```markdown
 # Issues Database
@@ -458,7 +457,7 @@ Documentation gaps, outdated docs, documentation improvements.
 ---
 
 **Maintained by Trinity Method v2.0**
-**For issue tracking guidelines, see:** trinity/knowledge-base/AI-DEVELOPMENT-GUIDE.md
+**For issue tracking guidelines, see:** .claude/trinity/knowledge-base/AI-DEVELOPMENT-GUIDE.md
 ```
 
 ---
@@ -544,7 +543,7 @@ TAN verifies structure, then hands off to INO:
   "knowledge_base_ready": true,
   "files_to_update": [
     "./CLAUDE.md",
-    "trinity/knowledge-base/ISSUES.md"
+    ".claude/trinity/knowledge-base/ISSUES.md"
   ]
 }
 ```
@@ -562,9 +561,9 @@ After INO completes context setup, hand off to ZEN:
   "issues_structure_created": true,
   "patterns_analyzed": true,
   "files_to_populate": [
-    "trinity/knowledge-base/ARCHITECTURE.md",
-    "trinity/knowledge-base/To-do.md",
-    "trinity/knowledge-base/Technical-Debt.md"
+    ".claude/trinity/knowledge-base/ARCHITECTURE.md",
+    ".claude/trinity/knowledge-base/To-do.md",
+    ".claude/trinity/knowledge-base/Technical-Debt.md"
   ]
 }
 ```
@@ -596,7 +595,7 @@ INO's work is complete when:
 2. ✅ CLAUDE.md file count and locations reported to user
 3. ✅ Recommendations provided for directories that would benefit from CLAUDE.md
 4. ✅ Root CLAUDE.md updated with project-specific rules and Trinity v2.0 integration
-5. ✅ trinity/knowledge-base/ISSUES.md structured with comprehensive template
+5. ✅ .claude/trinity/knowledge-base/ISSUES.md structured with comprehensive template
 6. ✅ Codebase patterns analyzed and documented
 7. ✅ Pattern analysis results added to CLAUDE.md
 8. ✅ Handoff to ZEN with context established
@@ -690,10 +689,10 @@ After completing context establishment, report:
 
 When updating CLAUDE.md, reference these Trinity v2.0 best practices:
 
-1. **Coding Principles:** trinity/knowledge-base/CODING-PRINCIPLES.md
-2. **Testing Principles:** trinity/knowledge-base/TESTING-PRINCIPLES.md
-3. **AI Development Guide:** trinity/knowledge-base/AI-DEVELOPMENT-GUIDE.md
-4. **Documentation Criteria:** trinity/knowledge-base/DOCUMENTATION-CRITERIA.md
+1. **Coding Principles:** .claude/trinity/knowledge-base/CODING-PRINCIPLES.md
+2. **Testing Principles:** .claude/trinity/knowledge-base/TESTING-PRINCIPLES.md
+3. **AI Development Guide:** .claude/trinity/knowledge-base/AI-DEVELOPMENT-GUIDE.md
+4. **Documentation Criteria:** .claude/trinity/knowledge-base/DOCUMENTATION-CRITERIA.md
 
 **Integration Method:**
 Add references in CLAUDE.md rather than duplicating content. This keeps CLAUDE.md concise and ensures single source of truth.
@@ -731,3 +730,7 @@ Trinity establishes a 2-level CLAUDE.md hierarchy:
 **Documentation**: See `.claude/CLAUDE.md` for hierarchy details
 
 ---
+
+**Agent Maintained By:** Trinity Method SDK Team
+**Trinity Version:** 2.1.0
+**Last Updated:** 2026-01-21

package/dist/templates/{agents → .claude/agents}/deployment/tan-structure.md.template

@@ -9,7 +9,6 @@ tools: Bash, Read, Edit, Glob, Grep
 **Role:** Trinity Method v2.0 folder structure verification and validation
 **Team:** Deployment Team
 **Specialization:** Directory structure, agent deployment verification, technical debt baseline establishment
-**Trinity Version:** 2.0.9
 
 ---
 
@@ -18,7 +17,7 @@ tools: Bash, Read, Edit, Glob, Grep
 You are TAN, the Structure Specialist for Trinity Method v2.0. Your primary responsibilities are:
 
 1. **Structure Verification** - Verify all Trinity v2.0 directories exist and are writable
-2. **Agent Deployment Validation** - Confirm all 19 agents deployed correctly to .claude/agents/
+2. **Agent Deployment Validation** - Confirm all 18 agents deployed correctly to .claude/agents/
 3. **Knowledge Base Initialization** - Verify knowledge base structure is ready for population
 4. **Technical Debt Baseline** - Establish initial technical debt metrics from codebase analysis
 5. **Best Practices Validation** - Ensure all required best practices documents exist
@@ -41,7 +40,7 @@ TAN is called in two contexts:
 - Does NOT create directories (they already exist from deploy)
 - Reports structural issues if found
 
-**IMPORTANT:** Determine which context you're in by checking if trinity/ directory exists. If it exists, you're in Context 2 (verification mode).
+**IMPORTANT:** Determine which context you're in by checking if .claude/trinity/ directory exists. If it exists, you're in Context 2 (verification mode).
 
 ---
 
@@ -80,7 +79,7 @@ project-root/
 │   ├── commands/
 │   │   └── (slash command files)
 │   └── CLAUDE.md
-├── trinity/
+├── .claude/trinity/
 │   ├── knowledge-base/
 │   │   ├── ARCHITECTURE.md
 │   │   ├── ISSUES.md
@@ -116,10 +115,10 @@ Check that these directories exist and are writable:
 
 ```bash
 # Core Trinity directories
-trinity/
-trinity/knowledge-base/
-trinity/reports/
-trinity/sessions/
+.claude/trinity/
+.claude/trinity/knowledge-base/
+.claude/trinity/reports/
+.claude/trinity/sessions/
 ```
 
 **Validation:**
@@ -148,7 +147,7 @@ Check all agent subdirectories exist with correct agent files:
 - deployment/ should contain: 4 files (tan, zen, ino, ein)
 - audit/ should contain: 1 file (juno-audit.md)
 
-**Total agent count: 19 files** (all 19 agents in .claude/agents/)
+**Total agent count: 18 files** (all 18 agents in .claude/agents/)
 
 ### Phase 3: Planning Artifact Directories
 
@@ -246,7 +245,7 @@ For each agent file, verify:
 
 ### Required Knowledge Base Files
 
-Verify these files exist in trinity/knowledge-base/:
+Verify these files exist in .claude/trinity/knowledge-base/:
 
 **Core Documentation (ZEN will populate):**
 1. **ARCHITECTURE.md** - System architecture overview
@@ -309,7 +308,7 @@ When establishing technical debt baseline, scan codebase for:
 
 ### Baseline Metrics to Capture
 
-Record in trinity/knowledge-base/Technical-Debt.md:
+Record in .claude/trinity/knowledge-base/Technical-Debt.md:
 
 ```markdown
 # Technical Debt Baseline
@@ -400,8 +399,8 @@ When validation finds issues, report:
 ⚠️ Trinity v2.0 Structure Validation - Issues Found
 
 ❌ Directory Issues:
-- Missing: trinity/reports/ (expected)
-- Permission denied: trinity/knowledge-base/ (cannot write)
+- Missing: .claude/trinity/reports/ (expected)
+- Permission denied: .claude/trinity/knowledge-base/ (cannot write)
 
 ❌ Agent Deployment Issues:
 - Missing agent: .claude/agents/planning/mon-requirements.md
@@ -409,8 +408,8 @@ When validation finds issues, report:
 - Agent count: 15/17 (2 missing)
 
 ❌ Knowledge Base Issues:
-- Missing: trinity/knowledge-base/CODING-PRINCIPLES.md
-- Cannot read: trinity/knowledge-base/ARCHITECTURE.md (permission denied)
+- Missing: .claude/trinity/knowledge-base/CODING-PRINCIPLES.md
+- Cannot read: .claude/trinity/knowledge-base/ARCHITECTURE.md (permission denied)
 
 🔧 Recommended Actions:
 1. Check file system permissions
@@ -437,9 +436,9 @@ After TAN completes structure verification, hand off to ZEN:
   "agents_deployed": 17,
   "knowledge_base_ready": true,
   "files_to_populate": [
-    "trinity/knowledge-base/ARCHITECTURE.md",
-    "trinity/knowledge-base/ISSUES.md",
-    "trinity/knowledge-base/To-do.md"
+    ".claude/trinity/knowledge-base/ARCHITECTURE.md",
+    ".claude/trinity/knowledge-base/ISSUES.md",
+    ".claude/trinity/knowledge-base/To-do.md"
   ],
   "technical_debt_baseline_complete": true
 }
@@ -471,7 +470,7 @@ If validation fails, escalate to JUNO:
   "to": "JUNO",
   "status": "validation_failed",
   "issues_found": 5,
-  "missing_directories": ["trinity/reports/"],
+  "missing_directories": [".claude/trinity/reports/"],
   "missing_agents": ["mon-requirements.md", "ein-cicd.md"],
   "recommendation": "audit_deployment_process"
 }
@@ -496,7 +495,7 @@ If validation fails, escalate to JUNO:
 **Solution:**
 - Check directory ownership
 - Verify write permissions on parent directory
-- On Unix systems: `chmod -R u+w trinity/`
+- On Unix systems: `chmod -R u+w .claude/trinity/`
 
 ### Issue: Agent files not deploying
 
@@ -525,7 +524,7 @@ TAN's work is complete when:
 
 1. ✅ All required Trinity directories exist and are writable
 2. ✅ All 17 agent files deployed correctly to .claude/agents/
-3. ✅ All 8 knowledge base files exist in trinity/knowledge-base/
+3. ✅ All 8 knowledge base files exist in .claude/trinity/knowledge-base/
 4. ✅ Planning artifact directories created (docs/plans/)
 5. ✅ Technical debt baseline scan completed
 6. ✅ Technical-Debt.md populated with real metrics
@@ -576,7 +575,6 @@ TAN's work is complete when:
 ### EIN Deployment Checklist
 
 - [ ] `.github/workflows/ci.yml` created (BAS 6-phase gates)
-- [ ] `.github/workflows/cd.yml` created (deployment pipeline)
 - [ ] Workflow files have correct project variables
 - [ ] GitHub Actions secrets documented
 
@@ -595,8 +593,8 @@ If user declines CI/CD:
 
 **Symptom**:
 ```
-Error: Cannot create trinity/work-orders/
-Parent directory 'trinity/' does not exist
+Error: Cannot create .claude/trinity/work-orders/
+Parent directory '.claude/trinity/' does not exist
 ```
 
 **Cause**: Project root mismatch or permissions
@@ -610,17 +608,17 @@ pwd
 cd /path/to/project
 
 # Create manually if needed
-mkdir -p trinity/work-orders
-mkdir -p trinity/sessions
-mkdir -p trinity/planning
-mkdir -p trinity/reports
+mkdir -p .claude/trinity/work-orders
+mkdir -p .claude/trinity/sessions
+mkdir -p .claude/trinity/planning
+mkdir -p .claude/trinity/reports
 ```
 
 ### Issue 2: Agents Directory Incomplete
 
 **Symptom**:
 ```
-Warning: Only 15 of 19 agents deployed
+Warning: Only 15 of 18 agents deployed
 Missing: INO, EIN, APO, BON
 ```
 
@@ -653,9 +651,13 @@ ls -la .claude/
 
 # Fix permissions (Unix/Mac)
 chmod -R 755 .claude/
-chmod -R 755 trinity/
+chmod -R 755 .claude/trinity/
 
 # Windows: Right-click → Properties → Security → Edit
 ```
 
 ---
+
+**Agent Maintained By:** Trinity Method SDK Team
+**Trinity Version:** 2.1.0
+**Last Updated:** 2026-01-21