0.3.4

0.3.4 — 2026-09-03

Patch release, no behavior change beyond bug fixes. Fixed Issue #110
(cosmetic LIVE_PARENT jq bug in scripts/verify-repo-identity.sh —
gh repo view --json parent never returns .parent.nameWithOwner; the
fork-detected warning now correctly names the real parent repo instead
of printing an empty string). Fixed Issue #107 (the devcontainer
template's empty-workspace bootstrap left its inner Coder Agent stuck
timeout/never connected — the nested devcontainer container couldn't
resolve host.docker.internal since neither Coder nor its own
--add-host=...:host-gateway point it at the real Coder server; the
bootstrap script now resolves and pins the outer container's real IP as
a literal --add-host runArg). Both fixes were live-verified end to end
against the real running stack (before/after coder show states, no
mocks) — see PR #112 and PR #113. Filed Issue #114 as a follow-up: the
same host.docker.internal gap also affects a repo-provided
devcontainer.json (not just the bootstrap-generated one), reproduced
live against the real tbrandenburg/cade repo's own .devcontainer/;
not yet fixed.

0.3.2

Patch release. Fixed Issue #103 (srt sandbox policy silently failed
OPEN — empty, unrestricted policy — whenever repo_url pointed at a repo
without agent-host/srt-settings.json; the platform's default policy is
now baked into the workspace image at /etc/cade/srt-settings.default.json
and used as a fallback). Genericized repo_url across all 4 Coder
templates (Issue #104): defaults to empty (bring-your-own-project)
instead of cade's own repo, with a real empty-workspace bootstrap path
added for devcontainer. Live-verified (Issue #105) that the existing
manual github_token/GIT_ASKPASS mechanism successfully clones private
github.com repos on docker-workspace and agent-workspace. Added a
canonical REPO_SLUG/ASSUMED_VISIBILITY source of truth plus a
warn-only drift detector wired into make doctor (Issue #102).

See PR #106 for full live E2E evidence.

Known open follow-up: Issue #107 (devcontainer empty-workspace
bootstrap's inner Coder Agent connect timeout).

0.3.0

Per-workspace agentic-session sandboxing/bridging, dashboard-app tile
integrations (Temporal, omnigent, JupyterLab, Node-RED), Coder-API-driven
persistent-workspace orchestration, and a round of live-verified
host/template hardening fixes. See VERSION.md for the full changelog.

0.2.0

0.2.0 — 2026-08-30

Coder AI integration and CI agent automation, plus sandboxing/hardening
fixes discovered along the way. Highlights since 0.1.0:

• Coder Agents integration: AI providers/models reconciler
  (make ai-bootstrap/make ai-token/make verify-ai), MCP wiring, and
  a new agent-workspace Coder template with OSS boundary egress
  control (Issue #13; explored further in Issue #16).
• GitHub external auth (CODER_EXTERNAL_AUTH_0_*) and a real
  .github/workflows/agent-chat.yml CI workflow that lets a
  agent-chat-labeled GitHub issue drive a Coder Agents chat and post
  results back to GitHub (Issue #17).
• Resolved the long-standing srt/bwrap unprivileged-userns sandbox
  failure with scoped seccomp+AppArmor host security profiles, verified
  live end-to-end including enforcement denial (Issue #23).
• Replaced the devcontainer template's docker-outside-of-docker design
  with per-workspace nested Docker-in-Docker, per Coder's own reference
  guidance (Issues #5/#6).
• Build/governance hardening: OPA build.authz gate for
  run_build_command, templates-push Makefile target, CACERT support
  for corporate TLS-intercepting proxies, print-URLs UX, and assorted
  README/docs fixes (Issues #8-#10, #12).
• Rebranded devenv-cloud -> cade (Continuous Agentic Development
  Environment) (#3).

See AGENTS.md's "Lessons Learned" section and the referenced
milestone/issue docs (docs/ai-coder.md, docs/security.md) for full
evidence of each item above.

0.1.0

First release of devenv-cloud.

• All 16 milestones across 5 phases delivered and evidenced
• Final E2E acceptance and all three durability boundary tests verified against the real stack
• Full backup/restore cycle verified for the required categories

Known limitations are documented in the repository README and security documentation.