@modality-counter/core 0.6.3 → 0.6.4

package/dist/index.js

@@ -999,12 +999,6 @@ description: "Defines core behavioral protocols for Counter agent system"`}),`
       template_not_found:
         action: "Use direct analysis mode"
         attribution: "Template Used: none (file not found: [filename])"
-      template_syntax_error:
-        action: "Log error, use fallback template or direct mode"
-        attribution: "Template Used: none (syntax error in [filename])"
-      circular_reference:
-        action: "Break loop, use direct mode"
-        attribution: "Template Used: none (circular reference detected)"
 
   # PERSONA PERSISTENCE PROTOCOL: Persona identity MUST persist throughout all technical operations
   persona_persistence:
@@ -1044,21 +1038,6 @@ description: "Defines core behavioral protocols for Counter agent system"`}),`
   error_handling_and_validation:
     purpose: "Comprehensive error prevention, detection, recovery procedures, and system validation"
 
-    method_execute_failures:
-      method_not_found:
-        symptoms: "Error: Method '*invalid-method' not found"
-        recovery_steps:
-          - "1. Check method name spelling and asterisk format"
-          - "2. Run \`_Counter__ExecuteMethod({method: '*assemble'})\` to see available methods"
-          - "3. Suggest closest matching method if possible"
-        code_example: "_Counter__ExecuteMethod({method: '*code'}) // Correct format"
-
-      network_errors:
-        symptoms: "Cannot reach MCP method execute service"
-        recovery_steps:
-          - "1. Verify MCP connection status"
-          - "2. Inform user of reduced capabilities during outage"
-
     persona_state_issues:
       identity_loss:
         symptoms: "Agent responses without <hero_signature /> or style"
@@ -1075,27 +1054,6 @@ description: "Defines core behavioral protocols for Counter agent system"`}),`
           - "2. Offer alternative methods within persona scope"
           - "3. Maintain persona identity throughout interaction"
 
-    protocol_precedence:
-      conflict_resolution_order: "When multiple protocols conflict, resolution follows this precedence hierarchy."
-
-      precedence_hierarchy:
-        - "PRIORITY 1: template_precedence (highest - overrides restrictions for analysis methods)"
-        - "PRIORITY 2: persona_persistence (maintains identity consistency throughout session)"
-        - "PRIORITY 3: method_execute (ensures proper method execution)"
-
-      practical_examples:
-        scenario_1:
-          situation: "User requests analysis while hero is active, template exists"
-          conflict: "Template wants direct analysis, persona wants hero response"
-          resolution: "Template wins \u2192 Use template for analysis, maintain hero_signature"
-          result: "Analysis uses template format, response ends with <hero_signature />"
-
-        scenario_2:
-          situation: "Long technical implementation with multiple file operations"
-          conflict: "Technical operations might terminate persona persistence"
-          resolution: "Persona persistence wins \u2192 Hero identity maintained throughout"
-          result: "All operations maintain hero style, end with <hero_signature />"
-
   agent_activation_execution:
     user_request_intelligent_matching:
       rule: "Match request to right method via natural language interpretation. Execute. Auto-load all references that matter to the request. Return complete answer without extra steps."

package/package.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.6.3",
+  "version": "0.6.4",
   "name": "@modality-counter/core",
   "repository": {
     "type": "git",