Maple onboarding

Wire OpenTelemetry traces, logs, and metrics into every app and service in the repo so telemetry streams to Maple. Use native OpenTelemetry APIs and each framework's documented bootstrap. If a stack stumps you, read the OTel docs for that language; don't guess.

Companion skills

Read maple-onboarding-style first (span pattern, resource attributes, framework notes, signal quality, verification), then the skill for each stack in the repo: maple-nextjs-style, maple-nodejs-style, maple-python-style, maple-effect-style, maple-go-style, maple-rust-style, maple-java-style, maple-csharp-style, maple-kotlin-style. If they are not installed next to this skill, fetch them from https://raw.githubusercontent.com/MapleTechLabs/maple/main/skills/<skill-name>/SKILL.md, only the ones this repo needs. Stacks without one (Ruby, Elixir, PHP, Deno, ...) use maple-onboarding-style and the upstream OTel docs. A service that calls an LLM also gets maple-agent-tracing.

Step 0: Region, endpoint, and key

A key only works in the region that issued it; the other region answers 401.

Pick the region in this order: an ingest endpoint in the prompt (use it verbatim), an EU mention or eu.maple.dev URL, otherwise US. <dashboard> and <mcp> below mean that region's hosts.