Trinity Method SDK v2.2.4

Fixed

• Trinity docs templates are now framework-agnostic - Removed Node.js/Express/TypeScript bias
  from 21 templates across discovery, guides, investigations, validation, and reports (Issue #25)
  • Replaced framework-specific code examples with generic instructions using {{FRAMEWORK}},
    {{LANGUAGE}}, and {{PACKAGE_MANAGER}} template variables
  • Templates now work correctly for Node.js, Python, Rust, Flutter, and Go projects
  • Net reduction of 684 lines by replacing verbose code samples with concise instructions

---

Full Changelog: CHANGELOG.md
npm: npm install trinity-method-sdk@2.2.4

Trinity Method SDK v2.2.3

Added

• CLAUDE.md context file refresh in trinity update - Update command now refreshes
  CLAUDE.md hierarchy and EMPLOYEE-DIRECTORY.md during updates (Issue #23)
  • Root CLAUDE.md and .claude/trinity/CLAUDE.md are always overwritten (SDK-managed)
  • .claude/EMPLOYEE-DIRECTORY.md is always overwritten (SDK-managed)
  • Source directory CLAUDE.md files are deployed if missing, skipped if they exist
  • tests/CLAUDE.md is deployed if tests/ exists but CLAUDE.md is missing
  • New claudeFilesUpdated stat displayed in update summary
  • Dry-run preview now lists CLAUDE.md and Employee Directory updates

---

Full Changelog: CHANGELOG.md
npm: npm install trinity-method-sdk@2.2.3

Trinity Method SDK v2.2.2

Changed

• Simplified gitignore patterns - Deploy and update commands now add .claude/ and
  *CLAUDE.md to .gitignore instead of granular .claude/trinity/archive/ and
  .claude/trinity/templates/ patterns. Migration handles cleanup of old patterns. (Issue #18)

Fixed

• Work order numbering scans archive directory - Added explicit WO numbering instructions to
  /utility:trinity-workorder template. Numbers now derived only from work-orders/ and
  sessions/ directories, ignoring archives. New sessions start fresh at WO-001. (Issue #19)
• trinity-end command not archiving all session files - Updated STRICT ARCHIVING PROTOCOL
  in /session:trinity-end template to archive from all .claude/trinity/ subdirectories
  (Issue #17)
  • Added archiving of completed work orders from work-orders/ directory
  • Added archiving of completed investigations and plans from investigations/ directory
  • Added archiving of Claude Code plan mode files from plans/ directory
  • Added loose archive file organization into YYYY-MM-DD date folders
  • Expanded clean slate verification to cover plans/ directory

---

Full Changelog: CHANGELOG.md
npm: npm install trinity-method-sdk@2.2.2

Trinity Method SDK v2.2.1

Added

• Legacy deployment migration in update command - trinity update now detects pre-2.2.0
  trinity/ deployments at project root and automatically migrates them to .claude/trinity/
  (Issue #14)
  • New migration.ts module with detectLegacyDeployment(), migrateLegacyDeployment(),
    and updateGitignoreForMigration()
  • Pre-flight checks updated to recognize legacy layouts instead of failing
  • Version detection falls back to trinity/VERSION for legacy deployments
  • User knowledge base files preserved during migration
• Gitignore migration in update command - trinity update now updates .gitignore
  patterns on every run, replacing old trinity/ entries with current .claude/trinity/
  patterns (Issue #14)

Fixed

• Restored *CLAUDE.md to deploy gitignore patterns - trinity deploy now adds
  *CLAUDE.md back to .gitignore, preventing project-specific CLAUDE.md files from being
  committed to version control (Issue #14)
• depcheck false positive for markdownlint-cli - Added markdownlint-cli to depcheck
  ignores in CI workflow since it is used by npm scripts, not imported in code
• Integration test timeout on Windows CI - Bumped integration test timeout from 60s to
  120s in jest.config.js for slow Windows runners

---

Full Changelog: CHANGELOG.md
npm: npm install trinity-method-sdk@2.2.1

Trinity Method SDK v2.2.0

Added

• Markdown linting in CI pipeline and pre-commit hook - Added blocking markdownlint-cli2
  validation for *.md, docs/**/*.md, and src/**/*.md in both CI and pre-commit
  • CI: Added lint step to docs job in .github/workflows/ci.yml
  • Pre-commit: Added Stage 4 to .husky/pre-commit running markdownlint on all tracked
    markdown directories
  • Enforces markdown syntax standards across all 78 markdown files using
    .markdownlint.json config
• New /trinity-breakdown slash command - Guided, user-driven implementations where CC
  acts as an instructor walking users through changes step-by-step instead of executing them
  directly (Issue #11)
• GitHub Releases workflow - Automated draft release creation on version tags (v*.*.*)
  via .github/workflows/release.yml (Issue #5)
  • 5-job pipeline: version extraction, CHANGELOG release notes extraction,
    tag-vs-package.json version validation, full CI quality gates, and draft GitHub release
  • Uses softprops/action-gh-release@v2 with draft: true — releases require manual
    publishing
  • CHANGELOG extraction uses Node.js script (not sed) matching ## [X.Y.Z] Keep a
    Changelog format
  • Fails fast on version mismatch or missing/empty CHANGELOG section
  • Coverage thresholds mirror CI pipeline: lines >= 75%, branches >= 65%,
    functions >= 80%, statements >= 75%
  • No npm publish automation — publishing remains manual via npm publish

Changed

• Enabled all TypeScript strict mode flags - Turned on strictNullChecks,
  strictPropertyInitialization, noUnusedLocals, and noUnusedParameters in
  tsconfig.json (Issue #6)
  • All four flags were previously disabled, weakening compile-time type safety
  • Codebase required zero changes for strictNullChecks and
    strictPropertyInitialization (already null-safe)
  • Prefixed 6 unused parameters with _ to satisfy noUnusedParameters
    (5 in deploy-linting.ts, 1 in summary.ts)
  • All 417 tests pass, 0 type errors, lint clean
• Added metrics module test coverage - Created comprehensive test suites for
  dependency-parser.ts and framework-detector.ts (Issue #6)
  • dependency-parser.ts coverage: 9.37% → 100% (23 tests covering Node.js, Python,
    Rust, Flutter, Go, and error paths)
  • framework-detector.ts coverage: 36.36% → 95.23% (24 tests covering all version
    detectors and package manager detection)
  • Overall project coverage improved from 83% → 89% (464 tests total)
• Fixed all 32 devDependency vulnerabilities - Resolved minimatch ReDoS, ajv ReDoS,
  and markdown-it ReDoS via npm audit fix and overrides in package.json (Issue #6)
  • npm audit fix resolved ajv (<6.14.0), markdown-it (13.0.0-14.1.0), and
    @isaacs/brace-expansion (5.0.0) — 9 vulnerabilities
  • Added overrides for minimatch@^10.2.1 to force resolution of 23 remaining
    transitive dependency vulnerabilities through eslint, jest, and typedoc
  • npm audit now reports 0 vulnerabilities (was 32: 30 high, 2 moderate)
• Restructured trinity/ into .claude/trinity/ - Consolidated deployment footprint
  from two top-level directories to one (Issue #3)
  • trinity deploy now creates .claude/trinity/ instead of a separate trinity/
    directory
  • trinity update manages .claude/trinity/ with consolidated backup (single .claude/
    backup covers everything)
  • All 50+ template files updated with new deployment target paths
  • All relative paths recalculated for new directory depth
  • 417 tests pass with restructured paths
• Updated .gitignore entries - Trinity deployment now only ignores
  .claude/trinity/archive/ and .claude/trinity/templates/ instead of all .claude/,
  *CLAUDE.md, TRINITY.md, and trinity/ allowing agents, commands, and context files
  to be tracked in version control
• Removed .claude/trinity/patterns/ directory - No longer deployed as an empty
  placeholder; directory structure reduced from 17 to 16 directories

Fixed

• Resolved ~600 markdownlint violations across 78 markdown files - Fixed all markdown
  syntax errors in docs/, root (*.md), and src/ directories (Issue #6)

  • docs/ (72 files): ~580 violations fixed (MD013 line length, MD022 blanks around
    headings, MD031/MD032 blanks around fences/lists, MD040 code fence languages, MD009
    trailing spaces, MD036 emphasis as heading, MD026 trailing punctuation)
  • README.md: 16 violations fixed (MD013, MD022, MD026, MD036, MD040)
  • CONTRIBUTING.md: 6 violations fixed (MD013, MD009, MD031, MD032, MD040)
  • CLAUDE.md: 4 violations fixed (MD022 blanks around headings)
  • src/CLAUDE.md: 42 violations fixed (MD022, MD031, MD032, MD040, MD013)
  • src/README.md: 3 violations fixed (MD013, MD040)
  • Updated .markdownlint.json config: added siblings_only: true to MD024 for Keep a
    Changelog duplicate heading compatibility

• CRITICAL: Pre-commit hooks non-functional for Node.js - Switched from Python's
  pre-commit framework to husky + lint-staged for Node.js/React projects (Issue #4)

  • Node.js/React projects now deploy .husky/pre-commit with npx lint-staged instead
    of .pre-commit-config.yaml
  • Added husky@^9.1.7 and lint-staged@^16.2.0 as devDependencies with
    prepare: 'husky' script
  • Hooks activate automatically on npm install — no manual setup required
  • lint-staged configuration injected into package.json (eslint + prettier for TS/JS,
    prettier for JSON/MD/YAML)
  • Python/Flutter/Rust projects continue to use .pre-commit-config.yaml (unchanged)
  • Existing pre-commit configurations detected and preserved (.husky/,
    .pre-commit-config.yaml, or husky/lint-staged in package.json)

• CRITICAL: CI/CD workflow templates never deployed - Fixed enableCICD from
  interactive config never bridging to ciDeploy deployment flag

  • Added bridge in deploy orchestrator:
    if (config.enableCICD) { options.ciDeploy = true; }
  • CI templates now correctly deploy when user selects CI/CD during trinity deploy

• CI template variables not processed - Added processTemplate() call to CI workflow
  deployment

  • {{PROJECT_NAME}}, {{FRAMEWORK}}, and other template variables now resolve in
    deployed ci.yml
  • Passes variables from deploy orchestrator through deployCICD() to
    deployCITemplates()

• No --force protection for GitHub Actions templates - Added existence check matching
  GitLab's pattern

  • .github/workflows/ci.yml now skipped if it already exists (unless --force is used)
  • Both GitHub and GitLab platforms now have consistent --force flag protection

• Configuration display showed wrong filename - Changed trinity-ci.yml to ci.yml
  in interactive prompt output

  • Both detected-platform and unknown-platform display now show correct filename

• CI workflow template header - Changed CI/CD Pipeline to CI Pipeline in
  ci.yml.template

Removed

• TRINITY.md root file - No longer deployed; Trinity context is now at
  .claude/trinity/CLAUDE.md
  • Deleted src/templates/root/TRINITY.md.template
  • Removed deployTrinityMarkdown() function from deploy pipeline
• Dead template files - Deleted cd.yml.template (used undefined {{DOMAIN}}
  variable) and github-actions.yml (orphaned, never referenced)
• CD workflow references - Removed all Continuous Deployment workflow references from
  source code, templates (EIN, TAN, init, verify), CI workflow, tests, and documentation

---

Full Changelog: CHANGELOG.md
npm: npm install trinity-method-sdk@2.2.0

Trinity Method SDK v2.1.0 - Autonomous Documentation Maintenance

Major release introducing the trinity-docs-update command for autonomous documentation maintenance with JUNO audit orchestration and 3-parallel APO execution system.

✨ Key Features

• NEW /trinity-docs-update command with autonomous execution
• JUNO audit system with database & environment verification protocols
• 3 parallel APO instances with mandatory codebase verification
• Verification loop ensuring 100% completion before final audit
• 42 new API documentation files in organized structure
• Comprehensive README accuracy corrections (88 components, 19 agents)

🚀 What's New

Autonomous Documentation System

• trinity-docs-update command: Automated documentation maintenance workflow
• JUNO Integration: Audit orchestration with comprehensive verification
• Parallel APO Execution: 3 instances running simultaneously for faster updates
• Verification Loop: Ensures 100% task completion before final audit

Documentation Improvements

• 42 new API documentation files with organized structure
• README accuracy audit: Component counts, agent organization, template structure
• Corrected agent breakdown: 7 execution + 1 audit + 4 infrastructure + 3 leadership + 4 planning
• Updated command categories: Added maintenance/ with 4 commands

📦 Component Overview

88 Production Components:

• 19 Agent Templates (organized across 5 teams)
• 20 Slash Commands (7 categories)
• 9 Knowledge Base Templates
• 5 Investigation Templates
• 6 Work Order Templates
• 25 Documentation Templates
• 2 Root Templates
• 2 CI/CD Workflow Templates

Plus 13 Linting Configurations for Node.js, Python, Flutter, and Rust

🔄 Breaking Changes

None - This is a backward-compatible release.

📝 Migration Guide

To update your existing Trinity deployment:

npx trinity-method-sdk update

Trinity Method SDK v1.0.0

Changelog

All notable changes to Trinity Method SDK will be documented in this file.

The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.

1.0.0 - 2025-10-01

Added

• Initial release of Trinity Method SDK for Claude Code
• 7 specialized Trinity agents (Aly, AJ, TAN, ZEN, INO, Ein, JUNO)
• Claude Code-exclusive deployment
• Interactive deployment with linting and CI/CD configuration
• Linting configuration (ESLint, Prettier, etc.)
• CI/CD automation (GitHub Actions, GitLab CI)
• Matrix testing support
• Coverage integration (Codecov, Coveralls)
• Employee Directory with agent documentation
• Trinity structure (knowledge-base, templates)
• CLAUDE.md context file deployment
• README injection for Trinity Method section
• 8 slash commands (/trinity-init, /trinity-verify, /trinity-docs, /trinity-start, /trinity-continue, /trinity-end, /trinity-workorder, /trinity-agents)
• Session management with archival system
• Comprehensive CLI documentation

Strategic Decision

• Focused exclusively on Claude Code for exceptional user experience
• Community contributions welcome for other coding agents