stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 2 Releases Wiki Activity

prep docs and service updates
Some checks failed
Docs CI / lint-and-preview (push) Has been cancelled
Details

Browse Source
This commit is contained in:
master
2025-11-21 06:56:36 +00:00
parent ca35db9ef4
commit d519782a8f
242 changed files with 17293 additions and 13367 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
docs/modules/scanner/prep/2025-11-20-node-isolated-runner.md
View File

@@ -27,6 +27,7 @@ Scope: Requirements and plan to provide an isolated/scoped runner so targeted No
- Document usage in `src/Scanner/__Tests/README.md`.
## Blocking items
- None identified; all inputs are local to the repo/offline feeds.
- Upstream Concelier projects in solution filter currently do not build (`StellaOps.Concelier.Storage.Mongo` duplicate `AdvisoryObservationSourceDocument` definition and missing `NatsJSContext` type), so `dotnet test` fails before Node analyzer tests execute. Needs Concelier fix or temporary exclusion to validate runner.
- 2025-11-20 follow-up: deduplication + JetStream package added in Concelier.Storage.Mongo and Scanner tests now set `UseConcelierTestInfra=false`, but the shared Directory.Build.props still injects Concelier connectors into the restore/build graph; Node tests remain blocked until Concelier test infra is fully detachable or those projects are excluded from the filter.
This note satisfies PREP-SCANNER-ANALYZERS-NODE-22-001-NEEDS-ISOL by defining the isolated runner plan and artefact locations.

16
docs/modules/scanner/prep/2025-11-21-scanner-records-prep.md Normal file
View File

@@ -0,0 +1,16 @@
# Scanner Record Payloads Prep — PREP-SCANNER-RECORDS
Status: Draft (2025-11-21)
Owners: Scanner Guild · Policy Guild
Scope: Stabilize record/observation payload schema for scanner workers so downstream policy/graph pipelines can rely on consistent envelopes.
Needs
- Confirm per-language analyzer output fields (package coordinates, vuln refs, evidence hashes) and common envelope keys.
- Decide deterministic ordering for findings within a record to support replay/air-gap.
- Define maximum payload size, chunking rules, and checksum strategy (SHA256 over canonical JSON).
- Align timestamp format (UTC, RFC3339) and monotonic sequencing for job-level ordering.
Next actions
- Pull latest analyzer outputs from scanner worker prototypes and normalize into a shared JSON Schema.
- Share sample NDJSON record set for Policy/Graph consumers.
- Publish links into relevant sprints once schema draft is frozen.