deepspace 0.25.0 → 0.26.1

package/CHANGELOG.md

@@ -1,5 +1,46 @@
 # deepspace
 
+## 0.26.1
+
+### Patch Changes
+
+- Remove the unused platform-owned conversation, directory, and inbox stack,
+  including its hooks, schemas, routes, bindings, Durable Object class, and
+  dead client platform context/WebSocket helpers.
+
+  Make the bundled messaging feature honest and smaller by supporting public
+  channels only, confirming membership writes, and removing duplicate multi-chat,
+  DM, private-group, invitation, and unread-state implementations. Remove the
+  overbuilt sidebar feature and reduce search to a controlled inline component
+  plus local ranking.
+
+  Make generated Playwright runs own their test server and refuse busy ports
+  (`port_in_use`, after a bounded grace for a server still shutting down), gate
+  suite readiness on the auth plane, settle screenshots before capture (with
+  opt-in `--wait-for-selector`), add the router hydration fallback, bound deploy
+  JSON progress, and label `app usage` as account-wide.
+
+  Migration for existing apps: removed `deepspace` exports include
+  `useConversation`, the `client/directory` hooks (`useConversations`,
+  `useCommunities`, `usePosts`), the client platform context
+  (`PlatformProvider`, `usePlatformWS`), `ChannelInvitation`,
+  `CHANNEL_INVITATIONS_SCHEMA`, `CONVERSATION_SCHEMAS`, `VOTING_SCHEMAS`,
+  `DIRECTORY_SCHEMAS`, and the messaging display utils
+  (`formatMessageTime`, `groupReactionsForMessage`, `parseMessageMetadata`, …).
+  Apps that installed the pre-0.27 messaging feature should delete the copied
+  `chat-multi/` components, `ChatMultiPage`, and `useMultiChannel` (they import
+  the removed exports), and drop `channel-invitations` from their schemas. The
+  bundled `channels` schema now admits only `type: 'public'`: existing
+  `private`/`dm` rows keep reading but fail validation on writes that echo the
+  old value — delete those rows or keep an app-local schema that still declares
+  them.
+
+## 0.26.0
+
+### Minor Changes
+
+- Source authority is inferred from use, never registered, and the 0.25.0 AX-pass defects are fixed. Nothing is declared "at the beginning": the `source_unclaimed` deploy refusal is gone — an unclaimed app whose checkout has a GitHub remote deploys as GitHub automatically (no git gates, no credential probe; `github_credentials_required` no longer exists), and each release records the observed repository. The first `deepspace push` (or an unclaimed app's deploy sync) claims DeepSpace source at the git receive path, once, permanently — and now says so on stderr at the moment it happens. The claim fires on the pack POST rather than the ref advert, so a `git push --dry-run` or an abandoned push never pins the app — and an admin-tier push to an unclaimed app refuses (`admin_cannot_claim`): support must neither claim an app nor create history on an unclaimed one. `deepspace app source` is now read-only (`source_inferred` refuses the old setter, and reporting an unregistered checkout never mints); the server's `POST /source` route and the transfer protocol (ref/release proofs, `github_push_required`, the transfer-preparation `source_changed` checks — deploy's own `source_changed` race check remains — the owner-only import receive path and its `X-DeepSpace-Source-Revision` header) are removed. A claimed GitHub app's stale `space` git remote is now removed by `deploy` (the old claim command did this). Releases also record the dirty flag on commit-bearing `--no-push` deploys (`commit abc123 (dirty worktree)`), and a rollback carries its TARGET release's source evidence and dirty flag instead of losing them. App registration is also no longer an upfront step: apps register on FIRST USE. Any verb that USES the app — `secrets set`/`upload`/`pull` before the first deploy, `dev start`, `test run`, `deploy`, and `push` once the repo has commits — mints and stamps its id through the one resolver chokepoint when wrangler.toml has none (same registration `app init` performs, announced on stderr with the plane and account; the initial scaffold commit is made by `app init` and `deploy` only). A wrangler.toml whose COMMITTED content still carries the `__APP_ID__` placeholder refuses (a shared repo must not mint one app per clone), a typo'd `--env` name still refuses (`no_app_id_for_env`) — minting only fills a declared env block or the top level — and a malformed existing id still refuses (`invalid_app_id`), never minted over. Healing is scoped twice: only a wrangler.toml that DECLARES `DEEPSPACE_APP_ID` (the scaffold's placeholder) can mint — an unrelated Cloudflare Workers repo refuses as before — and only the verbs whose purpose is building or using the app register (`deploy`, `dev`, `test`, `push`, and the `secrets` WRITE verbs); read and ownership verbs (`secrets list/get/download`, `logs`, `releases`, `collaborators`, `transfer`, …) keep the `app_not_initialized` refusal rather than consuming a quota slot as a side effect. Only `app init`/`deploy` create the initial scaffold commit (the resolver never authors git commits). Dependencies also install on first use: a fresh clone's `dev`/`test`/`deploy`/`add` runs the detected package manager itself (streamed to `.deepspace/install.log`, bounded at 5 minutes, retried on the next command after a failure, `DEEPSPACE_NO_INSTALL=1` restores the old `deps_missing` refusal — note this includes workspace worktrees, which get their own install). Collaborator pushes now claim DeepSpace source like the owner's (the old owner-only claim would have left collaborator-built apps unclaimed — with claiming and pushing at the same receive path, an app with cloud history is always claimed), and inferred-GitHub evidence travels as its own field so a 0.25.0 worker's stale-base guard is never skipped by it; the retired `POST /source` answers 410 `source_inferred` instead of a misleading 404. `npm create` → any command works with no intermediate step; a logged-out scaffold exits 0; `app init` remains the explicit spelling and the only path that can replace an id (`--new-id`). `app undeploy` automation must pass `--yes` (the repo's own reaper and harness scripts updated). Consent: `app undeploy` under `--json` or a non-TTY stdin now refuses `confirmation_required` without `--yes` instead of treating the command as consent. Releases: a deploy records `sourceDirty` — whether the shipped working tree carried uncommitted changes — and `releases`/`status` label a dirty GitHub-source release (`GitHub · owner/repo, dirty worktree`), so a rollback no longer picks between clean and dirty releases blind. `push` over a dirty worktree now warns and carries `uncommitted` in `--json` (push publishes committed history only). `test accounts create` accepts `--password-stdin` (argv passwords discouraged). `test run` refuses a zombie dev server (`port_in_use`, bounded wait) instead of letting Playwright adopt a dying one mid-run. `not_app_owner` refusals name the recoveries (ask the owner, `app transfer offer`, `app init --new-id`). An unknown subcommand that exactly names a command elsewhere in the tree is suggested there (`auth status` → `status`, not `auth logout`).
+
 ## 0.25.0
 
 ### Minor Changes

package/README.md

@@ -129,15 +129,16 @@ GitHub source is explicit and manual because the developer owns that repository:
 ```bash
 git remote add origin git@github.com:owner/repository.git
 git push -u origin main
-npx deepspace app source github
 npx deepspace deploy
 ```
 
-DeepSpace verifies GitHub but never writes it. Inspect or transfer authority with
-`deepspace app source`, `deepspace app source github`, or
-`deepspace app source deepspace`. Transfers mirror branches and tags before one
-atomic authority change; switching back uses the same commands. Commands support
-`--json` for agents. Use `deepspace --help`, command-specific `--help`, and the
+Nothing to declare: a checkout with a GitHub remote deploys as GitHub
+automatically — DeepSpace never reads or writes the GitHub repository, and
+each release records which repository the checkout pointed at (and whether
+the tree was dirty). The first `deepspace push` instead claims DeepSpace
+source, permanently — using it is choosing it; there are no transfers.
+Inspect with `deepspace app source` (read-only). Commands support `--json`
+for agents. Use `deepspace --help`, command-specific `--help`, and the
 [public manual](https://docs.deep.space) for workspaces, releases, and
 rollback.
 

package/dist/{chunk-2GUGZLAX.js → chunk-YBXIUDZJ.js}

@@ -1274,7 +1274,7 @@ function renderInlineMarkdown(value) {
 import { useEffect as useEffect6, useRef as useRef5, useState as useState5 } from "react";
 
 // package.json
-var version = "0.25.0";
+var version = "0.26.1";
 
 // src/documentation/runtime/navigation.tsx
 import { Fragment as Fragment4, jsx as jsx6, jsxs as jsxs6 } from "react/jsx-runtime";
@@ -1954,4 +1954,4 @@ export {
   DefaultDocumentation,
   DocumentationContent
 };
-//# sourceMappingURL=chunk-2GUGZLAX.js.map
+//# sourceMappingURL=chunk-YBXIUDZJ.js.map