SOP: v1.2 — website build stack + SSR signal in capture and report

docs/operations/beta-audit-process.md

@@ -1,6 +1,6 @@
 # VeriPath Beta Audit Process
 
-**Status:** Locked v1.1 — 2026-08-15, for beta use (v1.1 decision: `docs/decisions/2026-08-15-audit-pipeline-v1-1.md`)
+**Status:** Locked v1.2 — 2026-08-17, for beta use (v1.2: `docs/operations/decisions/DR-003-website-stack-fingerprinting.md`)
 **Supersedes:** 2026-08-14 draft lock
 
 ## Purpose
@@ -21,7 +21,7 @@ The client-facing report includes material findings only, covering:
 - NAP consistency
 - Hours consistency, with Google Business Profile as the source of truth
 - Review velocity
-- Website reachability and schema conflicts
+- Website reachability, schema conflicts, build stack, and SSR (rendering) signal
 
 ## Process
 
@@ -46,6 +46,13 @@ The pipeline writes the full required artifact set itself. `report_gate`
 fails the run (non-zero exit) if the §6 gate fails — a failing run does
 not deliver.
 
+Website capture also fingerprints the build stack and records the SSR signal
+(`website.stack.primary`, `website.stack.ssr_signal` in the raw JSON). When
+`primary` is not `unknown`, the client report states how the website was
+built. When `ssr_signal` is `weak` (fewer than 50 words in the raw HTML), the
+report flags that non-JavaScript AI crawlers cannot read the page body, and
+any capture-based finding about website content must be qualified accordingly.
+
 ### 3. Human validation (reviewer decision loop)
 
 The reviewer must resolve every engine finding to exactly one disposition.