Skip to content

Session handover — 2026-07-11 (pt2)

Short session: deployed capability-backlog #3 — the FloatingCTA/Social globals — to WCP live, the one held item from priority #1 of session-2026-07-11-handover.md. Detectors 1 & 2 stay reporting-only (no deploy, as intended). Wiki updated + published at /session-end.

What shipped (deployed live this session)

FloatingCTA/Social overlays now serve on wcp.dcathal.org (homepage + /gallery subpage verified; icons resolve, no loud-fail placeholders). This closes the last piece of capability-backlog.md #3 — the CMS-lane silent-drop is now not just build-verified (commit 6bc7a95) but live.

  • No worker rebuild. The floating adapters + Base.astro globals lookup were already in the deployed WCP build (6f2cb2cf); globals are read from D1 at request time. The deploy was a surgical ec_globals append to WCP's site row.
  • Data derived from the live Wix site (build inputs aren't in this checkout, and WCP's last regen was a live re-crawl — not worth repeating for two cosmetic globals): the pinned WhatsApp StylableButton (comp-mi8nzhwv) → fcr.floating-cta (bottom-right, api.whatsapp.com/send?phone=353879830236); facebook+youtube → fcr.floating-social rail (right edge, real URLs — the topbar carried these two platforms with empty URLs, so the floating rail is where the real links live).
  • Graft-divergence check passed — the live site global was byte-identical to the committed seed (same 4 blocks, same keys) → clean/never-edited → safe to append.
  • Full rationale + the reusable deploy path: new known-patterns entry "Deploying a newly-registered site-global is a surgical ec_globals append, not a re-crawl — when the deployed worker already carries the render path".

Wiki changes

  • known-issues.md — deleted the resolved "CMS lane silently drops FloatingCTA / FloatingSocial" entry (its own reopen instruction was "delete once WCP is redeployed"); fixed two now-stale references it left behind (the "still dropped" residual in the unmatched-section entry + the near-match-scorecard entry's dangling "see its own entry" pointer).
  • capability-backlog.md — #3 marked deployed live.
  • known-patterns.md — one new entry (the surgical-globals-append deploy path).
  • apps/cms/seed/waterfordcountypainters.json — reconciled with the two floating globals so a future full reseed can't drop them (seed ↔ live D1 now match).

State

Committed to master this session-end: the seed reconciliation + the three wiki files above + this handover. Live WCP D1 written (ec_globals site row, +2 blocks); no worker redeploy, no page rows touched, no D1 pages touched. Recovery anchor: D1 Time Travel bookmark 00000075-00000008-000050a5-e1e13195c1ae77afe40c2b85d4b0226f (pre-write). Left alone (untracked/unrelated): infra/ (undecided ownership — known-issues), .claude/settings.local.json, scripts/.tmp/, apps/cms/scripts/.tmp/.

Next session (priority order)

  1. Capability backlog #2 — header/logo layout + bring globals into the scorecard (capability-backlog.md). Highest-leverage build item: globals are "FULLY BLIND" today (junk-filtered out of every scorecard axis), and this session's deploy is the template for the next held-globals capability. Asset-source-agnostic; no live infra.
  2. Capability backlog #1/#4/#6 — hero carousel+video variant (has an asset half → Slice 5), video gallery, matcher precision (only against built FCR sites — matcher tuning scope).
  3. Slice 6 calibration — wire both detector vetoes into the gate + fit thresholds on the 30–50-site batch; promote hero-variant/scrim/textTone to scored DIMS then (lib/calibration.json still fitted:false).