Add new features and tests for AirGap and Time modules

- Introduced `SbomService` tasks documentation.
- Updated `StellaOps.sln` to include new projects: `StellaOps.AirGap.Time` and `StellaOps.AirGap.Importer`.
- Added unit tests for `BundleImportPlanner`, `DsseVerifier`, `ImportValidator`, and other components in the `StellaOps.AirGap.Importer.Tests` namespace.
- Implemented `InMemoryBundleRepositories` for testing bundle catalog and item repositories.
- Created `MerkleRootCalculator`, `RootRotationPolicy`, and `TufMetadataValidator` tests.
- Developed `StalenessCalculator` and `TimeAnchorLoader` tests in the `StellaOps.AirGap.Time.Tests` namespace.
- Added `fetch-sbomservice-deps.sh` script for offline dependency fetching.

docs/modules/scheduler/prep/2025-11-20-surface-fs-pointer.md

@@ -0,0 +1,27 @@
+# Surface FS Pointer Contract (Draft) — PREP-SCHED-SURFACE-01
+
+Status: Draft (2025-11-20)
+Owners: Scheduler Worker Guild
+Scope: Define pointer model for Surface FS to unblock scheduler worker planning.
+
+## Pointer model
+- Identifier: `surfacefs://<tenant>/<dataset>/<version>`.
+- Fields:
+  - `tenant_id`
+  - `dataset` (e.g., `sbom`, `findings`, `reachability`)
+  - `version` (content hash or monotonic version)
+  - `storage_uri` (unset/relative in sealed mode; content-addressed path recommended)
+  - `created_at` (RFC3339 UTC)
+- Deterministic JSON serialization with sorted keys.
+
+## Scheduler usage
+- Workers receive pointer in job payload; pointer is immutable per job.
+- Cache key = `surface_fs_pointer`.
+- Validation: ensure `dataset` is allowlisted; reject untrusted storage_uri when sealed mode is on.
+
+## Open decisions
+- Final allowlist of datasets.
+- Whether inline `storage_uri` is permitted under sealed mode or requires local mirror resolution.
+
+## Handoff
+Use this doc as the PREP artefact for PREP-SCHED-SURFACE-01; update once datasets and sealed-mode rule are agreed.

docs/modules/scheduler/prep/2025-11-20-worker-23-101-prep.md

@@ -0,0 +1,21 @@
+# Scheduler Worker PREP — SCHED-WORKER-23-101
+
+Status: Draft (2025-11-20)
+Owners: Scheduler Worker Guild · Policy Guild
+Scope: Capture activation event contract and throttle source needed for worker 23-101.
+
+## Required inputs
+- Activation event schema from Policy guild: expected fields `{job_id, policy_run_id, tenant_id, priority, throttle_source}`.
+- Throttle source definition (static config vs dynamic policy signals).
+
+## Proposed contract
+- Event type: `scheduler.policy.activation.requested`.
+- Payload: `{job_id, policy_run_id, tenant_id, priority, requested_at_utc, throttle_source}`.
+- Throttle source values: `scheduler-default`, `policy-signal`, `manual-override` (to be confirmed).
+
+## Open decisions
+- Whether to carry bundle pointers (policy/export) in the activation event.
+- Retry/backoff policy if Policy service is down.
+
+## Handoff
+Use this doc as PREP artefact for SCHED-WORKER-23-101; update once Policy guild provides final schema/throttle rules.