@wei840222/qmd 2026.9.6 → 2026.9.25

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wei840222/qmd",
-  "version": "2026.9.6",
+  "version": "2026.9.25",
   "packageManager": "pnpm@11.15.1",
   "description": "Query Markup Documents - On-device hybrid search for markdown files with BM25, vector search, and LLM reranking",
   "type": "module",
@@ -65,7 +65,7 @@
   },
   "dependencies": {
     "@modelcontextprotocol/server": "2.0.0",
-    "@node-rs/jieba": "2.0.2",
+    "@node-rs/jieba": "2.0.3",
     "fast-glob": "3.3.3",
     "node-llama-cpp": "3.20.0",
     "picomatch": "4.0.5",

package/scripts/sync-zh-dict.mjs

@@ -77,7 +77,10 @@ async function downloadPinnedSource(source, label) {
 
 async function updateRemotePin(source, label) {
   const response = await fetch(apiUrl(source), {
-    headers: { Accept: "application/vnd.github+json" },
+    headers: {
+      Accept: "application/vnd.github+json",
+      "User-Agent": "qmd-dict-sync",
+    },
     redirect: "error",
   });
   if (!response.ok) throw new Error(`${label} commit lookup failed with HTTP ${response.status}.`);

package/skills/qmd/SKILL.md

@@ -201,6 +201,17 @@ qmd query "merchant support product reality" -c concepts -c sources -n 10
 
 > **Performance Tip for Agents:** Collection filters (`-c`) are natively indexed in both lexical and vector virtual tables. Scoping by collection guarantees millisecond search latency and avoids ranking dilution from unrelated collections. Omit `-c` only when searching across the entire workspace.
 
+## Filter by metadata
+
+Documents can carry typed metadata in a `qmd.metadata` frontmatter block (strings, numbers, booleans, or flat arrays). `search`, `vsearch`, and `query` accept `--filter` with a recursive JSON AST; every returned result satisfies it:
+
+```bash
+qmd search "authentication" --filter '{"key":"status","operator":"eq","value":"published"}'
+qmd query "dependency injection" --filter '{"operator":"and","operands":[{"key":"topics","operator":"all","value":["typescript"]},{"key":"status","operator":"nin","value":["draft","archived"]}]}'
+```
+
+Nodes are discriminated by `operator`: groups `and`/`or` take `operands`, `not` takes one `operand`, and conditions take `key` + `value` with operators `eq`/`ne`/`gt`/`gte`/`lt`/`lte` (comparison), `in`/`nin`/`all` (membership), or `exists` (presence). Matching is typed and exact; missing keys do not match `ne`/`nin` (add an `exists: false` branch in an `or` group to include them). The MCP `query` tool accepts the same AST as a `filter` object. JSON output includes each result's `metadata`.
+
 ## MCP Tool: `query`
 
 When using the MCP server, prefer structured searches:

package/skills/release/SKILL.md

@@ -1,141 +0,0 @@
----
-name: release
-description: Manage releases for this project. Validates changelog, installs git hooks, and cuts releases. Use when user says "/release", "release 1.0.5", "cut a release", or asks about the release process. NOT auto-invoked by the model.
-disable-model-invocation: true
----
-
-# Release
-
-Cut a release, validate the changelog, and ensure git hooks are installed.
-
-## Usage
-
-`/release 1.0.5` or `/release patch` (bumps patch from current version).
-
-## Process
-
-When the user triggers `/release <version>`:
-
-1. **Gather context** — run `skills/release/scripts/release-context.sh <version>`.
-   This silently installs git hooks and prints everything needed: version info,
-   working directory status, commits since last release, files changed, current
-   `[Unreleased]` content, and the previous release entry for style reference.
-
-2. **Commit outstanding work** — if the context shows staged, modified, or
-   untracked files that belong in this release, commit them first. Use the
-   /commit skill or make well-formed commits directly.
-
-3. **Write the changelog** — if `[Unreleased]` is empty, write it now using
-   the commits and file changes from the context output. Follow the changelog
-   standard below. Re-run the context script after committing if needed.
-
-4. **Check dependency updates** — before cutting the release, check for
-   updates to `sqlite-vec` (and platform packages), `node-llama-cpp`,
-   and `better-sqlite3`. Run `pnpm outdated` and report any available
-   updates for these packages. If updates exist, bump them (pinned, no
-   `^` ranges) and re-run tests before proceeding.
-
-5. **Cut the release** — run `scripts/release.sh <version>`. This renames
-   `[Unreleased]` → `[X.Y.Z] - date`, inserts a fresh `[Unreleased]`,
-   bumps `package.json` and the plugin version in
-   `.claude-plugin/marketplace.json` (so installed plugins see the update),
-   commits, and tags.
-
-6. **Show the final changelog** — print the full `[Unreleased]` +
-   minor series rollup via `scripts/extract-changelog.sh <version>`.
-   Ask the user to confirm before pushing.
-
-7. **Push** — after explicit confirmation, run `git push origin main --tags`.
-
-8. **Watch CI** — after the push, start a background dispatch to watch the
-   publish workflow. Use `interactive_shell` in dispatch mode with:
-   ```
-   gh run watch $(gh run list --workflow=publish.yml --limit=1 --json databaseId --jq '.[0].databaseId') --exit-status
-   ```
-   The agent will be notified when CI completes and should report the result.
-
-If any step fails, stop and explain. Never force-push or skip validation.
-
-## Dependency Policy
-
-All dependencies must be pinned to exact versions (no `^` or `~` ranges).
-The lockfile ensures reproducible installs. When adding or updating any
-dependency, always use the exact version string (e.g. `"3.18.1"` not
-`"^3.18.1"`).
-
-## Changelog Standard
-
-The changelog lives in `CHANGELOG.md` and follows [Keep a Changelog](https://keepachangelog.com/) conventions.
-
-### Heading format
-
-- `## [Unreleased]` — accumulates entries between releases
-- `## [X.Y.Z] - YYYY-MM-DD` — released versions
-
-### Structure of a release entry
-
-Each version entry has two parts:
-
-**1. Highlights (optional, 1-4 sentences of prose)**
-
-Immediately after the version heading, before any `###` section. The elevator
-pitch — what would you tell someone in 30 seconds? Only for significant
-releases; skip for small patches.
-
-```markdown
-## [1.1.0] - 2026-03-01
-
-QMD now runs on both Node.js and Bun, with up to 2.7x faster reranking
-through parallel contexts. GPU auto-detection replaces the unreliable
-`gpu: "auto"` with explicit CUDA/Metal/Vulkan probing.
-```
-
-**2. Detailed changelog (`### Changes` and `### Fixes`)**
-
-```markdown
-### Changes
-
-- Runtime: support Node.js (>=22) alongside Bun. The `qmd` wrapper
-  auto-detects a suitable install via PATH. #149 (thanks @igrigorik)
-- Performance: parallel embedding & reranking — up to 2.7x faster on
-  multi-core machines.
-
-### Fixes
-
-- Prevent VRAM waste from duplicate context creation during concurrent
-  `embedBatch` calls. #152 (thanks @jkrems)
-```
-
-### Writing guidelines
-
-- **Explain the why, not just the what.** The changelog is for users.
-- **Include numbers.** "2.7x faster", "17x less memory".
-- **Group by theme, not by file.** "Performance" not "Changes to llm.ts".
-- **Don't list every commit.** Aggregate related changes.
-- **Credit contributors:** end bullets with `#NNN (thanks @username)` for
-  external PRs. No need to credit the repo owner.
-
-### What not to include
-
-- Internal refactors with no user-visible effect
-- Dependency bumps (unless fixing a user-facing bug)
-- CI/tooling changes (unless affecting the release artifact)
-- Test additions (unless validating a fix worth mentioning)
-
-## GitHub Release Notes
-
-Each GitHub release includes the full changelog for the **minor series** back
-to x.x.0. The `scripts/extract-changelog.sh` script handles this, and the
-publish workflow (`publish.yml`) calls it to populate the GitHub release.
-
-## Git Hooks
-
-The pre-push hook (`scripts/pre-push`) blocks `v*` tag pushes unless:
-
-1. `package.json` version matches the tag
-2. `CHANGELOG.md` has a `## [X.Y.Z] - date` entry for the version
-3. CI passed on GitHub (warns in non-interactive shells, blocks in terminals)
-
-Hooks are installed silently by the context script. They can also be installed
-manually via `skills/release/scripts/install-hooks.sh` or automatically via
-`bun install` (prepare script).

package/skills/release/scripts/install-hooks.sh

@@ -1,38 +0,0 @@
-#!/usr/bin/env bash
-set -euo pipefail
-
-# Install git hooks for release validation.
-# Idempotent — safe to run multiple times.
-
-REPO_ROOT=$(git rev-parse --show-toplevel 2>/dev/null)
-if [[ -z "$REPO_ROOT" ]]; then
-  echo "Error: not in a git repository" >&2
-  exit 1
-fi
-
-HOOKS_DIR="$REPO_ROOT/.git/hooks"
-SOURCE="$REPO_ROOT/scripts/pre-push"
-
-if [[ ! -f "$SOURCE" ]]; then
-  echo "Error: scripts/pre-push not found at $SOURCE" >&2
-  exit 1
-fi
-
-# Install pre-push hook
-if [[ -L "$HOOKS_DIR/pre-push" ]] && [[ "$(readlink "$HOOKS_DIR/pre-push")" == "$SOURCE" ]]; then
-  echo "pre-push hook: already installed (symlink)"
-elif [[ -f "$HOOKS_DIR/pre-push" ]]; then
-  # Existing hook that isn't our symlink — back it up
-  BACKUP="$HOOKS_DIR/pre-push.backup.$(date +%s)"
-  echo "pre-push hook: backing up existing hook to $(basename "$BACKUP")"
-  mv "$HOOKS_DIR/pre-push" "$BACKUP"
-  ln -sf "$SOURCE" "$HOOKS_DIR/pre-push"
-  echo "pre-push hook: installed (symlink → scripts/pre-push)"
-else
-  ln -sf "$SOURCE" "$HOOKS_DIR/pre-push"
-  echo "pre-push hook: installed (symlink → scripts/pre-push)"
-fi
-
-# Ensure the source is executable
-chmod +x "$SOURCE"
-echo "Done."

package/skills/release/scripts/release-context.sh

@@ -1,129 +0,0 @@
-#!/usr/bin/env bash
-set -euo pipefail
-
-# Gather release context for the /release skill (skills/release/SKILL.md step 1).
-# Silently installs git hooks, then prints version info, working-tree status,
-# commits and files since the last release tag, the current [Unreleased]
-# changelog block, and the previous release entry for style reference.
-#
-# Usage: skills/release/scripts/release-context.sh [patch|minor|major|<version>]
-
-VERSION_ARG="${1:?Usage: release-context.sh [patch|minor|major|<version>]}"
-
-SCRIPT_DIR=$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)
-
-REPO_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || true)
-if [[ -z "$REPO_ROOT" ]]; then
-  echo "Error: not in a git repository" >&2
-  exit 1
-fi
-cd "$REPO_ROOT"
-
-# Hooks are installed silently — the skill documents this as the auto-install path.
-if [[ -x "$SCRIPT_DIR/install-hooks.sh" ]]; then
-  "$SCRIPT_DIR/install-hooks.sh" >/dev/null
-fi
-
-bump_version() {
-  local current="$1" type="$2"
-  IFS='.' read -r major minor patch <<< "$current"
-  case "$type" in
-    major) echo "$((major + 1)).0.0" ;;
-    minor) echo "$major.$((minor + 1)).0" ;;
-    patch) echo "$major.$minor.$((patch + 1))" ;;
-    *)     echo "$type" ;;
-  esac
-}
-
-if [[ ! -f package.json ]]; then
-  echo "Error: package.json not found in $REPO_ROOT" >&2
-  exit 1
-fi
-
-CURRENT=$(jq -r .version package.json)
-NEXT=$(bump_version "$CURRENT" "$VERSION_ARG")
-BRANCH=$(git branch --show-current)
-LAST_TAG=$(git describe --tags --abbrev=0 2>/dev/null || true)
-
-echo "=== Version ==="
-echo "Current:   $CURRENT"
-echo "Requested: $VERSION_ARG"
-echo "Next:      $NEXT"
-echo "Branch:    ${BRANCH:-"(detached)"}"
-if [[ -n "$LAST_TAG" ]]; then
-  echo "Last tag:  $LAST_TAG"
-else
-  echo "Last tag:  (none)"
-fi
-echo
-
-echo "=== Working tree ==="
-STATUS=$(git status --short)
-if [[ -z "$STATUS" ]]; then
-  echo "(clean)"
-else
-  printf '%s\n' "$STATUS"
-fi
-echo
-
-echo "=== Commits since last release ==="
-if [[ -n "$LAST_TAG" ]]; then
-  COMMITS=$(git log --oneline "${LAST_TAG}..HEAD")
-  if [[ -z "$COMMITS" ]]; then
-    echo "(none since $LAST_TAG)"
-  else
-    printf '%s\n' "$COMMITS"
-  fi
-else
-  echo "(no tags)"
-  git log --oneline
-fi
-echo
-
-echo "=== Files changed since last release ==="
-if [[ -n "$LAST_TAG" ]]; then
-  FILES=$(git diff --name-only "${LAST_TAG}..HEAD")
-  if [[ -z "$FILES" ]]; then
-    echo "(none since $LAST_TAG)"
-  else
-    printf '%s\n' "$FILES"
-  fi
-else
-  echo "(no tags)"
-fi
-echo
-
-echo "=== CHANGELOG [Unreleased] ==="
-if [[ -f CHANGELOG.md ]]; then
-  UNRELEASED=$(awk '
-    /^## \[Unreleased\]/ { p=1; next }
-    /^## \[/ { if (p) exit }
-    p { print }
-  ' CHANGELOG.md)
-  TRIMMED=$(printf '%s' "$UNRELEASED" | sed '/^[[:space:]]*$/d')
-  if [[ -z "$TRIMMED" ]]; then
-    echo "(empty)"
-  else
-    printf '%s\n' "$UNRELEASED"
-  fi
-else
-  echo "(CHANGELOG.md not found)"
-fi
-echo
-
-echo "=== Previous release entry ==="
-if [[ -f CHANGELOG.md ]]; then
-  PREVIOUS=$(awk '
-    /^## \[Unreleased\]/ { next }
-    /^## \[/ { if (p) exit; p=1 }
-    p { print }
-  ' CHANGELOG.md)
-  TRIMMED=$(printf '%s' "$PREVIOUS" | sed '/^[[:space:]]*$/d')
-  if [[ -z "$TRIMMED" ]]; then
-    echo "(none)"
-  else
-    printf '%s\n' "$PREVIOUS"
-  fi
-else
-  echo "(CHANGELOG.md not found)"
-fi