trace: cctrace >=0.41 trace store lives in the container home — persist it before bumping the pin

[lroolle]

Description

deva pins cctrace 0.40.0. cctrace 0.41 moved traces out of ./.cctrace (workspace, survives the container) into the trace store ~/.local/share/cctrace/traces/<project-key>/ (CCTRACE_DATA_DIR / --data-dir / --dir move it). Inside a deva container that is /home/deva/.local/share/cctrace, which deva does not mount, so with a newer pin traces die with --rm containers and are invisible to the host / other containers. The run registry already lives there too.

Blocks the make versions-up bump of CCTRACE_VERSION (currently 0.40.0 -> 0.43.0 in the dirty versions.env).

Type

• Enhancement

Details

Decide where the store lives and wire it on every traced launch:

• simplest: -e CCTRACE_DATA_DIR=<workspace>/.cctrace (or pass --dir) to keep today's workspace-local semantics; or
• mount a host-side ~/.local/share/cctrace into the container so the registry, dashboard and /s/ links work across containers (this is what the store was designed for — shared dir across containers).

Also stale in the same area: --trace is still rejected for opencode ("cctrace has no opencode profile (#89)") but cctrace 0.38 shipped the opencode client; and docs/advanced-usage.md still says traces land in .cctrace/.

Related Files

agents/shared_auth.sh, agents/claude.sh, agents/codex.sh, agents/grok.sh, agents/kimi.sh, agents/opencode.sh, docker-entrypoint.sh, docs/advanced-usage.md, versions.env

Test Plan

• deva.sh claude --trace --rm with the bumped pin: trace readable on the host after the container exits
• reattach to a traced container finds prior turns (cctrace view <sid>)
• docker-entrypoint.sh CA install still finds the key under the chosen data dir