Skip to content

fix(studio): correct save failure telemetry - #3499

Merged
miguel-heygen merged 1 commit into
mainfrom
fix/studio-save-failure-signal
Aug 30, 2026
Merged

miguel-heygen merged 1 commit into
mainfrom
fix/studio-save-failure-signal

Conversation

@miguel-heygen

Copy link
Copy Markdown
Collaborator

Summary

Studio save-failure analytics now represent actual persistence failures: expected GSAP direct-edit refusals emit studio:edit_blocked, while code-editor failures use the shared diagnostic path so HTTP status and file context survive.

Repeated identical code-editor failures emit once per five-second burst and become eligible again after a successful save, without changing save timing, retries, or conflict behavior. Studio write identity also remains available on secure contexts that expose crypto.getRandomValues but not crypto.randomUUID.

Tests

  • bun run --cwd packages/studio test — 4,486 passed
  • bun run --cwd packages/studio typecheck
  • bunx oxfmt --check and bunx oxlint on all changed files
  • bunx fallow audit --base origin/main --fail-on-issues

Compound Engineering
Codex

@miguel-heygen
miguel-heygen merged commit 28be8dd into main Aug 30, 2026
45 checks passed
@miguel-heygen
miguel-heygen deleted the fix/studio-save-failure-signal branch August 30, 2026 04:24
@miguel-heygen miguel-heygen mentioned this pull request Aug 30, 2026
3 tasks done
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant