>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3588756. --> Reported by: [ajv009](https://www.drupal.org/user/3653917) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>The site-analyzer agent takes source-site screenshots with the cookie/GDPR consent banner covering the content area, producing reference images that show the overlay instead of the actual page sections. Any downstream component-builder agent then receives corrupted reference material from the very first phase.</p> <p>In a recorded session against freelygive.io, every source-site screenshot from Phase 0&ndash;1 was captured with the cookie banner overlay present. The <code>cta-section</code> and <code>site-footer</code> screenshots &mdash; two of only five bundles ever captured &mdash; showed dark navy background with the cookie overlay instead of the section content. The agent saw the banner in its first snapshot (<code>e1: Cookie banner [region]</code>, <code>e2: OK [button]</code>) but had no instruction to dismiss it. An ad-hoc dismiss (<code>agent-browser click @e2</code>) was applied manually mid-session and worked, but the agent definition was never updated &mdash; so the next fresh run repeats the failure.</p> <p>This is not site-specific. Any GDPR-compliant site shows a banner on first visit. The agent has the capability to dismiss it; it lacks the instruction to do so before capturing.</p> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <ol> <li>Run the migrate-site skill against any site with a GDPR consent banner (e.g., freelygive.io).</li> <li>Inspect the generated <code>docs/migration/components/&lt;section&gt;/screenshot-1440.png</code> files for any below-fold section.</li> <li>Observe: screenshots show the consent banner overlay, not the actual section content.</li> <li>Inspect <code>plan.md</code>: no <code>COOKIE_BANNER_DISMISSED</code> log line exists.</li> </ol> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Add a mandatory pre-capture preflight step as STEP 0 in <code>.claude/agents/site-analyzer.md</code>:</p> <pre>STEP 0 &mdash; PRE-CAPTURE PREFLIGHT (mandatory, runs once per page): After page load, before any screenshot: a. Use agent-browser snapshot -i to detect consent banners b. If found (role="dialog" OR text matching "Accept"/"OK"/"Got it"/"Allow all" OR class containing "cookie"/"consent"/"gdpr"): - Click dismiss: agent-browser click @&lt;dismiss_button&gt; - Wait 500ms - Verify banner is gone (re-snapshot, check banner is absent) c. Log: "COOKIE_BANNER_DISMISSED: YES/NO" to plan.md Only after this preflight: proceed with screenshots.</pre><p>This instruction is proven to work in-session via the manual <code>agent-browser click</code> call. The fix is writing it into the agent definition so it runs automatically on every fresh run.</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <ul> <li>Add the STEP 0 PRE-CAPTURE PREFLIGHT block to <code>.claude/agents/site-analyzer.md</code> as the first step in the capture procedure.</li> <li>Add a Phase 0 preflight note to <code>.claude/skills/migrate-site/SKILL.md</code> referencing the banner-dismiss requirement (verify whether already partially present).</li> <li>Verify on a GDPR-banner site: <code>plan.md</code> contains <code>COOKIE_BANNER_DISMISSED: YES</code> for the first page captured.</li> <li>Verify on a site without a banner: agent logs <code>COOKIE_BANNER_DISMISSED: NO</code> and proceeds without error.</li> <li>Verify <code>cta-section/screenshot-1440.png</code> and <code>site-footer/screenshot-1440.png</code> show actual content, not the overlay.</li> </ul> <h3 id="summary-ui-changes">User interface changes</h3> <p>None.</p> <h3 id="summary-api-changes">API changes</h3> <p>None. The <code>agent-browser click</code> command already supports the required dismiss interaction; no new tooling needed.</p> <h3 id="summary-data-model-changes">Data model changes</h3> <p>One new log line in <code>plan.md</code>: <code>COOKIE_BANNER_DISMISSED: YES|NO</code>. Not a structural change &mdash; an additional informational line.</p> <h3 id="summary-internal-references">Internal references</h3> <ul> <li>Source markdown: <code>RESEARCH-2026-04-28/99-final/ISSUES/Sprint-1-Foundations/01-P0-3-cookie-gdpr-banner-never-dismissed.md</code> (id: P0-3)</li> <li>Original deep analysis: <code>RESEARCH-2026-04-28/00-existing-issues/prior-deep-analysis-key-points.md</code> (HIGH finding on cookie banner)</li> <li>Ad-hoc fix evidence: <code>RESEARCH-2026-04-28/06-jamie-demo-old/95q5i-77cf5bb9-half1/user-feedback.md</code> (L3259&ndash;3262)</li> <li>What-was-fixed evidence: <code>RESEARCH-2026-04-28/06-jamie-demo-old/95q5i-77cf5bb9-half2/what-was-fixed-in-second-session.md</code> (PARTIALLY ADDRESSED entry)</li> <li>Recommended verbatim text: <code>RESEARCH-2026-04-28/99-final/migrate-site-skill-recommendations.md</code> (<code>.claude/agents/site-analyzer.md</code> section)</li> <li>Pattern: <code>RESEARCH-2026-04-28/07-cross-cutting/patterns.md</code> &sect; B2 (Acquia WAF Blocks POST &mdash; same theme of agent not handling overlay state)</li> <li>User feedback: <code>RESEARCH-2026-04-28/07-cross-cutting/user-feedback-corpus.md</code> &sect; Group 1 ("Why Are You Stopping?")</li> <li>Anti-pattern: <code>RESEARCH-2026-04-28/07-cross-cutting/session-anti-patterns.md</code> &sect; AP1 (Retry Storm)</li> </ul> <h3 id="summary-open-questions">Open questions</h3> <ul> <li>The user explicitly deferred this in session 77cf5bb9 calling it "a deeper issue" but also said "NOT permanently abandoned." Confirm clearance before implementation.</li> <li>Test target: freelygive.io has the banner naturally, but check if any DDEV-local fixture can be used to avoid external dependencies.</li> </ul>