gustavosantos/GTI_GERENCIADOR_FISCAL
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: clarify legacy blocker resolution limits

Browse Source
This commit is contained in:
gti
2026-09-22 21:46:44 -03:00
parent 50254772e4
commit 283749e860
1 changed files with 5 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/CONTROL_PANEL_OPERATIONAL_UX_V1.md
+5
View File
@@ -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 Blocker details show evidence, first/last seen, retry count, related
events/jobs, and resolution audit history when available. 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 Resolving a blocker means saving validated operator context and queueing
reprocessing for that product; it does not directly write fiscal data or reprocessing for that product; it does not directly write fiscal data or
immediately mark historical blocker evidence resolved. The workflow requires a immediately mark historical blocker evidence resolved. The workflow requires a