fix: update asset paths and navigation in 404 page

Modified asset links in the 404 page to use absolute paths for consistency and improved navigation. Updated the "Back to Sajilo" link to redirect to the homepage instead of the index page. Enhanced the wrangler configuration to ensure proper handling of specific routes before serving assets, improving error handling for unmatched paths.

Author: adarshaacharya

apps/landing/404.html

@@ -6,14 +6,14 @@
 <title>Page not found: Sajilo</title>
 <meta name="robots" content="noindex">
 
-<link rel="icon" href="assets/favicon.png" type="image/png">
-<link rel="apple-touch-icon" href="assets/apple-touch-icon.png">
+<link rel="icon" href="/assets/favicon.png" type="image/png">
+<link rel="apple-touch-icon" href="/assets/apple-touch-icon.png">
 
 <link rel="preconnect" href="https://fonts.googleapis.com">
 <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
 <link href="https://fonts.googleapis.com/css2?family=Source+Serif+4:opsz,wght@8..60,500;8..60,600;8..60,700&family=Public+Sans:wght@400;500;600;700&display=swap" rel="stylesheet">
 
-<link rel="stylesheet" href="style.css">
+<link rel="stylesheet" href="/style.css">
 <style>
   .not-found {
     min-height: 60vh;
@@ -52,7 +52,7 @@
 <header class="wrap">
   <nav class="nav">
     <div class="brand">
-      <img src="assets/icon.png" alt="">
+      <img src="/assets/icon.png" alt="">
       Sajilo
     </div>
     <a class="github" href="https://github.com/adarshaacharya/sajilo" target="_blank" rel="noopener">
@@ -67,7 +67,7 @@
     <p class="glyph">404</p>
     <h1>This page doesn't exist.</h1>
     <p>The link may be old, or mistyped. The calendar, downloads, and install guide are all back home.</p>
-    <a class="btn-primary" href="index.html">Back to Sajilo</a>
+    <a class="btn-primary" href="/">Back to Sajilo</a>
   </div>
 </main>
 

apps/landing/wrangler.jsonc

@@ -5,7 +5,12 @@
   "assets": {
     "directory": ".",
     "binding": "ASSETS",
-    "not_found_handling": "404-page"
+    "not_found_handling": "404-page",
+    // Assets are served before the Worker runs, so `/dl/…` — which matches no
+    // file — was answered with 404.html and the redirect never happened. These
+    // routes have to reach the Worker first; every other path keeps the
+    // assets-first behaviour.
+    "run_worker_first": ["/dl/*"]
   },
   "d1_databases": [
     {