Added documentation and artifacts for Spec 377 regarding post-productization browser reaudit closeout gate. Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #448
2.4 KiB
2.4 KiB
Remaining Findings
Verification level: browser-verified for current browser observations, repo-verified for predecessor artifact facts, and derived from existing implementation for closeout impact.
Findings
| Finding ID | Severity | Surface | Verification level | Problem | Why it matters | Recommended follow-up | Closeout impact |
|---|---|---|---|---|---|---|---|
| F377-P2-001 | P2 | System Dashboard and System Operations | not verified for manual in-app browser, repo-verified for Spec 376 proof |
Direct manual browser attempts redirect to /system/login; Spec 377 cannot score the rendered system pages in the in-app browser. |
System surfaces are platform-admin operational surfaces, so manual review remains less convenient than admin/customer review. | Add or document a manual system-panel browser fixture only if future closeout reviews require human/manual system scoring. | Allows closed-with-follow-up; does not force open because Spec 376 browser-proved system reachability through platform guard fixtures. |
| F377-P3-002 | P3 | Historical before screenshots | not available |
Spec 368 numeric scorecard and findings are present, but its screenshot directory is not present in this checkout. | Visual before/after comparison cannot be replayed image-by-image from this branch alone. | Preserve future browser-audit screenshots in spec packages when numeric scorecards are created. | Does not block closeout because Spec 368 scores and findings are available. |
| F377-P3-003 | P3 | Admin/customer shell chrome | browser-verified |
The current app shell remains visible in most captured pages. | Shell density can still make page screenshots look busier than the underlying productized content. | Treat as optional polish or a future customer-mode shell discussion, not as Spec 377 runtime scope. | Does not block closeout; all reachable core surfaces have decision-first content above supporting detail. |
P0/P1 Status
| Severity | Count | Verification class | Closeout impact |
|---|---|---|---|
| P0 | 0 | derived from existing implementation |
No P0 finding blocks closeout. |
| P1 | 0 | derived from existing implementation |
No reachable customer/auditor safety P1 or reachable core P1 remains. |
| P2 | 1 | derived from existing implementation |
System manual fixture limitation supports closed-with-follow-up. |
| P3 | 2 | derived from existing implementation |
Optional/reporting polish only. |