devsync-ai 0.1.0-rc.6 → 0.1.0-rc.8

package/README.md

@@ -1,10 +1,69 @@
 # devsync-ai
 
-This package name is reserved for DevSync (https://devsync.ai), a neutral command surface for AI coding agents.
+DevSync (https://devsync.ai): one dashboard and command line for your AI coding agents (Claude Code, Codex and more), with memory that follows you across machines.
 
-It is under development. This 0.0.1 release is a placeholder and contains no functionality.
+Read this from any machine, before or after installing:
 
-## Distribution
+```
+npm view devsync-ai@next readme           # before installing
+cat "$(npm root -g)/devsync-ai/README.md" # after installing
+```
+
+## Upgrading to 0.1.0-rc.8 (the Go version)
+
+Do this on every machine, in a terminal on that machine. Your Claude sessions keep running throughout: DevSync starts them as background sessions, and quitting DevSync only closes its view of them.
+
+1. **Stop the old DevSync.** Quit every DevSync dashboard (`q`), then:
+   ```
+   devsync daemon stop
+   ```
+   Never run rc.7 and rc.8 at the same time: an old process left open beside the new one can corrupt the store.
+2. **Install:**
+   ```
+   npm install -g devsync-ai@next
+   devsync --version          # devsync 0.1.0-rc.8
+   ```
+3. **Set it up:**
+   ```
+   devsync install-hooks      # puts the new hook in ~/.devsync/bin and points Claude Code at it
+   devsync mcp sync           # registers DevSync's MCP server with Claude Code
+   devsync doctor             # expect: hooks 14 of 14, no errors
+   ```
+4. **Shared memory (optional).** Link your private rules repo. On a work computer, add `--pull-only`: it takes rules and can never send any.
+   ```
+   devsync global init <your-rules-repo-url> --pull-only
+   devsync global status
+   ```
+   On your own machine, leave out `--pull-only`. `devsync global push` shows exactly what will leave the machine and asks y/N.
+
+## Rolling back if rc.8 fails
+
+rc.8 uses the same store as rc.7 (schema v36), so rc.7 opens it unchanged.
+
+1. Quit every DevSync dashboard (`q`), then `devsync daemon stop`.
+2. Put rc.7 back:
+   ```
+   npm install -g devsync-ai@0.1.0-rc.7
+   devsync install-hooks      # puts rc.7's hook back
+   devsync doctor
+   ```
+3. Only if the store itself went bad, restore a backup. DevSync makes one daily, and `devsync backup` makes one now:
+   ```
+   ls ~/.devsync/backups/
+   devsync store restore ~/.devsync/backups/devsync-<date>.db.gz
+   ```
+   It refuses while anything has the store open, and sets the old files aside instead of deleting them.
+
+## What's new in 0.1.0-rc.8
+
+- DevSync is rebuilt in Go: same screens, commands and store, with the old bugs fixed.
+- The store-corruption bug is fixed at its root.
+- Pinned sessions load at launch (F1-F9 opens them at once), and a session follows a Remote Control switch instead of dropping you back on the dashboard.
+- Remote Control is only on your own sessions, not the ones agents start.
+- Auto-compact: sessions compact at 40% of the model's window. Change it with `devsync config set auto-compact <10..95|off>`.
+- Shared memory across machines with `devsync global`.
+
+## For maintainers: distribution
 
 How DevSync ships on npm (decision D12). Nothing here is published by agents; the user publishes.
 
@@ -62,14 +121,13 @@ Agents build and pack; only the user publishes.
 
 ```
 scripts/build.sh 1.2.3          # dist/<platform>/{devsync,devsync-hook} + dist/SHA256SUMS
-scripts/test-build.sh           # missing toolchains, reproducible host build, archs, no local paths
 scripts/pack.sh 1.2.3           # pack/devsync-ai-<platform>-1.2.3.tgz and pack/devsync-ai-1.2.3.tgz
 npm test                        # the launcher (node --test)
 ```
 
-`build.sh` builds the host and the Linux targets; the macOS targets build only on a Mac, because linking them needs Apple's SDK (chrono's local time zone pulls in CoreFoundation). With no platforms named it builds `linux-x64` and `linux-arm64`, plus both `darwin-*` on a Mac. Linux targets other than the host need `cargo-zigbuild` and `zig` (its header says how to add them). A release tag builds all four on GitHub runners, macOS natively on a Mac (`.github/workflows/release.yml`). `pack.sh` checks each binary against `dist/SHA256SUMS` and pins every platform package to exactly the same version.
+`build.sh` builds the Go binaries (`go/cmd/devsync`, `go/cmd/devsync-hook`, cgo for SQLCipher) for the host's own platform; another platform needs its own C toolchain, so a release tag builds the four on GitHub runners of their own (`.github/workflows/release.yml`: Linux x64 and arm64 natively, both macOS arches on one Apple-silicon Mac). A release holds the Go binaries alone: no Rust binary. `pack.sh` checks each binary against `dist/SHA256SUMS` and pins every platform package to exactly the same version.
 
-To ship a release, bump the workspace version in `tui/Cargo.toml` on main, then run:
+To ship a release, bump the version in `go/internal/version/version.go` and the workspace version in `tui/Cargo.toml` (`release.sh` reads the second) on main, then run:
 
 ```
 npm-devsync-ai/scripts/release.sh            # the workspace version; --dry-run first to see the plan
@@ -77,6 +135,18 @@ npm-devsync-ai/scripts/release.sh            # the workspace version; --dry-run
 
 It tags main as `v<version>` and pushes the tag (and main, if you say so), waits for the release workflow, downloads its tarballs and checks their names and versions, then publishes them in the order below with `--tag next` for a prerelease (`latest` otherwise; `--dist-tag` overrides). It asks before pushing and before publishing, and a rerun skips whatever is already done.
 
+Without GitHub Actions (the release workflow can't run), the Rust-era local scripts below still describe the old zigbuild release and have not been moved to Go; build with `scripts/build.sh` on each platform and `scripts/pack.sh` instead:
+
+```
+npm-devsync-ai/scripts/release-local.sh      # gate, linux-x64 + linux-arm64 (zigbuild, glibc 2.28), npm test, pack, sums, install check
+# on the Mac, from pack/devsync-src-<version>.tar.gz or a checkout of the same commit:
+npm-devsync-ai/scripts/build-macos.sh --test # darwin-arm64 + darwin-x64 -> devsync-macos-<version>.tar.gz
+# back here:
+npm-devsync-ai/scripts/release-local.sh --macos devsync-macos-<version>.tar.gz
+```
+
+`release-local.sh` stops before anything is tagged, pushed or published, and prints the publish commands; it exits 3 while the macOS binaries are missing. The macOS binaries can't be linked from Linux: they need Apple's SDK (Security for the Keychain, CoreFoundation), whose licence allows it only on Apple hardware. Each script's header lists its steps.
+
 By hand, publish the platform packages first, so `devsync-ai`'s optional dependencies exist when it lands:
 
 ```

package/bin/devsync.js

@@ -45,7 +45,10 @@ function locate(platform, arch, resolve) {
 
 /** Run `binary` with `args`, passing signals on, and exit as it does. */
 function run(binary, args) {
-  const child = spawn(binary, args, { stdio: 'inherit' });
+  // Handlers go in before the spawn: the binary can print and be signalled
+  // before this process runs again, and an unhandled SIGINT would kill the
+  // launcher and orphan the binary.
+  let child = null;
   const forward = ['SIGINT', 'SIGTERM', 'SIGHUP', 'SIGQUIT'];
   const handlers = forward.map((sig) => {
     const h = () => {
@@ -58,6 +61,7 @@ function run(binary, args) {
     process.on(sig, h);
     return [sig, h];
   });
+  child = spawn(binary, args, { stdio: 'inherit' });
   child.on('error', (e) => {
     process.stderr.write(`devsync: can't run ${binary}: ${e.message}\n`);
     process.exit(1);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "devsync-ai",
-  "version": "0.1.0-rc.6",
+  "version": "0.1.0-rc.8",
   "description": "DevSync (devsync.ai): one terminal screen over your coding-agent sessions, and the roadmap they work from.",
   "homepage": "https://devsync.ai",
   "keywords": [
@@ -19,9 +19,9 @@
     "node": ">=18"
   },
   "optionalDependencies": {
-    "devsync-ai-linux-x64": "0.1.0-rc.6",
-    "devsync-ai-linux-arm64": "0.1.0-rc.6",
-    "devsync-ai-darwin-x64": "0.1.0-rc.6",
-    "devsync-ai-darwin-arm64": "0.1.0-rc.6"
+    "devsync-ai-linux-x64": "0.1.0-rc.8",
+    "devsync-ai-linux-arm64": "0.1.0-rc.8",
+    "devsync-ai-darwin-x64": "0.1.0-rc.8",
+    "devsync-ai-darwin-arm64": "0.1.0-rc.8"
   }
 }