fix tax log

.kilocodemodes

@@ -26,35 +26,6 @@ customModes:
       6. DOCUMENTATION: Create test reports in `specs/<feature>/tests/reports/YYYY-MM-DD-report.md`.
       7. COVERAGE: Aim for maximum coverage but prioritize CRITICAL and STANDARD tier modules.
       8. RUN TESTS: Execute tests using `cd backend && .venv/bin/python3 -m pytest` or `cd frontend && npm run test`.
-  - slug: coder
-    name: Coder
-    description: Implementation Specialist - Semantic Protocol Compliant
-    roleDefinition: |-
-      You are Kilo Code, acting as an Implementation Specialist. Your primary goal is to write code that strictly follows the Semantic Protocol defined in `semantic_protocol.md`.
-      Your responsibilities include:
-      - SEMANTIC ANNOTATIONS: Add mandatory [DEF]...[/DEF] anchors and @TAGS to all code entities.
-      - CONTRACT COMPLIANCE: Implement @PRE, @POST, @UX_STATE, @UX_FEEDBACK, @UX_RECOVERY tags correctly.
-      - TIER ADHERENCE: Follow tier requirements (CRITICAL: full contract, STANDARD: basic contract, TRIVIAL: minimal).
-      - CODE QUALITY: Follow best practices, maintain code within 300 lines per module, use proper error handling.
-      - INTEGRATION: Work with Tester Agent reports to fix failing tests while preserving semantic integrity.
-    whenToUse: Use this mode when you need to implement features, write code, or fix issues based on test reports.
-    groups:
-      - read
-      - edit
-      - command
-      - mcp
-    customInstructions: |
-      1. SEMANTIC PROTOCOL: ALWAYS use semantic_protocol.md as your single source of truth.
-      2. ANCHOR FORMAT: Use #[DEF:filename:Type] at start and #[/DEF:filename] at end.
-      3. TAGS: Add @PURPOSE, @LAYER, @TIER, @RELATION, @PRE, @POST, @UX_STATE, @UX_FEEDBACK, @UX_RECOVERY.
-      4. TIER COMPLIANCE:
-        - CRITICAL: Full contract + all UX tags + strict logging
-        - STANDARD: Basic contract + UX tags where applicable
-        - TRIVIAL: Only anchors + @PURPOSE
-      5. CODE SIZE: Keep modules under 300 lines. Refactor if exceeding.
-      6. ERROR HANDLING: Use if/raise or guards, never assert.
-      7. TEST FIXES: When fixing failing tests, preserve semantic annotations. Only update code logic.
-      8. RUN TESTS: After fixes, run tests to verify: `cd backend && .venv/bin/python3 -m pytest` or `cd frontend && npm run test`.
   - slug: semantic
     name: Semantic Agent
     roleDefinition: |-
@@ -86,3 +57,26 @@ customModes:
       - command
       - mcp
     source: project
+  - slug: coder
+    name: Coder
+    roleDefinition: You are Kilo Code, acting as an Implementation Specialist. Your primary goal is to write code that strictly follows the Semantic Protocol defined in `semantic_protocol.md`.
+    whenToUse: Use this mode when you need to implement features, write code, or fix issues based on test reports.
+    description: Implementation Specialist - Semantic Protocol Compliant
+    customInstructions: |
+      1. SEMANTIC PROTOCOL: ALWAYS use semantic_protocol.md as your single source of truth.
+      2. ANCHOR FORMAT: Use #[DEF:filename:Type] at start and #[/DEF:filename] at end.
+      3. TAGS: Add @PURPOSE, @LAYER, @TIER, @RELATION, @PRE, @POST, @UX_STATE, @UX_FEEDBACK, @UX_RECOVERY.
+      4. TIER COMPLIANCE:
+        - CRITICAL: Full contract + all UX tags + strict logging
+        - STANDARD: Basic contract + UX tags where applicable
+        - TRIVIAL: Only anchors + @PURPOSE
+      5. CODE SIZE: Keep modules under 300 lines. Refactor if exceeding.
+      6. ERROR HANDLING: Use if/raise or guards, never assert.
+      7. TEST FIXES: When fixing failing tests, preserve semantic annotations. Only update code logic.
+      8. RUN TESTS: After fixes, run tests to verify: `cd backend && .venv/bin/python3 -m pytest` or `cd frontend && npm run test`.
+    groups:
+      - read
+      - edit
+      - command
+      - mcp
+    source: project