>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3578075. --> Reported by: [littlepixiez](https://www.drupal.org/user/2568718) Related to !5 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>After a DrupalPod build, QA needs an easy way to confirm what was actually installed without checking shell logs or repository state manually.</p> <p>Key information like the AI target, checked-out branch/tag, Composer version, and commit should be visible in Drupal itself.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <ol> <li>Add a small DrupalPod module that reads build metadata generated during the init workflow</li> <li>Show that metadata on <code>/admin/reports/status</code> in a dedicated DrupalPod section</li> <li>Format module version information so it is easy for QA to verify at a glance</li> </ol> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <ul> <li>[x] Create DrupalPod status report module</li> <li>[x] Export build metadata during init</li> <li>[x] Display build details in the status report</li> <li>[x] Show module versions in a compact, QA-friendly format</li> </ul> <h3 id="summary-api-changes">API changes</h3> <p>None.</p> <h3 id="summary-data-model-changes">Data model changes</h3> <p>None. A generated JSON metadata file is used during runtime.</p>