move tracing to dependencies

[Brendonovich]

Summary by CodeRabbit

• New Features
  • No user-facing features added.
• Refactor
  • Reordered server dependency initialization within the request handling pipeline; no changes to public APIs or interfaces.
• Chores
  • Updated internal server configuration; exports and behavior remain unchanged for end users.

[coderabbitai]

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title succinctly captures the primary change of moving the tracing layer into the dependencies merge, directly reflecting the key modification in the changeset without adding unnecessary detail.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix-rpc-tracing

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 42bb881 and 0697f77.

📒 Files selected for processing (1)

• apps/web/lib/server.ts (2 hunks)

🧰 Additional context used

📓 Path-based instructions (5)

apps/web/**/*.{ts,tsx}

📄 CodeRabbit inference engine (CLAUDE.md)

apps/web/**/*.{ts,tsx}: Use TanStack Query v5 for all client-side server state and data fetching in the web app
Web mutations should call Server Actions directly and perform targeted cache updates with setQueryData/setQueriesData rather than broad invalidations
Client code should use useEffectQuery/useEffectMutation and useRpcClient from apps/web/lib/EffectRuntime.ts; do not create ManagedRuntime inside components

Files:

• apps/web/lib/server.ts

**/*.{ts,tsx,js,jsx,rs}

📄 CodeRabbit inference engine (CLAUDE.md)

Do not add inline, block, or docstring comments in any language; code must be self-explanatory

Files:

• apps/web/lib/server.ts

**/*.{ts,tsx}

📄 CodeRabbit inference engine (CLAUDE.md)

Use strict TypeScript and avoid any; leverage shared types from packages

**/*.{ts,tsx}: Use a 2-space indent for TypeScript code.
Use Biome for formatting and linting TypeScript/JavaScript files by running pnpm format.

Files:

• apps/web/lib/server.ts

**/*.{ts,tsx,js,jsx}

📄 CodeRabbit inference engine (AGENTS.md)

**/*.{ts,tsx,js,jsx}: Use kebab-case for filenames for TypeScript/JavaScript modules (e.g., user-menu.tsx).
Use PascalCase for React/Solid components.

Files:

• apps/web/lib/server.ts

apps/web/**/*.{ts,tsx,js,jsx}

📄 CodeRabbit inference engine (AGENTS.md)

On the client, always use useEffectQuery or useEffectMutation from @/lib/EffectRuntime; never call EffectRuntime.run* directly in components.

Files:

• apps/web/lib/server.ts

🧠 Learnings (1)

📚 Learning: 2025-09-22T14:17:47.407Z

Learnt from: CR
PR: CapSoftware/Cap#0
File: CLAUDE.md:0-0
Timestamp: 2025-09-22T14:17:47.407Z
Learning: Applies to apps/web/app/api/**/route.ts : Provide dependencies via Layer.provide in API routes instead of manual provideService calls

Applied to files:

• apps/web/lib/server.ts

🧬 Code graph analysis (1)

apps/web/lib/server.ts (1)

apps/web/lib/tracing.ts (1)

• layerTracer (5-32)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

• GitHub Check: Build Desktop (x86_64-pc-windows-msvc, windows-latest)
• GitHub Check: Build Desktop (aarch64-apple-darwin, macos-latest)
• GitHub Check: Analyze (rust)

🔇 Additional comments (3)

apps/web/lib/server.ts (3)

38-38: LGTM!

The import statement is correct and properly integrates the tracing layer.

---

120-138: LGTM! Confirm middleware has access to tracing.

The placement of Layer.provideMerge(Dependencies) in the pipeline consolidates dependency provision. Verify that the span name generator middleware at line 128 correctly accesses the tracer provided by Dependencies at line 135, as Effect's layer resolution should make the tracer available throughout the pipeline.

---

71-83: LGTM — no duplicate tracing initialization found. layerTracer correctly centralizes tracing infrastructure.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}