The VectorCraft collection's Card picture field had no folder of its
own, so the editor saved an uploaded picture to public/assets/uploads/
and wrote /assets/uploads/<file> into the page's cover field. The
content schema only accepts a cover under /assets/uploads/<app>/, so
a page saved with such a cover failed the build.
The field now sets media_folder and public_folder to the vectorcraft
folder. scripts/cms-config.test.mjs checks that every collection with a
cover field uploads to the folder the schema accepts, and
npm run test:coverage runs it.
Chrome warns because Safe Browsing lists some craft.wiki pages as phishing, and
the Worker's sign-in page was a bare "Craft Wiki sign-in" title served from an
/api/ path with no branding, no explanation and no security headers. Give it the
wiki's branding, say that the password prompt belongs to discord.com, and send a
CSP with framing, referrer and content-type headers.
Add a script and a daily workflow that report Google's verdict for the domain,
so a listing is noticed without waiting for a browser to show it.
Sveltia labels its buttons after the backend, so the top one read "Sign In with
GitHub" even though it starts this Worker's Discord sign-in, and the lower one
never said which token it wanted. Rewrite both labels while the CMS bundle is
prepared, failing the build if a bundle update drops a label.