* origin/master: (57 commits)
fix(adapter-utils): extend the duplex fail-closed run disposition to the CLI lane (#11966)
fix(recovery): stop automatic stranded-task takeovers (#11961)
feat(sandbox): add the duplex bridge broker, gated transport selection, and fixed observability (#11769)
Drop the mission step from the wizard arc (#11935)
fix(runtime): guard empty Bash 3.2 array expansion (#11891)
chore(lockfile): refresh pnpm-lock.yaml (#11915)
feat(commitperclip): surface the Co-Authored-By trailers a squash merge needs (#11498)
Rebuild the onboarding agent arc on the prototype's step design (#11905)
fix(workspaces): read process cwd on macOS so port-owner adoption works (#11763)
fix(workspaces): attach PR preparation to existing branches (#11703)
fix(grok-local): stop defaulting --permission-mode to dontAsk (#11898)
Fix remote-only workspace base refs and pre-adapter retry loops (#11892)
feat(environments): refer to the managed default environment by name, not the sandbox driver key (#11838)
test(server): cover buffered duplex chunk drain after a late listener bind (#11865)
fix(server,ui,claude-local): verify auth on the adapter Test lane and enforce managed-sandbox tenant binding (#11810)
chore(lockfile): refresh pnpm-lock.yaml (#11867)
fix(kimi): align package with Node 24 policy (#11890)
feat(ui): rename "Agent mode" to "Auto mode" and show full work-mode labels (#11866)
fix(build): enforce Node 24 across Paperclip (#11792)
fix(server): end the duplex route on the pre-bind bounds when frames arrive before the bind (#11860)
...
# Conflicts:
# Dockerfile
# packages/db/src/migrations/meta/0226_snapshot.json
# packages/db/src/migrations/meta/_journal.json
# pnpm-lock.yaml
# server/package.json
# server/src/routes/agents.ts
# server/src/services/heartbeat.ts
# server/src/services/issues.ts
# server/src/services/recovery/service.ts
# ui/package.json
# ui/src/adapters/transcript.test.ts
# ui/src/components/TaskChatThread.test.tsx
# ui/src/components/TaskChatThread.tsx
# ui/src/components/task-chat/TaskChatTurn.tsx
# ui/src/index.css
# ui/src/pages/Agents.tsx
## Thinking Path
> - Paperclip is the open source app people use to manage AI agents for
work
> - The server emits OpenTelemetry spans so operators can trace agent
work
> - Each span needs a service version that identifies the code that
produced it
> - The current service version comes from a static environment value
and can become stale after a rebuild
> - This pull request records the built commit and resolves the service
version from the build stamp, runtime Git, the environment, or an
unknown fallback
> - The benefit is trace data that identifies the correct built commit
during development and deployment
## Linked Issues or Issue Description
**What happened?**
The server used a static `OTEL_SERVICE_VERSION` value for every
OpenTelemetry span. Rebuilds could produce traces with an old commit
value.
**Expected behavior**
The server should report the built commit when a build stamp exists. It
should use runtime Git, the environment value, or `unknown` as fallback.
**Steps to reproduce**
1. Set `OTEL_SERVICE_VERSION` to an old commit value.
2. Build the server at a different commit.
3. Start the server and inspect the OpenTelemetry service version.
4. Confirm that the built commit takes precedence over the old
environment value.
## What Changed
- Add a build script that writes the short Git commit to
`dist/build-info.json`.
- Resolve `service.version` from the build stamp, runtime Git, the
environment, or `unknown`.
- Log the resolved service version once during server startup.
- Add tests for the resolution order and safe behavior without Git.
- Document the resolution order in `doc/observability.md`.
## Verification
- `pnpm --filter @paperclipai/server build`
- `npx vitest run server/src/__tests__/service-version.test.ts`
- `pnpm --filter @paperclipai/server typecheck`
- Confirm that the build stamp contains the short commit.
- Confirm that the stamp wins over the environment value.
- Confirm that a build without Git exits successfully without a stamp.
## Risks
The server now prefers the built commit over `OTEL_SERVICE_VERSION`. A
build without Git uses the existing environment value or `unknown`. The
change needs no schema migration and has a single-commit rollback path.
## Model Used
OpenAI Codex, GPT-5, tool use and code execution. The runtime does not
expose the context window size or reasoning mode.
## Checklist
- [x] I have included a thinking path that traces from project context
to this change
- [x] I have specified the model used (with version and capability
details)
- [x] I have checked ROADMAP.md and confirmed this PR does not duplicate
planned core work
- [x] I have searched GitHub for duplicate or related PRs and linked
them above
- [x] I have either (a) linked existing issues with `Fixes: #` / `Closes
#` / `Refs #` OR (b) described the issue in-PR following the relevant
issue template
- [x] I have not referenced internal/instance-local Paperclip issues or
links (only public GitHub `#NNN` / `github.com/paperclipai/paperclip`
URLs)
- [x] My branch name describes the change (e.g. `docs/...`, `fix/...`)
and contains no internal Paperclip ticket id or instance-derived details
- [x] I have run tests locally and they pass
- [x] I have added or updated tests where applicable
- [x] I have updated relevant documentation to reflect my changes
- [x] I have considered and documented any risks above
- [x] All Paperclip CI gates are green
- [x] Greptile is 5/5 with no open P2s, recommendations, or follow-ups
- [x] I will address all Greptile and reviewer comments before
requesting merge
---------
Co-authored-by: Paperclip <noreply@paperclip.ing>
Keep the clean-consumer Runner D package out of first-publish CI enrollment while bundling its compiled runtime into the released server artifact.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
The dev-watch script was importing tsx via the internal path
'tsx/dist/cli.mjs', which is an undocumented implementation detail
that broke when tsx updated its internal structure.
Switched to the stable public export 'tsx/cli' which is the
officially supported entry point and won't break across versions.
Dotta