stabilize tests

src/Findings/AGENTS.md

@@ -1,4 +1,4 @@
-# Findings Ledger · AGENTS.md
+# Findings Ledger ?? AGENTS.md
 
 ## Working directory
 - Primary path: `src/Findings/StellaOps.Findings.Ledger` (and sibling test project under `src/Findings/__Tests` when exercising tests).
@@ -6,7 +6,7 @@
 
 ## Roles covered
 - Backend engineer: .NET 10/C# for ledger services, projections, provenance links, Merkle anchoring.
-- QA / determinism: replay harness, property/integration tests, load testing at ≥5M findings/tenant.
+- QA / determinism: replay harness, property/integration tests, load testing at ???5M findings/tenant.
 - Observability / DevOps: metrics, logs, dashboards, alert wiring, deployment/backup/offline kits.
 
 ## Required reading before DOING
@@ -19,8 +19,8 @@
   - `docs/modules/findings-ledger/airgap-provenance.md`  
   - `docs/modules/findings-ledger/schema.md` (sealed-mode and Merkle root structure)  
   - `docs/modules/findings-ledger/workflow-inference.md` (projection rules)
-- Observability policy: `docs/observability/policy.md`.
-- Triage & Unknowns (Alerts/Decisions): `docs/implplan/SPRINT_3602_0001_0001_evidence_decision_apis.md`.
+- Observability policy: `docs/modules/telemetry/guides/policy.md`.
+- Triage & Unknowns (Alerts/Decisions): `docs-archived/implplan/SPRINT_3602_0001_0001_evidence_decision_apis.md`.
 
 ## Triage Alerts & Decisions (SPRINT_3602)
 - REST endpoints live in `src/Findings/StellaOps.Findings.Ledger.WebService/Program.cs` and must remain deterministic and tenant-scoped:
@@ -37,7 +37,7 @@
   - Evidence hashes captured at decision time must be stable and ordered deterministically.
 
 ## Execution rules
-- Update sprint `Delivery Tracker` status when you start/stop/finish: TODO → DOING → DONE/BLOCKED.
+- Update sprint `Delivery Tracker` status when you start/stop/finish: TODO ??? DOING ??? DONE/BLOCKED.
 - If a contract/design decision is missing, mark the task BLOCKED in the sprint, add the decision needed under **Decisions & Risks**, then continue with other unblocked tasks.
 - Keep outputs deterministic: UTC ISO-8601 timestamps, stable ordering, seeded property tests, repeatable replay runs.
 
@@ -54,7 +54,7 @@
 - Load tests should record CPU/memory budgets as part of run artifacts; keep seeds and fixtures under version control.
 
 ## Observability & operations
-- Metrics/logs/traces via OpenTelemetry → OTLP → Prometheus/Tempo/Loki; respect `observability.enabled` flag.
+- Metrics/logs/traces via OpenTelemetry ??? OTLP ??? Prometheus/Tempo/Loki; respect `observability.enabled` flag.
 - Dashboards: include Grafana JSON exports under `offline/telemetry/dashboards/ledger`.
 - Alerts: wire as documented in `observability.md`; for air-gap emit to syslog + CLI incident scripts.
 - Deployments: follow `deployment.md` for Helm/Compose overlays, migrations, backup/restore, and offline kits.
@@ -69,3 +69,4 @@
 - Metrics/logs follow approved names and labels; dashboards/alerts updated if schemas change.
 - Replay harness run (or planned) for determinism-impacting changes; attach/report results.
 - Docs updated when contracts or workflows change (module docs, observability policy, sprint Decisions & Risks).
+