>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3618713. --> Reported by: [mably](https://www.drupal.org/user/3375160) Related to !77 >>> <p>A documentation sweep before alpha8 is tagged. Five findings, all documentation-shaped, no runtime code touched.</p> <h3>1. CHANGELOG stops at alpha7</h3> <p>Nothing is recorded for Drupal 12 compatibility, PHPStan level 3, the pre-alpha8 audit fixes, or the explicit transaction commits, in a file that claims Keep a Changelog. An alpha8 entry is added covering all of it, including a Security note for the ephemeral-key wipe fix and a Known limitation section for the one thing a Drupal 12 user needs to know.</p> <h3>2. Three places still say Drupal 11</h3> <p>docs/index.md, docs/installation.md and README.md each state a Drupal 11 requirement, while the root module and all eleven submodules declare ^11.3 || ^12. All three now say Drupal 11.3 or Drupal 12.</p> <h3>3. README claims there is no release</h3> <p>"No tagged release yet" has been wrong since alpha1. It now points at the project page rather than naming a version, which would go stale again on the next tag.</p> <h3>4. .gitlab-ci.yml describes a trait that no longer exists</h3> <p>Four comment blocks still explain that tests skip themselves on Drupal 12 through DependencyWithoutDrupal12Trait and tell the reader to grep for skipWithoutDrupal12(). Both were deleted when the last of the dependency patches landed, and nothing skips any more. The patches block also described only the consumers patch, when five webform ones now sit beside it.</p> <h3>5. The metrics snapshot is two months old</h3> <p>docs/metrics.md was measured on 2026-07-02, before PHPStan level 3 touched 32 classes and before the Drupal 12 work. Every cloc-derived figure had drifted: 378 files to 380, 28,199 lines of code to 28,668, and every language and submodule row with them. The four charts built from those numbers are regenerated with them. Its test-suite and architecture-surface sections were re-counted and are unchanged, so they are left alone: 76 test classes, 429 methods, 52 services, 61 routes.</p> <h3>Verified clean, so the next audit can start here</h3> <ul> <li>phpcs over the module root with Drupal and DrupalPractice: zero findings.</li> <li>cspell over the changed files: six unknown words, all already in .cspell-project-words.txt, so nothing to add.</li> <li>Translations: zero untranslated msgids across all ten .po files.</li> <li>Version constraints: 11 submodules plus the root all at ^11.3 || ^12, composer.json agreeing.</li> <li>No leftover empty directories and no remaining reference to the deleted trait.</li> </ul> <p>Note that PHPStan reports seven errors locally, all Drupal\message\MessageInterface in DormancyMessageTest, purely because drupal/message is a dev dependency that need not be installed. CI installs it and the job is green; this is not a finding.</p> <h3>Decisions recorded here so nobody has to re-derive them</h3> <ul> <li>The CHANGELOG gains a Security heading, which this file has not used before, for the ephemeral-key wipe. Keep a Changelog defines it, and that fix reads as routine under Fixed when it is not.</li> <li>It also gains a Known limitation section, which is not a standard Keep a Changelog heading. Announcing Drupal 12 support without saying that pdv_webform needs a Webform release that does not exist yet would mislead anyone using that submodule.</li> <li>No generator script is added for the metrics page. What a refresh actually needs is the chart geometry, so that is written into the Methodology section instead: the bar origins, the scaling constants and the row pitch. Four lines of prose rather than a tool to keep working.</li> </ul> <p>Two things the regeneration itself turned up, both fixed here. The page counts its own Markdown, so writing it changes the numbers it just wrote; it has to be run to a fixed point rather than once. And the generated submodule table ran straight into the Test suite heading with no blank line between them, which Markdown needs.</p> <p>AI-Generated: Yes (Claude Code was used to help draft this issue summary and to write the changes on the merge request. I reviewed both. The findings come from running the linters and cloc against the branch; there is no behaviour change here to test.)</p>