Explain invocation presentation failures
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# Invocation reporting audit remediation
|
||||
|
||||
Status: remediation in progress; 2 of 7 findings complete.
|
||||
Status: remediation in progress; 3 of 7 findings complete.
|
||||
|
||||
## Review scope
|
||||
|
||||
@@ -185,7 +185,12 @@ detail-rendering path as needed to establish that the shared fix applies there.
|
||||
|
||||
## 3. Explain failures introduced by CommandKit presentation
|
||||
|
||||
Priority: P2. Status: open.
|
||||
Priority: P2. Status: complete.
|
||||
|
||||
- [x] Completed: presentation failures that turn success into failure now retain
|
||||
a core-owned rendering/delivery explanation. Supplied explanations and causes,
|
||||
generic handler fallback, quiet rendering, domain status, and failed-sink
|
||||
behavior remain covered. Validation: `GOTOOLCHAIN=local go test ./...` at root.
|
||||
|
||||
### Finding and evidence
|
||||
|
||||
|
||||
Reference in New Issue
Block a user