Give the other pages somewhere to go, and move the stylesheets under src/main

MARKETING, not decoration — each of these was a page that stopped:

- The HOMEPAGE never mentioned catering. A customer found the page by reading the nav. It now has a
  section with a photo, what the three tables cover, and a button.
- PRODUCTS was a title and a grid. It gets a line saying what it is ("cakes and decorated cookies are
  made to order, so most of what follows started as somebody describing what they wanted") and a closing
  band with somewhere to go — an order, or the catering page.
- CONTACT was a form and nothing else. The things somebody on that page actually wants — when we're open,
  where we are, the phone number — were on the homepage and in the footer but not there. Now beside the
  form, with a card pointing at catering.
- OUR STORY got the shop's own front as a band and an ending, so the story leads somewhere.
- The FOOTER gained the opening hours, which is what people come to a bakery's site for and is now on
  every page.

CLEANED UP ON THE WAY. The hours and the address were about to exist in three places, so they are one
fragment (fragments/visit.html) that takes the classes that vary by where it sits — cream in the footer,
sage on white in a card. A shop that changes its Saturday hours should change them once.

STYLES MOVED to src/main/styles, with the rest of the app's source, and split by what each file is for:
theme.css (the fonts and the palette — names, nothing drawn), base.css (bare elements), components.css
(the site's own classes), admin.css (the admin's controls), and site.css as the entry that imports them in
cascade order and declares what Tailwind scans. It was one grab-bag file called tokens.css in a folder at
the repo root. node_modules has to stay beside them — Tailwind resolves `@import "tailwindcss"` by walking
up from the CSS file — so the whole npm project moved together, and the pom, .gitignore and README moved
with it.

53 tests green, `mvn package` builds the stylesheet from its new home, and every class used on all five
pages resolves in the compiled CSS (185/159/175/148/140, none missing).

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>

src/main/styles/components.css

@@ -0,0 +1,60 @@
+/*
+ * The public site's own classes — the ones that would be unreadable as a string of utilities in every
+ * template that needs them. The admin's controls are in admin.css.
+ */
+
+/* In @layer components, matching the old site. That ordering matters: a utility like `px-4` — which
+   the markup applies alongside `container` on nearly every section — has to win over this, or every
+   gutter on the site silently widens. */
+@layer components {
+  .container {
+    @apply max-w-7xl mx-auto px-4 sm:px-6 lg:px-8;
+  }
+
+  /*
+   * The two branch marks of the wordmark, as masks rather than inline SVG.
+   *
+   * They have to take their colour from the surrounding text — sage in the header, cream on the hero
+   * and in the footer — which an <img> cannot do. React solved that by inlining them through svgr,
+   * but these files are 31 KB each and the lockup appears up to three times on a page: inlining them
+   * in server-rendered HTML would add ~190 KB to every response. A mask over `currentColor` keeps the
+   * tinting, keeps the files cacheable, and costs two requests once.
+   */
+  .mark {
+    background-color: currentColor;
+    -webkit-mask-repeat: no-repeat;
+    mask-repeat: no-repeat;
+    -webkit-mask-position: center;
+    mask-position: center;
+    -webkit-mask-size: contain;
+    mask-size: contain;
+  }
+  .mark-r {
+    -webkit-mask-image: url('/images/logo_R.svg');
+    mask-image: url('/images/logo_R.svg');
+  }
+  .mark-l {
+    -webkit-mask-image: url('/images/logo_L.svg');
+    mask-image: url('/images/logo_L.svg');
+  }
+
+  /*
+   * The photo strip on a product card scrolls, but a scrollbar across the bottom of a photo is not part
+   * of the design. Hiding it is safe here because the strip is not the only way through the photos: it
+   * snaps, it takes arrow keys, and the arrows and dots are on top of it.
+   */
+  .no-scrollbar {
+    scrollbar-width: none;
+  }
+  .no-scrollbar::-webkit-scrollbar {
+    display: none;
+  }
+}
+
+/* The mobile menu is a <details>; its default disclosure triangle would sit next to the hamburger. */
+summary {
+  list-style: none;
+}
+summary::-webkit-details-marker {
+  display: none;
+}