2 Commits

Include renames

Author	SHA1	Message	Date
Nicky LeachandPaperclip	1de105c475	fix(observability): pin the Sentry browser SDK and gate the optional Sentry server peer on the exact version (#12270) ... ## Thinking Path > - Paperclip is the open source app people use to manage AI agents for work. > - Paperclip uses separate server and browser packages for runtime services and the board. > - Sentry integrations need an exact SDK version and safe optional loading. > - A version range can select an SDK that the privacy tests did not audit. > - Missing peer metadata does not describe the optional server SDK contract. > - This pull request pins the browser SDK and gates the optional server SDK on its exact version. > - The benefit is a clear SDK contract with fail-open startup behavior. ## Linked Issues or Issue Description **What happened?** The browser package used the range ^10.71.0, so a lockfile refresh could select a newer SDK. The server loaded @sentry/node dynamically but did not declare its optional peer contract. **Expected behavior** The browser package must use the audited 10.71.0 version. The server must load @sentry/node only when the installed peer matches 10.71.0. The server must start when the optional peer is absent. **Steps to reproduce** 1. Install the project dependencies. 2. Inspect the browser Sentry version and the server package metadata. 3. Start the server without installing @sentry/node. 4. Confirm that the server starts and that the dynamic Sentry bootstrap does not load an unsupported peer version. **Paperclip version or commit** 9c57c0f119 **Deployment mode** Built from source with pnpm dev or pnpm build. **Installation method** Built from source. **Agent adapter(s) involved** Not adapter-specific (core change). **Database mode** Not database-related. ## What Changed - Pin @sentry/browser to exactly 10.71.0 as a UI development dependency. - Declare @sentry/node as an optional server peer dependency at 10.71.0. - Gate the dynamic server bootstrap on the exact peer version. - Add tests for the browser pin, peer metadata, version gate, and fail-open loading. - Document the supported server SDK version. - Keep the lockfile unchanged because the pull request workflow regenerates it for manifest changes. ## Verification - Server tests pass with six expected skips when @sentry/node is absent. - UI tests pass. - The UI build emits the lazy Sentry browser chunk. - git diff --check passes. - GitHub pull request checks must pass after this pull request opens. - Greptile must return a 5/5 score with no open findings. ## Risks The exact version gate prevents Sentry startup when an unsupported SDK version exists. The integration remains optional and fail-open. The lockfile workflow must regenerate the lockfile before frozen downstream jobs run. The label-gated Storybook visual job must not run until it can restore the generated lockfile artifact. ## Model Used OpenAI Codex, GPT-5, tool use and code review support, exact context window details are managed by the execution platform. ## Checklist - [x] I have included a thinking path that traces from project context to this change - [x] I have specified the model used (with version and capability details) - [x] I have checked ROADMAP.md and confirmed this PR does not duplicate planned core work - [x] I have searched GitHub for duplicate or related PRs and linked them above - [x] I have either (a) linked existing issues with Fixes: # / Closes: # / Refs: # OR (b) described the issue in-PR following the relevant issue template - [x] I have not referenced internal/instance-local Paperclip issues or links - [x] My branch name describes the change and contains no internal Paperclip ticket id or instance-derived details - [x] I have run tests locally and they pass - [x] I have added or updated tests where applicable - [x] I have updated relevant documentation to reflect my changes - [x] I have considered and documented any risks above - [x] All Paperclip CI gates are green - [x] Greptile is 5/5 with no open P2s, recommendations, or follow-ups - [x] I will address all Greptile and reviewer comments before requesting merge --------- Co-authored-by: Paperclip <noreply@paperclip.ing>	2026-08-27 07:20:03 -07:00
Nicky LeachandPaperclip	8f1e3cfe24	feat(observability): add opt-in Sentry error monitoring for the server and the browser (#12190) ... ## Thinking Path > - Paperclip is the open source app people use to manage AI agents for work. > - The server and the browser need clear error reports when an operator enables external monitoring. > - Paperclip already uses an opt-in OpenTelemetry pattern for server traces. > - Sentry can provide error reports for both runtime paths when the operator sets one data source name. > - This pull request adds one opt-in Sentry gate for the server and the browser. > - The benefit is faster diagnosis while the default setup sends no Sentry data. ## Linked Issues or Issue Description **What is improved?** Paperclip gains optional error monitoring for server and browser failures. **Subsystem affected** Cross-cutting (server, UI, and shared authentication data). **Current behavior** Paperclip has no built-in Sentry error capture for server failures or browser boundary failures. Operators must inspect local logs and browser tools. **Proposed behavior** When the operator sets `SENTRY_DSN`, the server and authenticated browser use the same Sentry project. When the variable is absent, both paths stay inactive. The server loads Sentry dynamically and fails open when the optional package is absent. **Reason and benefit** Operators can inspect runtime errors in one Sentry project. The default setup remains local and sends no monitoring data. **Breaking changes** None when `SENTRY_DSN` remains unset. Authenticated session responses add the optional `sentryDsn` field. **Additional context** The implementation uses built-in Sentry privacy options. It disables default HTTP context and breadcrumb integrations and keeps `sendDefaultPii` false. ## What Changed - Add an opt-in server Sentry gate with dynamic package loading and fail-open behavior. - Add the Sentry data source name to the authenticated session response. - Add an authenticated browser Sentry gate and React error boundary capture. - Add tests for server, browser, route, and application error paths. - Document activation, installation, privacy settings, capture behavior, and operator controls. ## Verification - Run `npx vitest run server/src/__tests__/sentry.test.ts`. - Run `npx vitest run ui/src/lib/sentry.test.ts`. - Run `npx vitest run server/src/__tests__/auth-routes.test.ts server/src/__tests__/shutdown.test.ts`. - Confirm that the full continuous integration suite passes on this pull request. - Leave `SENTRY_DSN` unset and confirm that the server and browser gates stay inactive. - Set `SENTRY_DSN` and install the optional Sentry packages before a manual capture check. ## Risks The operator controls the Sentry project and accepts the data risk when the operator enables the feature. Error objects can contain messages, stacks, or cause chains with private values. The default configuration sends no data because the feature stays off without `SENTRY_DSN`. A missing optional server package does not stop server boot. ## Model Used OpenAI Codex, GPT-5, with tool use, repository inspection, GitHub CLI operations, and code review support. ## Checklist - [x] I have included a thinking path that traces from project context to this change - [x] I have specified the model used (with version and capability details) - [x] I have checked ROADMAP.md and confirmed this PR does not duplicate planned core work - [x] I have searched GitHub for duplicate or related PRs and linked them above - [x] I have either (a) linked existing issues with `Fixes: #` / `Closes #` / `Refs #` OR (b) described the issue in-PR following the relevant issue template - [x] I have not referenced internal/instance-local Paperclip issues or links (only public GitHub `#NNN` / `github.com/paperclipai/paperclip` URLs) - [x] My branch name describes the change (e.g. `docs/...`, `fix/...`) and contains no internal Paperclip ticket id or instance-derived details - [x] I have run tests locally and they pass - [x] I have added or updated tests where applicable - [x] I have updated relevant documentation to reflect my changes - [x] I have considered and documented any risks above - [x] All Paperclip CI gates are green - [x] Greptile is 5/5 with no open P2s, recommendations, or follow-ups - [x] I will address all Greptile and reviewer comments before requesting merge --------- Co-authored-by: Paperclip <noreply@paperclip.ing>	2026-08-26 11:15:45 -07:00