Updated: Require sevenx-themes-media 1.5.61, whose header has a user menu and whose header search fits a phone

The media design's header gets a user button beside the search. Its menu leads to sign in,
registration, the basket, the sitemap and the tag cloud, or, signed in, to the user's own pages, the
administration and sign out, each only where the user's policies allow it. The header search becomes a
button, and on phones its open form spans the header below the bar instead of running off the left edge
of the screen. The manifest carries the new checksums of composer.json and the changelog.

Updated: Require ezupdate 1.1.18, whose page header no longer warns that error and message are already defined

Every ezupdate page wrote "Variable 'error' is already defined" and "Variable 'message' is already defined"
into the warning log: the views pass both to the header, also when they have none. 1.1.18 reads them through
first_set() into variables of its own. The file manifest carries the new checksum of composer.json.

Updated: The file manifest carries the checksums of composer.json and the 6.0.15 changelog

Updated: explayouts is required at ~1.4.29, whose admininterface.ini.append.php is a valid settings file again

explayouts 1.4.28 put a comment naming translations/*/translation.ts into settings/admininterface.ini.append.php;
its */ closed the PHP comment that wraps the file, so the settings parsers read a broken file and
expIniRoundTripTest failed. 1.4.29 says the same in words.

Updated: The file manifest carries the checksums of the catalogues, the translator and its test, the templates and settings of the German administration wave, composer.json and the changelog

Updated: explayouts is required at ~1.4.28 and xrowextract at ~2.5.14, whose tabs and preset summaries are translated

explayouts 1.4.28 names the translation context of the node view's Layouts and Authors tabs ("Autoren" in German);
xrowextract 2.5.14 translates the one-line summary of a preset on the CSV and schedule pages.

Updated: The German administration is German below the header; an empty placeholder no longer replaces a translation

Extension catalogues are read after the kernel's, and some carry copies of kernel contexts whose messages are empty
placeholders. The translator took an empty translation for the English source, so ezstarrating's copy of
kernel/content turned "Top Level Nodes" at the top of the content tree back into English. A message with an empty
translation now keeps the translation read before it; a later message with a translation still replaces it. A test
covers both.

The administration asked for messages the catalogues did not have, each one English on the page and a missing
translation in the debug output: the content job pages, the template view's override messages, the RAD page's
content policy limitation and cronjob part filter, the workflow event statuses, the SVG upload error, the content
finder and package messages, the AdminAid and eZFind navigation parts, the audit console's labels (content finder,
sessions, deactivated users, API keys, paused cronjob parts, removed packages) and the setup wizard's editor
siteaccess texts. Translations that were still English or unfinished are German: Extensions, Sessions and PDF export
in the Setup menu, the package list's repositories, the user and status IDs, the RAD descriptions of datatypes and
template operators, the active extensions cache ("Erweitungen") and the AJAX uploader, wishlist, OAuth admin and
search messages. eng-US and untranslated carry every new message.

- Setup > Cache management translates the names of the caches extensions declare in site.ini in kernel/cache, as it
  does the kernel's own
- the RAD page translates the labels of the survey counts once, in expRADSurvey::groupCounts(); the template no longer
  translates them a second time
- an additional node view tab can name the context of its Title and Description with TranslationContext=
  (admininterface.ini); without it they are shown as written
- the dashboard's maintenance block reads "for more information", in the template and in every catalogue's source

All catalogues validate against ts.rng and hold each message once.