@fusion.dev/helix-diagnostics 0.187.0 → 0.188.0

package/README.md

@@ -174,6 +174,23 @@ runs in, or the file `--config <path>` names, and refuses a setting that names
 nothing, as the page does. It exits 1 on a finding at `error`, and 3 where the
 project installs no Helix lint data. `--json` prints the run.
 
+## Run it on a page, from the command line
+
+`helix diagnostics --once <url>` opens the page headless, runs this package's
+diagnostics in it once the page holds still, prints each finding and what the
+library logged as it ran, and exits. Nothing is added to your app: the
+command serves the installed package on the page's own origin. Repeat
+`--once` for each page.
+
+```sh
+npx helix diagnostics --once http://localhost:5173/ --once http://localhost:5173/settings
+```
+
+It needs `@fusion.dev/helix-cli` and Playwright installed beside this package.
+It exits 1 on a finding at `error`, and 3 where a page could not be opened.
+`--out` writes the runs to the CI file, and `--json` prints one document a
+page. An agent gets the same runs from the MCP tool `helix_check_page`.
+
 ## Run it once, directly
 
 `diagnose()` is one run, which `initDiagnostics()` makes for you. Call it

package/dist/analyze.d.ts

@@ -54,8 +54,8 @@ export declare const analyze: (rules: Located[], tags: Map<string, Published>, f
  * it happens, with both class objects in hand, which is a position nothing
  * later can improve on: by the time a page can be scanned, the losing class is
  * unreachable and all that is left is an identity mismatch to infer from. So
- * this reads `duplicateRegistrations()` rather than re-deriving it, which is
- * `AGENTS.md`'s rule about where a fix lives applied to a detector.
+ * this reads `duplicateRegistrations()` and does not re-derive it, so the fact
+ * comes from where the fault starts.
  *
  * The identity check stays as a fallback, for the copy that never went through
  * Helix's own decorator: a fork, a hand-written `customElements.define`, or a

package/dist/collect.d.ts

@@ -36,8 +36,8 @@ export interface Located {
  * because its class sets `styles = [HelixIconButton.styles, styles].flat()`:
  * it borrows another component's stylesheet outright. That is not inheritance,
  * not a mixin and not a part, so no manifest field describes it and `cem` records
- * nothing. Two correct declarations in this repository's own `landing.module.css`
- * were called dead on the strength of that silence.
+ * nothing. Two correct declarations in a site's stylesheet were called dead on
+ * the strength of that silence.
  *
  * A `var(--x)` inside the element's own shadow styles is direct evidence that
  * the element reads the property, which is a stronger claim than the manifest

package/dist/version.d.ts

@@ -6,4 +6,4 @@
  * release, so the two never disagree; a spec beside this holds them to it.
  * Nothing else in the running code knows which release it is.
  */
-export declare const VERSION = "0.187.0";
+export declare const VERSION = "0.188.0";

package/dist/version.js

@@ -1 +1 @@
-export const VERSION = '0.187.0';
+export const VERSION = '0.188.0';

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@fusion.dev/helix-diagnostics",
   "description": "Finds the Helix mistakes that are valid CSS: dead parts, misnamed hooks, two copies of the library.",
-  "version": "0.187.0",
+  "version": "0.188.0",
   "license": "MIT",
   "author": "Ross Sheppard <ross.sheppard@fusion.dev>",
   "repository": {
@@ -33,7 +33,7 @@
   },
   "bugs": "https://github.com/project-fusion/fusion/issues",
   "devDependencies": {
-    "@fusion.dev/helix-testing": "0.187.0",
+    "@fusion.dev/helix-testing": "0.188.0",
     "@types/bun": "^1.4.2"
   },
   "homepage": "https://fusion.dev",