feat(telemetry): report filesystem failures that are only logged or shown

Merged
RY
2d ago
+703-8

EPERM, EBUSY and similar errors from Windows file locks mostly never reach PostHog: chat turns, AI edits and agent tools show them in the chat, and app delete, pnpm install and workspace cleanup only log them. The one EPERM in PostHog came from the one path that sends exceptions.

Adds fs:operation-failed, sent from those catch sites when the error (or its cause) came from a filesystem call:

  • flow: chat_stream, local_agent, agent_tool, apply_edits, app_delete, pnpm_install or workspace_cleanup; tool for agent tools.
  • code and syscall (EPERM, open).
  • location: app, user_data, temp, program_files, home or other. Sites that know the app pass its folder, so apps outside the apps folder (imported in place) still count as app.
  • in_onedrive, and file_category (node_modules, git, build_output, gitignore, lockfile, package_json, env_file, source, other).

The path itself is never sent. Other errors are ignored, so the chat sites don't report every failed turn. The event skips non-Pro sampling, since the affected users are mostly on free plans. App delete now keeps the original error as cause.

Tests: unit tests for the path classifier (Windows, OneDrive, long-path prefix, POSIX, apps outside the apps folder), real fs errors through the agent's write_file tool and the AI edit apply path. A throwaway integration spike with real permission errors also confirmed the chat stream (the #4980 read-only .gitignore case), app delete and workspace cleanup events. The local agent turn and pnpm install calls are not exercised by any test.

Not covered: failures inside the npm install pnpm child process, which only surface as output text.