From 283749e86024e1c0165321d8db6872860bdc7d53 Mon Sep 17 00:00:00 2001 From: gti Date: Tue, 22 Sep 2026 21:46:44 -0300 Subject: [PATCH] docs: clarify legacy blocker resolution limits --- docs/CONTROL_PANEL_OPERATIONAL_UX_V1.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/CONTROL_PANEL_OPERATIONAL_UX_V1.md b/docs/CONTROL_PANEL_OPERATIONAL_UX_V1.md index 046c393..f676ef1 100644 --- a/docs/CONTROL_PANEL_OPERATIONAL_UX_V1.md +++ b/docs/CONTROL_PANEL_OPERATIONAL_UX_V1.md @@ -90,6 +90,11 @@ with pagination; event rows expose related job/product links when present. Blocker details show evidence, first/last seen, retry count, related events/jobs, and resolution audit history when available. +Legacy blocker rows without a persisted installation binding remain visible at +tenant level, but the panel does not offer context resolution or reprocessing +for them. The detail page explains that an exact server cannot be proven; direct +resolution attempts return a conflict rather than guessing an Agent. + Resolving a blocker means saving validated operator context and queueing reprocessing for that product; it does not directly write fiscal data or immediately mark historical blocker evidence resolved. The workflow requires a