>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3588760. --> Reported by: [ajv009](https://www.drupal.org/user/3653917) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>Post-Phase gate prompts report only new artifacts created in the phase, omitting existing components, total discovered sections, and coverage ratios. The user cannot assess migration health at any checkpoint.</p> <p>In a recorded session, the post-Phase-3.5 gate prompt listed "Atoms (0): none / Molecules (0): none / Organisms (5): blog-grid, cta-section, hero-section, site-footer, site-header." The user reasonably concluded that only 5 components exist for the entire site. The gate never mentioned: the 25 pre-existing components already in <code>src/components/</code>, the 28 discovered sections across 8 pages, the 11 identified gaps from Phase 2 audit, or how the 5 bundled organisms map to the 28 sections. Coverage was actually 5 new bundles + 25 existing = 30 total against 28 sections &mdash; but the user was shown "5 organisms" with no denominator.</p> <p>Additionally, <code>phase1-summary.json</code> wrote <code>page_count: 0</code> even though 8 pages existed, and the artifact-checker passed without detecting this silent data corruption. Gates pass on metadata presence, not metadata validity.</p> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <ol> <li>Run the migrate-site skill against any multi-page site.</li> <li>At Phase 1 and Phase 3.5 gates, read the prompt shown to the user.</li> <li>Observe: only "new artifacts in this phase" are listed; no totals, ratios, or denominators.</li> <li>Open <code>docs/migration/workflow/phase1-summary.json</code>: <code>page_count</code> may be 0 even when pages were discovered. The artifact-checker accepted this.</li> </ol> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Rewrite the post-Phase-1 and post-Phase-3.5 gate templates in <code>SKILL.md</code> to include cumulative metrics:</p> <pre>PHASE 1 GATE SUMMARY: - Total pages discovered: N - Total sections found: M (across N pages) - Total existing components in src/components/: X - New component bundles captured: Y - New sections with bundle: A - Extend sections with bundle: B - Reuse-unchanged sections (no bundle needed): C - Gaps remaining: D new + E extend + F global CSS - Coverage estimate: (X + Y) components available for M sections PHASE 3.5 GATE SUMMARY: - Components available: X existing + N newly built = X+N total - Sections covered: M of T total sections have a mapped component - Coverage ratio: M/T = P% - Still unmapped: list specific section names - Issues found in QA: K issues filed</pre><p>Add artifact-checker validation rules: <code>page_count</code> in <code>phase1-summary.json</code> must equal the actual page count from <code>plan.md</code>; <code>bundle_count</code> must equal directory count in <code>docs/migration/components/</code>; any zero-value field must be flagged as potential corruption and halt the gate.</p> <p>If <code>phase1-summary.json</code> has wrong values: add "run finalize script before artifact-checker" as a mandatory pre-gate step.</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <ul> <li>Rewrite Phase 1 and Phase 3.5 gate templates in <code>SKILL.md</code> with the cumulative metrics shown above.</li> <li>Add artifact-checker validation rules for <code>phase1-summary.json</code> field values.</li> <li>Determine whether gate prompts are generated by SKILL.md text or by a script &mdash; fix the right surface.</li> <li>Verify on a run: gate prompt includes all six cumulative metrics for Phase 1 and the coverage ratio for Phase 3.5.</li> <li>Verify <code>page_count: 0</code> bug is detected: artifact-checker fails the gate when the field disagrees with the page inventory.</li> <li><strong>Optional addition (per scope-update note):</strong> append a "Scope coverage" row populated by the verify-scopes preflight (1-08) &mdash; listing capabilities available via API vs. browser-fallback.</li> </ul> <h3 id="summary-ui-changes">User interface changes</h3> <p>None (this is the gate prompt text shown in the assistant's turn output).</p> <h3 id="summary-api-changes">API changes</h3> <p>None.</p> <h3 id="summary-data-model-changes">Data model changes</h3> <p>New required fields in Phase summary JSONs: cumulative metrics (existing component count, total section count, coverage ratio). New artifact-checker validity-check rules.</p> <h3 id="summary-internal-references">Internal references</h3> <ul> <li>Source markdown: <code>RESEARCH-2026-04-28/99-final/ISSUES/Sprint-1-Foundations/05-P0-7-gate-summaries-mislead-user.md</code> (id: P0-7)</li> <li>HIGH finding + verbatim "should-say" template: <code>RESEARCH-2026-04-28/00-existing-issues/prior-deep-analysis-key-points.md</code></li> <li><code>page_count: 0</code> evidence: <code>RESEARCH-2026-04-28/06-jamie-demo-old/95q5i-77cf5bb9-half1/issues-found.md</code> (I2)</li> <li>Theme analysis: <code>RESEARCH-2026-04-28/00-existing-issues/issue-themes.md</code> (Theme 2)</li> <li>Scope-coverage extension: <code>RESEARCH-2026-04-28/99-final/SCOPE-REFERENCE-2026-05-01.md</code> &sect; "MEDIUM impact"</li> <li>Pattern: <code>RESEARCH-2026-04-28/07-cross-cutting/patterns.md</code> &sect; A1</li> <li>Anti-pattern: <code>RESEARCH-2026-04-28/07-cross-cutting/session-anti-patterns.md</code> &sect; AP2</li> </ul> <h3 id="summary-open-questions">Open questions</h3> <ul> <li>Where is the gate prompt currently generated &mdash; SKILL.md template the orchestrator fills in, or <code>artifact-checker.md</code> agent that queries the filesystem? Determines fix location.</li> <li><code>phase1-summary.json</code> zero-count: is this a finalize-script bug (writes 0) or an artifact-checker bug (doesn't validate before passing)? Both need fixing but the root differs.</li> <li>How are existing components counted? Tracked in plan artifacts, or does artifact-checker need a new filesystem query?</li> <li>Should the scope-coverage summary appear in every gate or only Phase 8? Depends on per-phase scope-probing cost.</li> </ul>