Skip to content

docs: close the security-review record - D12, resolution, current counts - #67

Merged
bgard68 merged 1 commit into
mainfrom
docs/close-the-record
Jul 29, 2026
Merged

docs: close the security-review record - D12, resolution, current counts#67
bgard68 merged 1 commit into
mainfrom
docs/close-the-record

Conversation

@bgard68

@bgard68 bgard68 commented Jul 29, 2026

Copy link
Copy Markdown
Owner

Final consistency pass over the review record.

D12 — the finding only a browser could surface

Every header check passed, the site rendered — and the console still logged one violation. Angular's inlineCritical ships an inline onload handler that script-src 'self' rightly blocks, leaving the full stylesheet silently print-only. Recorded with:

  • Analysis — why nothing errored and nothing looked broken (767-byte stylesheet: the inlined "critical" portion was effectively all of it)
  • FixinlineCritical: false; at that size the optimization bought nothing with or without a CSP
  • Tests preventing recurrencecheck:swa scans the built index.html for inline handlers and script bodies (proven to fail on the reinjected defect), and the post-CSP browser pass asserting zero console violations

Also

  • Deployment-status table: D4/D11 now live — the record no longer reads as an open incident
  • SWA-outage section marked resolved, with how it ended
  • Lesson 29 postscript: the recovering control plane was the tell that one retry had become worth attempting
  • Two smoke-test counts said 27 where the suite is now 32

🤖 Generated with Claude Code

D12 records the finding that only a real browser could surface: every header
check passed and the console still logged one violation, because Angular's
inlineCritical optimization ships an inline onload handler that script-src
'self' rightly blocks - leaving the full stylesheet silently print-only. The
entry carries the analysis, the fix (inlineCritical off; the stylesheet is 767
bytes, so the optimization bought nothing), and the two tests that prevent
recurrence: check:swa scanning the BUILT index.html for inline script, and the
zero-violations browser pass after any CSP change.

The deployment-status table and the SWA-outage narrative now record the
resolution instead of reading as an open incident, lesson 29 gets its ending
(the recovering control plane was the tell that one retry had become worth
attempting), and two smoke-test counts that described the present said 27
where the suite is now 32.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@bgard68
bgard68 merged commit 752fab7 into main Jul 29, 2026
5 checks passed
@bgard68
bgard68 deleted the docs/close-the-record branch July 29, 2026 00:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant