These are produced by the runtime-release workflow / local packaging and
published to GitHub Releases, not committed. The compiled library under
dist/ and dist/src/ stays tracked.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Deployments resolve a deterministic releases/download/runtime-latest/ URL
instead of the mutable /releases/latest/ pointer (which collides with the
human-facing v* release track). Keeps --latest=false so GitHub's "Latest
release" stays on the v* tags. Per-commit runtime-<sha> release retained for
traceability.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The workflow used pnpm install --frozen-lockfile against a stale pnpm-lock.yaml
while the repo migrated to npm (current package-lock.json v3), so it failed and
never published a release -> the deploy's download of
openclaw-multi-session-plugins-runtime-all.tar.gz from releases/latest 404'd.
Switch to npm ci + npm run build and trigger on package-lock.json.
- Resolve critical task-synchronization and configuration-passing issues
- Leverage task-registry, session.store, and refined gateway routing
- Eliminate redundant manual management and enforce a single source of truth for task states
- Ensure proper propagation of expectedArtifactDirs
- Register session.start hook to call prepareXWorkmateArtifacts best-effort
so subsequent export calls have a ready scope.
- Use scope directory birthtime/mtime as a floor for sinceUnixMs when the
scope is already prepared, so files written before export are still
picked up.
- Fall back to scanning params.expectedArtifactDirs (under workspaceRoot)
when no scoped candidates are found, so callers can point at ad-hoc
output directories.
Adds a new gateway method that copies recent outputs from the OpenClaw media
and tmp directories into the current task scope's artifacts directory,
returning a snapshot manifest. XWorkmate Bridge can then call the existing
xworkmate.artifacts.export to hand the snapshot to the XWorkmate APP.
