deepspace 0.9.0 → 0.9.2

package/CHANGELOG.md

@@ -1,5 +1,39 @@
 # deepspace
 
+## 0.9.2
+
+### Patch Changes
+
+- Restore traditional manual deployment for GitHub-authoritative apps: ordinary
+  deploys now ship the local working tree, including uncommitted changes, without
+  Git verification, commits, pushes, or recoverable commit lineage. Commit-first
+  sync and workspace lineage remain exclusive to DeepSpace source.
+
+  Track versioned app migrations in `deepspace.migrations.json` and carry that
+  manifest in normal deploy bundles and release metadata. Migration completion is
+  now independent of Git commit lineage, so the same `deepspace app migrate`
+  workflow works for manual GitHub deploys and packaged DeepSpace-source deploys.
+  Legacy identity orchestration now lives under the migration command/control
+  plane: prepared journals can be canceled, committed cutovers recover forward,
+  and ordinary deploy, rollback, ownership, source, and deployment-recording
+  paths carry no migration-specific state hooks.
+
+  Bind the bundled messaging schemas' owner fields to the authenticated caller,
+  and avoid false-positive owner-field warnings for collections ordinary clients
+  cannot create. New apps use Vitest 4 with a standalone unit-test configuration
+  so Vite's Cloudflare Worker plugin cannot leak into the Node test runner, and
+  include the current app-migration manifest.
+
+## 0.9.1
+
+### Patch Changes
+
+- Keep `deepspace app migrate` as the permanent ordered app-upgrade runner and
+  repair obsolete `x-app-name` platform identity wiring before a canonical app
+  deployment, without changing retained `APP_NAME` data namespaces. Track
+  source-only migration commits against live release lineage so both GitHub and
+  DeepSpace apps are guided through the required deploy.
+
 ## 0.9.0
 
 ### Minor Changes

package/README.md

@@ -90,9 +90,9 @@ npx deepspace deploy     # deploy to *.app.space
 ```
 
 The [normative CLI hierarchy](../../docs/platform/cli-contract.md#public-command-hierarchy)
-keeps durable app identity and lifecycle operations under `deepspace app`,
+keeps durable app lifecycle and version migrations under `deepspace app`,
 while checkout-oriented Git, workspace, release, and deploy operations stay
-top-level. In particular, legacy identity migration is
+top-level. In particular, app migration is
 `deepspace app migrate`; there is no top-level `deepspace migrate` alias.
 
 Every app has one authoritative Git repository. DeepSpace source is the packaged
@@ -118,23 +118,36 @@ atomic authority change; switching back uses the same commands. Commands support
 [repository guide](https://github.com/deepdotspace/deepspace/blob/main/docs/platform/repo-store-git.md)
 for workspaces, releases, and rollback.
 
-Legacy GitHub apps whose `DEEPSPACE_APP_ID` is still name-shaped migrate in
-place with one resumable command:
+`deepspace app migrate` is the permanent upgrade runner for breaking app
+changes. It contains an ordered set of structural, idempotent migrations, so
+agents and developers keep using the same command across releases:
 
 ```bash
 npx deepspace app migrate --dry-run
 npx deepspace app migrate
 ```
 
-The dry-run lists the exact registry rows that will be re-keyed and the
-physical stores that remain at the existing resource id. The command then
-pauses for the normal manual GitHub commit/push and finishes with one deploy.
+The dry-run lists pending source migrations without changing files. For a
+legacy GitHub app whose `DEEPSPACE_APP_ID` is still name-shaped, it also lists
+the exact registry rows that will be re-keyed and the physical stores that
+remain at the existing resource id. The command applies only transformations
+it recognizes safely, pauses for normal commit/push, and finishes with one
+deploy. Applied steps live in the checked-in `deepspace.migrations.json`
+manifest. Normal deploy bundles record that manifest in the release, so the
+next run can determine whether the migration is live without depending on Git
+commit lineage. Rerun after each returned action; when nothing is pending it
+reports `up_to_date`. This is the same workflow for GitHub and DeepSpace
+source; only their normal push behavior differs. `APP_NAME`-based
+legacy room and storage addresses are retained; canonical `DEEPSPACE_APP_ID`
+is used only for logical identity and platform authentication.
+
 Keep deploy, release rollback, and undeploy idle from the mutating command until
 that returned deploy begins; normal app traffic continues throughout.
-Before that deploy starts, `--cancel` reverses a prepared migration and
-`--rollback` reverses a committed migration; both require the restored legacy
-configuration to be committed and pushed first. DeepSpace never writes the
-GitHub repository.
+Before the registry cutover commits, `--cancel` reverses a prepared migration
+after the restored legacy configuration is committed and pushed. After the
+cutover, recovery is deliberately forward-only: deploy the canonical app and
+rerun `deepspace app migrate` to verify the live release. DeepSpace never
+writes the GitHub repository.
 
 ## Debugging