docs: record content and media acceptance

docs/reviews/audience-validation.md

@@ -1,6 +1,8 @@
 # Evidence-first audience validation
 
-Status: **PENDING — no independent reviewer session has been run.**
+Status: **PENDING — the 2026-09-05 compiled-preview acceptance review passed its
+single-reviewer five-second identity check, but no independent three-person
+session has been run.**
 
 This is a release checkpoint, not an automated substitute for people. It must use at least three independent reviewers representing hiring-screening and technical-interview perspectives. Reviewers use Static or reduced motion first so the information hierarchy is judged without relying on the scene.
 
@@ -29,6 +31,22 @@ This is a release checkpoint, not an automated substitute for people. It must us
 
 Any threshold failure requires content or hierarchy revision. It is not a reason to add visual effects.
 
+## 2026-09-05 acceptance observation
+
+One uncoached compiled-preview review was performed at desktop, 320×568,
+200%-zoom-equivalent, Static, reduced-motion, keyboard-only, no-JavaScript, and
+print-relevant states. At the initial view, the reviewer could identify Luca
+Pîslaru, the equal “System Administrator & Full-Stack Developer” positioning,
+and the email action. The first scan also exposed Nextcloud migration/recovery
+as the principal operations proof and the private medication tracker as the
+principal developer proof. The evidence hierarchy remained readable over the
+night-drive scene, and the final Contact section again presented email as the
+dominant action.
+
+This observation is technical release evidence only. It is one review, not
+three independent hiring/technical participants, so it does not satisfy or
+replace the threshold below.
+
 ## Evidence form
 
 | Reviewer  | Perspective         | Mode/browser/viewport | 30 s identity/role/contact | 60 s systems proof | 60 s software proof | Professional/readable (1–5) | Balance (1–5) | Notes |

docs/reviews/visual-qa.md

@@ -1,6 +1,6 @@
 # Portfolio visual QA
 
-Status date: 2026-09-03
+Status date: 2026-09-05
 
 ## Automated capture contract
 
@@ -28,7 +28,8 @@ Each default viewport asserts:
 - dark professional composition with restrained chromatic accent coverage;
 - no panel background imagery, filters, glowing text, or content scanlines;
 - intentional widths for each desktop layout family, including 68% diagram/toolkit corridors and a 46% destination capped at 42rem, plus readable mobile single-column widths;
-- zero public project image/video elements while the approval-bound manifest is empty.
+- only approval-bound project image elements, with authored captions and text
+  alternatives; no project video is published in the current manifest.
 
 Static receives a two-capture perceptual-stability assertion. Contact arrival must resolve the Contact heading, route HUD, `ARRIVED` state, identity, and visible email action together.
 
@@ -53,6 +54,35 @@ npm run test:browser -- tests/browser/visual-regression.spec.ts
 
 The final 2026-09-02 complete browser run passed 167 checks with 43 deliberate project/capability skips. Two desktop heading-focus geometry checks reached the correct target but timed out under the four-worker run; both files then passed 9/9 unchanged with one worker, including the two affected checks. The 16 visual checks ran once in the available current Chromium project; the duplicate mobile-project visual cases were skipped intentionally.
 
+## Content, SEO, and media acceptance — 2026-09-05
+
+The final focused desktop/mobile Chromium matrix passed 94 checks with 26
+intentional project/capability skips and no failures. It covered semantics,
+keyboard operation, no-JavaScript output, reduced motion, forced colors,
+reflow, responsive layout, approved-media policy and failure behavior, and the
+visual-regression oracle. The compiled preview retained all eight locked
+sections in order.
+
+One broad compiled-preview review covered 1440×900 desktop, 320×568 mobile,
+200%-zoom-equivalent layout, Static, reduced motion, keyboard-only,
+no-JavaScript, and print-relevant views. The opening view communicated Luca's
+name and equal systems/software role immediately. Infrastructure preserved a
+readable request-flow diagram and made the Nextcloud migration the primary
+operations proof. The private medication tracker remained the primary
+developer visual through its three approved screenshots and captions. Footy
+Tracker clearly described collaboration, Luca's contribution, measured
+results, and limitations without publishing the rights-unconfirmed broadcast
+frame. Opinion Dynamics remained a supporting project with two explained
+charts and an exact-values table. Contact kept email as the dominant action.
+
+No high-impact visual or content defect was found. On the shortest 320×568 and
+200%-zoom-equivalent opening views, the fixed drive controls occupy the lower
+viewport edge and can sit beside the end of the opening action row. The row and
+all following content remain scroll-reachable, keyboard-reachable, and clear
+of focus obscuration; the reflow and target-geometry gates passed. This is
+recorded as a non-blocking compact-height tradeoff rather than a reason for a
+preference-driven layout iteration.
+
 The compact 320×568 capture initially revealed that the fixed drive controls occupied 43.5% of the viewport and obscured the opening content. The mobile-only control grid reduced that surface to 24.0%; a regression guard now caps it at 34%. After the trace-driven fixed section navigation landed, the captures exposed the decorative HUD intersecting the navigation at phone widths and the controls at 768×1024. A shared exact navigation-height variable now keeps the fixed navigation and visible compact HUD edge-adjacent, reserves their space in the header, and leaves the controls independent. The final measured bounds were 0–93px navigation and 93–125px HUD at 320×568, and 0–45px navigation and 45–77px HUD at 768×1024. Fixed-navigation focus now uses an inward standards outline so the indicator remains visible inside the viewport. Passive-section coverage now positions the target safely beyond the actual 35% activation line rather than relying on a relative `offsetTop` or exact fractional equality.
 
 A one-sampled-pixel accent floor was relaxed from 0.001 to 0.0005 after the capture remained visibly intentional and the original value missed by only 0.00002; the dark and maximum-accent limits remain unchanged.
@@ -185,7 +215,9 @@ Tall navigator signs had also retained the 390px phone pose throughout the entir
 - [x] The infrastructure flow exposes a visible legend and a complete text equivalent.
 - [x] The GPU budget accounts for composer and bloom render targets without changing ownership or disposal.
 - [x] Contact remains a clear destination with email as the primary action.
-- [x] No unapproved project derivative is published; the manifest remains empty.
+- [x] Only approved project/social derivatives are published; the manifest and
+  compiled asset closure match exactly, and rights-unconfirmed media remains
+  omitted.
 
 The checked items above describe code/invariant inspection, not unsupported human audience approval.
 
@@ -196,7 +228,8 @@ The checked items above describe code/invariant inspection, not unsupported huma
 - [ ] Repeat the named current/previous-stable browser matrix available to release CI.
 - [ ] Inspect portrait and landscape on the physical iPhone 13 and Pixel 6, including browser chrome and safe areas.
 - [ ] Execute NVDA+Firefox and VoiceOver+Safari scripts recorded in the accessibility documents.
-- [ ] Bind and inspect final project derivatives only after Luca approves exact hashes and confirms rights.
+- [x] Bind and inspect the approved project/social derivatives against their
+  exact manifest records, captions, and text alternatives.
 - [ ] Complete the three-person audience record in `docs/reviews/audience-validation.md`.
 
 No unavailable platform or human checkpoint is silently converted into a pass.