@xelth/eck-snapshot 6.0.0 → 6.0.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@xelth/eck-snapshot",
-  "version": "6.0.0",
+  "version": "6.0.2",
   "description": "A powerful CLI tool to create and restore single-file text snapshots of Git repositories. Optimized for AI context, LLM workflows, and multi-agent Swarm coordination.",
   "main": "index.js",
   "type": "module",

package/setup.json

@@ -188,6 +188,19 @@
           "lib"
         ],
         "priority": 6
+      },
+      "postgresql": {
+        "files": [
+          "postgresql.conf",
+          "pg_hba.conf",
+          "PG_VERSION"
+        ],
+        "directories": [
+          "data/base",
+          "data/global",
+          "data/pg_wal"
+        ],
+        "priority": 10
       }
     }
   },
@@ -532,6 +545,38 @@
           ".so",
           ".out"
         ]
+      },
+      "postgresql": {
+        "filesToIgnore": [
+          "PG_VERSION",
+          "postmaster.pid",
+          "postmaster.opts",
+          "pg_ident.conf",
+          "*.log"
+        ],
+        "dirsToIgnore": [
+          "base/",
+          "global/",
+          "pg_wal/",
+          "pg_xact/",
+          "pg_commit_ts/",
+          "pg_dynshmem/",
+          "pg_logical/",
+          "pg_multixact/",
+          "pg_notify/",
+          "pg_replslot/",
+          "pg_serial/",
+          "pg_snapshots/",
+          "pg_stat/",
+          "pg_stat_tmp/",
+          "pg_subtrans/",
+          "pg_tblspc/",
+          "pg_twophase/"
+        ],
+        "extensionsToIgnore": [
+          ".fsm",
+          ".vm"
+        ]
       }
     }
   },
@@ -576,70 +621,70 @@
         "capabilities": ["npm", "git", "basic editing"],
         "restrictions": ["Do not use for complex architectural tasks"]
       },
-      "jas": {
-        "active": true,
-        "name": "Junior Architect (Sonnet 4.5)",
-        "description": "Project Mode Orchestrator (Claude Code only). Smart & Fast Manager. Manages GLM Z.AI workers for efficient task delegation.",
-        "guiSupport": true,
-        "identification": {
-          "markers": ["sonnet", "fast_architect"]
-        },
-        "capabilities": [
-          "glm_zai_frontend",
-          "glm_zai_backend",
-          "glm_zai_qa",
-          "glm_zai_refactor",
-          "glm_zai_general",
-          "git operations",
-          "npm run dev"
-        ],
-        "restrictions": [
-          "Prefer delegating heavy coding to GLM Z.AI workers",
-          "Focus on glue code and logic verification"
-        ]
-      },
-      "jao": {
-        "active": true,
-        "name": "Junior Architect (Opus 4.5)",
-        "description": "Project Mode Orchestrator (Claude Code only). Deep Thinker & Planner. Expensive. Use for critical architecture, security, and complex logic.",
-        "guiSupport": true,
-        "identification": {
-          "markers": ["opus", "deep_architect"]
-        },
-        "capabilities": [
-          "glm_zai_frontend",
-          "glm_zai_backend",
-          "glm_zai_qa",
-          "glm_zai_refactor",
-          "glm_zai_general",
-          "analysis"
-        ],
-        "restrictions": [
-          "STRICTLY DELEGATE boilerplate to GLM Z.AI",
-          "Verify every line of code generated by workers",
-          "Plan before execution"
-        ]
-      },
-      "jaz": {
-        "active": true,
-        "name": "Junior Architect (GLM-4.7 via OpenCode)",
-        "description": "Project Orchestrator for OpenCode. Highly accessible/budget-friendly. Manages the GLM Z.AI worker swarm.",
-        "guiSupport": true,
-        "identification": {
-          "markers": ["opencode", "glm-4.7"]
-        },
-        "capabilities": [
-          "glm_zai_frontend",
-          "glm_zai_backend",
-          "glm_zai_qa",
-          "glm_zai_refactor",
-          "glm_zai_general",
-          "git operations"
-        ],
-        "restrictions": [
-          "Strictly delegate complex/large logic to workers to preserve context window"
-        ]
-      },
+      "jas": {
+        "active": true,
+        "name": "Junior Architect (Sonnet 4.5)",
+        "description": "Project Mode Orchestrator (Claude Code only). Smart & Fast Manager. Manages GLM Z.AI workers for efficient task delegation.",
+        "guiSupport": true,
+        "identification": {
+          "markers": ["sonnet", "fast_architect"]
+        },
+        "capabilities": [
+          "glm_zai_frontend",
+          "glm_zai_backend",
+          "glm_zai_qa",
+          "glm_zai_refactor",
+          "glm_zai_general",
+          "git operations",
+          "npm run dev"
+        ],
+        "restrictions": [
+          "Prefer delegating heavy coding to GLM Z.AI workers",
+          "Focus on glue code and logic verification"
+        ]
+      },
+      "jao": {
+        "active": true,
+        "name": "Junior Architect (Opus 4.5)",
+        "description": "Project Mode Orchestrator (Claude Code only). Deep Thinker & Planner. Expensive. Use for critical architecture, security, and complex logic.",
+        "guiSupport": true,
+        "identification": {
+          "markers": ["opus", "deep_architect"]
+        },
+        "capabilities": [
+          "glm_zai_frontend",
+          "glm_zai_backend",
+          "glm_zai_qa",
+          "glm_zai_refactor",
+          "glm_zai_general",
+          "analysis"
+        ],
+        "restrictions": [
+          "STRICTLY DELEGATE boilerplate to GLM Z.AI",
+          "Verify every line of code generated by workers",
+          "Plan before execution"
+        ]
+      },
+      "jaz": {
+        "active": true,
+        "name": "Junior Architect (GLM-4.7 via OpenCode)",
+        "description": "Project Orchestrator for OpenCode. Highly accessible/budget-friendly. Manages the GLM Z.AI worker swarm.",
+        "guiSupport": true,
+        "identification": {
+          "markers": ["opencode", "glm-4.7"]
+        },
+        "capabilities": [
+          "glm_zai_frontend",
+          "glm_zai_backend",
+          "glm_zai_qa",
+          "glm_zai_refactor",
+          "glm_zai_general",
+          "git operations"
+        ],
+        "restrictions": [
+          "Strictly delegate complex/large logic to workers to preserve context window"
+        ]
+      },
       "production_server": {
         "active": true,
         "name": "Production Server Agent (AGENT_PROD_SERVER)",

package/src/templates/opencode/coder.template.md

@@ -6,17 +6,20 @@ You are an Expert Developer. The architecture is already decided. Your job is to
 ## DEFINITION OF DONE (CRITICAL)
 When task is complete, you must report back and sync context.
 
-**OPTION A: Using MCP Tool (Recommended)**
-Call the \`eck_finish_task\` tool. Pass your detailed markdown report into the \`status\` argument.
-- The tool will automatically write the report to \`AnswerToSA.md\`, commit, and generate a snapshot.
-- **DO NOT** manually write to \`AnswerToSA.md\` with your file editing tools (it will fail safety checks).
-- **WARNING: USE ONLY ONCE.** Do not use \`eck_finish_task\` for intermediate testing. It spams snapshot history.
+**PRIMARY METHOD: Use `eck_finish_task` MCP tool.**
+Pass your detailed markdown report into the `status` argument.
+- The tool will automatically write the report, commit, and generate a snapshot.
+- **DO NOT** manually write to `AnswerToSA.md` with your file editing tools.
+- **WARNING: USE ONLY ONCE.** Do not use for intermediate testing.
 
-**OPTION B: Manual CLI (Fallback)**
-If the MCP tool is unavailable:
-1. **READ** \`.eck/lastsnapshot/AnswerToSA.md\` using your \`Read\` tool (REQUIRED by safety rules before overwriting).
-2. **WRITE** your report to that file.
-3. Run \`eck-snapshot update\` in terminal.
+**FALLBACK METHOD (Only if MCP tool is missing):**
+If `eck_finish_task` is NOT in your available tools, you MUST do the following:
+0. **WARN THE USER:** State clearly in your response: "⚠️ `eck-core` MCP server is not connected. Proceeding with manual fallback."
+1. **READ:** Read `.eck/lastsnapshot/AnswerToSA.md` using your `Read` tool (REQUIRED before overwriting).
+2. **WRITE:** Overwrite that file with your report.
+3. **COMMIT (CRITICAL):** Run `git add .` and `git commit -m "chore: task report"` in the terminal.
+4. **SNAPSHOT:** Run `eck-snapshot update` in the terminal.
+*(Note: The snapshot compares against the git anchor. If you skip step 3, it will say "No changes detected").*
 
 ## PROJECT CONTEXT (.eck DIRECTORY)
 The `.eck/` directory contains critical project documentation. **Before starting your task, you MUST:**

package/src/templates/opencode/junior-architect.template.md

@@ -36,18 +36,21 @@ For bulk work where delegation saves YOUR expensive context window, YOU MUST del
 ## 4. DEFINITION OF DONE (CRITICAL)
 When you have completed your coding task and verified it works, you must report back and sync context.
 
-**OPTION A: Using MCP Tool (Recommended)**
-Call the \`eck_finish_task\` tool. Pass your detailed markdown report into the \`status\` argument.
-- The tool will automatically write the report to \`AnswerToSA.md\`, commit, and generate a snapshot.
-- **DO NOT** manually write to \`AnswerToSA.md\` with your file editing tools.
-- **WARNING: USE ONLY ONCE.** Do not use \`eck_finish_task\` for intermediate testing. It spams snapshot history.
+**PRIMARY METHOD: Use `eck_finish_task` MCP tool.**
+Pass your detailed markdown report into the `status` argument.
+- The tool will automatically write the report, commit, and generate a snapshot.
+- **DO NOT** manually write to `AnswerToSA.md` with your file editing tools.
+- **WARNING: USE ONLY ONCE.** Do not use for intermediate testing.
 
-**OPTION B: Manual CLI (Fallback)**
-If the MCP tool is unavailable:
-1. **READ** \`.eck/lastsnapshot/AnswerToSA.md\` using your \`Read\` tool (REQUIRED by safety rules before overwriting).
-2. **WRITE** your report to that file.
-3. Run \`eck-snapshot update\` in terminal.
-4. If you are entirely blocked, use the \`eck_fail_task\` tool.
+**FALLBACK METHOD (Only if MCP tool is missing):**
+If `eck_finish_task` is NOT in your available tools, you MUST do the following:
+0. **WARN THE USER:** State clearly in your response: "⚠️ `eck-core` MCP server is not connected. Proceeding with manual fallback."
+1. **READ:** Read `.eck/lastsnapshot/AnswerToSA.md` using your `Read` tool (REQUIRED before overwriting).
+2. **WRITE:** Overwrite that file with your report.
+3. **COMMIT (CRITICAL):** Run `git add .` and `git commit -m "chore: task report"` in the terminal.
+4. **SNAPSHOT:** Run `eck-snapshot update` in the terminal.
+*(Note: The snapshot compares against the git anchor. If you skip step 3, it will say "No changes detected").*
+5. If you are entirely blocked, use the `eck_fail_task` tool.
 
 ## 5. SWARM ERROR RECOVERY & THE RALPH LOOP
 **Core Directive:** You are "deterministically persistent". Failures are expected, giving up is not.

package/src/utils/claudeMdGenerator.js

@@ -48,9 +48,18 @@ Your task is NOT complete until code works globally.
 2. **Finish & Report:** Use the \`eck_finish_task\` MCP tool.
    - Pass your full markdown report into the \`status\` argument.
    - The tool will automatically write the report to \`.eck/lastsnapshot/AnswerToSA.md\`, commit, and generate a snapshot.
-   - **DO NOT** try to manually write to \`.eck/lastsnapshot/AnswerToSA.md\` with the \`Write\` tool (it will fail safety checks).
+   - **DO NOT** try to manually write to \`.eck/lastsnapshot/AnswerToSA.md\` with the \`Write\` tool.
    - **WARNING:** USE ONLY ONCE PER TASK. Do not use this tool or \`eck-snapshot update\` for intermediate testing.
 
+**FALLBACK METHOD (Only if MCP tool is missing):**
+If \`eck_finish_task\` is NOT in your available tools, you MUST do the following:
+0. **WARN THE USER:** State clearly in your response: "⚠️ \`eck-core\` MCP server is not connected. Proceeding with manual fallback."
+1. **READ:** Read \`.eck/lastsnapshot/AnswerToSA.md\` using your \`Read\` tool (REQUIRED before overwriting).
+2. **WRITE:** Overwrite that file with your report.
+3. **COMMIT (CRITICAL):** Run \`git add .\` and \`git commit -m "chore: task report"\` in the terminal.
+4. **SNAPSHOT:** Run \`eck-snapshot update\` in the terminal.
+*(Note: The snapshot compares against the git anchor. If you skip step 3, it will say "No changes detected").*
+
 ## 5. SWARM ERROR RECOVERY & ARCHITECT HYPOTHESES
 1. **Runtime Check:** Always check the \`.eck/RUNTIME_STATE.md\` and running processes before coding.
 2. **Challenge the Architect:** If the Architect's hypothesis is not confirmed during verification, discard it and look for the real root cause in the runtime.
@@ -72,17 +81,20 @@ You are an Expert Developer. The architecture is already decided. Your job is to
 ## DEFINITION OF DONE (CRITICAL)
 When task is complete, you must report back and sync context.
 
-**OPTION A: Using MCP Tool (Recommended)**
-Call the \`eck_finish_task\` tool. Pass your detailed markdown report into the \`status\` argument.
-- The tool will automatically write the report to \`AnswerToSA.md\`, commit, and generate a snapshot.
-- **DO NOT** manually write to \`AnswerToSA.md\` with your file editing tools (it will fail safety checks).
-- **WARNING: USE ONLY ONCE.** Do not use \`eck_finish_task\` for intermediate testing.
-
-**OPTION B: Manual CLI (Fallback)**
-If the MCP tool is unavailable:
-1. **READ** \`.eck/lastsnapshot/AnswerToSA.md\` using your \`Read\` tool (REQUIRED by safety rules before overwriting).
-2. **WRITE** your report to that file.
-3. Run \`eck-snapshot update\` in terminal.
+**PRIMARY METHOD: Use \`eck_finish_task\` MCP tool.**
+Pass your detailed markdown report into the \`status\` argument.
+- The tool will automatically write the report, commit, and generate a snapshot.
+- **DO NOT** manually write to \`AnswerToSA.md\` with your file editing tools.
+- **WARNING: USE ONLY ONCE.** Do not use for intermediate testing.
+
+**FALLBACK METHOD (Only if MCP tool is missing):**
+If \`eck_finish_task\` is NOT in your available tools, you MUST do the following:
+0. **WARN THE USER:** State clearly in your response: "⚠️ \`eck-core\` MCP server is not connected. Proceeding with manual fallback."
+1. **READ:** Read \`.eck/lastsnapshot/AnswerToSA.md\` using your \`Read\` tool (REQUIRED before overwriting).
+2. **WRITE:** Overwrite that file with your report.
+3. **COMMIT (CRITICAL):** Run \`git add .\` and \`git commit -m "chore: task report"\` in the terminal.
+4. **SNAPSHOT:** Run \`eck-snapshot update\` in the terminal.
+*(Note: The snapshot compares against the git anchor. If you skip step 3, it will say "No changes detected").*
 
 ## PROJECT CONTEXT (.eck DIRECTORY)
 The \`.eck/\` directory contains critical project documentation. **Before starting your task, you MUST:**