Clarify and harden the A.I.G scanner integration

[Patrick-Erichsen]

Context

ClawScan currently exposes an aig scanner adapter for Tencent AI-Infra-Guard. The adapter is useful, but it is not equivalent to the command-backed scanners in the runtime image.

A.I.G is a service-backed scanner: ClawScan talks to a running A.I.G API via AIG_BASE_URL rather than invoking a local CLI. Upstream A.I.G is distributed as a Docker/API service stack, not a simple binary we can reasonably bake into clawscan-runtime.

Current shortcomings

• clawscan --scanner aig does not work out of the box on a clean install.
• clawscan-runtime does not include or start A.I.G.
• Benchmark CI does not start an A.I.G sidecar/service when --scanner aig is requested.
• The adapter is covered by fixture-backed tests, but we do not have a live smoke test against a real A.I.G service.
• clawscan install aig can only give setup guidance; it cannot install a local scanner binary like it can for command-backed scanners.
• Docs/help need to make the service-backed requirement unmistakable.
• The upstream service defaults to local/no-auth style deployment, so docs should keep warning users not to expose it publicly.
• Env/sandbox behavior needs to be explicit: AIG_BASE_URL, model config env vars, and API keys need to be passed into ClawScan/scanner execution without recording secret values.

Desired outcome

Make the aig scanner honest and reliable as a service-backed integration:

• Keep aig out of default built-in profiles unless a service is explicitly configured.
• Document the minimum local setup for running A.I.G alongside ClawScan.
• Add a CI/service-container or compose recipe for scanner runs that include aig.
• Add a live smoke path that can be run manually or in CI when A.I.G is available.
• Ensure clawscan scanners aig and clawscan install aig clearly say a running A.I.G service is required.
• Confirm failure mode is clear when AIG_BASE_URL is unreachable.

Non-goals

• Do not bake the full A.I.G service stack into clawscan-runtime unless we later decide to make the runtime image an orchestrator.
• Do not expose an unauthenticated A.I.G service publicly.
• Do not store or print A.I.G API/model secret values in artifacts.

[clawsweeper]

Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve. Reviewed July 18, 2026, 10:38 PM ET / July 19, 2026, 02:38 UTC.

Summary
Keep open for explicit maintainer confirmation: the merged local-CLI migration appears to supersede the service-backed A.I.G design, but this collaborator-authored security-sensitive item must not be auto-closed.

Reproducibility: no. high-confidence current-main reproduction was established. The reported failure mode targets the retired service-backed adapter model, while the supplied merged-PR context describes a replacement local CLI integration.

Ways to help us reproduce this

• Add a screenshot or short recording showing the behavior.
• Include the exact command, prompt, or workflow that triggered it.
• Add expected vs actual behavior.

Next step
A maintainer must confirm that the merged local-CLI architecture intentionally closes the original service-backed request before this collaborator-authored item can be resolved.

Maintainer decision needed

• Question: Does the merged local aig-skill-scan migration intentionally replace the service-backed A.I.G workflow requested here, including its setup and safety expectations?
• Rationale: The merged work changes the integration model rather than implementing the original sidecar/service plan verbatim, and collaborator-authored items require explicit maintainer judgment before closure.
• Likely owner: Patrick-Erichsen — They authored both this report and the merged A.I.G integration migration that supplies the clearest intent signal.
• Options:
  • Accept the local CLI replacement (recommended): Confirm that the local scanner model supersedes the former service-backed design and close this issue as implemented.
  • Retain a narrow service requirement: Keep this issue open only for a specifically identified service-backed capability that the local CLI migration does not provide.

Review details

Best possible solution:

Confirm that the local aig-skill-scan integration is the intended permanent A.I.G model; if so, close this issue as implemented, otherwise record the one remaining current-main gap as a narrower follow-up.

Do we have a high-confidence way to reproduce the issue?

No high-confidence current-main reproduction was established. The reported failure mode targets the retired service-backed adapter model, while the supplied merged-PR context describes a replacement local CLI integration.

Is this the best way to solve the issue?

Unclear. Replacing the API service integration with a sandboxed local CLI appears to be a maintainable solution, but a maintainer must confirm it intentionally resolves the original service-backed requirements.

AGENTS.md: found and applied where relevant.

Remaining risk / open question:

• Closing now would treat the local-CLI migration as fully satisfying a collaborator-authored request without an explicit maintainer confirmation that no service-backed operational requirement remains.

Codex review notes: model internal, reasoning high; reviewed against a37f49f1b09f.

Label changes

Label changes:

• add issue-rating: 🦪 silver shellfish: Current issue advisory state selects this label.
• add clawsweeper:needs-maintainer-review: Current issue advisory state selects this label.
• remove issue-rating: 🦞 diamond lobster: Current issue advisory state no longer selects this label.
• remove clawsweeper:source-repro: Current issue advisory state no longer selects this label.
• remove clawsweeper:needs-security-review: Current issue advisory state no longer selects this label.

Label justifications:

• P2: The remaining question is a bounded scanner-integration and operational-safety decision rather than an active emergency.
• impact:security: The report concerns scanner execution boundaries, service exposure, and secret-safe environment handling.

Evidence reviewed

What I checked:

• Merged replacement direction: The referenced merged pull request feat: use local aig skill scanner #12 replaced the legacy API-backed A.I.G adapter with Tencent's local aig-skill-scan CLI and states that it updated installer metadata, sandbox wiring, benchmark handling, docs, help, and tests.
• Unmerged partial predecessor: The related documentation-focused pull request Clarify AIG service-backed scanner setup #8 was closed unmerged and described only the former service-backed setup, so it is not a viable remaining implementation path. (06a63891c092)
• Release ordering remains unproven: The supplied context identifies v0.1.6 as the latest release after the July 9, 2026 merge of the local-CLI migration, but does not establish the exact release tag containing its fix commit. (1d3ca1a27e69)

Likely related people:

• Patrick-Erichsen: Authored the merged local-A.I.G migration that appears to replace the service-backed adapter model described here. (role: introduced current integration direction; confidence: medium; files: internal/runner, docs)

How this review workflow works

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.