Skip to content

feat(scan): emit native artifacts with correlated loot - #85

Open
M09Ic wants to merge 10 commits into
masterfrom
feat/native-artifact-loot
Open

feat(scan): emit native artifacts with correlated loot#85
M09Ic wants to merge 10 commits into
masterfrom
feat/native-artifact-loot

Conversation

@M09Ic

@M09Ic M09Ic commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Summary

  • emit scanner-native Artifact messages and independent Loot markers joined by result_id
  • preserve native gogo, spray, zombie, and Neutron SDK results without legacy scan summary/error artifact schemas
  • reuse sdktypes.TemplateResult for Neutron output and wire --broad-poc into scan profiles
  • reuse shared LLM_BASE_URL, LLM_API_KEY, and LLM_MODEL as provider fallback for Mapping/serverless execution
  • infer the OpenAI-compatible provider from the configured base URL while retaining standalone AIScan configuration
  • pin the canonical cyber-ui protocol schemas from feat(aop): correlate loot and support ranged file reads cyber-ui#11 and regenerate Go bindings
  • make Run.Wait a cleanup barrier so rotating commands cannot observe a completed run as active

Tests

  • go test ./...
  • go test -race ./pkg/runner
  • go test ./... in aop/
  • go vet ./...
  • go test ./pkg/runner -run TestClearRotatesToAnEmptyContinuationSession -count=100
  • go run ./cmd/gen twice with protoc 35.1 (stable generated diff)
  • npm run build --prefix web/frontend
  • no-flag agent invocation with only shared LLM_* returned the expected DeepSeek marker
  • serverless invocation inherited shared LLM_* without any nonempty AISCAN_* variables

Dependency

Note

The branch includes the existing local prerequisite commit bfbb17f on top of v0.4.0. The native record tool is intentionally excluded and will be proposed as a separate PR.

M09Ic and others added 8 commits August 5, 2026 20:42
Teach the agent to publish confirmed vulnerabilities to the bound IOA
space as natural-language checkpoint messages (kind=finding), making
discoveries observable via ioa read and reviewable through the
checkpoint status trail. result_id is the finding's single identity:
report files are named findings/<result_id>.md and the ioa message
cites it, so no separate finding-id exists.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant