>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3588768. --> Reported by: [ajv009](https://www.drupal.org/user/3653917) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>Phase 6 of the migrate-site skill uses two LLM-driven agents (menu-builder, site-configurator) for tasks that have zero ambiguity. Site name comes from <code>plan.md</code>. Menu structure comes from <code>content/*.md</code> or <code>pages/&lt;slug&gt;/index.json</code>. Logo URL comes from <code>media-map.md</code>. These are read operations followed by a fixed sequence of browser form fills and clicks. No LLM judgment is needed or beneficial at any step &mdash; the LLM adds inference cost, hallucination risk, and compaction-knowledge-loss exposure without adding value.</p> <p>Recorded cost: Phase 6 in two combined sessions consumed 88 minutes (17 min actual work + 64 min idle from menu-builder auth misdiagnosis + 7 min debugging). A deterministic script would complete the same work in under 5 minutes. The user explicitly stated the design principle: "Menu creation, site configuration and such are all deterministic flows, should be easily handled with browser automation in bulk."</p> <p>The original design used LLM agents because the exact form field names, URL paths, and button selectors on the Acquia admin UI were unknown at design time. Those are now documented (e.g., site config lives at <code>/admin/config/system/site-settings</code>, NOT <code>/admin/config/system/site-information</code> &mdash; the latter returns 403). Browser automation is now scripted-friendly.</p> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <ol> <li>Run the migrate-site skill against an Acquia Source instance.</li> <li>Reach Phase 6. Observe the orchestrator dispatching the LLM-driven menu-builder and site-configurator agents.</li> <li>Observe the agents performing fixed form fills based on data already present in <code>plan.md</code>, <code>media-map.md</code>, and content manifests &mdash; no LLM inference is required for any field.</li> <li>Observe (separately) the cost: ~88 minutes wall-clock for a task that pure scripting completes in &lt; 5 minutes.</li> </ol> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p><strong>Step 1 &mdash; Audit script inputs.</strong> Confirm the artifacts that contain each input: site name (from <code>plan.md</code>), menu structure (likely <code>content/&lt;slug&gt;.md</code>, <code>pages/&lt;slug&gt;/index.json</code>, or a dedicated <code>menus.json</code>), logo MID (from <code>media-map.md</code>), front page (from <code>plan.md</code>). Document the exact field-by-field mapping before writing the script.</p> <p><strong>Step 2 &mdash; Write <code>scripts/create-menus.sh</code>.</strong> Pseudocode:</p> <pre>#!/usr/bin/env bash # create-menus.sh &mdash; deterministic menu creation for Acquia Source migration set -euo pipefail MENUS_FILE="${1:-docs/migration/plan.md}" CMS_URL="${CANVAS_SITE_URL:-}" # For each menu (main, footer): # For each item (title, url, parent, weight): # 1. agent-browser open "$CMS_URL/admin/structure/menu/manage/$MENU_NAME/add" # 2. agent-browser fill @title "$ITEM_TITLE" # 3. agent-browser fill @link-uri "$ITEM_URL" # 4. (if has parent): agent-browser select @parent "$PARENT_TITLE" # 5. agent-browser click @save # 6. Check redirect URL: # - contains "/item/" and "/edit" &rarr; SUCCESS, log "Menu item saved: $ITEM_TITLE" # - contains "source.acquia.com" or "id.acquia.com" &rarr; WAF block, retry up to 4x # - after 4x WAF retry: append to blocked.md, continue to next item</pre><p><strong>Step 3 &mdash; Write <code>scripts/configure-site.sh</code>.</strong> Pseudocode:</p> <pre>#!/usr/bin/env bash # configure-site.sh &mdash; deterministic site config for Acquia Source migration SITE_NAME=$(grep "site_name:" docs/migration/plan.md | head -1 | cut -d: -f2 | xargs) LOGO_MID=$(grep "logo:" docs/migration/media-map.md | head -1 | awk '{print $2}') # Use /admin/config/system/site-settings (NOT site-information &mdash; 403) agent-browser open "$CMS_URL/admin/config/system/site-settings" agent-browser fill @site-name "$SITE_NAME" # ... front page field, logo upload, etc. agent-browser click @save</pre><p><strong>Step 4 &mdash; Update SKILL.md Phase 6:</strong> call these scripts in place of dispatching the LLM subagents. Keep the LLM agents as documented fallbacks for complex cases that cannot be scripted, but default to the scripts.</p> <p><strong>Step 5 &mdash; Add reusable helper <code>scripts/acquia-browser-helpers.sh</code>:</strong></p> <pre>acquia_form_submit() { local url="$1" max_retries=4 attempt=0 while [ $attempt -lt $max_retries ]; do agent-browser open "$url" # ... fill form fields agent-browser click @save REDIRECT_URL=$(agent-browser current-url) if [[ "$REDIRECT_URL" == *"/item/"* &amp;&amp; "$REDIRECT_URL" == *"/edit"* ]]; then echo "SUCCESS: $REDIRECT_URL"; return 0 elif [[ "$REDIRECT_URL" == *"source.acquia.com"* || "$REDIRECT_URL" == *"id.acquia.com"* ]]; then echo "WAF block (attempt $((attempt+1))/$max_retries), retrying..." ((attempt++)) else echo "Unknown redirect: $REDIRECT_URL"; return 1 fi done echo "BLOCKED after $max_retries attempts" &gt;&gt; docs/migration/workflow/blocked.md return 1 }</pre><p>Empirical note (probed 2026-05-01): an API-first variant using <code>menu:administer</code> + <code>site_settings:administer</code> scopes was speculatively considered but is currently blocked. Both scopes mint OAuth tokens, but neither has a JSON:API write endpoint on the current Acquia Source release. The browser-automation script design above remains the primary implementation. Re-evaluate when those endpoints land (see 2-05 and 2-06).</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <ul> <li>Audit migration artifacts to confirm exact field-by-field input mapping for each script.</li> <li>Create <code>scripts/create-menus.sh</code> (executable) and <code>scripts/configure-site.sh</code> (executable).</li> <li>Create <code>scripts/acquia-browser-helpers.sh</code> with the WAF-vs-Drupal redirect distinction reusable function.</li> <li>Update <code>.claude/skills/migrate-site/SKILL.md</code> Phase 6 to call the scripts; retire or downgrade the LLM agents to fallbacks.</li> <li>Verify against a staging Acquia instance: all menu items created in &lt; 5 minutes; simulated WAF blocks retry up to 4x and write <code>blocked.md</code>; Drupal success redirects are correctly recognized.</li> <li>Verify Phase 6 total wall-clock drops from ~88 min to &lt; 10 min on a clean run.</li> </ul> <h3 id="summary-ui-changes">User interface changes</h3> <p>None.</p> <h3 id="summary-api-changes">API changes</h3> <p>None. Scripts use existing <code>agent-browser</code> commands and the same Drupal admin endpoints the LLM agents currently use.</p> <h3 id="summary-data-model-changes">Data model changes</h3> <p>New skill artifacts: <code>scripts/create-menus.sh</code>, <code>scripts/configure-site.sh</code>, <code>scripts/acquia-browser-helpers.sh</code>.</p> <h3 id="summary-internal-references">Internal references</h3> <ul> <li>Source markdown: <code>RESEARCH-2026-04-28/99-final/ISSUES/Sprint-2-Determinism/02-P1-9-menu-site-config-should-be-deterministic.md</code> (id: P1-9)</li> <li>User design principle: <code>RESEARCH-2026-04-28/00-existing-issues/unsorted-issues.md</code> (Thread 2)</li> <li>efi-ed vs freelygive-ai contrast (config endpoint paths): <code>RESEARCH-2026-04-28/05-freelygive-ai/patterns-vs-efi-ed.md</code></li> <li>Recommended verbatim text: <code>RESEARCH-2026-04-28/99-final/migrate-site-skill-recommendations.md</code> ("Skills/Agents to Retire" section)</li> <li>Pattern: <code>RESEARCH-2026-04-28/07-cross-cutting/patterns.md</code> &sect; B2 (WAF vs success redirect distinction)</li> <li>Anti-pattern: <code>RESEARCH-2026-04-28/07-cross-cutting/session-anti-patterns.md</code> &sect; AP1 (Retry Storm &mdash; explicit 4x cap prevents the dispatch storm)</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>Empirical probe (API-first variant blocked): <code>RESEARCH-2026-04-28/99-final/SCOPE-PROBE-FINDINGS-2026-05-01.md</code> &sect; "Affected issues &mdash; UNCHANGED but with new context" (P1-9 row)</li> </ul> <h3 id="summary-open-questions">Open questions</h3> <ul> <li>The user said "all deterministic flows, should be easily handled with browser automation in bulk" &mdash; does "in bulk" mean batched/parallel form submits, or just "all menus in one pass without manual intervention"? Affects script architecture.</li> <li>What is the exact source format for menu data? <code>content/&lt;slug&gt;.md</code>, <code>pages/&lt;slug&gt;/index.json</code>, <code>plan.md</code>, or a dedicated <code>menus.json</code>? Read actual artifacts before writing the script.</li> <li>Does the <code>agent-browser</code> CLI support a <code>current-url</code> query after a form submit, or does the script need to use snapshot + URL extraction?</li> <li>Does efi-ed's <code>ddev drush config:set</code> approach offer reusable lessons for the Acquia Source case? Same configs (site name, logo, front page); different transport (Drush vs browser form).</li> </ul>