auditor-lambda 0.2.6 → 0.2.9

package/README.md

@@ -11,6 +11,7 @@ Normal product usage should:
 - use the active conversation model by default
 - use project files and attached repository context by default
 - avoid manual paths, provider flags, and model-selection arguments
+- keep semantic review with the active conversation agent by default
 - advance the audit automatically until it completes or no further automatic progress is possible
 
 ## Conversation Setup
@@ -29,10 +30,17 @@ audit-code install
 
 That bootstraps repo-local `/audit-code` surfaces for the hosts we can automate today, including:
 
-- VS Code / GitHub Copilot prompt files
-- OpenCode custom commands
-- Claude Code custom slash commands
-- compatibility instruction files such as `AGENTS.md` and `CLAUDE.md`
+- Codex skill bundle, `AGENTS.md` guidance, and MCP setup notes
+- Claude Desktop local MCP bundle artifacts and project template guidance
+- OpenCode command, skill, and `opencode.json` surfaces
+- VS Code prompt, custom agent, Copilot instructions, and `.vscode/mcp.json`
+- Antigravity planning-mode guidance plus the shared repo-local MCP launcher
+
+After bootstrap, you can smoke-test the generated host assets and launcher from the repository root:
+
+```bash
+audit-code verify-install
+```
 
 After that, open a supported conversation surface in the repository and invoke `/audit-code`.
 
@@ -42,7 +50,7 @@ If a host still needs manual prompt import after bootstrap, open:
 .audit-code/install/GETTING-STARTED.md
 ```
 
-That repo-local guide now includes dedicated quick-start sections for VS Code, OpenCode, Claude Code, Claude Desktop, and Antigravity, plus the installed canonical prompt asset path for manual-import hosts.
+That repo-local guide now includes dedicated quick-start sections for Codex, Claude Desktop, OpenCode, VS Code, and Antigravity, plus the installed canonical prompt asset path for prompt-import fallback flows.
 
 For narrower compatibility, `audit-code install-host --host copilot` still exists.
 
@@ -79,6 +87,7 @@ This wrapper:
 - auto-builds `dist/` if it is missing
 - advances fresh worker sessions automatically until the audit completes or the remaining work requires imported results or an interactive provider
 - continues through provider-assisted audit review automatically when `.audit-artifacts/session-config.json` selects an interactive provider bridge
+- keeps those provider bridges as fallback compatibility modes rather than the primary product path
 - emits `contract_version: "audit-code/v1alpha1"`
 - refreshes `.audit-artifacts/operator-handoff.json` and `.audit-artifacts/operator-handoff.md` with suggested evidence-import paths and continuation hints
 
@@ -114,6 +123,12 @@ For task-to-coverage inspection without reverse-engineering multiple artifacts:
 audit-code explain-task <task_id>
 ```
 
+For a local stdio MCP server entrypoint:
+
+```bash
+audit-code mcp
+```
+
 The backend wrapper response schema is `schemas/audit-code-v1alpha1.schema.json`.
 
 ## Backend Provider Modes
@@ -147,6 +162,7 @@ Optional backend config:
 - use `audit-code` from the repository root only when you need the repo-local backend fallback
 - use omitted provider or `local-subprocess` for the safest deterministic fallback behavior
 - use `provider: "auto"` only when you want best-effort routing across installed backends
+- treat explicit provider bridges as compatibility fallback, not as the intended owner of semantic review
 
 ## Implementation Next Steps
 
@@ -156,8 +172,9 @@ The next implementation work is tracked in:
 
 The short version is:
 
-- reduce prompt-import friction in the conversation setup flow
-- make the conversation route feel more native in the first target hosts
+- realign review dispatch around the conversation-owned, non-overlapping lens-block workflow
+- prove the generated Codex, Claude Desktop, OpenCode, VS Code, and Antigravity guidance in real host flows
+- tighten the repo-local MCP-first bootstrap where host smoke tests expose friction
 - polish provider-assisted continuation and failure guidance
 - finish publish and release hardening for packaged installs
 
@@ -168,9 +185,14 @@ npm install
 npm run verify:release
 ```
 
+For GitHub Actions publication and npm Trusted Publishing setup, see `docs/releasing.md`.
+
 ## Key Docs
 
 - `docs/product-direction.md`
+- `docs/workflow-refactor-brief.md`
+- `docs/remediation-baseline.md`
+- `docs/releasing.md`
 - `docs/production-readiness.md`
 - `docs/production-launch-bar.md`
 - `docs/next-steps.md`