## Summary

Stacked on #744. Implements the identity follow-up discussed on #735
(see the "Identity model note" comment there): the engine gains a
CRI-style orchestrator reference, and the runner stops squatting the
engine's `name` slot to carry the control-plane box id.

```text
before                                after
──────                                ─────
runner: WithName(cloudId)             runner: WithExternalRef(cloudId)
engine: name = cloudId (squatted)     engine: external_ref = cloudId
        name unavailable for users            name free for a future
                                              user-facing box name
```

Industry precedent (verified sources):
- CRI `PodSandboxMetadata.uid` — the orchestrator's id travels as a
dedicated metadata field; the runtime mints its own id ([cri-api
api.proto](https://github.com/kubernetes/cri-api/blob/master/pkg/apis/runtime/v1/api.proto),
`message PodSandboxMetadata`)
- ECS agent attaches `com.amazonaws.ecs.task-arn` as a docker label
([docker_task_engine.go](https://github.com/aws/amazon-ecs-agent/blob/master/agent/engine/docker_task_engine.go))
- The caller-supplied-id pattern (OCI runtime spec `create
<container-id>`) applies to stateless executors (runc/firecracker), not
to stateful daemons like this engine — hence a reference field, not id
injection.

## What changed

- **engine**: `BoxOptions.external_ref` (opaque, json-persisted via the
existing config blob — no DB migration; `lookup_box` already scans
configs). Duplicate refs are rejected at create. Lookup order: exact id
→ name → external_ref → id prefix. `BoxInfo` exposes it, omitted when
unset.
- **C SDK**: `boxlite_options_set_external_ref`, `CBoxInfo.external_ref`
(NULL when unset, freed on drop — the leak-count test now expects 5
inner CStrings), header regenerated by the crate build.
- **Go SDK**: `WithExternalRef`, `BoxInfo.ExternalRef`.
- **Node SDK**: field filled with `None` (orchestrator-facing knob; not
exposed in JS options yet).
- **CLI**: `inspect` shows `ExternalRef` only when present; `list`
columns unchanged (nothing empty is rendered).
- **runner**: `WithName(dto.Id)` → `WithExternalRef(dto.Id)`; restart
recovery (`runtime.Get(dto.Id)`) resolves through the external_ref
match.

## Verification

- engine lib tests: 735/735; the new `lookup_box_by_external_ref` test
was verified two-sided (fails with the lookup clause reverted, passes
restored)
- boxlite-c: 55/55
- CLI / Node / Python crates compile; `go vet` clean on `sdks/go` and
`apps/runner/pkg/boxlite` (final cgo link needs the prebuilt
`libboxlite.a`, absent in this worktree)

## Merge order

#743 → #735 → #744 → this PR. Self-contained: reverting is closing this
PR.

## Summary

Stacked on #744. Implements the identity follow-up discussed on #735
(see the "Identity model note" comment there): the engine gains a
CRI-style orchestrator reference, and the runner stops squatting the
engine's `name` slot to carry the control-plane box id.

```text
before                                after
──────                                ─────
runner: WithName(cloudId)             runner: WithExternalRef(cloudId)
engine: name = cloudId (squatted)     engine: external_ref = cloudId
        name unavailable for users            name free for a future
                                              user-facing box name
```

Industry precedent (verified sources):
- CRI `PodSandboxMetadata.uid` — the orchestrator's id travels as a
dedicated metadata field; the runtime mints its own id ([cri-api
api.proto](https://github.com/kubernetes/cri-api/blob/master/pkg/apis/runtime/v1/api.proto),
`message PodSandboxMetadata`)
- ECS agent attaches `com.amazonaws.ecs.task-arn` as a docker label
([docker_task_engine.go](https://github.com/aws/amazon-ecs-agent/blob/master/agent/engine/docker_task_engine.go))
- The caller-supplied-id pattern (OCI runtime spec `create
<container-id>`) applies to stateless executors (runc/firecracker), not
to stateful daemons like this engine — hence a reference field, not id
injection.

## What changed

- **engine**: `BoxOptions.external_ref` (opaque, json-persisted via the
existing config blob — no DB migration; `lookup_box` already scans
configs). Duplicate refs are rejected at create. Lookup order: exact id
→ name → external_ref → id prefix. `BoxInfo` exposes it, omitted when
unset.
- **C SDK**: `boxlite_options_set_external_ref`, `CBoxInfo.external_ref`
(NULL when unset, freed on drop — the leak-count test now expects 5
inner CStrings), header regenerated by the crate build.
- **Go SDK**: `WithExternalRef`, `BoxInfo.ExternalRef`.
- **Node SDK**: field filled with `None` (orchestrator-facing knob; not
exposed in JS options yet).
- **CLI**: `inspect` shows `ExternalRef` only when present; `list`
columns unchanged (nothing empty is rendered).
- **runner**: `WithName(dto.Id)` → `WithExternalRef(dto.Id)`; restart
recovery (`runtime.Get(dto.Id)`) resolves through the external_ref
match.

## Verification

- engine lib tests: 735/735; the new `lookup_box_by_external_ref` test
was verified two-sided (fails with the lookup clause reverted, passes
restored)
- boxlite-c: 55/55
- CLI / Node / Python crates compile; `go vet` clean on `sdks/go` and
`apps/runner/pkg/boxlite` (final cgo link needs the prebuilt
`libboxlite.a`, absent in this worktree)

## Merge order

#743 → #735 → #744 → this PR. Self-contained: reverting is closing this
PR.

…ents (#744)

## Summary

Stacked on #735. The Box entity's identity collapsed there into a single
12-char id; the `boxId` fields on `BoxDto` / the admin overview DTO were
kept only as value mirrors of `id` to avoid touching the API contract
and generated clients in that PR. This PR removes the mirror everywhere:

```text
before (after #735)                 after (this PR)
───────────────────                 ───────────────
entity/DB:   id  ✅ single          unchanged
BoxDto:      id + boxId (same       id only
             value, legacy shape)
admin DTO:   id + boxId mirror      id only
clients:     Box/AdminBoxItem/      boxId field gone (TS + Go)
             Workspace carry boxId
dashboard:   reads .boxId ?? .id    reads .id
```

- API: `BoxDto.boxId`, admin overview `boxId`, dual-id correlation
matching in admin observability — all removed.
- Dashboard: `box-identity` helpers read `.id`; dual-id cache updates
and the uuid-shaped-name special case removed (after the DB rebuild a
box name can never be a uuid).
- Generated clients: regenerated with the repo's own codegen **inside a
disposable BoxLite box** (CI-faithful: Linux + JDK + GNU sed, no host
gofmt drift). Drift is exactly the `boxId` removal on the `Box` /
`AdminBoxItem` / `Workspace` models in the TS and Go clients.
- Untouched on purpose: route/query parameter names like `:boxId` (they
carry the single id), other tables' `boxId` FK column names, and the
analytics `ModelsBoxUsage.boxId` (a real data field, not the mirror).

## Verification

- API jest: 38 suites / 112 tests pass
- Dashboard: `tsc --noEmit` clean against the regenerated client
- Regen ran in a BoxLite box (`boxlite run node:22-bookworm`); output is
byte-for-byte what CI's api-client-drift check regenerates

## Merge order

#743 (remove TS cloud SDK) → #735 (image pipeline + single box identity)
→ this PR.

…main)" (#743) (#751)

Reverts #743. Restores `apps/libs/sdk-typescript` and the dashboard
cloudBox usage to the pre-#743 state (clean `git revert` of ad155d9, no
manual edits).

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **New Features**
* Added TypeScript code snippet support to the Playground alongside
existing Python support.
* Introduced the BoxLite TypeScript SDK (`@boxlite-ai/sdk`), a new
package providing APIs for box management, file operations, git
workflows, code execution, and desktop automation.

* **Refactor**
* Migrated internal dashboard box operations to use the new SDK client
library.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

…oolbox/workspace surfaces and box verbs

- Delete toolbox.deprecated.{controller,service,dto} (68 proxy endpoints).
  Their only real consumer was the TypeScript cloud SDK removed in #743;
  the dashboard Playground/VNC routes that also called them are dark.
- Delete workspace.deprecated.controller + dtos (legacy Daytona alias
  surface, zero consumers).
- Delete createBox/deleteBox/startBox/stopBox from box.controller.
  Box verbs are now owned solely by the Box API contract
  (openapi/box.openapi.yaml), served by boxlite-rest. Cloud-capability
  endpoints (signed URLs, ssh, archive, recover, paginated reads, getBox)
  stay: they consume cloud-only ingredients the engine cannot provide.
- boxlite-rest CreateBoxDto + box.openapi.yaml: add cloud-optional create
  fields (labels/public/auto_stop_interval/auto_delete_interval) so the
  dashboard create form can speak the Box API dialect. Local engine
  servers ignore them (serde drops unknown fields).
- metrics.interceptor: move box-create/start/stop capture from the
  removed /api/box routes to the /api/v1 boxes routes.
- apps/api/Dockerfile: drop the toolbox-api-client COPY (package removed
  later in this branch).