fix(observability): restack ambiguous alert JSON integrity on current main

[seonghobae]

Purpose

Rebuild only PR #313's operational-alert JSON-integrity hardening onto current protected main after #305 advanced the base. No predecessor CI, review, scanner, coverage, model, release, deployment, KPI, production, or acquisition authority transfers.

Exact construction

• protected main immediately before publication: 534bf1708a6277c443867e87092ac5f2c05ea490;
• source PR fix(observability): restack ambiguous alert JSON integrity on current main #313 exact unchanged head at the pre-write refetch: bbec93552e1b68b943a4860c6cc47cd38ad108e3;
• successor exact head: 8d553a640d5c13b61a235aa0e7bd6e74b35e4ea4;
• ancestry: exactly 1 commit ahead / 0 behind protected main, merge base exactly protected main;
• net scope: exactly two paths: scripts/evaluate-observability-alerts.mjs and test/observability-alert-input-integrity.test.ts.

The protected-main movement since #313's prior base changes only the distributed rate-limiter source/tests, so this successor overlays #313's exact two head blobs without overwriting intervening protected bytes.

Observability integrity contract

JSON-looking operational-alert NDJSON records are rejected on escape-equivalent duplicate decoded keys before route/status/latency/error/window classification. Malformed UTF-8 remains fail-closed and non-JSON Wrangler diagnostic noise remains tolerated. This is evidence-validation hardening only; it does not prove production KPI data, deployment, alert delivery, or operational acceptance.

Evidence boundary

Keep Draft until this unchanged exact head receives fresh terminal-success application ci, reviewer-ci, and protected-base-eligible central Security Scan, exact 100% owned production statement/branch/function/line coverage using realistic tests, and zero valid unresolved findings. Pending, queued, skipped, absent, neutral, failed, cancelled, stale, predecessor, status-only, model-only, or rate-limited evidence is non-passing.

Immediately before Ready or merge, independently re-resolve protected main, exact head/base/ancestry, reviews/threads, checks and checkout SHAs, live rulesets, central Security Scan revision/triggers/base filters/thresholds, releases, and writer state.

Supersedes #313 only after fresh exact-head verification and protected integration.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: eb205e2d-9983-46d7-8687-ce512d04903b

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}