@hublo/sentinel 1.2.0-alpha.3 → 1.2.0-alpha.4

package/dist/bin/sentinel.js

@@ -21,7 +21,7 @@ import {
   registerAdapters,
   resolve,
   resolveBin
-} from "../chunk-YZ4EKBK7.js";
+} from "../chunk-6DBTDMSN.js";
 
 // bin/sentinel.ts
 import { program } from "commander";

package/dist/{chunk-YZ4EKBK7.js → chunk-6DBTDMSN.js}

@@ -469,7 +469,7 @@ var BUILD_CONFIG_FILES = [
 ];
 var BUILD_PRESET_SPECIFIER = "@hublo/sentinel/build/react";
 var BUILD_SCRIPT_NAME = "build";
-var SENTINEL_BUILD_COMMAND = "sentinel --run --build";
+var SENTINEL_BUILD_COMMAND = "sentinel --run --build --";
 var DEV_SCRIPT_NAME = "serve";
 var SENTINEL_DEV_COMMAND = "sentinel --run --dev";
 function buildTarget() {
@@ -726,7 +726,9 @@ function buildScripts(cwd) {
     const own2 = moduleName(cwd);
     scripts[DEV_SCRIPT_NAME] = composeDevScript(
       existingDev,
-      `${selfCommand(cwd, "--run --dev") ?? SENTINEL_DEV_COMMAND} --module ${own2}`
+      // Trailing `--` for the same reason as the build script: whatever the caller appends
+      // reaches Vite, not sentinel's parser. It goes after `--module`, which is sentinel's own.
+      `${selfCommand(cwd, "--run --dev") ?? SENTINEL_DEV_COMMAND} --module ${own2} --`
     );
   }
   return scripts;
@@ -935,22 +937,24 @@ var ViteDevAdapter = class extends ViteRoleAdapter {
     return "dev";
   }
   /**
-   * There is no such thing as adopting the dev server on its own.
+   * `--init --dev` does the same thing as `--init --build`, and now says so.
    *
-   * `ViteRoleAdapter.plan()` is shared with `--build` because everything else about the two
-   * targets is shared, and inheriting it here made `--init --dev` perform the FULL build
-   * adoption, silently, under a message that only ever mentioned the build. Exiting 0 on that
-   * is the worst of the options: it teaches that dev can be adopted by itself, and that belief
-   * is what produces the half-migrated module this role exists to prevent (see the class
-   * comment above, and `registerBuild`).
-   *
-   * A single plan writes both scripts, so the honest answer is to name the command that does
-   * it rather than to do it under a different name.
+   * The shared plan is deliberate (see `ViteRoleAdapter.plan`): one plan writes both scripts,
+   * because adopting one without the other leaves the module half-migrated. What was missing
+   * was only the telling: the run printed a message about the build and nothing about `serve`,
+   * so a developer could believe the dev server had been adopted on its own. Refusing was the
+   * wrong correction, it added friction to a command that already produced the right result.
    */
-  plan() {
-    throw new Error(
-      "the dev server is adopted together with the build, never on its own. Run --init --build: one plan writes both the `build` and the `serve` scripts."
-    );
+  plan(context) {
+    const planned = super.plan(context);
+    if (planned.operations.length === 0) return planned;
+    return {
+      ...planned,
+      notes: [
+        ...planned.notes ?? [],
+        "--init --dev adopts the build too: one plan writes both `build` and `serve`."
+      ]
+    };
   }
   /**
    * Start the dev server. It does not return until stopped, so there is no verdict to report
@@ -6261,4 +6265,4 @@ export {
   detectFramework,
   dispatch
 };
-//# sourceMappingURL=chunk-YZ4EKBK7.js.map
+//# sourceMappingURL=chunk-6DBTDMSN.js.map

package/dist/index.js

@@ -7,7 +7,7 @@ import {
   registerAdapters,
   resolve,
   setDefaultRunner
-} from "./chunk-YZ4EKBK7.js";
+} from "./chunk-6DBTDMSN.js";
 export {
   BaseAdapter,
   all,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hublo/sentinel",
-  "version": "1.2.0-alpha.3",
+  "version": "1.2.0-alpha.4",
   "description": "One CLI that guards code health across Hublo repos: shared lint/typescript/build/test presets, static & dynamic analysis, and architecture checks.",
   "type": "module",
   "license": "MIT",