appback-remoteagent 0.15.5 → 0.15.6

package/dist/services/bridge-service.js

@@ -4,9 +4,10 @@ import os from "node:os";
 import path from "node:path";
 import { stopSpawnedExecution } from "../adapters/windows-shell.js";
 const MODEL_PRESETS = {
-    codex: ["gpt-5.5", "gpt-5.4", "gpt-5.4-mini", "gpt-5.2", "gpt-5.1-codex-max"],
+    codex: ["gpt-5.6-sol", "gpt-5.6-terra", "gpt-5.6-luna", "gpt-5.6", "gpt-5.5", "gpt-5.4", "gpt-5.4-mini", "gpt-5.2", "gpt-5.1-codex-max"],
     claude: ["sonnet", "opus", "haiku"],
 };
+const DEFAULT_CODEX_MODEL = "gpt-5.6-sol";
 export class BridgeService {
     store;
     adapters;
@@ -59,7 +60,7 @@ export class BridgeService {
             cwd: workspace,
             pairedAt: new Date().toISOString(),
             sessionId: undefined,
-            model: provider === "codex" ? "gpt-5.5" : "sonnet",
+            model: this.defaultModelFor(provider),
             sandboxMode: provider === "codex" ? this.defaultCodexSandboxMode : undefined,
             lastUsedAt: undefined,
         }, workspace);
@@ -94,7 +95,7 @@ export class BridgeService {
             cwd: workspace,
             pairedAt: new Date().toISOString(),
             sessionId: normalizedSessionId,
-            model: existing?.session[provider]?.model ?? (provider === "codex" ? "gpt-5.5" : "sonnet"),
+            model: existing?.session[provider]?.model ?? this.defaultModelFor(provider),
             sandboxMode: provider === "codex"
                 ? (existing?.session[provider]?.sandboxMode ?? this.defaultCodexSandboxMode)
                 : undefined,
@@ -655,7 +656,7 @@ export class BridgeService {
         return next?.trim() || current || this.defaultWorkspace;
     }
     defaultModelFor(provider) {
-        return provider === "codex" ? "gpt-5.5" : "sonnet";
+        return provider === "codex" ? DEFAULT_CODEX_MODEL : "sonnet";
     }
     describeEffectiveAccess(session) {
         if (!session.codex) {

package/docs/OPERATIONS.md

@@ -9,9 +9,17 @@ RemoteAgent production is operated from one canonical Git history:
 - production package: `appback-remoteagent`
 - branch used for production releases: `main`
 
-Do not treat stale server paths or duplicate worktrees as authoritative.
+Use `origin/main` as the authoritative source.
 Code changes should be committed and pushed to `origin/main`, published to npm, and then server 30/26 should be updated from that npm version.
-Installing a local tarball directly on a server is an emergency hotfix only; it is not a completed production release until the same version is published to npm and both targets are reconciled to that npm version.
+Production release commands are:
+
+```bash
+npm run release:publish
+npm run release:deploy -- <version> all
+```
+
+Local tarball installation is an emergency runtime restoration path.
+The production release is completed by publishing the same version to npm and running `npm run release:deploy -- <version> all`.
 
 ## Product shape in operations
 
@@ -33,7 +41,7 @@ Current production bot ownership is intentionally split:
 - server 30: RemoteAgent production bots
 - local machine 21: local-only bot runtime
 
-Do not run the same Telegram bot token from multiple runtimes at the same time.
+Assign each Telegram bot token to one runtime at a time.
 Bot polling conflicts are treated as incidents, not harmless warnings.
 
 When a runtime has several configured Telegram bots, polling pressure can become operationally visible.
@@ -135,7 +143,14 @@ If a temporary branch is unavoidable, merge it back to `main`, push it, and depl
 
 A task is not done until commit and push both happened.
 A production deployment is not done until server 30 and server 26 are running the published npm version and the runtime path has been verified.
-If npm publish fails with `403`, do not keep retrying or switch to source deployment. Confirm the npm token has publish rights for the unscoped `appback-remoteagent` package, then publish. See `docs/RELEASING.md`.
+If npm publish returns `403`, use a publish-capable npm token for the unscoped `appback-remoteagent` package and run:
+
+```bash
+source ~/.config/remoteagent/npm-token.env
+npm run release:publish
+```
+
+See `docs/RELEASING.md`.
 
 See `docs/RELEASING.md` for the detailed versioning rules.
 

package/docs/RELEASING.md

@@ -1,187 +1,176 @@
-# Releasing
+# RemoteAgent Release Runbook
 
-## Versioning rule
+This runbook is command-first. Use the scripts below as the release interface.
 
-RemoteAgent uses semantic versioning for every production deployment:
+## 1. Bump Version
 
-- `MAJOR`: breaking command changes, storage/runtime contract changes, or migrations that can break an existing installation
-- `MINOR`: new user-facing capabilities, new commands, new adapters, or non-breaking workflow expansion
-- `PATCH`: bug fixes, reliability improvements, security fixes, text-only corrections, and non-breaking maintenance
+Patch release:
 
-Do not deploy production changes without bumping the package version first.
-
-## Decision guide
-
-Use `PATCH` when the behavior is supposed to stay the same but gets safer or more correct.
-Use `MINOR` when the owner can do something new after the release without needing migration.
-Use `MAJOR` when an older installation, script, or user workflow would need active adjustment.
+```bash
+npm run release:version -- patch
+```
 
-When unsure between two levels, choose the higher one and explain why in the commit message.
+Minor release:
 
-## Required release flow
+```bash
+npm run release:version -- minor
+```
 
-A release is only considered complete when all of the following are done in order:
+Major release:
 
-1. Choose the release scope: `patch`, `minor`, or `major`
-2. Bump the version in `package.json` and `package-lock.json`
-3. Run `npm run check`
-4. Run `npm run build`
-5. Commit the completed work
-6. Push `main` to `origin/main`
-7. Publish `appback-remoteagent@<version>` to npm using a token/account that is proven to have publish rights for this unscoped package
-8. Install that exact npm version on server 30 and server 26
-9. Restart `remoteagent.service` on each target if runtime code changed
-10. Verify the relevant runtime path, logs, or Telegram behavior on each target
+```bash
+npm run release:version -- major
+```
 
-If commit or push is missing, the work is not done.
-If server 30 or server 26 is not running the published npm version, the production deployment is incomplete.
+Versioning guide:
 
-## Commands
+- `patch`: reliability fixes, bug fixes, text fixes, safe maintenance
+- `minor`: new commands, new user-facing behavior, new non-breaking workflow
+- `major`: storage/runtime contract changes or breaking command behavior
 
-Version bump helpers:
+## 2. Validate
 
 ```bash
-./scripts/bump-version.sh patch
-./scripts/bump-version.sh minor
-./scripts/bump-version.sh major
+npm run check
+npm run build
 ```
 
-Equivalent npm shortcuts:
+## 3. Commit And Push
 
 ```bash
-npm run version:patch
-npm run version:minor
-npm run version:major
+git status --short
+git add -A
+git commit -m "Release <version>"
+git push origin main
 ```
 
-Typical local release sequence:
+Example:
 
 ```bash
-./scripts/bump-version.sh patch
-npm run check
-npm run build
-git status
-git add -A
-git commit -m "Release 0.12.3"
-git push origin main
-npm pack
+git commit -m "Release 0.15.5"
 ```
 
-## npm publish procedure
+## 4. Publish To npm
 
-Use this package-specific path for `appback-remoteagent`.
+Load the npm token when the shell has not loaded it yet:
 
-Direct `npm publish` is blocked by `prepublishOnly`.
-The only normal publish command is:
+```bash
+source ~/.config/remoteagent/npm-token.env
+```
+
+Publish:
 
 ```bash
 npm run release:publish
 ```
 
-Do not publish this package with the machine 21 `21token`.
-That token can authenticate as `appbackhub`, but it does not currently have publish rights for the unscoped `appback-remoteagent` package.
-It fails at publish time with:
+The publish script performs:
 
-```text
-403 Forbidden - You may not perform that action with these credentials.
-```
+- clean working tree check
+- `npm whoami`
+- `npm owner ls appback-remoteagent`
+- `npm run check`
+- `npm run build`
+- `npm pack`
+- guarded `npm publish`
+- registry version verification
+
+The package publish entrypoint is `npm run release:publish`.
+`scripts/prepublish-guard.mjs` routes manual publish attempts back to that entrypoint.
+
+## 5. Deploy Published Version
 
-Before publishing, always verify both identity and package ownership:
+Deploy to server 30:
 
 ```bash
-npm whoami
-npm owner ls appback-remoteagent
+npm run release:deploy -- <version> 30
 ```
 
-Authentication alone is not enough.
-If `npm whoami` works but `npm publish` returns `403`, stop and get a publish-capable npm token instead of retrying with the same token.
+Deploy to server 26:
+
+```bash
+npm run release:deploy -- <version> 26
+```
 
-The guarded registry publish path is:
+Deploy to both production targets:
 
 ```bash
-npm run release:publish
-npm view appback-remoteagent version
+npm run release:deploy -- <version> all
 ```
 
-If registry caching briefly returns the previous version after publish, wait a few seconds and rerun `npm view appback-remoteagent version` before installing to servers.
+Example:
 
-## Emergency tarball install
+```bash
+npm run release:deploy -- 0.15.5 all
+```
 
-An emergency tarball install is allowed only to restore a broken runtime when npm publish is blocked.
-It is not a completed release and must be reported as a temporary hotfix.
+The deploy script performs:
 
-Rules:
+- npm registry version check for `appback-remoteagent@<version>`
+- server 30 npm install, install hook, systemd restart, version/log verification
+- server 26 npm install, install hook, user-process restart, version/log verification
 
-- do not call it "npm deployed" or "released"
-- do not delete runtime state
-- do not use source checkout deployment
-- confirm no active provider process is running before restart
-- install the exact local package tarball with `npm install -g /tmp/appback-remoteagent-<version>.tgz`
-- follow up by publishing the same version to npm once a publish-capable token is available
+## 6. Verify
 
-Emergency server 30 flow:
+Registry:
 
 ```bash
-VERSION=0.14.0
-npm pack
-scp appback-remoteagent-$VERSION.tgz au2223@192.168.0.30:/tmp/
-ssh au2223@192.168.0.30 "VERSION=$VERSION bash -s" <<'REMOTE'
-set -euo pipefail
-export PATH="/home/au2223/.local/bin:/home/au2223/.nvm/versions/node/v22.22.0/bin:$PATH"
-pgrep -af 'codex|claude' || true
-npm install -g "/tmp/appback-remoteagent-$VERSION.tgz"
-remoteagent-install
-sudo -n systemctl restart remoteagent
-systemctl is-active remoteagent
-node -p 'require("/home/au2223/.nvm/versions/node/v22.22.0/lib/node_modules/appback-remoteagent/package.json").version'
-journalctl -u remoteagent --since '2 minutes ago' --no-pager
-REMOTE
-rm -f appback-remoteagent-$VERSION.tgz
+npm view appback-remoteagent version
 ```
 
-## Target deployment sequence
-
-Server 30 uses a systemd service:
+Server 30:
 
 ```bash
-VERSION=0.14.0
-ssh au2223@192.168.0.30 "VERSION=$VERSION bash -s" <<'REMOTE'
-set -euo pipefail
+ssh au2223@192.168.0.30 'bash -lc '"'"'
 export PATH="/home/au2223/.local/bin:/home/au2223/.nvm/versions/node/v22.22.0/bin:$PATH"
-npm install -g appback-remoteagent@$VERSION
-/home/au2223/.nvm/versions/node/v22.22.0/bin/remoteagent-install
-sudo -n systemctl restart remoteagent
 systemctl is-active remoteagent
-node -p 'require("/home/au2223/.nvm/versions/node/v22.22.0/lib/node_modules/appback-remoteagent/package.json").version'
-journalctl -u remoteagent --since '2 minutes ago' --no-pager
-REMOTE
+node -p "require(\"/home/au2223/.nvm/versions/node/v22.22.0/lib/node_modules/appback-remoteagent/package.json\").version"
+journalctl -u remoteagent --since "5 minutes ago" --no-pager | tail -80
+'"'"''
 ```
 
-Do not run `sudo npm install -g` on server 30. The global RemoteAgent package is installed under
-`/home/au2223/.nvm/versions/node/v22.22.0`; only the `systemctl restart remoteagent` step needs sudo.
-Runtime state remains in `/home/au2223/.remoteagent` and must not be deleted during npm upgrades.
-
-Server 26 currently uses user-level start/stop scripts, not a systemd `remoteagent.service`:
+Server 26:
 
 ```bash
-VERSION=0.14.0
-ssh ospadmin@192.168.0.26 "VERSION=$VERSION bash -s" <<'REMOTE'
-set -euo pipefail
-npm install -g appback-remoteagent@$VERSION
-remoteagent-install
-~/.remoteagent/stop-remoteagent.sh || true
-sleep 2
-~/.remoteagent/start-remoteagent.sh
-sleep 3
+ssh ospadmin@192.168.0.26 'bash -lc '"'"'
+npm list -g appback-remoteagent --depth=0
 pgrep -af "appback-remoteagent/dist/index.js"
 tail -80 ~/.remoteagent/logs/agent.log
-REMOTE
+'"'"''
 ```
 
-## Other Runtime Follow-up
+## Release 0.15.5
+
+Date: 2026-07-08
 
-Server 30 and server 26 are production runtime targets.
-Machine 21 or any other host should be updated only when it intentionally runs a separate RemoteAgent service.
+Changes:
 
-At minimum, the operator should run the install/update flow again and verify the process comes back up cleanly.
-For npm installs, the package contains `dist/`, so the target machine should not need a repository checkout or a separate manual build step.
+- Telegram file attachment download now writes to `.part` first.
+- Telegram file attachment download resumes partial files with `curl -C -`.
+- Telegram file attachment download retries up to 4 attempts.
+- Download timeout changed from one 60-second attempt to resumable 120-second attempts.
+- npm publish flow is guarded by `prepublishOnly`.
+- Standard publish command is `npm run release:publish`.
+- Standard deploy command is `npm run release:deploy -- <version> <30|26|all>`.
+
+Validated:
+
+```bash
+npm run check
+npm run build
+npm run release:publish
+npm run release:deploy -- 0.15.5 all
+```
+
+Published:
+
+```text
+appback-remoteagent@0.15.5
+```
+
+Runtime targets:
+
+```text
+server 30: 0.15.5 active
+server 26: 0.15.5 running
+```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "appback-remoteagent",
-  "version": "0.15.5",
+  "version": "0.15.6",
   "description": "Personal installable session server for continuing local AI work across PC and Telegram",
   "license": "MIT",
   "type": "module",
@@ -21,10 +21,9 @@
     "selftest:telegram": "npm run build && node scripts/selftest-telegram-update.mjs",
     "prepare": "npm run build",
     "prepublishOnly": "node scripts/prepublish-guard.mjs",
+    "release:version": "bash scripts/release-version.sh",
     "release:publish": "bash scripts/release-publish.sh",
-    "version:patch": "npm version --no-git-tag-version patch",
-    "version:minor": "npm version --no-git-tag-version minor",
-    "version:major": "npm version --no-git-tag-version major"
+    "release:deploy": "bash scripts/release-deploy.sh"
   },
   "dependencies": {
     "dotenv": "^16.6.1",

package/scripts/prepublish-guard.mjs

@@ -5,15 +5,12 @@ if (process.env.REMOTEAGENT_PUBLISH_GUARD_OK === "1") {
 }
 
 console.error([
-  "Direct npm publish is blocked for appback-remoteagent.",
+  "RemoteAgent publishes through the guarded release command.",
   "",
-  "Use the documented release path instead:",
+  "Command:",
   "  npm run release:publish",
   "",
-  "Reason:",
-  "- direct publish has repeatedly used the wrong npm token",
-  "- appback-remoteagent must be published only through the guarded script",
-  "- emergency tarball installs are not completed releases",
+  "This command checks the working tree, npm identity, package owner, build, pack, publish, and registry version.",
 ].join("\n"));
 
 process.exit(1);

package/scripts/release-deploy.sh

@@ -0,0 +1,79 @@
+#!/usr/bin/env bash
+set -euo pipefail
+
+usage() {
+  echo "Usage: npm run release:deploy -- <version> <30|26|all>" >&2
+  echo "Example: npm run release:deploy -- 0.15.5 all" >&2
+}
+
+if [[ $# -ne 2 ]]; then
+  usage
+  exit 1
+fi
+
+VERSION="$1"
+TARGET="$2"
+
+if [[ ! "$VERSION" =~ ^[0-9]+\.[0-9]+\.[0-9]+$ ]]; then
+  usage
+  exit 1
+fi
+
+case "$TARGET" in
+  30|26|all)
+    ;;
+  *)
+    usage
+    exit 1
+    ;;
+esac
+
+PACKAGE_NAME="appback-remoteagent"
+REGISTRY_VERSION="$(npm view "$PACKAGE_NAME@$VERSION" version)"
+if [[ "$REGISTRY_VERSION" != "$VERSION" ]]; then
+  echo "Registry version check failed for $PACKAGE_NAME@$VERSION" >&2
+  exit 1
+fi
+
+deploy_30() {
+  ssh au2223@192.168.0.30 "VERSION=$VERSION bash -s" <<'REMOTE'
+set -euo pipefail
+export PATH="/home/au2223/.local/bin:/home/au2223/.nvm/versions/node/v22.22.0/bin:$PATH"
+npm install -g "appback-remoteagent@$VERSION"
+remoteagent-install
+sudo -n systemctl restart remoteagent
+sleep 5
+systemctl is-active remoteagent
+node -p 'require("/home/au2223/.nvm/versions/node/v22.22.0/lib/node_modules/appback-remoteagent/package.json").version'
+journalctl -u remoteagent --since '1 minute ago' --no-pager | tail -80
+REMOTE
+}
+
+deploy_26() {
+  ssh ospadmin@192.168.0.26 "VERSION=$VERSION bash -s" <<'REMOTE'
+set -euo pipefail
+export PATH="$HOME/.local/bin:$PATH"
+npm install -g "appback-remoteagent@$VERSION"
+remoteagent-install
+~/.remoteagent/stop-remoteagent.sh || true
+sleep 2
+~/.remoteagent/start-remoteagent.sh
+sleep 5
+npm list -g appback-remoteagent --depth=0
+pgrep -af 'appback-remoteagent/dist/index.js'
+tail -80 ~/.remoteagent/logs/agent.log
+REMOTE
+}
+
+case "$TARGET" in
+  30)
+    deploy_30
+    ;;
+  26)
+    deploy_26
+    ;;
+  all)
+    deploy_30
+    deploy_26
+    ;;
+esac

package/scripts/release-version.sh

@@ -0,0 +1,27 @@
+#!/usr/bin/env bash
+set -euo pipefail
+
+usage() {
+  echo "Usage: npm run release:version -- <patch|minor|major>" >&2
+  echo "Example: npm run release:version -- patch" >&2
+}
+
+if [[ $# -ne 1 ]]; then
+  usage
+  exit 1
+fi
+
+case "$1" in
+  patch|minor|major)
+    ;;
+  *)
+    usage
+    exit 1
+    ;;
+esac
+
+ROOT="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
+cd "$ROOT"
+
+npm version --no-git-tag-version "$1"
+node -p "'RemoteAgent version is now ' + require('./package.json').version"

package/scripts/bump-version.sh

@@ -1,23 +0,0 @@
-#!/usr/bin/env bash
-set -euo pipefail
-
-if [ $# -ne 1 ]; then
-  echo "Usage: $0 <patch|minor|major>" >&2
-  exit 1
-fi
-
-case "$1" in
-  patch|minor|major)
-    ;;
-  *)
-    echo "Release type must be one of: patch, minor, major" >&2
-    exit 1
-    ;;
-esac
-
-ROOT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
-export PATH="$HOME/.local/bin:$PATH"
-cd "$ROOT_DIR"
-
-npm version --no-git-tag-version "$1"
-node -p "'RemoteAgent version is now ' + require('./package.json').version"