npm - trinity-method-sdk - Versions diffs - 2.0.8 → 2.1.0 - Mend

trinity-method-sdk 2.0.8 → 2.1.0

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.

Files changed (123) hide show

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

@@ -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 RENAMED Viewed

@@ -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]
@@ -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 RENAMED Viewed

@@ -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]
@@ -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 RENAMED Viewed

@@ -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]
@@ -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 RENAMED Viewed

@@ -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]
@@ -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*

package/dist/templates/{work-orders → trinity/templates/work-orders}/VERIFICATION-TEMPLATE.md.template RENAMED Viewed

@@ -4,19 +4,6 @@
 ---
-## AUTHORIZATION
-```
-TRINITY COUNCIL APPROVAL:
-☑ LUKA: APPROVED - [Need for verification]
-☑ TRINITY: APPROVED - [Verification approach]
-☑ CC: PENDING - Awaiting your acknowledgment
-STATUS: APPROVED FOR EXECUTION
-```
----
 ## MISSION OBJECTIVE
 [Clear statement of what needs to be verified and why]
@@ -268,6 +255,3 @@ If verification reveals critical issues:
 ---
 **Remember:** Verification is about confirming that implementations work as intended without introducing new issues. Be thorough but efficient. Document everything clearly. Verifications are read-only - no file modifications or git operations.
-*Trinity Method v2.0 - Verification Work Order Template*
-*Project-Isolated Architecture with Dynamic Paths*

package/package.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
   "name": "trinity-method-sdk",
-  "version": "2.0.8",
+  "version": "2.1.0",
   "description": "Trinity Method SDK - Investigation-first development methodology for any project",
   "type": "module",
   "main": "dist/index.js",