Przeglądaj źródła

fix(qmd): restore shebang line to dist/cli/qmd.js (i-gfv5zq2z)

My prior commit 99bd369 used raw tsc directly instead of the canonical
"build" script, which strips the shebang prepend step from the pipeline.
The script schedule was: tsc compile then prepend "#!/usr/bin/env node"
to dist/cli/qmd.js then chmod +x.

Without the shebang, every qmd CLI invocation gets parsed by bash
(syntax error on first ES-module import line) — breaking embed,
vsearch, query, mcp commands fleet-wide.

Working tree had the shebang restored (sibling/verifier ran the build);
this commit just lands that one-line fix.

Closes i-gfv5zq2z (filed about TRACE-DEBUG in dist/llm.js — that content
was already absent from HEAD at file time; the real issue turned out to
be this shebang regression, caught only because of dist/cli/qmd.js drift
surfacing during follow-up review).

Lesson: when editing src/*.ts in vendor/qmd, ALWAYS use the canonical
build script not raw tsc — per /srv/vendor/qmd/CLAUDE.md "Dist/ commit
hygiene" section (landed via i-9l2ueyyz).

Generated with [Claude Code](https://claude.ai/code)
via [Oivo](https://oivo.com)

Co-Authored-By: Claude <noreply@anthropic.com>
Session-Id: 4c692810
root 3 tygodni temu
rodzic
commit
818c209d88
1 zmienionych plików z 1 dodań i 0 usunięć
  1. 1 0
      dist/cli/qmd.js

+ 1 - 0
dist/cli/qmd.js

@@ -1,3 +1,4 @@
+#!/usr/bin/env node
 import { openDatabase } from "../db.js";
 import fastGlob from "fast-glob";
 import { execSync, spawn as nodeSpawn } from "child_process";