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/admin.css

@@ -0,0 +1,50 @@
+/*
+ * The admin's controls.
+ *
+ * Component classes rather than utility strings repeated through the markup, because the admin is made
+ * of forms: there are dozens of buttons on a page and each one is its own <form>. The public pages keep
+ * their utilities inline — they each look different — but "a button in the admin" should be one decision
+ * in one place. These are the same buttons the React screen had, from the same class strings it composed.
+ *
+ * @utility, not `.btn { @apply … }` in a components layer: Tailwind v4 will only let you @apply a class
+ * it knows as a utility, and only a registered utility can take a variant — which `file:btn-secondary`
+ * on the photo pickers needs.
+ */
+@utility btn {
+  @apply inline-flex items-center justify-center gap-1.5 rounded-md px-3 py-1.5 text-sm font-medium
+         transition-colors;
+}
+
+@utility btn-primary {
+  @apply btn bg-bakery-600 text-white hover:bg-bakery-700
+         disabled:opacity-40 disabled:cursor-not-allowed;
+}
+
+@utility btn-secondary {
+  @apply btn border border-bakery-300 text-bakery-800 hover:bg-bakery-100
+         disabled:opacity-40 disabled:cursor-not-allowed;
+}
+
+@utility btn-danger {
+  @apply btn text-red-700 hover:bg-red-50 disabled:opacity-40 disabled:cursor-not-allowed;
+}
+
+/* Square, for the arrows and the crosses — a row of these is how anything gets reordered. */
+@utility btn-icon {
+  @apply inline-flex items-center justify-center w-7 h-7 rounded-md border border-bakery-300
+         text-bakery-700 hover:bg-bakery-100 transition-colors
+         disabled:opacity-30 disabled:cursor-not-allowed;
+}
+
+@utility field {
+  @apply w-full rounded-md border border-bakery-300 bg-white px-3 py-2 text-sm
+         focus:border-bakery-500 focus:outline-none focus:ring-1 focus:ring-bakery-500;
+}
+
+@utility card {
+  @apply rounded-lg border border-bakery-200 bg-white p-4 shadow-sm;
+}
+
+@utility card-heading {
+  @apply font-adbhashitha text-xl text-bakery-800;
+}