trinity-method-sdk 2.0.9 → 2.2.0

package/dist/templates/{investigations → trinity/templates/investigations}/bug.md.template

@@ -399,7 +399,7 @@ describe('Regression: {{title}}', () => {
 
 ### Investigation Report Format
 **Filename:** `INV-{{investigationId}}-findings-[TIMESTAMP].md`
-**Location:** `trinity/reports/`
+**Location:** `.claude/trinity/reports/`
 
 ### Required Sections
 1. **Investigation Summary** - Brief overview of what was investigated
@@ -422,22 +422,22 @@ describe('Regression: {{title}}', () => {
 
 When investigation is complete:
 1. **Create Investigation Report:**
-   - [ ] Save findings report to `trinity/reports/INV-{{investigationId}}-findings-[TIMESTAMP].md`
+   - [ ] Save findings report to `.claude/trinity/reports/INV-{{investigationId}}-findings-[TIMESTAMP].md`
    - [ ] Include all required sections listed above
    - [ ] Attach all evidence and supporting documentation
 
 2. **Move Investigation File:**
-   - [ ] Move this investigation file (INV-{{investigationId}}.md) to `trinity/sessions/`
-   - [ ] Keep report in `trinity/reports/` until end of session
+   - [ ] Move this investigation file (INV-{{investigationId}}.md) to `.claude/trinity/sessions/`
+   - [ ] Keep report in `.claude/trinity/reports/` until end of session
 
 3. **Session Cleanup:**
    - [ ] Run `/trinity-end` to archive both investigation and report
-   - [ ] Investigation will be archived to `trinity/archive/investigations/YYYY-MM-DD/`
-   - [ ] Report will be archived to `trinity/archive/reports/YYYY-MM-DD/`
+   - [ ] Investigation will be archived to `.claude/trinity/archive/investigations/YYYY-MM-DD/`
+   - [ ] Report will be archived to `.claude/trinity/archive/reports/YYYY-MM-DD/`
 
 4. **Clean Slate:**
-   - [ ] Verify `trinity/sessions/` is empty (ready for next session)
-   - [ ] Verify `trinity/reports/` is empty (ready for next session)
+   - [ ] Verify `.claude/trinity/sessions/` is empty (ready for next session)
+   - [ ] Verify `.claude/trinity/reports/` is empty (ready for next session)
 
 ---
 
@@ -445,15 +445,15 @@ When investigation is complete:
 
 **Trinity Method Core:**
 - [Trinity Method Protocols](../../CLAUDE.md) - Root Trinity guidance
-- [Investigation Requirements](../../trinity/CLAUDE.md#investigation-protocols) - Investigation-first methodology
+- [Investigation Requirements](../../.claude/trinity/CLAUDE.md#investigation-protocols) - Investigation-first methodology
 - [Agent Directory](../../.claude/EMPLOYEE-DIRECTORY.md) - 19-agent Trinity team
 
 **Knowledge Base:**
-- [Architecture](../../trinity/knowledge-base/ARCHITECTURE.md) - System architecture and patterns
-- [Known Issues](../../trinity/knowledge-base/ISSUES.md) - Issue patterns database
-- [Technical Debt](../../trinity/knowledge-base/Technical-Debt.md) - Debt tracking
-- [Testing Standards](../../trinity/knowledge-base/TESTING-PRINCIPLES.md) - Test requirements
-- [Coding Standards](../../trinity/knowledge-base/CODING-PRINCIPLES.md) - Code quality
+- [Architecture](../../.claude/trinity/knowledge-base/ARCHITECTURE.md) - System architecture and patterns
+- [Known Issues](../../.claude/trinity/knowledge-base/ISSUES.md) - Issue patterns database
+- [Technical Debt](../../.claude/trinity/knowledge-base/Technical-Debt.md) - Debt tracking
+- [Testing Standards](../../.claude/trinity/knowledge-base/TESTING-PRINCIPLES.md) - Test requirements
+- [Coding Standards](../../.claude/trinity/knowledge-base/CODING-PRINCIPLES.md) - Code quality
 
 **Investigation Protocols:**
 - READ-ONLY: No file modifications during investigation

package/dist/templates/{investigations → trinity/templates/investigations}/feature.md.template

@@ -473,15 +473,15 @@ describe('Feature E2E', () => {
 
 **Trinity Method Core:**
 - [Trinity Method Protocols](../../CLAUDE.md) - Root Trinity guidance
-- [Investigation Requirements](../../trinity/CLAUDE.md#investigation-protocols) - Investigation-first methodology
+- [Investigation Requirements](../../.claude/trinity/CLAUDE.md#investigation-protocols) - Investigation-first methodology
 - [Agent Directory](../../.claude/EMPLOYEE-DIRECTORY.md) - 19-agent Trinity team
 
 **Knowledge Base:**
-- [Architecture](../../trinity/knowledge-base/ARCHITECTURE.md) - System architecture and patterns
-- [Known Issues](../../trinity/knowledge-base/ISSUES.md) - Issue patterns database
-- [Technical Debt](../../trinity/knowledge-base/Technical-Debt.md) - Debt tracking
-- [Testing Standards](../../trinity/knowledge-base/TESTING-PRINCIPLES.md) - Test requirements
-- [Coding Standards](../../trinity/knowledge-base/CODING-PRINCIPLES.md) - Code quality
+- [Architecture](../../.claude/trinity/knowledge-base/ARCHITECTURE.md) - System architecture and patterns
+- [Known Issues](../../.claude/trinity/knowledge-base/ISSUES.md) - Issue patterns database
+- [Technical Debt](../../.claude/trinity/knowledge-base/Technical-Debt.md) - Debt tracking
+- [Testing Standards](../../.claude/trinity/knowledge-base/TESTING-PRINCIPLES.md) - Test requirements
+- [Coding Standards](../../.claude/trinity/knowledge-base/CODING-PRINCIPLES.md) - Code quality
 
 **Investigation Protocols:**
 - READ-ONLY: No file modifications during investigation
@@ -495,7 +495,7 @@ describe('Feature E2E', () => {
 
 ### Investigation Report Format
 **Filename:** `INV-{{investigationId}}-findings-[TIMESTAMP].md`
-**Location:** `trinity/reports/`
+**Location:** `.claude/trinity/reports/`
 
 ### Required Sections
 1. **Investigation Summary** - Feature analysis overview and business value
@@ -519,22 +519,22 @@ describe('Feature E2E', () => {
 
 When investigation is complete:
 1. **Create Investigation Report:**
-   - [ ] Save findings report to `trinity/reports/INV-{{investigationId}}-findings-[TIMESTAMP].md`
+   - [ ] Save findings report to `.claude/trinity/reports/INV-{{investigationId}}-findings-[TIMESTAMP].md`
    - [ ] Include all required sections listed above
    - [ ] Attach all evidence and supporting documentation
 
 2. **Move Investigation File:**
-   - [ ] Move this investigation file (INV-{{investigationId}}.md) to `trinity/sessions/`
-   - [ ] Keep report in `trinity/reports/` until end of session
+   - [ ] Move this investigation file (INV-{{investigationId}}.md) to `.claude/trinity/sessions/`
+   - [ ] Keep report in `.claude/trinity/reports/` until end of session
 
 3. **Session Cleanup:**
    - [ ] Run `/trinity-end` to archive both investigation and report
-   - [ ] Investigation will be archived to `trinity/archive/investigations/YYYY-MM-DD/`
-   - [ ] Report will be archived to `trinity/archive/reports/YYYY-MM-DD/`
+   - [ ] Investigation will be archived to `.claude/trinity/archive/investigations/YYYY-MM-DD/`
+   - [ ] Report will be archived to `.claude/trinity/archive/reports/YYYY-MM-DD/`
 
 4. **Clean Slate:**
-   - [ ] Verify `trinity/sessions/` is empty (ready for next session)
-   - [ ] Verify `trinity/reports/` is empty (ready for next session)
+   - [ ] Verify `.claude/trinity/sessions/` is empty (ready for next session)
+   - [ ] Verify `.claude/trinity/reports/` is empty (ready for next session)
 
 ---
 

package/dist/templates/{investigations → trinity/templates/investigations}/performance.md.template

@@ -537,7 +537,7 @@ describe('Performance: getUserOrders', () => {
 
 ### Investigation Report Format
 **Filename:** `INV-{{investigationId}}-findings-[TIMESTAMP].md`
-**Location:** `trinity/reports/`
+**Location:** `.claude/trinity/reports/`
 
 ### Required Sections
 1. **Investigation Summary** - Performance issue overview and user impact
@@ -561,22 +561,22 @@ describe('Performance: getUserOrders', () => {
 
 When investigation is complete:
 1. **Create Investigation Report:**
-   - [ ] Save findings report to `trinity/reports/INV-{{investigationId}}-findings-[TIMESTAMP].md`
+   - [ ] Save findings report to `.claude/trinity/reports/INV-{{investigationId}}-findings-[TIMESTAMP].md`
    - [ ] Include all required sections listed above
    - [ ] Attach all evidence and supporting documentation
 
 2. **Move Investigation File:**
-   - [ ] Move this investigation file (INV-{{investigationId}}.md) to `trinity/sessions/`
-   - [ ] Keep report in `trinity/reports/` until end of session
+   - [ ] Move this investigation file (INV-{{investigationId}}.md) to `.claude/trinity/sessions/`
+   - [ ] Keep report in `.claude/trinity/reports/` until end of session
 
 3. **Session Cleanup:**
    - [ ] Run `/trinity-end` to archive both investigation and report
-   - [ ] Investigation will be archived to `trinity/archive/investigations/YYYY-MM-DD/`
-   - [ ] Report will be archived to `trinity/archive/reports/YYYY-MM-DD/`
+   - [ ] Investigation will be archived to `.claude/trinity/archive/investigations/YYYY-MM-DD/`
+   - [ ] Report will be archived to `.claude/trinity/archive/reports/YYYY-MM-DD/`
 
 4. **Clean Slate:**
-   - [ ] Verify `trinity/sessions/` is empty (ready for next session)
-   - [ ] Verify `trinity/reports/` is empty (ready for next session)
+   - [ ] Verify `.claude/trinity/sessions/` is empty (ready for next session)
+   - [ ] Verify `.claude/trinity/reports/` is empty (ready for next session)
 
 ---
 
@@ -584,15 +584,15 @@ When investigation is complete:
 
 **Trinity Method Core:**
 - [Trinity Method Protocols](../../CLAUDE.md) - Root Trinity guidance
-- [Investigation Requirements](../../trinity/CLAUDE.md#investigation-protocols) - Investigation-first methodology
+- [Investigation Requirements](../../.claude/trinity/CLAUDE.md#investigation-protocols) - Investigation-first methodology
 - [Agent Directory](../../.claude/EMPLOYEE-DIRECTORY.md) - 19-agent Trinity team
 
 **Knowledge Base:**
-- [Architecture](../../trinity/knowledge-base/ARCHITECTURE.md) - System architecture and patterns
-- [Known Issues](../../trinity/knowledge-base/ISSUES.md) - Issue patterns database
-- [Technical Debt](../../trinity/knowledge-base/Technical-Debt.md) - Debt tracking
-- [Testing Standards](../../trinity/knowledge-base/TESTING-PRINCIPLES.md) - Test requirements
-- [Coding Standards](../../trinity/knowledge-base/CODING-PRINCIPLES.md) - Code quality
+- [Architecture](../../.claude/trinity/knowledge-base/ARCHITECTURE.md) - System architecture and patterns
+- [Known Issues](../../.claude/trinity/knowledge-base/ISSUES.md) - Issue patterns database
+- [Technical Debt](../../.claude/trinity/knowledge-base/Technical-Debt.md) - Debt tracking
+- [Testing Standards](../../.claude/trinity/knowledge-base/TESTING-PRINCIPLES.md) - Test requirements
+- [Coding Standards](../../.claude/trinity/knowledge-base/CODING-PRINCIPLES.md) - Code quality
 
 **Investigation Protocols:**
 - READ-ONLY: No file modifications during investigation

package/dist/templates/{investigations → trinity/templates/investigations}/security.md.template

@@ -632,7 +632,7 @@ security:
 
 ### Investigation Report Format
 **Filename:** `INV-{{investigationId}}-findings-[TIMESTAMP].md`
-**Location:** `trinity/reports/`
+**Location:** `.claude/trinity/reports/`
 
 ### Required Sections
 1. **Investigation Summary** - Vulnerability overview, type, and severity (CVSS score)
@@ -656,23 +656,23 @@ security:
 
 When investigation is complete:
 1. **Create Investigation Report:**
-   - [ ] Save findings report to `trinity/reports/INV-{{investigationId}}-findings-[TIMESTAMP].md`
+   - [ ] Save findings report to `.claude/trinity/reports/INV-{{investigationId}}-findings-[TIMESTAMP].md`
    - [ ] Include all required sections listed above
    - [ ] Attach all evidence and supporting documentation
    - [ ] **CRITICAL:** Ensure report does NOT contain sensitive exploit details that could enable attacks
 
 2. **Move Investigation File:**
-   - [ ] Move this investigation file (INV-{{investigationId}}.md) to `trinity/sessions/`
-   - [ ] Keep report in `trinity/reports/` until end of session
+   - [ ] Move this investigation file (INV-{{investigationId}}.md) to `.claude/trinity/sessions/`
+   - [ ] Keep report in `.claude/trinity/reports/` until end of session
 
 3. **Session Cleanup:**
    - [ ] Run `/trinity-end` to archive both investigation and report
-   - [ ] Investigation will be archived to `trinity/archive/investigations/YYYY-MM-DD/`
-   - [ ] Report will be archived to `trinity/archive/reports/YYYY-MM-DD/`
+   - [ ] Investigation will be archived to `.claude/trinity/archive/investigations/YYYY-MM-DD/`
+   - [ ] Report will be archived to `.claude/trinity/archive/reports/YYYY-MM-DD/`
 
 4. **Clean Slate:**
-   - [ ] Verify `trinity/sessions/` is empty (ready for next session)
-   - [ ] Verify `trinity/reports/` is empty (ready for next session)
+   - [ ] Verify `.claude/trinity/sessions/` is empty (ready for next session)
+   - [ ] Verify `.claude/trinity/reports/` is empty (ready for next session)
 
 5. **Security-Specific Actions:**
    - [ ] Notify security team of findings
@@ -685,15 +685,15 @@ When investigation is complete:
 
 **Trinity Method Core:**
 - [Trinity Method Protocols](../../CLAUDE.md) - Root Trinity guidance
-- [Investigation Requirements](../../trinity/CLAUDE.md#investigation-protocols) - Investigation-first methodology
+- [Investigation Requirements](../../.claude/trinity/CLAUDE.md#investigation-protocols) - Investigation-first methodology
 - [Agent Directory](../../.claude/EMPLOYEE-DIRECTORY.md) - 19-agent Trinity team
 
 **Knowledge Base:**
-- [Architecture](../../trinity/knowledge-base/ARCHITECTURE.md) - System architecture and patterns
-- [Known Issues](../../trinity/knowledge-base/ISSUES.md) - Issue patterns database
-- [Technical Debt](../../trinity/knowledge-base/Technical-Debt.md) - Debt tracking
-- [Testing Standards](../../trinity/knowledge-base/TESTING-PRINCIPLES.md) - Test requirements
-- [Coding Standards](../../trinity/knowledge-base/CODING-PRINCIPLES.md) - Code quality
+- [Architecture](../../.claude/trinity/knowledge-base/ARCHITECTURE.md) - System architecture and patterns
+- [Known Issues](../../.claude/trinity/knowledge-base/ISSUES.md) - Issue patterns database
+- [Technical Debt](../../.claude/trinity/knowledge-base/Technical-Debt.md) - Debt tracking
+- [Testing Standards](../../.claude/trinity/knowledge-base/TESTING-PRINCIPLES.md) - Test requirements
+- [Coding Standards](../../.claude/trinity/knowledge-base/CODING-PRINCIPLES.md) - Code quality
 
 **Investigation Protocols:**
 - READ-ONLY: No file modifications during investigation

package/dist/templates/{investigations → trinity/templates/investigations}/technical.md.template

@@ -315,7 +315,7 @@ describe('Technical Implementation', () => {
 
 ### Investigation Report Format
 **Filename:** `INV-{{investigationId}}-findings-[TIMESTAMP].md`
-**Location:** `trinity/reports/`
+**Location:** `.claude/trinity/reports/`
 
 ### Required Sections
 1. **Investigation Summary** - Technical challenge overview and context
@@ -339,22 +339,22 @@ describe('Technical Implementation', () => {
 
 When investigation is complete:
 1. **Create Investigation Report:**
-   - [ ] Save findings report to `trinity/reports/INV-{{investigationId}}-findings-[TIMESTAMP].md`
+   - [ ] Save findings report to `.claude/trinity/reports/INV-{{investigationId}}-findings-[TIMESTAMP].md`
    - [ ] Include all required sections listed above
    - [ ] Attach all evidence and supporting documentation
 
 2. **Move Investigation File:**
-   - [ ] Move this investigation file (INV-{{investigationId}}.md) to `trinity/sessions/`
-   - [ ] Keep report in `trinity/reports/` until end of session
+   - [ ] Move this investigation file (INV-{{investigationId}}.md) to `.claude/trinity/sessions/`
+   - [ ] Keep report in `.claude/trinity/reports/` until end of session
 
 3. **Session Cleanup:**
    - [ ] Run `/trinity-end` to archive both investigation and report
-   - [ ] Investigation will be archived to `trinity/archive/investigations/YYYY-MM-DD/`
-   - [ ] Report will be archived to `trinity/archive/reports/YYYY-MM-DD/`
+   - [ ] Investigation will be archived to `.claude/trinity/archive/investigations/YYYY-MM-DD/`
+   - [ ] Report will be archived to `.claude/trinity/archive/reports/YYYY-MM-DD/`
 
 4. **Clean Slate:**
-   - [ ] Verify `trinity/sessions/` is empty (ready for next session)
-   - [ ] Verify `trinity/reports/` is empty (ready for next session)
+   - [ ] Verify `.claude/trinity/sessions/` is empty (ready for next session)
+   - [ ] Verify `.claude/trinity/reports/` is empty (ready for next session)
 
 ---
 
@@ -362,15 +362,15 @@ When investigation is complete:
 
 **Trinity Method Core:**
 - [Trinity Method Protocols](../../CLAUDE.md) - Root Trinity guidance
-- [Investigation Requirements](../../trinity/CLAUDE.md#investigation-protocols) - Investigation-first methodology
+- [Investigation Requirements](../../.claude/trinity/CLAUDE.md#investigation-protocols) - Investigation-first methodology
 - [Agent Directory](../../.claude/EMPLOYEE-DIRECTORY.md) - 19-agent Trinity team
 
 **Knowledge Base:**
-- [Architecture](../../trinity/knowledge-base/ARCHITECTURE.md) - System architecture and patterns
-- [Known Issues](../../trinity/knowledge-base/ISSUES.md) - Issue patterns database
-- [Technical Debt](../../trinity/knowledge-base/Technical-Debt.md) - Debt tracking
-- [Testing Standards](../../trinity/knowledge-base/TESTING-PRINCIPLES.md) - Test requirements
-- [Coding Standards](../../trinity/knowledge-base/CODING-PRINCIPLES.md) - Code quality
+- [Architecture](../../.claude/trinity/knowledge-base/ARCHITECTURE.md) - System architecture and patterns
+- [Known Issues](../../.claude/trinity/knowledge-base/ISSUES.md) - Issue patterns database
+- [Technical Debt](../../.claude/trinity/knowledge-base/Technical-Debt.md) - Debt tracking
+- [Testing Standards](../../.claude/trinity/knowledge-base/TESTING-PRINCIPLES.md) - Test requirements
+- [Coding Standards](../../.claude/trinity/knowledge-base/CODING-PRINCIPLES.md) - Code quality
 
 **Investigation Protocols:**
 - READ-ONLY: No file modifications during investigation

package/dist/templates/{work-orders → trinity/templates/work-orders}/ANALYSIS-TEMPLATE.md.template

@@ -130,31 +130,31 @@ STATUS: APPROVED FOR EXECUTION
    - [ ] All deliverables include required sections listed above
 
 **Step 2: 🚨 MOVE THIS WORK ORDER FILE 🚨** ✅
-   - [ ] **IMMEDIATELY** move this file from `trinity/work-orders/` to `trinity/sessions/`
-   - [ ] **THIS STEP IS MANDATORY** - Work orders left in trinity/work-orders/ are considered incomplete
+   - [ ] **IMMEDIATELY** move this file from `.claude/trinity/work-orders/` to `.claude/trinity/sessions/`
+   - [ ] **THIS STEP IS MANDATORY** - Work orders left in .claude/trinity/work-orders/ are considered incomplete
 
    **Execute this exact command:**
    ```bash
-   mv trinity/work-orders/{{workOrderFilename}} trinity/sessions/
+   mv .claude/trinity/work-orders/{{workOrderFilename}} .claude/trinity/sessions/
    ```
 
 **Step 3: Verify File Locations** ✅
-   - [ ] This work order file NOW EXISTS in: `trinity/sessions/{{workOrderFilename}}`
+   - [ ] This work order file NOW EXISTS in: `.claude/trinity/sessions/{{workOrderFilename}}`
    - [ ] Completion report exists in: `${PROJECT_REPORTS}/[COMPONENT]-ANALYSIS-[TIMESTAMP].md`
-   - [ ] This work order NO LONGER EXISTS in: `trinity/work-orders/`
+   - [ ] This work order NO LONGER EXISTS in: `.claude/trinity/work-orders/`
 
    **If any verification fails, the work order is NOT complete. Fix immediately.**
 
 **Step 4: Session Cleanup (when entire session complete):**
    - [ ] When session is complete, run `/trinity-end`
-   - [ ] trinity-end will archive ALL files from `trinity/sessions/` and `${PROJECT_REPORTS}/`
+   - [ ] trinity-end will archive ALL files from `.claude/trinity/sessions/` and `${PROJECT_REPORTS}/`
    - [ ] Next session starts with empty sessions/ and reports/ folders
 
 **Archive Destination (via trinity-end):**
-- Work order → `trinity/archive/work-orders/YYYY-MM-DD/`
-- Completion report → `trinity/archive/reports/YYYY-MM-DD/`
-- JUNO audit report → `trinity/archive/reports/YYYY-MM-DD/` (if applicable)
-- Session summary → `trinity/archive/sessions/YYYY-MM-DD/`
+- Work order → `.claude/trinity/archive/work-orders/YYYY-MM-DD/`
+- Completion report → `.claude/trinity/archive/reports/YYYY-MM-DD/`
+- JUNO audit report → `.claude/trinity/archive/reports/YYYY-MM-DD/` (if applicable)
+- Session summary → `.claude/trinity/archive/sessions/YYYY-MM-DD/`
 
 ---
 
@@ -271,6 +271,3 @@ Quality and completeness are the ONLY metrics that matter.
 ---
 
 **Remember:** Analysis should be objective, evidence-based, and actionable. Present findings clearly with appropriate confidence levels. When uncertain, state limitations explicitly. Analyses are read-only - no file modifications or git operations.
-
-*Trinity Method v2.0 - Analysis Work Order Template*
-*Project-Isolated Architecture with Dynamic Paths*

package/dist/templates/{work-orders → trinity/templates/work-orders}/AUDIT-TEMPLATE.md.template

@@ -4,19 +4,6 @@
 
 ---
 
-## AUTHORIZATION
-
-```
-TRINITY COUNCIL APPROVAL:
-☑ LUKA: APPROVED - [Strategic need for audit]
-☑ TRINITY: APPROVED - [Technical audit scope]
-☑ CC: PENDING - Awaiting your acknowledgment
-
-STATUS: APPROVED FOR EXECUTION
-```
-
----
-
 ## MISSION OBJECTIVE
 
 [Clear statement of what needs to be audited and against what standards]
@@ -142,31 +129,31 @@ Passing_Score: 70
    - [ ] All deliverables include required sections listed above
 
 **Step 2: 🚨 MOVE THIS WORK ORDER FILE 🚨** ✅
-   - [ ] **IMMEDIATELY** move this file from `trinity/work-orders/` to `trinity/sessions/`
-   - [ ] **THIS STEP IS MANDATORY** - Work orders left in trinity/work-orders/ are considered incomplete
+   - [ ] **IMMEDIATELY** move this file from `.claude/trinity/work-orders/` to `.claude/trinity/sessions/`
+   - [ ] **THIS STEP IS MANDATORY** - Work orders left in .claude/trinity/work-orders/ are considered incomplete
 
    **Execute this exact command:**
    ```bash
-   mv trinity/work-orders/{{workOrderFilename}} trinity/sessions/
+   mv .claude/trinity/work-orders/{{workOrderFilename}} .claude/trinity/sessions/
    ```
 
 **Step 3: Verify File Locations** ✅
-   - [ ] This work order file NOW EXISTS in: `trinity/sessions/{{workOrderFilename}}`
+   - [ ] This work order file NOW EXISTS in: `.claude/trinity/sessions/{{workOrderFilename}}`
    - [ ] Completion report exists in: `${PROJECT_REPORTS}/AUDIT-[COMPONENT]-[TIMESTAMP].md`
-   - [ ] This work order NO LONGER EXISTS in: `trinity/work-orders/`
+   - [ ] This work order NO LONGER EXISTS in: `.claude/trinity/work-orders/`
 
    **If any verification fails, the work order is NOT complete. Fix immediately.**
 
 **Step 4: Session Cleanup (when entire session complete):**
    - [ ] When session is complete, run `/trinity-end`
-   - [ ] trinity-end will archive ALL files from `trinity/sessions/` and `${PROJECT_REPORTS}/`
+   - [ ] trinity-end will archive ALL files from `.claude/trinity/sessions/` and `${PROJECT_REPORTS}/`
    - [ ] Next session starts with empty sessions/ and reports/ folders
 
 **Archive Destination (via trinity-end):**
-- Work order → `trinity/archive/work-orders/YYYY-MM-DD/`
-- Completion report → `trinity/archive/reports/YYYY-MM-DD/`
-- JUNO audit report → `trinity/archive/reports/YYYY-MM-DD/` (if applicable)
-- Session summary → `trinity/archive/sessions/YYYY-MM-DD/`
+- Work order → `.claude/trinity/archive/work-orders/YYYY-MM-DD/`
+- Completion report → `.claude/trinity/archive/reports/YYYY-MM-DD/`
+- JUNO audit report → `.claude/trinity/archive/reports/YYYY-MM-DD/` (if applicable)
+- Session summary → `.claude/trinity/archive/sessions/YYYY-MM-DD/`
 
 ---
 
@@ -257,6 +244,3 @@ For each issue found:
 ---
 
 **Remember:** Be thorough but fair. The goal is to improve quality, not to find fault. Focus on actionable findings with clear remediation paths. Audits are read-only - no file modifications or git operations.
-
-*Trinity Method v2.0 - Audit Work Order Template*
-*Project-Isolated Architecture with Dynamic Paths*

package/dist/templates/{work-orders → trinity/templates/work-orders}/IMPLEMENTATION-TEMPLATE.md.template

@@ -4,19 +4,6 @@
 
 ---
 
-## AUTHORIZATION
-
-```
-TRINITY COUNCIL APPROVAL:
-☑ LUKA: APPROVED - [Strategic approval]
-☑ TRINITY: APPROVED - [Technical validation]
-☑ CC: PENDING - Awaiting your acknowledgment
-
-STATUS: APPROVED FOR EXECUTION
-```
-
----
-
 ## MISSION OBJECTIVE
 
 [Clear statement of what needs to be implemented and the expected outcome]
@@ -113,31 +100,31 @@ Supporting_Files:
    - [ ] All deliverables include required sections listed above
 
 **Step 2: 🚨 MOVE THIS WORK ORDER FILE 🚨** ✅
-   - [ ] **IMMEDIATELY** move this file from `trinity/work-orders/` to `trinity/sessions/`
-   - [ ] **THIS STEP IS MANDATORY** - Work orders left in trinity/work-orders/ are considered incomplete
+   - [ ] **IMMEDIATELY** move this file from `.claude/trinity/work-orders/` to `.claude/trinity/sessions/`
+   - [ ] **THIS STEP IS MANDATORY** - Work orders left in .claude/trinity/work-orders/ are considered incomplete
 
    **Execute this exact command:**
    ```bash
-   mv trinity/work-orders/{{workOrderFilename}} trinity/sessions/
+   mv .claude/trinity/work-orders/{{workOrderFilename}} .claude/trinity/sessions/
    ```
 
 **Step 3: Verify File Locations** ✅
-   - [ ] This work order file NOW EXISTS in: `trinity/sessions/{{workOrderFilename}}`
+   - [ ] This work order file NOW EXISTS in: `.claude/trinity/sessions/{{workOrderFilename}}`
    - [ ] Completion report exists in: `${PROJECT_REPORTS}/[COMPONENT]-IMPLEMENTATION-COMPLETE-[TIMESTAMP].md`
-   - [ ] This work order NO LONGER EXISTS in: `trinity/work-orders/`
+   - [ ] This work order NO LONGER EXISTS in: `.claude/trinity/work-orders/`
 
    **If any verification fails, the work order is NOT complete. Fix immediately.**
 
 **Step 4: Session Cleanup (when entire session complete):**
    - [ ] When session is complete, run `/trinity-end`
-   - [ ] trinity-end will archive ALL files from `trinity/sessions/` and `${PROJECT_REPORTS}/`
+   - [ ] trinity-end will archive ALL files from `.claude/trinity/sessions/` and `${PROJECT_REPORTS}/`
    - [ ] Next session starts with empty sessions/ and reports/ folders
 
 **Archive Destination (via trinity-end):**
-- Work order → `trinity/archive/work-orders/YYYY-MM-DD/`
-- Completion report → `trinity/archive/reports/YYYY-MM-DD/`
-- JUNO audit report → `trinity/archive/reports/YYYY-MM-DD/` (if applicable)
-- Session summary → `trinity/archive/sessions/YYYY-MM-DD/`
+- Work order → `.claude/trinity/archive/work-orders/YYYY-MM-DD/`
+- Completion report → `.claude/trinity/archive/reports/YYYY-MM-DD/`
+- JUNO audit report → `.claude/trinity/archive/reports/YYYY-MM-DD/` (if applicable)
+- Session summary → `.claude/trinity/archive/sessions/YYYY-MM-DD/`
 
 ---
 
@@ -255,6 +242,3 @@ Quality and completeness are the ONLY metrics that matter.
 ---
 
 **Remember:** Make changes systematically, test frequently, and maintain code quality throughout the implementation. Report all changes to LUKA for git operations.
-
-*Trinity Method v2.0 - Implementation Work Order Template*
-*Project-Isolated Architecture with Dynamic Paths*

package/dist/templates/{work-orders → trinity/templates/work-orders}/INVESTIGATION-TEMPLATE.md.template

@@ -4,19 +4,6 @@
 
 ---
 
-## AUTHORIZATION
-
-```
-TRINITY COUNCIL APPROVAL:
-☑ LUKA: APPROVED - [Approval reason]
-☑ TRINITY: APPROVED - [Technical justification]
-☑ CC: PENDING - Awaiting your acknowledgment
-
-STATUS: APPROVED FOR EXECUTION
-```
-
----
-
 ## MISSION OBJECTIVE
 
 [Clear, single paragraph describing what needs to be investigated and why]
@@ -111,31 +98,31 @@ STATUS: APPROVED FOR EXECUTION
    - [ ] All deliverables include required sections listed above
 
 **Step 2: 🚨 MOVE THIS WORK ORDER FILE 🚨** ✅
-   - [ ] **IMMEDIATELY** move this file from `trinity/work-orders/` to `trinity/sessions/`
-   - [ ] **THIS STEP IS MANDATORY** - Work orders left in trinity/work-orders/ are considered incomplete
+   - [ ] **IMMEDIATELY** move this file from `.claude/trinity/work-orders/` to `.claude/trinity/sessions/`
+   - [ ] **THIS STEP IS MANDATORY** - Work orders left in .claude/trinity/work-orders/ are considered incomplete
 
    **Execute this exact command:**
    ```bash
-   mv trinity/work-orders/{{workOrderFilename}} trinity/sessions/
+   mv .claude/trinity/work-orders/{{workOrderFilename}} .claude/trinity/sessions/
    ```
 
 **Step 3: Verify File Locations** ✅
-   - [ ] This work order file NOW EXISTS in: `trinity/sessions/{{workOrderFilename}}`
+   - [ ] This work order file NOW EXISTS in: `.claude/trinity/sessions/{{workOrderFilename}}`
    - [ ] Completion report exists in: `${PROJECT_REPORTS}/[TYPE]-INVESTIGATION-[TIMESTAMP].md`
-   - [ ] This work order NO LONGER EXISTS in: `trinity/work-orders/`
+   - [ ] This work order NO LONGER EXISTS in: `.claude/trinity/work-orders/`
 
    **If any verification fails, the work order is NOT complete. Fix immediately.**
 
 **Step 4: Session Cleanup (when entire session complete):**
    - [ ] When session is complete, run `/trinity-end`
-   - [ ] trinity-end will archive ALL files from `trinity/sessions/` and `${PROJECT_REPORTS}/`
+   - [ ] trinity-end will archive ALL files from `.claude/trinity/sessions/` and `${PROJECT_REPORTS}/`
    - [ ] Next session starts with empty sessions/ and reports/ folders
 
 **Archive Destination (via trinity-end):**
-- Work order → `trinity/archive/work-orders/YYYY-MM-DD/`
-- Completion report → `trinity/archive/reports/YYYY-MM-DD/`
-- JUNO audit report → `trinity/archive/reports/YYYY-MM-DD/` (if applicable)
-- Session summary → `trinity/archive/sessions/YYYY-MM-DD/`
+- Work order → `.claude/trinity/archive/work-orders/YYYY-MM-DD/`
+- Completion report → `.claude/trinity/archive/reports/YYYY-MM-DD/`
+- JUNO audit report → `.claude/trinity/archive/reports/YYYY-MM-DD/` (if applicable)
+- Session summary → `.claude/trinity/archive/sessions/YYYY-MM-DD/`
 
 ---
 
@@ -202,5 +189,3 @@ ALL team members (CC, TRINITY, specialists) are PERMANENTLY FORBIDDEN from perfo
 
 **Remember:** Focus on discovering patterns and root causes, not just symptoms. Your investigation will guide our next strategic decisions. Investigations are read-only - no file modifications or git operations.
 
-*Trinity Method v2.0 - Investigation Work Order Template*
-*Project-Isolated Architecture with Dynamic Paths*

package/dist/templates/{work-orders → trinity/templates/work-orders}/PATTERN-TEMPLATE.md.template

@@ -4,19 +4,6 @@
 
 ---
 
-## AUTHORIZATION
-
-```
-TRINITY COUNCIL APPROVAL:
-☑ LUKA: APPROVED - [Pattern work justification]
-☑ TRINITY: APPROVED - [Pattern approach validation]
-☑ CC: PENDING - Awaiting your acknowledgment
-
-STATUS: APPROVED FOR EXECUTION
-```
-
----
-
 ## MISSION OBJECTIVE
 
 [Clear statement about pattern work - either extracting patterns from issues or implementing pattern-based fixes]
@@ -171,31 +158,31 @@ Probable_Matches:
    - [ ] All deliverables include required sections listed above
 
 **Step 2: 🚨 MOVE THIS WORK ORDER FILE 🚨** ✅
-   - [ ] **IMMEDIATELY** move this file from `trinity/work-orders/` to `trinity/sessions/`
-   - [ ] **THIS STEP IS MANDATORY** - Work orders left in trinity/work-orders/ are considered incomplete
+   - [ ] **IMMEDIATELY** move this file from `.claude/trinity/work-orders/` to `.claude/trinity/sessions/`
+   - [ ] **THIS STEP IS MANDATORY** - Work orders left in .claude/trinity/work-orders/ are considered incomplete
 
    **Execute this exact command:**
    ```bash
-   mv trinity/work-orders/{{workOrderFilename}} trinity/sessions/
+   mv .claude/trinity/work-orders/{{workOrderFilename}} .claude/trinity/sessions/
    ```
 
 **Step 3: Verify File Locations** ✅
-   - [ ] This work order file NOW EXISTS in: `trinity/sessions/{{workOrderFilename}}`
+   - [ ] This work order file NOW EXISTS in: `.claude/trinity/sessions/{{workOrderFilename}}`
    - [ ] Completion report exists in: `${PROJECT_REPORTS}/PATTERN-[NAME]-[TIMESTAMP].md`
-   - [ ] This work order NO LONGER EXISTS in: `trinity/work-orders/`
+   - [ ] This work order NO LONGER EXISTS in: `.claude/trinity/work-orders/`
 
    **If any verification fails, the work order is NOT complete. Fix immediately.**
 
 **Step 4: Session Cleanup (when entire session complete):**
    - [ ] When session is complete, run `/trinity-end`
-   - [ ] trinity-end will archive ALL files from `trinity/sessions/` and `${PROJECT_REPORTS}/`
+   - [ ] trinity-end will archive ALL files from `.claude/trinity/sessions/` and `${PROJECT_REPORTS}/`
    - [ ] Next session starts with empty sessions/ and reports/ folders
 
 **Archive Destination (via trinity-end):**
-- Work order → `trinity/archive/work-orders/YYYY-MM-DD/`
-- Completion report → `trinity/archive/reports/YYYY-MM-DD/`
-- JUNO audit report → `trinity/archive/reports/YYYY-MM-DD/` (if applicable)
-- Session summary → `trinity/archive/sessions/YYYY-MM-DD/`
+- Work order → `.claude/trinity/archive/work-orders/YYYY-MM-DD/`
+- Completion report → `.claude/trinity/archive/reports/YYYY-MM-DD/`
+- JUNO audit report → `.claude/trinity/archive/reports/YYYY-MM-DD/` (if applicable)
+- Session summary → `.claude/trinity/archive/sessions/YYYY-MM-DD/`
 
 ---
 
@@ -315,6 +302,3 @@ Note what must remain manual:
 ---
 
 **Remember:** Pattern work is about maximizing impact through systematic fixes. One pattern fix can resolve dozens of issues. Document patterns thoroughly for future reuse. Report all changes to LUKA for git operations.
-
-*Trinity Method v2.0 - Pattern Work Order Template*
-*Project-Isolated Architecture with Dynamic Paths*