create-astrale-domain 0.3.0-beta.158 → 0.3.0-beta.159

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-astrale-domain",
-  "version": "0.3.0-beta.158",
+  "version": "0.3.0-beta.159",
   "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.158",
-    "@astrale-os/adapter-cloudflare": "0.5.0-beta.165",
+    "@astrale-os/adapter-astrale": "0.5.0-beta.159",
+    "@astrale-os/adapter-cloudflare": "0.5.0-beta.166",
     "@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.10",
+    "@astrale-os/sdk": "0.6.0-beta.11",
     "@types/node": "^22.0.0",
     "esbuild": "^0.28.2",
     "oxfmt": "0.63.0",

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

@@ -1,6 +1,6 @@
 # Astrale Domain
 
-This project uses the framework-neutral frontend escape hatch. `application.ts` binds declared
+This project uses the framework-neutral frontend escape hatch. `domain.ts` binds declared
 Schema Views to `defineFrontend`; `vite.config.ts` owns the ordinary `frontend/` Vite root you can
 replace with any framework; `ui/` owns presentation assets. The starter route uses
 `handshake: 'none'`, so it mounts as a plain hosted app. Change that route to `handshake: 'shell'`
@@ -9,7 +9,7 @@ only after your browser entrypoint boots the Shell protocol.
 ```text
 schema/             public Domain contract, including View declarations
 runtime.ts          Actions, Workflows, Integrations, Providers, and initialization
-application.ts      Schema, Runtime, and frontend composition
+domain.ts           Schema, Runtime, and frontend composition
 views/application/   application View projection and mount behavior
 frontend/            browser entrypoint and assets
 ui/application/      application presentation, tokens, and styles
@@ -19,7 +19,7 @@ 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
-and browser assets.
+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/custom/__tests__/variant.test.ts

@@ -1,11 +1,11 @@
-import { application } from '../application.js'
+import { domain } from '../domain.js'
 
 describe('custom frontend variant', () => {
   /** @evidence SDK-V1-SCAFFOLD-CUSTOM */
   it('rejects missing authored frontend composition', () => {
-    expect(application.frontend).toBeDefined()
-    expect(application.frontend?.source.kind).toBe('vite')
-    expect(application.frontend?.routes.application).toMatchObject({
+    expect(domain.frontend).toBeDefined()
+    expect(domain.frontend?.source.kind).toBe('vite')
+    expect(domain.frontend?.routes.application).toMatchObject({
       path: '/application',
       handshake: 'none',
     })

package/template/.variants/custom/{application.ts → domain.ts}

@@ -1,4 +1,4 @@
-import { defineApplication, defineFrontend, requirements, vite } from '@astrale-os/sdk/application'
+import { defineDomain, defineFrontend, requirements, vite } from '@astrale-os/sdk/domain'
 import { K } from '@astrale-os/sdk/schema'
 
 import { schema } from '#schema'
@@ -15,7 +15,7 @@ const frontend = defineFrontend({
 })
 
 /** Build and publication composition; provider effects live in astrale.config.ts. */
-export const application = defineApplication({
+export const domain = defineDomain({
   schema,
   runtime,
   frontend,

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

@@ -5,13 +5,13 @@ This is a callable-only Domain with no frontend artifact or browser assets.
 ```text
 schema/             public Domain contract
 runtime.ts          Actions, Workflows, Integrations, Providers, and initialization
-application.ts      Schema and Runtime composition
+domain.ts           Schema and Runtime composition
 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. Add `views/` and
+onto that Environment's exact Astrale 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/none/__tests__/variant.test.ts

@@ -1,8 +1,8 @@
-import { application } from '../application.js'
+import { domain } from '../domain.js'
 
 describe('none frontend variant', () => {
   /** @evidence SDK-V1-SCAFFOLD-NONE */
-  it('rejects an implicit browser frontend by keeping Application headless', () => {
-    expect(application.frontend).toBeUndefined()
+  it('rejects an implicit browser frontend by keeping the Domain headless', () => {
+    expect(domain.frontend).toBeUndefined()
   })
 })

package/template/.variants/none/{application.ts → domain.ts}

@@ -1,4 +1,4 @@
-import { defineApplication, requirements } from '@astrale-os/sdk/application'
+import { defineDomain, requirements } from '@astrale-os/sdk/domain'
 import { K } from '@astrale-os/sdk/schema'
 
 import { schema } from '#schema'
@@ -6,7 +6,7 @@ import { schema } from '#schema'
 import runtime from './runtime.js'
 
 /** Build and publication composition; provider effects live in astrale.config.ts. */
-export const application = defineApplication({
+export const domain = defineDomain({
   schema,
   runtime,
   requirements: requirements({ functions: [K.functions.query, K.functions.mutate] }),

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

@@ -1,6 +1,6 @@
 # Astrale Domain
 
-This project is an ordinary Vite React application. `application.ts` owns the small Worker-safe,
+This project is an ordinary Vite React application. `domain.ts` owns the small Worker-safe,
 Schema-bound frontend deployment contract; `frontend/` owns TanStack Router and browser
 composition; `ui/` owns reusable presentation. It has no mandatory Shell runtime: add
 `@astrale-os/shell-react` independently when the application genuinely needs Shell sessions, graph
@@ -9,7 +9,7 @@ context, or View-stage integration.
 ```text
 schema/             public Domain contract, including View declarations
 runtime.ts          Functions, Integrations, Providers, and initialization
-application.ts      Schema, Runtime, and frontend composition
+domain.ts           Schema, Runtime, and frontend composition
 frontend/            Vite, file-based TanStack Router, and Tailwind entrypoint
 ui/                  styles and pure presentation components
 tests/               cross-layer executable journeys
@@ -18,7 +18,7 @@ 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
-frontend output, and `pnpm run deploy production` to deploy through the selected adapter. Add semantic `rules/`, `queries/`,
+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.
 
 Domain projects intentionally own no `.spec` trees. Import authoring contracts through semantic

package/template/.variants/react/__tests__/variant.test.ts

@@ -1,11 +1,11 @@
-import { application } from '../application.js'
+import { domain } from '../domain.js'
 
 describe('react frontend variant', () => {
   /** @evidence SDK-V1-SCAFFOLD-REACT */
   it('rejects missing authored frontend composition', () => {
-    expect(application.frontend).toBeDefined()
-    expect(application.frontend?.source.kind).toBe('vite')
-    expect(application.frontend?.routes.application).toMatchObject({
+    expect(domain.frontend).toBeDefined()
+    expect(domain.frontend?.source.kind).toBe('vite')
+    expect(domain.frontend?.routes.application).toMatchObject({
       path: '/application',
       handshake: 'none',
     })

package/template/.variants/react/{application.ts → domain.ts}

@@ -1,4 +1,4 @@
-import { defineApplication, defineFrontend, requirements, vite } from '@astrale-os/sdk/application'
+import { defineDomain, defineFrontend, requirements, vite } from '@astrale-os/sdk/domain'
 import { K } from '@astrale-os/sdk/schema'
 
 import { schema } from '#schema'
@@ -15,7 +15,7 @@ const frontend = defineFrontend({
 })
 
 /** Build and publication composition; provider effects live in astrale.config.ts. */
-export const application = defineApplication({
+export const domain = defineDomain({
   schema,
   runtime,
   frontend,

package/template/CLAUDE.md

@@ -11,10 +11,10 @@ npx skills add astrale-os/cli -g
 This scaffold is intentionally minimal. React and custom projects include one schema-declared
 application View to prove frontend delivery; `--frontend none` is callable-only. Start each real
 behavior in its semantic submodule, keep owners explicit, put focused tests in `__tests__`, use
-registered package `#` imports across owners, and keep `runtime.ts` and `application.ts` limited to
+registered package `#` imports across owners, and keep `runtime.ts` and `domain.ts` limited to
 their exact composition responsibilities.
 Actions perform one semantic asynchronous operation; Workflows name every explicit multi-step operation.
-The scaffold's Kernel dependency and `query`/`mutate` Application requirements authorize bound graph
+The scaffold's Kernel dependency and `query`/`mutate` Domain requirements authorize bound graph
 executors. Retain them while handlers access graph state; use `graph.self` for Domain-owned facts.
 
 Add `schema/modules/<module>/states/` only when a Schema business module owns a finite persisted

package/template/index.ts

@@ -1,3 +1,3 @@
-export { application } from './application.js'
+export { domain } from './domain.js'
 export { default as runtime } from './runtime.js'
 export { schema } from '#schema'

package/template/tests/e2e/domain.test.ts

@@ -0,0 +1,9 @@
+import { domain, runtime, schema } from '../../index.js'
+
+describe('domain composition', () => {
+  it('keeps authored Domain and Runtime composition exact', () => {
+    expect(domain.schema).toBe(schema)
+    expect(domain.runtime).toBe(runtime)
+    expect(runtime.functions).toEqual([])
+  })
+})

package/template/tsconfig.json

@@ -57,7 +57,7 @@
     "ui",
     "utils",
     "tests",
-    "application.ts",
+    "domain.ts",
     "runtime.ts",
     "index.ts",
     "astrale.config.ts",

package/template/tests/e2e/application.test.ts

@@ -1,9 +0,0 @@
-import { application, runtime, schema } from '../../index.js'
-
-describe('application composition', () => {
-  it('keeps authored Application and Runtime composition exact', () => {
-    expect(application.schema).toBe(schema)
-    expect(application.runtime).toBe(runtime)
-    expect(runtime.functions).toEqual([])
-  })
-})