auditor-lambda 0.6.5 → 0.6.6

package/audit-code-wrapper-lib.mjs

@@ -2781,9 +2781,14 @@ async function runDistCommandInline(commandName, argv) {
   await mkdir(artifactsDir, { recursive: true });
   await ensureBuilt();
 
-  const distUrl = new URL(`file:///${distEntry.replace(/\\/g, '/')}`);
+  // Import the module that exports runCli (dist/cli.js). dist/index.js has no
+  // exports — it is the bare entrypoint that runs `runCli(process.argv)` as an
+  // import side effect — so importing it here both fails to provide runCli and
+  // double-starts the command from this process's argv.
+  const distCliEntry = join(repoRoot, 'dist', 'cli.js');
+  const distUrl = new URL(`file:///${distCliEntry.replace(/\\/g, '/')}`);
   const cli = await import(distUrl.href);
-  await cli.runCli([process.execPath, distEntry, commandName, ...commandArgs]);
+  await cli.runCli([process.execPath, distCliEntry, commandName, ...commandArgs]);
 }
 
 export async function runAuditCodeWrapper({

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "auditor-lambda",
-  "version": "0.6.5",
+  "version": "0.6.6",
   "private": false,
   "description": "Portable hybrid code-auditing framework for arbitrary repositories.",
   "type": "module",

package/skills/audit-code/SKILL.md

@@ -83,10 +83,12 @@ audit-code
 
 from the target repository root.
 
-When developing inside the `auditor-lambda` repository itself, prefer:
+When developing `auditor-lambda` itself, prefer the local wrapper at
+`packages/audit-code/audit-code.mjs` (there is no `audit-code.mjs` at the
+monorepo root):
 
 ```bash
-node audit-code.mjs
+node packages/audit-code/audit-code.mjs   # from the monorepo root
 ```
 
 That keeps the run pinned to the local wrapper and local `dist/` output instead

package/skills/audit-code/audit-code.prompt.md

@@ -17,10 +17,12 @@ First, make sure the repository has current local audit assets:
 audit-code ensure --quiet
 ```
 
-Inside the `auditor-lambda` repository itself, use:
+When developing `auditor-lambda` itself, the entrypoint lives at
+`packages/audit-code/audit-code.mjs` (there is no `audit-code.mjs` at the
+monorepo root). From the monorepo root use:
 
 ```bash
-node audit-code.mjs ensure --quiet
+node packages/audit-code/audit-code.mjs ensure --quiet
 ```
 
 Then ask the backend for exactly one next step:
@@ -29,10 +31,10 @@ Then ask the backend for exactly one next step:
 audit-code next-step
 ```
 
-Inside the `auditor-lambda` repository itself, use:
+When developing `auditor-lambda` itself, from the monorepo root use:
 
 ```bash
-node audit-code.mjs next-step
+node packages/audit-code/audit-code.mjs next-step
 ```
 
 Read the returned JSON only far enough to find `prompt_path`, then read and