@suwujs/codex-vault 0.7.0 → 0.7.2

package/README.md

@@ -174,6 +174,14 @@ npx @suwujs/codex-vault upgrade     # Upgrade hooks and skills (preserves vault
 npx @suwujs/codex-vault uninstall   # Remove hooks and skills (preserves vault data)
 ```
 
+## Testing
+
+```bash
+npm test                # Full E2E test suite
+npm run test:cli        # CLI commands only (22 tests)
+npm run test:hooks      # Hook scripts only (33 tests)
+```
+
 ## Requirements
 
 - Git

package/README.zh-CN.md

@@ -154,6 +154,14 @@ npx @suwujs/codex-vault upgrade     # 升级 hooks 和 skills（保留 vault 数
 npx @suwujs/codex-vault uninstall   # 移除 hooks 和 skills（保留 vault 数据）
 ```
 
+## 测试
+
+```bash
+npm test                # 完整 E2E 测试
+npm run test:cli        # CLI 命令测试（22 个）
+npm run test:hooks      # Hook 脚本测试（33 个）
+```
+
 ## 配置
 
 | 配置项 | 文件 | 说明 |

package/bin/cli.js

@@ -7,7 +7,7 @@ const fs = require('fs');
 
 const PKG_ROOT = path.resolve(__dirname, '..');
 const INSTALL_SH = path.join(PKG_ROOT, 'plugin', 'install.sh');
-const VERSION = fs.readFileSync(path.join(PKG_ROOT, 'plugin', 'VERSION'), 'utf8').trim();
+const VERSION = JSON.parse(fs.readFileSync(path.join(PKG_ROOT, 'package.json'), 'utf8')).version;
 
 const args = process.argv.slice(2);
 const cmd = args[0] || 'init';

package/package.json

@@ -1,12 +1,17 @@
 {
   "name": "@suwujs/codex-vault",
-  "version": "0.7.0",
+  "version": "0.7.2",
   "description": "Persistent knowledge vault for LLM agents (Claude Code, Codex CLI)",
   "license": "MIT",
   "repository": {
     "type": "git",
     "url": "https://github.com/sukbearai/codex-vault"
   },
+  "scripts": {
+    "test": "bash tests/test_e2e.sh",
+    "test:cli": "bash tests/test_cli.sh",
+    "test:hooks": "bash tests/test_hooks.sh"
+  },
   "bin": {
     "codex-vault": "bin/cli.js"
   },

package/bin/codex-vault-run.sh

@@ -1,28 +0,0 @@
-#!/bin/bash
-# Codex-Vault wrapper — shows vault banner then launches Codex CLI
-# Usage: codex-vault-run [codex args...]
-
-SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
-PROJECT_DIR="$(pwd)"
-
-# Find session-start hook relative to project or plugin
-HOOK=""
-for candidate in \
-  "$PROJECT_DIR/plugin/hooks/codex/session-start.py" \
-  "$PROJECT_DIR/.codex-vault/hooks/codex/session-start.py" \
-  "$SCRIPT_DIR/../plugin/hooks/codex/session-start.py"; do
-  if [ -f "$candidate" ]; then
-    HOOK="$candidate"
-    break
-  fi
-done
-
-if [ -n "$HOOK" ]; then
-  SUMMARY=$(echo '{}' | python3 "$HOOK" 2>/dev/null \
-    | python3 -c "import sys,json; d=json.load(sys.stdin); print(d.get('systemMessage',''))" 2>/dev/null)
-  if [ -n "$SUMMARY" ]; then
-    echo "  $SUMMARY"
-  fi
-fi
-
-exec codex "$@"

package/plugin/VERSION

@@ -1 +0,0 @@
-0.6.0

package/vault/.claude/settings.json

@@ -1,39 +0,0 @@
-{
-  "hooks": {
-    "SessionStart": [
-      {
-        "matcher": "startup|resume|compact",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "python3 .codex-vault/hooks/claude/session-start.py",
-            "timeout": 30
-          }
-        ]
-      }
-    ],
-    "UserPromptSubmit": [
-      {
-        "hooks": [
-          {
-            "type": "command",
-            "command": "python3 .codex-vault/hooks/claude/classify-message.py",
-            "timeout": 15
-          }
-        ]
-      }
-    ],
-    "PostToolUse": [
-      {
-        "matcher": "Write|Edit",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "python3 .codex-vault/hooks/claude/validate-write.py",
-            "timeout": 15
-          }
-        ]
-      }
-    ]
-  }
-}

package/vault/.claude/skills/dump/SKILL.md

@@ -1,29 +0,0 @@
----
-name: dump
-description: "Freeform capture — dump anything (notes, ideas, decisions, links) and it gets classified and routed to the right vault location. Triggers: 'dump this', 'capture', 'save this thought', 'note this down', 'remember this', 'jot down'."
-license: MIT
-metadata:
-  author: sukbearai
-  version: "1.0.0"
-  homepage: "https://github.com/sukbearai/codex-vault"
----
-
-Process the following freeform dump. For each distinct piece of information:
-
-1. **Classify** it: decision, project update, win/achievement, or general work note.
-2. **Search first**: Check if a related note already exists. Prefer updating over creating.
-3. **Create or update** the appropriate note:
-   - Correct folder (work/active/, brain/, etc.)
-   - Full YAML frontmatter (date, description, tags)
-   - All relevant [[wikilinks]]
-4. **Update indexes**: `work/Index.md`, `brain/` notes as needed.
-5. **Cross-link**: Every new note links to at least one existing note.
-
-After processing, summarize:
-- What was captured and where
-- New notes created (with paths)
-- Existing notes updated
-- Anything unclear (ask the user)
-
-Content to process:
-$ARGUMENTS

package/vault/.claude/skills/ingest/SKILL.md

@@ -1,63 +0,0 @@
----
-name: ingest
-description: "Import external content (URLs, files, text) into the vault as structured source notes. Triggers: 'ingest', 'import this', 'save this article', 'add source', 'read and save'."
-license: MIT
-metadata:
-  author: sukbearai
-  version: "1.0.0"
-  homepage: "https://github.com/sukbearai/codex-vault"
----
-
-Ingest a source into the vault. Follow these steps:
-
-### 1. Locate the Source
-
-The user provides either:
-- A filename in `sources/` (e.g., `sources/karpathy-llm-wiki.md`)
-- A URL to fetch (use `defuddle parse <url> --md` or `curl` to save to `sources/` first)
-
-If a URL, save the raw content to `sources/` before proceeding — sources are the immutable record.
-
-### 2. Read the Source
-
-Read the full source document. Do not skim — ingestion depends on thorough reading.
-
-### 3. Discuss Key Takeaways
-
-Present the top 3-5 takeaways to the user. Ask:
-- Which points are most relevant to current work?
-- Any connections to existing vault notes?
-- Anything to skip or emphasize?
-
-Wait for user input before proceeding.
-
-### 4. Create a Source Summary
-
-Create a note in `work/active/` using the **Source Summary** template:
-- Fill in all YAML frontmatter (date, description, source, tags)
-- Write Key Takeaways, Summary, Connections (with [[wikilinks]]), Quotes/Data Points
-- The `source` field should reference the file in `sources/` or the original URL
-
-### 5. Update Indexes
-
-- Add the summary to `work/Index.md` under a "Sources" section (create the section if it doesn't exist)
-- Update relevant `brain/` notes if the source contains decisions (`Key Decisions.md`), patterns (`Patterns.md`), or context worth remembering (`Memories.md`)
-
-### 6. Cross-Link
-
-Check existing vault notes for connections:
-- Do any active projects relate to this source?
-- Does the source reinforce or challenge any existing decisions?
-- Add [[wikilinks]] in both directions where relevant
-
-### 7. Report
-
-Summarize what was done:
-- Source file location
-- Summary note created (path)
-- Indexes updated
-- Cross-links added
-- Brain notes updated (if any)
-
-Source to process:
-$ARGUMENTS

package/vault/.claude/skills/recall/SKILL.md

@@ -1,54 +0,0 @@
----
-name: recall
-description: "Search vault memory for a topic — finds relevant notes across brain, work, reference, and sources. Triggers: 'recall', 'what do I know about', 'search memory', 'find notes about', 'look up'."
-license: MIT
-metadata:
-  author: sukbearai
-  version: "1.0.0"
-  homepage: "https://github.com/sukbearai/codex-vault"
----
-
-Search the vault for information about the given topic.
-
-### 1. Parse the Query
-
-Extract the key topic or question from the user's input.
-
-### 2. Search the Vault
-
-Two-pass search — semantic first, keyword fallback:
-
-**Pass 1 — Frontmatter scan (semantic):**
-Read the first 5 lines (YAML frontmatter) of every `.md` file in the vault. Use the `description` and `tags` fields to judge relevance semantically — match by meaning, not just keywords. For example, a query about "caching" should match a note with description "Redis selection for session storage".
-
-Scan in priority order:
-1. `brain/` — persistent memory
-2. `work/active/` — current projects
-3. `reference/` — saved analyses
-4. `work/archive/` — completed work
-5. `sources/` — raw source documents
-
-**Pass 2 — Keyword grep (fallback):**
-If Pass 1 finds fewer than 2 relevant files, supplement with a keyword grep across file contents.
-
-### 3. Read Matches
-
-Read the top 3-5 relevant files in full. Prioritize files where the topic appears in:
-- The description or tags (strongest signal)
-- Headings
-- Multiple times in the body
-
-### 4. Synthesize
-
-Present what the vault knows about this topic:
-- **Found in**: list the files (as [[wikilinks]])
-- **Summary**: synthesize the relevant information across all matches
-- **Connections**: note any links between the matched notes
-- **Gaps**: flag if the vault has limited or no information on this topic
-
-### 5. Offer Writeback
-
-If the synthesis is substantial (combines 3+ sources), offer to save it as a reference note.
-
-Topic to recall:
-$ARGUMENTS

package/vault/.claude/skills/wrap-up/SKILL.md

@@ -1,35 +0,0 @@
----
-name: wrap-up
-description: "End-of-session wrap-up — commits changes, updates indexes, captures decisions made. Triggers: 'wrap up', 'end session', 'save progress', 'commit and close', 'done for today'."
-license: MIT
-metadata:
-  author: sukbearai
-  version: "1.0.0"
-  homepage: "https://github.com/sukbearai/codex-vault"
----
-
-Session wrap-up. Review what was done and leave the vault clean.
-
-### 1. Review
-Scan the conversation for notes created or modified. List them all.
-
-### 2. Verify Quality
-For each note: frontmatter complete? At least one [[wikilink]]? Correct folder?
-
-### 3. Check Indexes
-- `work/Index.md` — new notes linked? Completed projects moved?
-- `brain/Memories.md` — Recent Context updated?
-- `brain/Key Decisions.md` — new decisions captured?
-- `brain/Patterns.md` — new patterns observed?
-
-### 4. Check for Orphans
-Any new notes not linked from at least one other note?
-
-### 5. Archive Check
-Notes in `work/active/` that should move to `work/archive/`?
-
-### 6. Report
-- **Done**: what was captured
-- **Fixed**: issues resolved
-- **Flagged**: needs user input
-- **Suggested**: improvements for next time

package/vault/.codex/config.toml

@@ -1,2 +0,0 @@
-[features]
-codex_hooks = true

package/vault/.codex/hooks.json

@@ -1,28 +0,0 @@
-{
-  "hooks": {
-    "SessionStart": [
-      {
-        "matcher": "startup|resume",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "python3 .codex-vault/hooks/codex/session-start.py",
-            "timeout": 30,
-            "statusMessage": "\ud83d\udcda Codex-Vault loading..."
-          }
-        ]
-      }
-    ],
-    "UserPromptSubmit": [
-      {
-        "hooks": [
-          {
-            "type": "command",
-            "command": "python3 .codex-vault/hooks/codex/classify-message.py",
-            "timeout": 15
-          }
-        ]
-      }
-    ]
-  }
-}

package/vault/.codex/skills/dump/SKILL.md

@@ -1,29 +0,0 @@
----
-name: dump
-description: "Freeform capture — dump anything (notes, ideas, decisions, links) and it gets classified and routed to the right vault location. Triggers: 'dump this', 'capture', 'save this thought', 'note this down', 'remember this', 'jot down'."
-license: MIT
-metadata:
-  author: sukbearai
-  version: "1.0.0"
-  homepage: "https://github.com/sukbearai/codex-vault"
----
-
-Process the following freeform dump. For each distinct piece of information:
-
-1. **Classify** it: decision, project update, win/achievement, or general work note.
-2. **Search first**: Check if a related note already exists. Prefer updating over creating.
-3. **Create or update** the appropriate note:
-   - Correct folder (work/active/, brain/, etc.)
-   - Full YAML frontmatter (date, description, tags)
-   - All relevant [[wikilinks]]
-4. **Update indexes**: `work/Index.md`, `brain/` notes as needed.
-5. **Cross-link**: Every new note links to at least one existing note.
-
-After processing, summarize:
-- What was captured and where
-- New notes created (with paths)
-- Existing notes updated
-- Anything unclear (ask the user)
-
-Content to process:
-$ARGUMENTS

package/vault/.codex/skills/ingest/SKILL.md

@@ -1,63 +0,0 @@
----
-name: ingest
-description: "Import external content (URLs, files, text) into the vault as structured source notes. Triggers: 'ingest', 'import this', 'save this article', 'add source', 'read and save'."
-license: MIT
-metadata:
-  author: sukbearai
-  version: "1.0.0"
-  homepage: "https://github.com/sukbearai/codex-vault"
----
-
-Ingest a source into the vault. Follow these steps:
-
-### 1. Locate the Source
-
-The user provides either:
-- A filename in `sources/` (e.g., `sources/karpathy-llm-wiki.md`)
-- A URL to fetch (use `defuddle parse <url> --md` or `curl` to save to `sources/` first)
-
-If a URL, save the raw content to `sources/` before proceeding — sources are the immutable record.
-
-### 2. Read the Source
-
-Read the full source document. Do not skim — ingestion depends on thorough reading.
-
-### 3. Discuss Key Takeaways
-
-Present the top 3-5 takeaways to the user. Ask:
-- Which points are most relevant to current work?
-- Any connections to existing vault notes?
-- Anything to skip or emphasize?
-
-Wait for user input before proceeding.
-
-### 4. Create a Source Summary
-
-Create a note in `work/active/` using the **Source Summary** template:
-- Fill in all YAML frontmatter (date, description, source, tags)
-- Write Key Takeaways, Summary, Connections (with [[wikilinks]]), Quotes/Data Points
-- The `source` field should reference the file in `sources/` or the original URL
-
-### 5. Update Indexes
-
-- Add the summary to `work/Index.md` under a "Sources" section (create the section if it doesn't exist)
-- Update relevant `brain/` notes if the source contains decisions (`Key Decisions.md`), patterns (`Patterns.md`), or context worth remembering (`Memories.md`)
-
-### 6. Cross-Link
-
-Check existing vault notes for connections:
-- Do any active projects relate to this source?
-- Does the source reinforce or challenge any existing decisions?
-- Add [[wikilinks]] in both directions where relevant
-
-### 7. Report
-
-Summarize what was done:
-- Source file location
-- Summary note created (path)
-- Indexes updated
-- Cross-links added
-- Brain notes updated (if any)
-
-Source to process:
-$ARGUMENTS

package/vault/.codex/skills/recall/SKILL.md

@@ -1,54 +0,0 @@
----
-name: recall
-description: "Search vault memory for a topic — finds relevant notes across brain, work, reference, and sources. Triggers: 'recall', 'what do I know about', 'search memory', 'find notes about', 'look up'."
-license: MIT
-metadata:
-  author: sukbearai
-  version: "1.0.0"
-  homepage: "https://github.com/sukbearai/codex-vault"
----
-
-Search the vault for information about the given topic.
-
-### 1. Parse the Query
-
-Extract the key topic or question from the user's input.
-
-### 2. Search the Vault
-
-Two-pass search — semantic first, keyword fallback:
-
-**Pass 1 — Frontmatter scan (semantic):**
-Read the first 5 lines (YAML frontmatter) of every `.md` file in the vault. Use the `description` and `tags` fields to judge relevance semantically — match by meaning, not just keywords. For example, a query about "caching" should match a note with description "Redis selection for session storage".
-
-Scan in priority order:
-1. `brain/` — persistent memory
-2. `work/active/` — current projects
-3. `reference/` — saved analyses
-4. `work/archive/` — completed work
-5. `sources/` — raw source documents
-
-**Pass 2 — Keyword grep (fallback):**
-If Pass 1 finds fewer than 2 relevant files, supplement with a keyword grep across file contents.
-
-### 3. Read Matches
-
-Read the top 3-5 relevant files in full. Prioritize files where the topic appears in:
-- The description or tags (strongest signal)
-- Headings
-- Multiple times in the body
-
-### 4. Synthesize
-
-Present what the vault knows about this topic:
-- **Found in**: list the files (as [[wikilinks]])
-- **Summary**: synthesize the relevant information across all matches
-- **Connections**: note any links between the matched notes
-- **Gaps**: flag if the vault has limited or no information on this topic
-
-### 5. Offer Writeback
-
-If the synthesis is substantial (combines 3+ sources), offer to save it as a reference note.
-
-Topic to recall:
-$ARGUMENTS

package/vault/.codex/skills/wrap-up/SKILL.md

@@ -1,35 +0,0 @@
----
-name: wrap-up
-description: "End-of-session wrap-up — commits changes, updates indexes, captures decisions made. Triggers: 'wrap up', 'end session', 'save progress', 'commit and close', 'done for today'."
-license: MIT
-metadata:
-  author: sukbearai
-  version: "1.0.0"
-  homepage: "https://github.com/sukbearai/codex-vault"
----
-
-Session wrap-up. Review what was done and leave the vault clean.
-
-### 1. Review
-Scan the conversation for notes created or modified. List them all.
-
-### 2. Verify Quality
-For each note: frontmatter complete? At least one [[wikilink]]? Correct folder?
-
-### 3. Check Indexes
-- `work/Index.md` — new notes linked? Completed projects moved?
-- `brain/Memories.md` — Recent Context updated?
-- `brain/Key Decisions.md` — new decisions captured?
-- `brain/Patterns.md` — new patterns observed?
-
-### 4. Check for Orphans
-Any new notes not linked from at least one other note?
-
-### 5. Archive Check
-Notes in `work/active/` that should move to `work/archive/`?
-
-### 6. Report
-- **Done**: what was captured
-- **Fixed**: issues resolved
-- **Flagged**: needs user input
-- **Suggested**: improvements for next time