chore: move to mallok 0.1.0-rc.11, the release with plugin API 2

[JasonYv]

What this is

Mallok published plugin API 2 — the extension points the rest of the shop was waiting for — in 0.1.0-rc.10 and 0.1.0-rc.11. This moves Nundar onto 0.1.0-rc.11 and removes the stand-ins it had for four Mallok behaviours that release answers. It builds nothing on the new API; that is the pull request stacked on this one.

mallok is pinned exactly. rc.11 is under npm's next tag only, and latest is still rc.10, so a range or a tag would not select it.

The five commits

Commit	What it does
chore: move to mallok 0.1.0-rc.11…	The upgrade, through npx mallok upgrade. It changed no code. wrangler.jsonc gains the second rate-limit binding the upgrade notes ask every site for, which mallok upgrade does not add
feat: label the inquiry form in German, French and Spanish	The inquiry plugin now reads its labels from the theme's language pack. The six keys are in the three packs the plugin has no words for, and deliberately not in the default one
refactor: take the tagline from the site's settings, per language	Mallok's tagline holds a value per language now, so the theme option that stood in front of it goes. home_description stays, as an option in its own right
refactor: link to a kind's list page through site.kinds	A template can now ask where a kind's list page is. The catalogue link stops being a theme option, and one breadcrumb partial serves every layout: home, the list of the kind, a product's collection, the page
docs: record what the move … changed and found	The design's new §16: what each extension point became in the release, and what happened to each stand-in

The theme is 0.5.0: two options were removed.

What stays as it was, on purpose

Switching a plugin or changing a setting can still leave cached pages as they were, and the admin's "Clear cached pages" can report success without clearing anything — Mallok's own finding on a deployed site, fixed on a branch and not released. So the plugins are still switched on before the first publish, the README still says so, and the tests still delete the cached home page by hand after changing settings.

How it was verified

Check	Result
npm run lint, npm run typecheck, npm run build	Pass
npm run test:project	48 of 48
npm run test:shop	449 of 449 inside workerd
npm run smoke, npm run smoke:shop, npm run preview -- --check	Pass on a real local Worker; the smoke run now reads each language's tagline from its home page, follows the catalogue link in each, and checks the French label of the inquiry form
Red and green	Seventeen deliberate breakages of the new behaviour, each noticed by the check meant for it
The longer breadcrumb	All 156 pages of the sample at nine widths, 320 to 1440 px: none scrolls sideways, no breadcrumb runs past its box
A kind with no list layout	Checked once by hand, by taking one kind's list layout away: its base address answers 404, in the address's language

Not verified

• Nothing was deployed.
• What the inquiry form's submit route answers with, by language, was not looked at.