auditor-lambda 0.3.4 → 0.3.5

package/docs/session-config.md

@@ -59,7 +59,9 @@ Current implementation note:
 
 - `claude-code`, `opencode`, `subprocess-template`, and `vscode-task` are backend compatibility bridges
 - they are not the intended default owner of semantic review when the active conversation agent can handle the work directly
-- to activate one of those bridges for semantic review, re-run the wrapper with an explicit `--provider <name>` flag
+- to activate one of those bridges for semantic review, either set `provider`
+  in this file intentionally or re-run the wrapper with an explicit
+  `--provider <name>` flag
 
 ### `timeout_ms`
 
@@ -141,11 +143,17 @@ This remains the safest fallback default while the semantic-review workflow is b
 Fields:
 
 - `command`: optional override for the Claude Code executable
-- `extra_args`: optional extra arguments appended before the built-in permission-skipping flag
+- `extra_args`: optional extra arguments for Claude Code
+- `dangerously_skip_permissions`: optional trusted-automation opt-in. When
+  `true`, the bridge appends `--dangerously-skip-permissions`. Leave this
+  unset for the safer default.
 
 Current implementation support only.
 
-Use this only when you intentionally want the backend fallback CLI to bridge review into an external Claude Code process, together with `audit-code --provider claude-code`.
+Use this only when you intentionally want the backend fallback CLI to bridge
+review into an external Claude Code process, either by setting
+`provider: "claude-code"` in this file or by running
+`audit-code --provider claude-code`.
 
 ### `opencode`
 

package/docs/supervisor.md

@@ -63,9 +63,11 @@ audit-code --provider subprocess-template
 audit-code --provider vscode-task
 ```
 
-Those `--provider` invocations are the explicit bridge handoff point.
-Without an explicit `--provider` flag, the backend stops at the semantic-review
-boundary and exposes scoped task artifacts for the slash-command orchestrator.
+Those `--provider` invocations are an explicit bridge handoff point.
+Without an explicit `--provider` flag or a non-local provider in
+`.audit-artifacts/session-config.json`, the backend stops at the
+semantic-review boundary and exposes scoped task artifacts for the
+slash-command orchestrator.
 
 ## Auto resolution rule
 

package/docs/workflow-refactor-brief.md

@@ -15,7 +15,8 @@ The implemented design is a compatibility-preserving packet layer:
 - group related task records into worker-facing review packets
 - make each worker read a coherent file set once and review multiple lenses in
   one pass
-- write one validated result file per underlying task
+- submit packet results through the backend so only assigned result files are
+  written
 
 ## Current Product Model
 
@@ -42,9 +43,11 @@ The refactor now includes:
 - packet-first pending-task ordering for provider-assisted batches
 - tiny homogeneous test-file batching before dispatch
 - graph-edge expansion from import, call, and reference edges
-- packet prompts that assign multiple task outputs to one worker
+- packet prompts that assign multiple task results to one worker
+- backend-owned packet submission that validates before writing result files
+- isolated large-file packet mode with mechanical anchors for targeted review
 - validation and merge checks for missing, duplicate, unknown, malformed, or
-  out-of-scope task results
+  out-of-scope task results, including swapped result files
 - compact `prepare-dispatch` and `merge-and-ingest` JSON envelopes
 - terse worker completion convention:
   `valid: <packet_id>, findings=<n>`
@@ -75,7 +78,10 @@ Packet mode adds or updates these artifacts:
 - `review_packets.json`
 - `audit_plan_metrics.json`
 - `<artifacts_dir>/runs/<run_id>/dispatch-plan.json`
+- `<artifacts_dir>/runs/<run_id>/dispatch-result-map.json`
 - `<artifacts_dir>/runs/<run_id>/task-results/*.prompt.md`
+- `<artifacts_dir>/runs/<run_id>/task-results/*.anchors.json`, only for
+  isolated large-file packets
 - `<artifacts_dir>/runs/<run_id>/task-results/*.json`
 - `<artifacts_dir>/runs/<run_id>/dispatch-warnings.json`, only when needed
 
@@ -86,7 +92,7 @@ remain backend-owned.
 
 Current in-repo verification:
 
-- `npm test` passes with 143 tests.
+- `npm test` passes with 148 tests.
 
 Relevant test coverage:
 
@@ -95,8 +101,11 @@ Relevant test coverage:
 - graph-connected packet merging
 - tiny test-file batching
 - packet prompt generation
-- packet merge compatibility with the legacy result array
+- packet submission and merge compatibility with the legacy result array
 - missing-result blocking
+- swapped-result blocking
+- collision-proof assigned result paths
+- isolated large-file anchor generation
 - path-heuristic regressions
 - graph extraction from source contents
 - selective deepening triggers and packet refresh

package/package.json

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

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

@@ -1,7 +1,7 @@
 ---
 description: Autonomous local loop code auditing - advances deterministic audit state, delegates bounded review tasks, and ingests validated results
 argument-hint: [target-dir]
-allowed-tools: [Read, Write, Bash, Glob, Grep, Agent]
+allowed-tools: [Read, Bash, Glob, Grep, Agent]
 ---
 
 # `/audit-code` Execution Directive
@@ -81,14 +81,19 @@ In a single message, launch one Agent/subagent call per dispatch-plan entry:
 Agent({ description: entry.description, prompt: "Read and follow the audit instructions in: " + entry.prompt_path })
 ```
 
+If the host supports per-subagent tool restrictions, give review subagents no
+Write tool and allow shell access only for the `audit-code submit-packet`
+command printed in their prompt.
+
 All subagent calls should be launched together. Wait for them to finish.
 
 Subagents own bounded semantic review. They must read only their prompt and
-assigned files, write exactly the requested audit result JSON to `output_path`,
-run the validation command in their prompt, retry up to 3 times if validation
-fails, and stop. They must not edit source files, remediate findings, create
-extra task results, run unrelated audits, or write the worker `result.json`
-control envelope.
+assigned files, produce the requested `AuditResult[]`, pipe it to the
+`submit-packet` command in their prompt, retry up to 3 times if submission
+fails, and stop. The backend command validates and writes the packet-owned
+result artifacts. They must not use direct file writes, edit source files,
+remediate findings, create extra task results, run unrelated audits, or write
+the worker `result.json` control envelope.
 
 Then run: