trinity-method-sdk 2.0.1 → 2.0.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -19,6 +19,32 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
19
19
 
20
20
  ### Security
21
21
 
22
+ ## [2.0.2] - 2026-01-02
23
+
24
+ ### Added
25
+
26
+ - **DOCUMENTATION RULES** section to all APO documentation commands (`/trinity-docs`, `/trinity-readme`, `/trinity-changelog`)
27
+ - Rule 1: No Self-Serving Trinity Documentation - Prevents APO from including Trinity Method information in user project documentation
28
+ - Provides clear ✅/❌ examples and rationale for focusing exclusively on user's codebase
29
+ - Explicit **Write tool execution commands** throughout `/trinity-docs` Phase 2
30
+ - Added 🚨 CRITICAL EXECUTION REQUIREMENT section at Phase 2 start
31
+ - Added **EXECUTION REQUIRED** code blocks for each seeding step
32
+ - Added **Phase 2 Execution Summary** with mandatory file creation checklist
33
+ - Ensures APO creates actual documentation files instead of just showing templates
34
+
35
+ ### Changed
36
+
37
+ - **`/trinity-docs` command:** Enhanced Phase 2 with explicit Write tool requirements
38
+ - Step 2 (Guides): Added execution requirements for getting-started.md and framework-specific guides
39
+ - Step 3 (API): Added execution requirements for api/README.md
40
+ - Step 4 (Architecture): Added execution requirements for architecture/overview.md
41
+ - Step 5 (Reference): Added execution requirements for reference/README.md
42
+ - Phase now requires minimum 4 files to be created: getting-started.md, api/README.md, architecture/overview.md, reference/README.md
43
+
44
+ ### Fixed
45
+
46
+ - **APO file creation issue:** `/trinity-docs` now explicitly commands APO to use Write tool, preventing scenario where directory structure is created but documentation files are not written
47
+
22
48
  ## [2.0.1] - 2025-12-29
23
49
 
24
50
  ### Added