diff --git a/docs/status/2026-05-07-state.md b/docs/status/2026-05-07-state.md
index ba14acf..6a1ba64 100644
--- a/docs/status/2026-05-07-state.md
+++ b/docs/status/2026-05-07-state.md
@@ -53,7 +53,7 @@
 - `k8s/benchmark/k6-job-prod.yaml` — load test для prod (Service port :80 fix)
 - `k8s/benchmark/synthetic-smoke-prod.yaml` — one-shot smoke (auth + 3 endpoints, exit code = pass/fail)
 - `k8s/benchmark/synthetic-smoke-cronjob-prod.yaml` — continuous monitoring (*/30 min)
-- `k8s/kafka/topic-orphan-fix.sh` — janitorial script для KafkaTopic READY=False
+- `k8s/kafka/topic-orphan-fix.sh` — janitorial script для KafkaTopic READY=False (✅ applied 2026-05-07 evening — все 3 topics unmanaged, alerts gone)
 - prometheus-rules group `ordinis.synthetic` (2 alerts: SmokeFailed/Stale, conditional на `prometheusRule.synthetic.enabled`)
 - `.gitlab-ci.yml` job `build-postgis-barman` (kaniko + REGISTRY_USER/REGISTRY auth, currently 401 — known issue, manual push fallback)
 
@@ -120,11 +120,11 @@
 
 ### 1.2. В процессе / nice-to-have
 
-- KafkaTopics CR показывают `READY=False`. Reason: "Decreasing partitions not supported" — `cluster-prod.yaml` указал partitions=3, broker имеет больше (orphan от старого setup). Fix: `k8s/kafka/topic-orphan-fix.sh` annotate'ит `strimzi.io/managed=false` (broker continues, alerts замолкают). Apply вручную.
+- ~~KafkaTopics READY=False~~ ✅ **APPLIED 2026-05-07 evening** через `k8s/kafka/topic-orphan-fix.sh`. Все 3 topics (.public/.internal/.restricted) теперь annotate'нуты `strimzi.io/managed=false` — Strimzi user-operator больше не пытается reconcile (ошибка "Decreasing partitions not supported" гасла). Topics в брокере продолжают жить, projection-writer connected. Alerts на READY=False больше не срабатывают.
 - Vault SASL passwords могут быть stale если Strimzi user-operator regenerated после Kafka cluster recreate — re-run `scripts/vault/populate.sh`
 - ~~`postgis-barman` image SPOF на staging registry~~ ✅ **CLOSED 2026-05-07 evening:** image mirrored в `repo.nstart.cloud/terravault/postgis-barman:18.3-3.6.2-2`, prod cluster.142 pull'ит оттуда. См. секцию 0.1 ниже про инцидент.
 - k6 benchmark на prod не прогнан (smoke 50 RPS / ramp 1k / sustain 5m готов в `k8s/benchmark/k6-job-prod.yaml`)
-- Synthetic smoke + alerts ready (`k8s/benchmark/synthetic-smoke-cronjob-prod.yaml` + prometheus-rules group `ordinis.synthetic`) — apply manually + helm upgrade с values-prod
+- Synthetic smoke + alerts ready (`k8s/benchmark/synthetic-smoke-cronjob-prod.yaml` + prometheus-rules group `ordinis.synthetic`). **Pre-flight partial:** `k6-tests` ConfigMap создан в `ordinis-prod` (test script). Осталось: создать `k6-keycloak-creds` Secret (требует Keycloak SA `ordinis-bench` client_secret — на стороне Keycloak admin), apply CronJob, helm upgrade с values-prod для активации alerts
 - Real ЦУОД data integration (отдельный epic после prod soak)
 
 ### 1.3. Roadmap (отложено)