n-seo 0.4.0 → 0.4.1

package/CHANGELOG.md

@@ -8,6 +8,19 @@ uses [Semantic Versioning](https://semver.org/).
 
 Nothing yet.
 
+## [0.4.1] - 2026-09-13
+
+### Added
+- **Every page says which engine built it.** The footer now carries
+  `n-seo <version>`, and when a newer one is published it carries the upgrade
+  command and a link to the release notes beside it. This matters most on a
+  published mirror: `/settings` is deliberately not exported, because it shows
+  local paths and the service-account email, so before this a mirror named no
+  version anywhere. The notice is baked in at export time from the file the
+  daily run writes — polling the registry from the browser would put every
+  viewer of a shared mirror onto npmjs.com on every page view, to learn
+  something that changes once a day.
+
 ## [0.4.0] - 2026-09-12
 
 Upgrading used to be something you found out about by accident. This release
@@ -388,7 +401,8 @@ First public release.
   `n-seo upgrade` gate — without changing the reported test counts, and an
   in-place install ran those assertions against the owner's live data.
 
-[Unreleased]: https://github.com/en-dash-consulting/n-seo/compare/v0.4.0...HEAD
+[Unreleased]: https://github.com/en-dash-consulting/n-seo/compare/v0.4.1...HEAD
+[0.4.1]: https://github.com/en-dash-consulting/n-seo/compare/v0.4.0...v0.4.1
 [0.4.0]: https://github.com/en-dash-consulting/n-seo/compare/v0.3.3...v0.4.0
 [0.3.3]: https://github.com/en-dash-consulting/n-seo/compare/v0.3.2...v0.3.3
 [0.3.2]: https://github.com/en-dash-consulting/n-seo/compare/v0.3.1...v0.3.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "n-seo",
-  "version": "0.4.0",
+  "version": "0.4.1",
   "description": "Agentic, local-first SEO / AEO / GEO control plane: pulls Search Console + GA4, probes your sites, and ranks the next moves. Your LLM writes the proposals; your coding agent works the queue over MCP.",
   "license": "MIT",
   "author": "En Dash Consulting (https://endash.us)",

package/public/styles.css

@@ -191,6 +191,10 @@ td.trunc { max-width: 380px; overflow: hidden; text-overflow: ellipsis; white-sp
 .flash { background: var(--good-soft); color: var(--good); font-weight: 600; font-size: 0.85rem; padding: 8px 14px; border-radius: 8px; }
 
 footer { max-width: 1480px; margin: 0 auto; padding: 16px 24px 40px; color: var(--muted); font-size: 0.75rem; border-top: 1px solid var(--line); }
+footer .foot-ver { font-weight: 600; color: var(--ink); }
+footer .foot-upd { background: var(--warn-soft); color: var(--warn); border-radius: 5px; padding: 1px 7px; font-weight: 600; }
+footer .foot-upd code { background: rgba(0,0,0,0.06); color: inherit; }
+footer .foot-upd a { color: inherit; text-decoration: underline; }
 
 /* ---- buttons + inline forms ---- */
 .btn {

package/src/views.tsx

@@ -1,6 +1,6 @@
 /** Server-rendered views (hono/jsx). */
 import type { FC, PropsWithChildren } from "hono/jsx";
-import { SITES, config, loadConfig, USING_EXAMPLE_CONFIG, type SiteCfg } from "./config.js";
+import { SITES, ENGINE_VERSION, config, loadConfig, USING_EXAMPLE_CONFIG, type SiteCfg } from "./config.js";
 import * as data from "./data.js";
 import { actionsFor, allActions, type Action } from "./actions.js";
 import { insights as loadInsights } from "./insights.js";
@@ -35,6 +35,7 @@ export const Layout: FC<PropsWithChildren<{ title: string; active: string }>> =
   loadConfig(); // refresh USING_EXAMPLE_CONFIG
   const cfg = config();
   const sites = cfg.sites;
+  const upd = data.updateCheck();
   return (
     <html lang="en">
       <head>
@@ -87,7 +88,26 @@ export const Layout: FC<PropsWithChildren<{ title: string; active: string }>> =
         )}
         <main>{children}</main>
         <footer>
-          Local controller · refreshed by <code>ops/daily.py</code> · queue in <code>config/backlog.json</code> · nothing here posts or publishes for you
+          {/* Which engine produced this page. On the static mirror that is
+              the only place it appears — /settings is not exported, because
+              it shows local paths and the service-account email — so without
+              this a published mirror named no version at all.
+
+              The update notice is baked in at export time from the file the
+              daily run writes. Polling the registry from the browser instead
+              would put every viewer of a shared mirror onto npmjs.com on
+              every page view, to learn something that changes once a day. */}
+          <span class="foot-ver">n-seo {ENGINE_VERSION}</span>
+          {upd?.newer && (
+            <>
+              {" "}
+              <span class="foot-upd">
+                {upd.latest} available — upgrade with <code>n-seo upgrade</code>
+                {upd.notes && <> · <a href={upd.notes} target="_blank" rel="noopener noreferrer">what changed</a></>}
+              </span>
+            </>
+          )}
+          {" · "}refreshed by <code>ops/daily.py</code> · queue in <code>config/backlog.json</code> · nothing here posts or publishes for you
         </footer>
         <script dangerouslySetInnerHTML={{ __html: `document.addEventListener('click',function(e){var d=e.target.closest('dialog');if(d&&e.target===d)d.close();});` }} />
       </body>