fix: backticks inside the nginx template literal

The comment I added used backticks around ?v= and no-cache, inside a template literal. That closed the
string early and made the file unparseable — committed and deployed before the typecheck was read.

Caught by tsgo immediately afterwards; officer stayed online because pm2 kept the previous module
loaded, but the next restart would not have come back.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

api/static-site.ts

@@ -246,11 +246,11 @@ const NGINX_CONF = `server {
   }
 
   # Everything a build produces. A year, and immutable — earned, not assumed: every asset the layout
-  # links carries `?v=<build id>`, so a build that changes a file changes its URL, and the HTML that
-  # carries the new URLs is `no-cache` and revalidated on every visit. The two cannot disagree.
+  # links carries a ?v= stamp of the build id, so a build that changes a file changes its URL, and
+  # the HTML carrying the new URLs is no-cache and revalidated every visit. They cannot disagree.
   #
-  # This was seven days for as long as the URLs were bare, which was correct then: a stable name with a
-  # long life means somebody running last week's script against this week's markup.
+  # It was seven days while the URLs were bare, which was correct then: a stable name with a long life
+  # means somebody running last week's script against this week's markup.
   location ~* \\.(css|js|webp|png|jpg|jpeg|gif|svg|ico|mp4)$ {
     expires 1y;
     add_header Cache-Control "public, immutable";