create-astrale-domain 0.3.0-beta.161 → 0.3.0-beta.162

package/README.md

@@ -11,14 +11,14 @@ npx -y create-astrale-domain@beta my-domain --yes --instance development
 The generated project must resolve the SDK and deployment adapters from npm; it must not retain
 workspace links or repository-only source paths.
 
-Managed generation requires an explicit Astrale instance and writes one installed `development`
-Environment; authors add staging and production only when their distinct instances exist.
-Cloudflare generation does not accept `--instance` and creates deploy-only development and
-production Environments. In both cases `pnpm dev` watches and deploys `development` remotely; no
-active instance, local Worker, Vite server, or tunnel is part of the standard Domain-author journey.
-An installed frontend Environment still opens its default View through generic Project tooling;
-stopping development closes only that local View session and retains the remote deployment and
-installation.
+Managed generation requires an explicit Astrale instance and writes one `development`
+Environment deployed through that instance's Services; authors add staging and production only when
+their distinct instances exist. Cloudflare generation does not accept `--instance` and creates
+development and production Environments. In both cases `pnpm dev` watches and deploys
+`development` remotely; no active instance, local Worker, Vite server, or tunnel is part of the
+standard Domain-author journey. A deploy never installs: install the URL it prints with
+`astrale domain install <url> --direct -i <instance>`. Stopping development retains the remote
+deployment.
 
 Generated projects have one package journey:
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-astrale-domain",
-  "version": "0.3.0-beta.161",
+  "version": "0.3.0-beta.162",
   "description": "Scaffold a standalone Astrale domain — npm create astrale-domain",
   "keywords": [
     "astrale",
@@ -30,14 +30,14 @@
     "registry": "https://registry.npmjs.org/"
   },
   "dependencies": {
-    "@astrale-os/adapter-astrale": "0.5.0-beta.161",
-    "@astrale-os/adapter-cloudflare": "0.5.0-beta.168",
+    "@astrale-os/adapter-astrale": "0.5.0-beta.162",
+    "@astrale-os/adapter-cloudflare": "0.5.0-beta.169",
     "@clack/prompts": "^0.11.0"
   },
   "devDependencies": {
     "@astrale-os/kernel-dsl": "0.2.0-beta.44",
     "@astrale-os/ox": "0.1.4",
-    "@astrale-os/sdk": "0.6.0-beta.13",
+    "@astrale-os/sdk": "0.6.0-beta.14",
     "@types/node": "^22.0.0",
     "esbuild": "^0.28.2",
     "oxfmt": "0.63.0",

package/template/.variants/custom/README.md

@@ -17,8 +17,8 @@ tests/               cross-layer executable journeys
 ```
 
 Run `pnpm dev` to watch, remotely deploy, and verify the committed `development` Environment. It
-starts no local Worker, browser server, or tunnel; when installation is configured it reconciles the
-ready Release onto that Environment's exact Astrale instance. Run `pnpm build` to build both Worker
+starts no local Worker, browser server, or tunnel, and never installs: install the URL it prints with
+`astrale domain install <url> --direct -i <instance>`. Run `pnpm build` to build both Worker
 and browser assets and print their build digest.
 Domain projects intentionally own no `.spec` trees and import authoring contracts only through
 semantic `@astrale-os/sdk/*` subpaths.

package/template/.variants/none/README.md

@@ -10,8 +10,8 @@ tests/               cross-layer executable journeys
 ```
 
 Run `pnpm dev` to watch, remotely deploy, and verify the committed `development` Environment. It
-starts no local Worker or tunnel; when installation is configured it reconciles the ready Release
-onto that Environment's exact Astrale instance. Run `pnpm build` to qualify its deploy bundle and print its build digest. Add `views/` and
+starts no local Worker or tunnel, and never installs: install the URL it prints with
+`astrale domain install <url> --direct -i <instance>`. Run `pnpm build` to qualify its deploy bundle and print its build digest. Add `views/` and
 `ui/` later only when the schema gains declared Views. Domain projects intentionally own no `.spec`
 trees and import authoring contracts only through semantic `@astrale-os/sdk/*` subpaths.
 

package/template/.variants/react/README.md

@@ -16,8 +16,8 @@ tests/               cross-layer executable journeys
 ```
 
 Run `pnpm dev` to watch, remotely deploy, and verify the committed `development` Environment. It
-starts no local Worker, Vite server, or tunnel; when installation is configured it reconciles the
-ready Release onto that Environment's exact Astrale instance. Run `pnpm build` to qualify Worker and
+starts no local Worker, Vite server, or tunnel, and never installs: install the URL it prints with
+`astrale domain install <url> --direct -i <instance>`. Run `pnpm build` to qualify Worker and
 frontend output and print their build digest, and `pnpm run deploy production` to deploy through the selected adapter. Add semantic `rules/`, `queries/`,
 `mutations/`, and `functions/` modules only when the Domain gains those responsibilities.
 

package/template/CLAUDE.md

@@ -33,12 +33,11 @@ adapters remain implementation inputs and are not published. Do not add a parall
 declaration-rewrite script.
 
 `pnpm dev` watches the generated `development` Environment. It builds and verifies locally, then
-deploys the Worker and frontend remotely through the Environment's adapter and reconciles the
-declared installation when present. It never reads an active instance or starts a local Worker,
-Vite server, or tunnel. Stop ends only local watching; it retains the remote deployment and
-installation. Do not add a parallel tunnel, install loop, frontend watcher, or shutdown uninstall.
-For an installed frontend Environment, Project tooling opens and refreshes the default View; stop
-closes only that local View session.
+deploys the Worker and frontend remotely through the Environment's adapter. It never installs,
+reads an active instance, or starts a local Worker, Vite server, or tunnel: install the URL it
+prints with `astrale domain install <url> --direct -i <instance>`. Stop ends only local watching; it
+retains the remote deployment. Do not add a parallel tunnel, install loop, frontend watcher, or
+shutdown uninstall. Do not declare `installation` on a Project Environment: it is refused.
 
 Domain projects do not contain `.spec` directories. Do not add one: public SDK types, package
 facades, the Domain knowledge rules, and executable tests are the contract guardrails. Import Core