>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3614034. --> Reported by: [mably](https://www.drupal.org/user/3375160) Related to !114 >>> <p>An audit of every change on 1.x since the 1.0.0-alpha1 tag found the code release-ready: CI is green per job, the queue holds no open bugs, and the tree carries no stray todo markers. What is behind is the shipping metadata, which is what a first impression of an alpha is made of. This issue bundles all of it so the tag can be cut from one merge.</p> <p><strong>1. The French translation has fallen behind.</strong> 54 strings have no entry in <code>translations/yoyaku.fr.po</code>: 18 from code and 36 from YAML, the latter down to 61% coverage because four submodules arrived with untranslated names, descriptions and permission labels. Visible gaps include the <code>Cancel booking orders</code> permission and its description, plus the <code>Areas</code>, <code>Schedule</code>, <code>Scope</code>, <code>View</code> and <code>Workflow settings</code> labels. Separately the file carries five duplicate msgids, and one of them, <code>Booker</code>, has two different translations, so which one the importer applies is arbitrary.</p> <p><strong>2. The cart module ships undocumented.</strong> <code>yoyaku_cart</code> is a user-facing module every booking surface routes through, and it appears in no module table, no documentation page and no navigation entry. The README module table is also missing <code>yoyaku_placement</code>, and the architecture module map is missing <code>yoyaku_cart</code>, <code>yoyaku_placement</code> and <code>yoyaku_ticket</code>.</p> <p><strong>3. The pricing seam is undocumented.</strong> <code>hook_yoyaku_summary_alter()</code> is what fills every ticket price and the order total, so it is the seam any pricing or payment integration needs. It is implemented, invoked and tested, but absent from <code>yoyaku.api.php</code>, which documents its two lesser siblings. An integrator reading the API file concludes it does not exist.</p> <p><strong>4. The ticket libraries fail at runtime, not at install.</strong> <code>yoyaku_ticket</code> needs <code>dompdf/dompdf</code> and <code>endroid/qr-code</code>. Both are declared under <code>suggest</code>, since requiring them in the single root composer.json would pull a PDF stack onto every Yoyaku site. Both call sites guard correctly, but the module has no requirements check of any kind, so a site installs it, configures ticketing, and discovers the gap only when a customer's confirmation mail tries to attach a ticket.</p> <p><strong>5. The metrics page is stale.</strong> <code>docs/metrics.md</code> presents itself as a measured snapshot but states figures from a much earlier commit, so every chart, ratio and percentage on it is wrong. A page whose whole value is that the numbers are real is worse than no page when they are not.</p> <p><strong>Proposed resolution</strong></p> <ul> <li>Translate the 54 missing strings, following the terminology already established in the file, and refresh the revision date.</li> <li>Remove the five duplicate msgids, keeping the dominant translation, and standardize <code>Booker</code> on the form every compound term already uses.</li> <li>Add a Cart documentation page and a navigation entry, and bring the README table and the architecture module map back in sync with the shipped modules.</li> <li>Document <code>hook_yoyaku_summary_alter()</code> with its array shape and the rule that the core never prices.</li> <li>Add an install requirement that blocks installation when the QR library is absent and warns when the bundled PDF renderer is, plus a runtime requirement naming the usable renderers on the status report, with kernel coverage.</li> <li>Regenerate <code>docs/metrics.md</code> with the bundled generator script.</li> </ul> <p>Two items from the same audit are deliberately left out, since neither is release blocking and both deserve their own issue: there is no FunctionalJavascript coverage over the place map and calendar JavaScript, and <code>VenueMapBuilder</code> loads every place of a venue uncached inside a form, which is the one unbounded hot path.</p>