@maligator/cli 0.1.0-alpha.20 → 0.1.0-alpha.22

package/README.md

@@ -57,11 +57,12 @@ maligator test [path ...] [--run name] [--shuffle [seed]] [--repeat count] [--ba
 Run commands from the project root. Maligator does not search parent directories
 for configuration.
 
-`run` and `dev` use the runtime embedded in the platform package for the supported
-single-process, asset-free, Intl-disabled development profile, so they do not need
-a local native toolchain. `dev` retains compiler identities between edits and
-restarts a fresh application VM after every successful rebuild. Build failures keep
-the watcher alive for recovery on the next edit.
+`run` and `dev` use compile-time-specialized runtimes embedded in the platform
+package for locked or mutable primordials, configured assets, the Web and Node
+surfaces, and Realm support when Intl is disabled. Those profiles do not need a local
+native toolchain. `dev` retains compiler identities between edits and restarts a fresh
+application VM after every successful rebuild. Build failures keep the watcher alive
+for recovery on the next edit.
 
 ## Testing
 
@@ -153,14 +154,17 @@ package declarations explicitly:
 Normal `maligator build`, `maligator run`, and `maligator test` commands share a
 content-addressed portable VM definition store. On a valid hit, Maligator skips
 parsing, module-graph construction, semantic analysis, optimization, register
-allocation, and VM lowering. For the single-process, asset-free, Intl-disabled
-development profile, `run` executes the restored definition with the isolated
-runtime embedded in the platform CLI; it does not generate C or invoke a native
-toolchain. Normal and production `build` commands emit
+allocation, and VM lowering. For supported Intl-disabled development profiles, `run`
+executes the restored definition with a matching compile-time-specialized runtime
+embedded in the platform CLI; it does not generate C or invoke a native toolchain.
+Normal and production `build` commands emit
 native translation units from the same restored definition. Those units and the native driver are
 compiled into independently content-addressed objects, so unchanged objects can
 be relinked without repeating C compilation. The final link still runs, and
-native runtime and Rust archives remain separately content-addressed.
+native runtime and Rust archives remain separately content-addressed. Runtime C
+objects use their preprocessed input as the feature projection, while distinct
+Rust feature archives share Cargo dependency work. Output executables remain
+statically linked and self-contained.
 
 Build cache invalidation includes source and transitive dependency content,
 package-resolution metadata, relevant configuration, the TypeScript erasure
@@ -259,7 +263,7 @@ explicitly:
 
 `maligator test` and supported `maligator run` profiles use the development runtime
 embedded in the platform CLI and do not require a native toolchain. Native `build`
-commands—and development runs using bundled assets, Intl, or multiprocessing—require:
+commands—and development runs using Intl—require:
 
 - A C23 compiler and archive tool: Apple clang, clang 19 or newer, or GCC 15 or
   newer

package/index.d.ts

@@ -47,9 +47,6 @@ export interface MaligatorBuildConfig {
 			languages?: Array<string>;
 		};
 	};
-	host?: {
-		scheduler?: "single" | "multiprocessing";
-	};
 	surface?: {
 		webPlatform?: boolean;
 		node?: boolean;

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@maligator/cli",
-	"version": "0.1.0-alpha.20",
+	"version": "0.1.0-alpha.22",
 	"description": "Ahead-of-time JavaScript compiler and native runtime",
 	"license": "MIT",
 	"homepage": "https://github.com/dirkdev98/maligator#readme",
@@ -45,6 +45,6 @@
 		}
 	},
 	"optionalDependencies": {
-		"@maligator/cli-darwin-arm64": "0.1.0-alpha.20"
+		"@maligator/cli-darwin-arm64": "0.1.0-alpha.22"
 	}
 }