@hanzo/design 0.5.6 → 0.5.7

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hanzo/design",
-  "version": "0.5.6",
+  "version": "0.5.7",
   "packageManager": "pnpm@11.17.0",
   "description": "Hanzo Design System \u2014 monochrome, dark-default tokens + components + brand assets, the single source of truth for every Hanzo surface. CSS + typed programmatic tokens.",
   "license": "MIT OR Apache-2.0",

package/scripts/lint.mjs

@@ -106,9 +106,16 @@ function lintUnresolved(rel, src) {
   }
 }
 
+/** A build product says so at the top, and there is no point telling anyone to
+ *  fix it — the fix belongs in the generator. Every convention in use is
+ *  accepted, and only the head of the file is read, so a file that merely
+ *  MENTIONS the phrase is still linted. */
+const GENERATED = /@generated|AUTO-?GENERATED|DO NOT EDIT|Generated by|autogenerated/i
+
 function lintFile(abs, root) {
   const rel = relative(root, abs).split(sep).join('/')
   const raw = readFileSync(abs, 'utf8')
+  if (GENERATED.test(raw.slice(0, 400))) return
   if (extname(rel) === '.md') {
     // Line numbers stay true: replace everything outside a css fence with
     // blanks rather than extracting the fences, so a reported line is the line.
@@ -248,10 +255,18 @@ function lintFile(abs, root) {
   //     an org switcher, an app launcher and a footer are ONE set of controls
   //     across every Hanzo surface — that is what makes them recognisable as
   //     one product. A local copy is a control that drifts by a release.
-  for (const m of src.matchAll(
-    /\b(?:function|const)\s+(Hanzo?(?:Header|Footer)|(?:Site|App|Global|Main|Top)(?:Header|Nav|Footer|Bar)|(?:Header|Nav|Command|Search)(?:Search|Palette|Trigger|Bar)|OrgSwitcher|OrgHeader|AppLauncher|MegaMenu)\b/g))
-    flag(rel, lineOf(src, m.index), 'shell-owned-chrome', m[1],
-      'import it from @hanzogui/shell — the chrome is one set of controls, fleet-wide')
+  //
+  //     A WRAPPER IS NOT A COPY, and the question is which one this is. A file
+  //     that imports the shell and composes it — passing this site's pages into
+  //     `HanzoHeader` — is doing exactly what it should, and hanzo.ai's
+  //     `SiteHeader`/`SiteFooter` are that. So the rule asks whether the shell
+  //     is in the file at all; if it is, the name is a local alias for shell
+  //     chrome and not a second implementation of it.
+  if (!/['"]@hanzogui\/shell/.test(src))
+    for (const m of src.matchAll(
+      /\b(?:function|const)\s+(Hanzo?(?:Header|Footer)|(?:Site|App|Global|Main|Top)(?:Header|Nav|Footer|Bar)|(?:Header|Nav|Command|Search)(?:Search|Palette|Trigger|Bar)|OrgSwitcher|OrgHeader|AppLauncher|MegaMenu)\b/g))
+      flag(rel, lineOf(src, m.index), 'shell-owned-chrome', m[1],
+        'import it from @hanzogui/shell — the chrome is one set of controls, fleet-wide')
 }
 
 // ── run ──────────────────────────────────────────────────────────────────