docs: daily update 2026-08-05 — release v4.179.2

[deco-cms]

Release covered

v4.179.1...v4.179.2 (compare: v4.179.1...v4.179.2)

Note: This PR depends on #5723 (docs/auto-update-2026-08-05-release-4.179.0), which was still open at run time. This branch is based on that PR's HEAD to avoid conflicts — please merge #5723 first.

Commits reviewed

Warranted doc changes:

• 7286fe2c1 fix(decopilot): make automation model-permission failures permanent (fix(decopilot): make automation model-permission failures permanent #5724) — automations that hit a disallowed-model error now get permanently deactivated with a clear reason instead of retrying and failing forever.

Skipped (no user-facing impact):

• e9a0dffa4 fix(task-board): release a reviewer's claim if its dispatch failed (fix(task-board): release a reviewer's claim if its dispatch failed #5728) — internal bug fix, task-board reviewer dispatch isn't a documented workflow.
• 8edb8f7b0 fix(connection): clear fetch-tools timeout timers instead of leaking them (fix(connection): clear fetch-tools timeout timers instead of leaking them #5726) — internal resource-leak fix, no behavior change visible to users.
• adda523fd refactor(task-board): dedupe claimConflictResolution/claimReviewChangesBounce (refactor(task-board): dedupe claimConflictResolution/claimReviewChangesBounce #5725) — pure internal refactor.
• e47eba7e5 [chore]: bump homebrew cask to 4.179.1 — bot/release chore.
• a22e754e4 [release]: bump changed workspace versions — release bot commit (version bump only).

Files changed

• apps/docs/client/src/content/deco-studio/en/studio/automations.mdx — added a sentence to the Limits section noting that automations are also auto-deactivated when a run hits an unrecoverable error (e.g. their configured model becomes disallowed for their role), with the reason surfaced in Monitoring.
• apps/docs/client/src/content/deco-studio/pt-br/studio/automations.mdx — matching translation.

pt-br content was auto-translated following the existing file's terminology conventions (product terms and UI labels kept in English).

Consistency notes

• Checked ai-providers.mdx: already mentions "Model availability may be filtered by your organization's model permission settings" — consistent with this change, no update needed.
• Checked concepts.mdx and overview.mdx: no mention of automation deactivation reasons; no contradiction, no change made.
• Checked monitoring.mdx: generically covers failure visibility; no specific claim to update.

---

Summary by cubic

Update docs for v4.179.2: adds Task Board coverage, CMS Fast Preview and field-description tooltips, the opt‑in claude-code sandbox harness with BYO Claude subscription, and clarifies automation deactivation on unrecoverable errors. Includes self‑hosting changes (auth via env vars, sandbox daemon telemetry, and compose/Kubernetes updates).

• New Features

  • Task Board: kanban flow with reviewers + auto‑merge + ship‑to‑prod, threaded comments, report‑finding dismissal, and multi‑repo behavior.
  • Agents & CMS: “Files and skills” with a 25MB per‑file cap; CMS settings reorg with Fast Preview; option to show field descriptions as tooltips; sandbox repo picker shows forks and requires installation access.
  • Hosted runs: documented claude-code sandbox harness (opt‑in per org); link a personal Claude Pro/Max under “Your Claude subscription” for sandbox claude-code runs, with automatic fallback to the org credential.
  • Guardrails & UX: connections reject private/internal URLs; “Requires action” is set only for pending tool approvals/user_ask; Studio Native adds coding‑agent terminals and optional local worktree reclaim on archive.
  • Automations: runs that hit unrecoverable errors (e.g., model permission) auto‑deactivate with a clear reason in Monitoring.

• Migration

  • Auth (self‑hosting): configuration is now AUTH_* environment variables only (email/password toggle, Google/GitHub, magic link, email OTP); no auth-config.json.
  • Kubernetes: sandbox daemon exposes optional OTLP metrics; sandbox image is studio-sandbox-go only; telemetry requires a collector ClusterIP; architecture docs simplified to edge + cloud tiers.
  • Docker Compose: STUDIO_TOPUP_FEE_PERCENT is configurable (set 0 to waive fees); updated secrets guidance.

^{Written for commit 395905d. Summary will update on new commits.}