feat: Add initial implementation of Vulnerability Resolver Jobs

- Created project for StellaOps.Scanner.Analyzers.Native.Tests with necessary dependencies.
- Documented roles and guidelines in AGENTS.md for Scheduler module.
- Implemented IResolverJobService interface and InMemoryResolverJobService for handling resolver jobs.
- Added ResolverBacklogNotifier and ResolverBacklogService for monitoring job metrics.
- Developed API endpoints for managing resolver jobs and retrieving metrics.
- Defined models for resolver job requests and responses.
- Integrated dependency injection for resolver job services.
- Implemented ImpactIndexSnapshot for persisting impact index data.
- Introduced SignalsScoringOptions for configurable scoring weights in reachability scoring.
- Added unit tests for ReachabilityScoringService and RuntimeFactsIngestionService.
- Created dotnet-filter.sh script to handle command-line arguments for dotnet.
- Established nuget-prime project for managing package downloads.

src/Excititor/StellaOps.Excititor.Worker/AGENTS.md

@@ -1,34 +1,39 @@
-# AGENTS
-## Role
-Background processing host coordinating scheduled pulls, retries, reconciliation, verification, and cache maintenance for Excititor.
+# Excititor Worker Charter
+
+## Mission
+Run Excititor background jobs (ingestion, linkset extraction, dedup/idempotency enforcement) under the Aggregation-Only Contract; orchestrate Core + Storage without applying consensus or severity.
+
 ## Scope
-- Hosted service (Worker Service) wiring timers/queues for provider pulls and reconciliation cycles.
-- Resume token management, retry policies, and failure quarantines for connectors.
-- Re-verification of stored attestations and cache garbage collection routines.
-- Operational metrics and structured logging for offline-friendly monitoring.
-## Participants
-- Triggered by WebService job requests or internal schedules to run connector pulls.
-- Collaborates with Storage.Mongo repositories and Attestation verification utilities.
-- Emits telemetry consumed by observability stack and CLI status queries.
-## Interfaces & contracts
-- Scheduler abstractions, provider run controllers, retry/backoff strategies, and queue processors.
-- Hooks for policy revision changes and cache GC thresholds.
-## In/Out of scope
-In: background orchestration, job lifecycle management, observability for worker operations.
-Out: HTTP endpoint definitions, domain modeling, connector-specific parsing logic.
-## Observability & security expectations
-- Publish metrics for pull latency, failure counts, retry depth, cache size, and verification outcomes.
-- Log correlation IDs & provider IDs; avoid leaking secret config values.
-## Tests
-- Worker orchestration tests, timer controls, and retry behavior will live in `../StellaOps.Excititor.Worker.Tests`.
+- Working directory: `src/Excititor/StellaOps.Excititor.Worker`
+- Job runners, pipelines, scheduling, DI wiring, health checks, telemetry for background tasks.
 
 ## Required Reading
 - `docs/modules/excititor/architecture.md`
-- `docs/modules/platform/architecture-overview.md`
+- `docs/modules/excititor/vex_observations.md`
+- `docs/ingestion/aggregation-only-contract.md`
+- `docs/modules/excititor/implementation_plan.md`
 
-## Working Agreement
-- 1. Update task status to `DOING`/`DONE` in both correspoding sprint file `/docs/implplan/SPRINT_*.md` and the local `TASKS.md` when you start or finish work.
-- 2. Review this charter and the Required Reading documents before coding; confirm prerequisites are met.
-- 3. Keep changes deterministic (stable ordering, timestamps, hashes) and align with offline/air-gap expectations.
-- 4. Coordinate doc updates, tests, and cross-guild communication whenever contracts or workflows change.
-- 5. Revert to `TODO` if you pause the task without shipping changes; leave notes in commit/PR descriptions for context.
+## Roles
+- Backend/worker engineer (.NET 10).
+- QA automation (background job + integration tests).
+
+## Working Agreements
+1. Track task status in sprint files; log notable operational decisions in Execution Log.
+2. Respect tenant isolation on all job inputs/outputs; never process cross-tenant data.
+3. Idempotent processing only: guard against duplicate bundles and repeated messages.
+4. Offline-first; no external fetches during jobs.
+5. Observability: structured logs, counters, and optional OTEL traces behind config flags.
+
+## Testing & Determinism
+- Provide deterministic job fixtures with seeded clocks/IDs; assert stable ordering of outputs and retries.
+- Simulate failure/retry paths; ensure idempotent writes in Storage.
+- Keep timestamps UTC ISO-8601; inject clock/GUID providers for tests.
+
+## Boundaries
+- Delegate domain logic to Core and persistence to Storage.Mongo; avoid embedding policy or UI concerns.
+- Configuration via appsettings/environment; no hard-coded secrets.
+
+## Ready-to-Start Checklist
+- Required docs reviewed.
+- Test harness prepared for background jobs (including retry/backoff settings).
+- Feature flags defined for new pipelines before enabling in production runs.