Maple onboarding

Wire OpenTelemetry traces, logs, and metrics into the user's project so telemetry streams to Maple. Cover every app and service in the repo — not just the one the user is currently sitting in.

Prefer native OpenTelemetry APIs and the framework's documented bootstrap over custom helper layers. If a specific stack stumps you, search the OTel docs for that language; don't guess.

Before editing, read the applicable companion skills:

• maple-onboarding-style for general OTel taste, VCS attributes, and smoke checks.
• maple-nextjs-style for Next.js / Vercel apps.
• maple-nodejs-style for plain Node servers (Express, Fastify, Hono, Bun).
• maple-python-style for Python services (FastAPI, Django, Flask).
• maple-effect-style for Effect-based services — Maple's first-class SDK.
• maple-go-style, maple-rust-style, maple-java-style, maple-csharp-style, maple-kotlin-style for those stacks.

If none match (Ruby, Elixir, PHP, plain Deno, …), use maple-onboarding-style as the fallback and consult the upstream OTel docs for that language.

Step 0 — Endpoint and key handling