Capstone: A Complete, Working Flexible-Routing Site

Sam opens the site. Apache's own mod_proxy_http forwards the request to server.js, kept alive under PM2 — the identical mechanism Astro's own capstone already confirmed, reused honestly rather than reinvented.

Sam enters the legacy admin credential. bcryptjs — the same package verified in this series for a third time — checks it against the stored $2y$-tagged hash, and express-session establishes a real session on success.

Through the hand-built admin interface — no free admin, no scaffold generator, matching Astro's own most-minimal finding — Sam creates programming, then general-purpose-languages, then java, then fundamentals, then chapter-1. Each save calls Chapter 2's own computeFullPath helper directly, with no ORM lifecycle hook anywhere in sight.

Visiting the full five-segment path, Chapter 3's /*splat route resolves it with a single raw SQL query, and Chapter 4's EJS partials render the breadcrumb and <%- page.body %> content, styled by Chapter 5's plain, zero-processing stylesheet.

Sam edits the Chapter 1 page's title. Chapter 8's endpoint and Zod validation handle the submission exactly as before — but Chapter 9's requireAuth middleware is now in place, the first genuine "place for an auth check" this course ever had. Logged out, the identical request now returns a 401 instead.

Sam decides fundamentals belongs under a different parent. Chapter 10's movePage updates fundamentals' own path directly, then Chapter 6's own recursive CTE finds every descendant — just chapter-1, here, but genuinely unbounded regardless of how deep the real chain went — in a single query, ordered so one linear pass writes each new path correctly.

Sam tries to delete java, which still has fundamentals beneath it. Chapter 2's ON DELETE RESTRICT constraint refuses the operation, and Chapter 10's try/catch turns the raw database exception into a real, readable 409 response — the same ceremony Laravel's and Astro's own capstones needed, not Rails' smoother built-in path.

Sam visits the kanji page. Chapter 7's resolution holds on every front: routing and rendering were already solved by Chapters 2 and 4, JavaScript's own UTF-16 string model — shared with Next.js and Astro, confirmed a third time — never risked corrupting the character, and the database's own utf8mb4 charset, present in db.js since Chapter 2, stores it correctly with nothing rediscovered along the way.

Sam checks the query log while loading the breadcrumb-heavy Chapter 1 page. Chapter 6's WITH RECURSIVE query resolves the full ancestor chain in one call — genuinely unbounded, the concrete answer to a limitation five separate ORMs in this series each admitted but never actually solved.

Sam confirms PM2 shows server.js running cleanly, with no build artifact anywhere to verify — the last confirmation in a series that has now rebuilt the same real site six separate times.