V2 preview · not for production

PHASE 6 · FINAL REVIEW — V4.2 RELEASE GATE (Nov 5)

V4.2 release gate — technical PASS; manual fallback owner-approved; one owner confirmation pending.

All five independent-review findings are corrected and regression-verified below (CTA clarity, mobile navigation, malformed canonicals, release traceability, lead-capture audit). The release validation was rerun on Nov 5 and passed in full (section G). The owner has approved the manual lead-monitoring fallback in principle, and its operational procedure is documented with evidence in section I — one verification step remains that only the owner can perform (signing in at /admin and opening Leads). Email notification delivery remains broken with the known platform-side 401; the Emergent support escalation stays open. Nothing deploys without explicit owner approval.

A · Five-issue resolution matrix

1 · Demo CTA destination clarity PASSSeverity: LOW

Problem: Fictional-styled contact buttons (Schedule Service, Call the 24/7 line, Book the free inspection, …) dialed Be rAIdy's real number without saying so.

Correction: All 30 contact CTAs across the seven demos now explicitly name Be rAIdy (“Call Be rAIdy — (857) 427-0343”, “Talk to Be rAIdy”, “Request a Be rAIdy consultation”). Three fictional service CTAs became non-operational in-page anchors (HVAC heating/cooling → plans; Water “Describe it to dispatch” → recovery). Zero forms on demo pages.

Files: All seven src/pages/design/*Concept.jsx

Evidence: grep audit: every PHONE_TEL label contains “Be rAIdy”; full inventory in section B; regression iteration_32 confirmed all 30 labels on the rendered pages.

2 · Mobile navigation overflow / header reflow PASSSeverity: MEDIUM

Problem: Custom .xx-btn { display:inline-flex } out-specified Tailwind's hiding utilities, so desktop CTAs rendered on mobile and pushed Menu buttons off-screen (measured: pest Menu at x=459 on a 390px viewport; hvac/garage/water/electrical similar at 320–430px; plumbing hero copy bled over its header).

Correction: Important-modifiers on the responsive utilities (!hidden sm:!inline-flex, md:!hidden / lg:!hidden menu buttons) in all seven concepts; plumbing hero converted to a min-height flow layout so its copy can never clip; garage openers table remains an intentional in-container scroll region.

Files: All seven src/pages/design/*Concept.jsx (navs + plumbing hero)

Evidence: 35-audit matrix before/after (scripts/capture_v4_qa.py): 11 nav overflows before → 0 after, at 320/375/390/430/768 closed + open menu; before/after screenshots in section C.

3 · Malformed canonical “https://beraidy.comundefined” PASSSeverity: MEDIUM

Problem: Seo.jsx built a canonical from an undefined path on the seven demo routes.

Correction: Canonical and og:url are now emitted only when an explicit path exists; path-less noindex demos get no canonical at all (and any stale tag is removed on client-side transitions). Demos stay noindex and out of the sitemap; production metadata untouched.

Files: src/components/Seo.jsx

Evidence: Regression iteration_32: all seven /for/* routes emit no canonical/og:url (direct load + client-side transition); production /, /plumbing-marketing, /plumbing-marketing/massachusetts canonicals correct; sitemap 33 URLs.

4 · Release traceability PASSSeverity: MEDIUM

Problem: QA report gave assurances without concrete release identifiers.

Correction: Section E below: release commit SHA, bundle identifier, tested revision, production checkpoint, rollback procedure, database non-overwrite statement and post-deploy verification steps.

Files: git + build logs (no app code)

Evidence: Release commit 5fab712; bundle main.3cdf18d0.js; verify:seo ALL CHECKS PASSED on that code.

5 · Lead capture, notifications and manual fallback FALLBACKSeverity: HIGH

Problem: Email notifications fail with the platform-side 401 (invalid X-Email-Key); delivery cannot be verified until Emergent re-provisions the key.

Correction: Owner approved the manual lead-monitoring fallback in principle (Nov 5). Controlled end-to-end test rerun with QA-labeled data (section F): lead accepted, persisted with status “new”, duplicate-rejected on resubmit, notification failure truthfully logged. Full operating procedure and evidence in section I; one owner confirmation step remains.

Files: None (verification only; no app changes)

Evidence: Sections F and I: API responses, MongoDB leads + email_log records, schedule, ownership and contingency protocol.

B · Contact CTA inventory — all seven demos

27 active call CTAs (every label names Be rAIdy; all dial +1 (857) 427-0343) + 3 fictional service CTAs kept as clearly non-operational in-page anchors + the fixed demo ribbon on every page. Zero forms, zero silent hand-offs to a fictional business.

Plumbing — BlueLine

tel:Call Be rAIdy (nav)
tel:Call Be rAIdy — (857) 427-0343 (mobile menu, hero, CTA band, closing)

HVAC — Meridian

tel:Talk to Be rAIdy (nav + hero + plan card)
tel:Call Be rAIdy — (857) 427-0343 (mobile menu)
in-pageBook a heating visit / Book a cooling visit → #plans

Roofing — Summit & Slate

tel:Call Be rAIdy — (857) 427-0343 (nav + estimate band)

Pest control — Willow Shield

tel:Call Be rAIdy — (857) 427-0343 (mobile menu, hero, CTA band)
tel:Or call Be rAIdy — (857) 427-0343 (hero)
tel:Talk to Be rAIdy (one-time plan)
tel:Request a Be rAIdy consultation (featured plan)
in-pageBook a free inspection → #plans

Garage door — Northgate

tel:Call Be rAIdy — (857) 427-0343 (mobile menu, hero, quote band)
tel:Talk to Be rAIdy (repairs band)
in-pageGet an exact quote → #quote

Water damage — DryLine

tel:Call Be rAIdy — (857) 427-0343 (nav, mobile menu, red band)
tel:Call Be rAIdy — 24/7 line (hero)
in-pageDescribe it to dispatch → #recovery

Electrical — Edge & Volt

tel:Call Be rAIdy — (857) 427-0343 (mobile menu, hero, booking band)
in-pageBook an assessment → #book

C · Mobile navigation — before / after (320–430px)

Measured across 320 / 375 / 390 / 430 / 768px, closed and open menu, all seven demos: 11 nav overflows before → 0 after. Root cause: the custom button classes' display:inline-flex out-specified Tailwind's responsive hiding, so desktop CTAs rendered on phones and pushed the Menu button off-screen.

Concept	320px	375px	390px	430px	768px
Plumbing	overlap* → ok	ok	ok	ok	ok
HVAC	OVERFLOW → ok	ok	ok	ok	ok
Roofing	ok	ok	ok	ok	ok
Pest control	clipped* → ok	OVERFLOW → ok	OVERFLOW → ok	OVERFLOW → ok	ok
Garage door	OVERFLOW → ok	OVERFLOW → ok	OVERFLOW → ok	OVERFLOW → ok	ok
Water damage	OVERFLOW → ok	ok	ok	ok	ok
Electrical	clipped* → ok	OVERFLOW → ok	OVERFLOW → ok	ok	ok

* visible clipping/overlap found in screenshots, not detectable via scrollWidth because the site clips horizontal overflow by design. “OVERFLOW → ok” = before → after. The garage openers table keeps its intentional in-container horizontal scroll (not navigation).

Pest control — Menu button pushed off-screen at 390px

before

after

Electrical — Menu button clipped at 390px

before

after

Garage doors — header CTA clipped at 320px

before

after

Water damage — header CTA clipped at 320px

before

after

Plumbing — hero copy overlapped the header at 320px

before

after

D · SEO evidence

✓ All seven /for/* demos: robots meta “noindex, nofollow”, no canonical tag, no og:url (direct load + client-side transition, checked in DOM)
✓ Zero “beraidy.comundefined” anywhere; zero demo routes in the sitemap (33 public URLs unchanged)
✓ Production titles/descriptions/canonicals unchanged and correct on /, national trade pages and Massachusetts/Boston pages
✓ yarn build + prerender + verify:seo ALL CHECKS PASSED on release commit 5fab712 (homepage 1,086 words; trades 1,226–1,538)
✓ GTM/consent untouched; only additions are site-consistent cta_click events on demo links

E · Release traceability

✓ V4.1 release commit: 5fab7125ff259d882133d07666fa7e3bbc112195 (short 5fab712) — contains every correction in this report
✓ Preview build identifier: static/js/main.3cdf18d0.js (yarn build 75.5s on commit 5fab712; prerender 33 URLs). The last fully verified build — including this report page — is static/js/main.4eff479d.js (commit 4a538a0, verify:seo ALL CHECKS PASSED). The V4.2 report-text update is a docs-only delta: rebuilt and re-run through verify:seo before release, with the final bundle id recorded in the release approval message
✓ Tested revision: the release-gate regression rerun (iteration_33, Nov 5) executed against this exact source — all eight categories PASS; iteration_32 results remain valid
✓ Current production: the owner's last deployment predates Phase V1 (E7B era) — its exact SHA/bundle are visible under Manage Publishing → deployment history; no V4.1 code is on production yet
✓ Verified rollback checkpoint: that live pre-V4 deployment, restorable via the platform's Rollback option (code-level only — V4/V4.1 performs no database migration)
✓ Environment: all V4.1 changes live in the PREVIEW environment; production is untouched until the owner approves deployment
✓ Database safety: the release ships code only; production records, Google Ads campaigns and customer data are not modified
✓ Post-deploy verification plan: confirm bundle filename matches the release build, homepage headline, /for/plumbing demo ribbon, no canonical on demos, 33-URL sitemap, one QA-labeled lead with truthful notified flag

F · Lead-handling verification (real results)

✓ Callback request submitted (preview API, QA-labeled: “QA V4.1 Test — DO NOT CONTACT”)
✓ Backend accepted: 200 {ok: true, lead_id: 3f1126d4-07a8-447b-be99-e049bd0f54aa, notified: false}
✓ Saved: MongoDB leads has exactly 1 record — status “new”, created_at 2026-11-05T19:07:54Z, environment “preview”, page_path /plumbing-marketing
✓ Duplicate prevention: identical resubmit → same lead_id, duplicate: true (no second record)
✓ Notification attempt logged: email_log has 2 rows (booking_owner + booking_ack), status “failed”, error “invalid X-Email-Key” — the failure is audited, not silent; the lead did NOT disappear
✓ Browser flow: BookingForm submitted once on /plumbing-marketing — success state rendered, URL clean of PII; dataLayer events carry lead_id/trade/landing only (no name/phone/email — code-verified; names go to tab-scoped sessionStorage, never router state)
✗ Delivery: still failing — platform-managed email key rejected 401 (external dependency, escalated to Emergent support)

Manual fallback — OWNER-APPROVED (Nov 5, in principle): the full operating procedure — checking schedule, ownership, how new leads are identified, how follow-up is recorded with the existing tools, and the outage contingency protocol — is documented in section I. Email delivery remains broken; this procedure is the temporary bridge until Emergent repairs the key.

G · Regression results

✓ Iteration 31 (V4 baseline): homepage showcase, 7 trade split heroes, 7 immersive demos, ribbon, report-card fallback, MA/Boston untouched, noindex/sitemap checks — 100%
✓ Iteration 32 (V4.1): all 30 CTA labels verified on rendered pages; 0 nav overflows at 320–768 (menu open states included); canonical/noindex/og:url checks on 7 demos + production pages; BookingForm browser submission with success state; 0 console errors after the compile fix
✓ Found & fixed during this run: the plumbing hero refactor had left an unbalanced JSX tag that broke the app — fixed and re-verified (the earlier build PASS predates that refactor; the final release build 5fab712 passes cleanly)
✓ Image library: pages load only referenced assets (homepage ~281 KB, trade heroes 65–112 KB); the 10.6 MB library is never loaded wholesale

H · Final recommendation

Technical PASS · Operational readiness pending one owner confirmation — GO once confirmed.

Every technical gate is green: the five review findings are corrected and verified, the Nov 5 release validation rerun passed all eight categories, SEO/build gates pass and the 33-URL baseline is intact. Lead-handling is managed by the owner-approved manual fallback (section I); email delivery itself remains broken with the known platform-side 401, escalated to Emergent support and kept open.

To complete operational readiness: the owner signs in at /admin with the owner-set credentials and opens Leads — the one verification step that requires the owner's own session (production credentials have been owner-activated since October; the preview admin login is intentionally disabled). Once confirmed, the verdict is GO, subject to the owner's explicit release approval. Nothing deploys automatically.

I · Operational readiness — manual lead monitoring (owner-approved)

Approved in principle by the owner on Nov 5 as a temporary bridge while email delivery is broken. It is not 24/7 monitoring and does not guarantee immediate responses. It uses the existing /admin Leads interface only — no new CRM, no backend changes. These checks distinguish the technical PASS above from operational readiness.

Checking schedule — Boston time

• Monday–Friday: 9:00 AM · 12:00 PM · 3:00 PM · 5:00 PM
• Saturday: 11:00 AM
• Sunday: covered by Monday 9:00 AM catch-up — leads keep saving with their original timestamps
• During active sales outreach, additional checks may be necessary

Ownership

• Primary owner: Maoui — performs the scheduled checks starting now.
• Backup: not yet assigned — this limitation stays visible until a backup is explicitly assigned and verified; until then, missed checks are covered by same-day catch-up.
• Future owner: Nick — intended long-term sales owner, pending his explicit confirmation; no admin access has been created or assumed for him.

Running a check with the existing /admin Leads interface

• Sign in: beraidy.com/admin with the owner credentials (brute-force lockout after 5 failed attempts — wait 15 minutes if triggered).
• New / uncontacted leads: the Leads table is sorted newest-first and every new lead arrives with status “new” — anything still “new” near the top of the table has not been worked yet.
• Timestamps: the Created column shows UTC — subtract 5 hours for Boston time (4 hours during daylight saving).
• Follow-up status (honest limitation): the Status column is display-only — the current admin UI has no edit control. Status changes occur only through the booking webhook (e.g., “meeting booked”) or a direct database edit; day-to-day contact attempts are tracked outside the tool. The admin is a lead inbox, not a CRM.
• Notifications tab: shows every email attempt; while delivery is broken, rows appear as “failed” (401) and this manual check is the safety net.

Contingency protocol — missed check or /admin unavailable

If a scheduled check is missed, perform a catch-up as soon as possible on the same day.
Record the missed check and any resulting follow-up delay.
If /admin is unavailable, immediately report the issue to Emergent Support.
Retry access periodically until service is restored.
Once access returns, review all leads received since the last successful check, prioritizing the oldest uncontacted leads.
Verify that leads continued to be saved — do not assume database persistence during an outage without confirmation.
If lead submission or storage is also affected, treat it as a critical incident and investigate immediately.

Operational verification evidence (Nov 5)

✓ Lead saved through the real API: QA-labeled “QA V4.2 Release Gate — DO NOT CONTACT”, status “new”, created_at 2026-11-05T19:34:35Z (lead_id b7d85bb4…); identical resubmit returned the same lead_id with duplicate: true.
✓ Failed notifications audited, not silent: email_log shows lead_owner + lead_ack rows, status “failed”, provider_status 401 “invalid X-Email-Key”.
✓ Leads API is auth-gated: GET /api/admin/leads without a token → 401; wrong credentials → 401.
✓ The /admin login form renders; the preview admin login is intentionally disabled (production credentials are owner-activated since October).
⚠ Pending owner confirmation: sign in at /admin and open Leads — the authenticated-administrator demonstration only the owner can perform.
✗ Email delivery remains broken (platform-side 401, escalated to Emergent support) — the fallback exists because of this, not instead of fixing it.

After — Electrical trade page hero, full-page desktop screenshot

Seven functioning demo links

Canonical routes /for/<trade> — chrome-free immersive demos with the fixed demo ribbon; noindex, excluded from the sitemap; the seven /for/ links kept working (old prospect report cards for other slugs still work too).

/for/plumbingBlueLine Plumbing & Drain — Bold Emergency
/for/hvacMeridian Comfort Co. — Modern Comfort
/for/roofingSummit & Slate Roofing — Premium Craftsmanship
/for/pestWillow Shield Pest Defense — Clean & Reassuring
/for/garageNorthgate Door Works — Architectural & Product-Led
/for/waterDryLine Restoration — Emergency & Recovery
/for/electricalEdge & Volt Electric — Precision & Technology

Resolution report — the five usability concerns

1. Concept pages rendered beneath the global BerAIdy nav

Severity: Medium — duplicated navigation diluted each concept's immersive design

Resolution: Resolved. Demos moved to the canonical /for/<trade> routes, which render chrome-free (the same treatment the old /for/ pages had). Be rAIdy's identity lives in the fixed demo ribbon instead of a competing nav.

2. Demo call buttons could confuse visitors about who they're calling

Severity: High — trust and conversion risk if a visitor thought they were calling the fictional company

Resolution: Resolved. A fixed demo ribbon sits on every demo page in every scroll position: “The business on this page is fictional. Phone buttons and contact links reach Be rAIdy, not the fictional company.” — with an explicit “Call Be rAIdy” link. Demo pages contain zero forms (grep-verified), so no lead can reach or come from a fictional business.

3. V2 previews trimmed FAQs and consolidated copy — production must keep SEO substance

Severity: High for SEO (300-word prerender gate + content substance)

Resolution: Resolved by not trimming. Production trade pages keep their full body copy and complete FAQ sets (1,226–1,538 words each, 60–72% unique). The preview trims remain preview-only evaluation artifacts.

4. Concept photography hotlinked from Unsplash

Severity: Low–Medium — long-term reliability inside the demo pages only

Resolution: Production pages are already fully self-hosted: the homepage showcase and all seven trade heroes use local optimized WebP captures (public/images/v2/). Demo pages keep licensed Unsplash hotlinks (Unsplash License, commercial use, each photo used once); self-hosting demo photos is optional polish after approval.

5. Per-concept web fonts add weight

Severity: Low — one-time ~40–60 KB per demo, cached afterwards

Resolution: Contained. Nunito Sans / Archivo / Space Grotesk load only inside demo pages. The homepage and trade pages add zero font weight — their showcases are static WebP + system/brand fonts.

Image performance & technical QA

Image performance (measured)

Homepage showcase imagery: ~281 KB total (3 desktop + 3 mobile hero captures, responsive srcset)
Trade-page hero imagery: 65–112 KB per trade (desktop 1440w+864w, mobile 390w+240w)
Image library on disk: 10.6 MB across 60 assets — pages load only what they reference
Iframes: None on the homepage or trade pages (demos open on their own routes)
Layout shift: width/height attributes on every showcase image; below-fold images lazy-load with decoding=async
New font weight on core pages: 0 — homepage and trade pages use existing brand fonts

SEO & conversion regression (yarn build + verify:seo, Nov 5)

✓ Build + prerender PASS; VERIFY:SEO — ALL CHECKS PASSED
✓ Sitemap baseline retained: exactly 33 public URLs (zero demo/preview URLs), robots.txt + llms.txt PASS
✓ Homepage: 1 H1, 1,086 words, Organization/ProfessionalService/WebPage schema
✓ Seven trade pages: 1,226–1,538 words each, full FAQ/Breadcrumb/Service schema, 60–72% unique content
✓ All 301 redirects and SPA fallbacks PASS; no broken routes
✓ Titles, meta descriptions, canonicals and structured data unchanged and passing on all 33 routes
✓ Forms, callback flow, pricing band and loyalty ladder untouched; zero demo forms exist; no database changes
✓ GA4/GTM: consent banner and dataLayer untouched; only additions are site-consistent cta_click events on the new demo links

Exact code files modified

src/App.js — /for/:slug now serves the seven approved concepts behind the demo ribbon; seven duplicate /design/<concept> routes removed; unused VerticalSite import removed
src/pages/Home.jsx — “Built for your trade” section replaced by the approved showcase (headline, 3 featured concepts, 7-trade strip); BuildScene import removed; all other sections untouched
src/pages/TradePage.jsx — Dark gradient hero replaced by the cream split hero (concept capture, phone overlay, “Concept · not a client” badge, fictional note, demo link, phone link); body content unchanged
src/content/showcase.js — NEW — canonical concept map (names, styles, domains, /for/ paths) + the three featured homepage concepts
src/components/v2/DemoRibbon.jsx — NEW — fixed demo trust ribbon on every public demo
src/components/v2/ConceptShowcase.jsx — GA4 cta_click tracking added to demo links (site-consistent vocabulary)
src/pages/design/DesignIndex.jsx, Proposal.jsx — Demo links/frames re-pointed to /for/*
src/pages/v2/V2Compare.jsx, V2Decision.jsx, V2HomePreview.jsx, V2TradePreview.jsx — Demo links re-pointed to /for/*
Untouched — sitemap.xml, robots.txt, llms.txt, scripts/verify_seo.py, all content/pages/*.js copy, MA/Boston landing pages, forms, booking flow, GTM/consent, backend, databases

Production deployment & rollback plan

Deploy (after your approval): press Deploy — the platform ships the built code exactly as verified here. No database or content migration is involved; the 33-URL SEO baseline is unchanged, so live rankings are unaffected by the swap.

Rollback: any checkpoint can be restored with the platform's free Rollback option (or the git history) — code-level only, since V4 touches no data. The replaced dark heroes and the old /for/ concept experience remain in git history if you ever want them back.

Verdict: V4 integration gates: PASS. The V4.2 release verdict (section H): technical PASS — GO pending the owner's /admin sign-in confirmation and explicit release approval.

Report updated Nov 5 (V4.2 release gate) — phases V1–V4.2, test iterations 24–33. Preview-only until you approve deployment.