refactor(eve): eve-owned instrumentation event payloads - #1618
Draft
chadhietala wants to merge 1 commit into
Draft
refactor(eve): eve-owned instrumentation event payloads#1618chadhietala wants to merge 1 commit into
chadhietala wants to merge 1 commit into
Conversation
The lifecycle contract derived five event fields from the AI SDK's callback types via `Parameters<NonNullable<Telemetry[K]>>[0]`, so any provider reading them was coupled to the model SDK's shapes. Publishing that bus would make an SDK upgrade a breaking change for every integration rather than for eve's own mapping code. Replace those fields with eve types derived from what the OTel provider actually reads, and confine the AI SDK types to `ai-sdk-hook-bridge.ts`, which is the mapping boundary. Guard rule 37 keeps `instrumentation-lifecycle.ts` from importing `ai` again. `attempt.started` loses its `step` field, which had no consumer. Spans and attributes are unchanged. Signed-off-by: Chad Hietala <chadhietala@gmail.com>
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Bundle + Package Summary:
|
| Area | Metric | Baseline | Current | Delta |
|---|---|---|---|---|
| Package | Packed tarball | 7.63 MB | 7.63 MB | +1.3 kB |
| Package | Unpacked publish size | 28.60 MB | 28.60 MB | +2.4 kB |
| Package | Installed footprint | 71.91 MB | 71.91 MB | +2.4 kB |
| Package | Published files | 3002 | 3002 | 0 |
| Package | Installed files | 6701 | 6701 | 0 |
| Runtime | Unique function payloads | 2 | 2 | 0 |
| Runtime | Total function bytes | 16.87 MB | 16.87 MB | +2.4 kB |
| Runtime | Public routes | 13 | 13 | 0 |
Changed function payloads vs main (601fb13) (2)
| Function | Status | Baseline | Current | Delta | Route changes |
|---|---|---|---|---|---|
functions/__server.func |
changed | 8.43 MB | 8.43 MB | +1.2 kB |
none |
functions/.well-known/workflow/v1/flow.func |
changed | 8.43 MB | 8.43 MB | +1.2 kB |
none |
eve init install
| Metric | Baseline | Current | Delta |
|---|---|---|---|
| Installed footprint | 110.32 MB | 110.33 MB | +2.4 kB |
| Installed packages | 121 | 121 | 0 |
| dependencies | 4 | 4 | 0 |
| devDependencies | 2 | 2 | 0 |
| Dependency package bytes | 43.01 MB | 43.01 MB | +2.4 kB |
| devDependency package bytes | 5.04 MB | 5.04 MB | 0 B ➖ |
Build Metadata
- Preset:
vercel - Nitro:
nitro@3.0.260610-beta - Output directory:
apps/fixtures/weather-agent/.vercel/output - Build metadata timestamp: 2026-08-04T19:11:05.194Z
- Route aliases: 13 public, 1 internal (14 total aliases)
- Vercel routes in config: 16
- Severity legend: 🔴 dominant/large, 🟠 notable, 🟡 watch, ⚪ small
Package Drill-Down
Package Details
- Package:
eve@0.30.2 - Package directory:
packages/eve - Tarball: 7.63 MB (
eve-0.30.2.tgz) - Unpacked payload: 28.60 MB across 3002 published files
- Installed footprint: 71.91 MB across 6701 installed files
- Installed root package: 27.24 MB
- Installed dependencies: 44.67 MB
- Runtime dependencies: 2
- Peer dependencies: 5 (4 optional)
Installed footprint is measured from an isolated temporary npm install of the packed tarball.
Heavy installed dependencies
eve: 27.24 MB (37.9%)@rolldown/binding-linux-x64-gnu: 19.34 MB (26.9%)ai: 6.60 MB (9.2%)zod: 5.07 MB (7.0%)undici: 3.50 MB (4.9%)
Publish payload breakdown
Published file size
🔴 dist/src/compiled/shadcn-registry/index.js [#################.......] 9.68 MB 33.9%
🟠 dist/src/compiled/@photon-ai/chat-adapter-ime... [####....................] 2.42 MB 8.5%
🟠 dist/src/compiled/experimental-ai-sdk-code-mo... [###.....................] 1.51 MB 5.3%
🟡 dist/src/compiled/_chunks/node/undici-DWL_MYm... [#.......................] 502.4 kB 1.8%
🟡 dist/src/compiled/_chunks/workflow/undici-DWL... [#.......................] 502.4 kB 1.8%
🔴 Other published files [########################] 13.98 MB 48.9%
Installed footprint breakdown
Installed package size
🔴 eve [########################] 27.24 MB 37.9%
🔴 @rolldown/binding-linux-x64-gnu [#################.......] 19.34 MB 26.9%
🔴 ai [######..................] 6.60 MB 9.2%
🔴 zod [####....................] 5.07 MB 7.0%
🟠 undici [###.....................] 3.50 MB 4.9%
🟠 nitro [##......................] 2.41 MB 3.3%
🔴 Other installed packages [#######.................] 7.75 MB 10.8%
Runtime dependencies (2)
| Package | Range | Notes |
|---|---|---|
nitro |
3.0.260610-beta |
|
undici |
8.9.0 |
Peer dependencies (5)
| Package | Range | Notes |
|---|---|---|
@opentelemetry/api |
^1.0.0 |
optional peer |
ai |
catalog: |
|
braintrust |
^3.0.0 |
optional peer |
just-bash |
^3.0.0 |
optional peer |
microsandbox |
^0.5.0 |
optional peer |
eve init install drill-down
eve init install details
- Command:
eve init my-agent - Package manager:
npm - Installed footprint: 110.33 MB across 8577 installed files
- Installed packages: 121 total (115 transitive-only)
- dependencies: 4 direct packages totaling 43.01 MB
- devDependencies: 2 direct packages totaling 5.04 MB
- Other transitive package files: 62.27 MB
Installed footprint is measured from an isolated temporary eve init my-agent using the current packed eve tarball.
Heavy installed dependencies
@typescript/typescript-linux-x64: 27.95 MB (25.3%)eve: 27.24 MB (24.7%)@rolldown/binding-linux-x64-gnu: 19.34 MB (17.5%)zod: 9.02 MB (8.2%)ai: 6.60 MB (6.0%)
Installed footprint breakdown
Installed package size
🔴 @typescript/typescript-linux-x64 [########################] 27.95 MB 25.3%
🔴 eve [#######################.] 27.24 MB 24.7%
🔴 @rolldown/binding-linux-x64-gnu [#################.......] 19.34 MB 17.5%
🔴 zod [########................] 9.02 MB 8.2%
🔴 ai [######..................] 6.60 MB 6.0%
🟠 undici [###.....................] 3.50 MB 3.2%
🔴 Other installed packages [##############..........] 16.67 MB 15.1%
dependencies (4)
| Package | Range | Installed size | Share |
|---|---|---|---|
@vercel/connect |
0.4.3 |
141.0 kB | 0.1% |
ai |
^7.0.38 |
6.60 MB | 6.0% |
eve |
file:eve-0.30.2.tgz |
27.24 MB | 24.7% |
zod |
4.4.3 |
9.02 MB | 8.2% |
devDependencies (2)
| Package | Range | Installed size | Share |
|---|---|---|---|
@types/node |
24.x |
2.54 MB | 2.3% |
typescript |
7.0.2 |
2.50 MB | 2.3% |
Function Drill-Down
Payload Size Graph
Unique function payload size and share of total
🔴 functions/.well-known/workflow/v1/flow.func [########################] 8.43 MB 50.0%
🔴 functions/__server.func [########################] 8.43 MB 50.0%
Top Function Payloads
🟠 functions/.well-known/workflow/v1/flow.func • 1 public route • 8.43 MB
| Metric | Value |
|---|---|
| Public routes | /.well-known/workflow/v1/flow |
| Runtime | nodejs24.x |
| Handler | index.mjs |
| Payload | 8.43 MB |
| Function files | 8.43 MB across 43 files |
| Traced dependencies | 0 B |
| Signal | 🟠 Bundled file index.mjs is 2.26 MB (26.8%) |
🟠 🔎 Dependency Analysis
📦 Bundled files:
Bundled file size
🟠 index.mjs [#######################.] 2.26 MB 26.8%
🟠 _chunks/runtime-artifacts.mjs [################........] 1.61 MB 19.1%
🟡 _libs/undici.mjs [##########..............] 980.5 kB 11.6%
🟡 _chunks/sandbox.mjs [########................] 769.0 kB 9.1%
🟡 _libs/@ai-sdk/gateway+[...].mjs [####....................] 432.8 kB 5.1%
🟠 Other bundled files [########################] 2.38 MB 28.2%
🧾 Vercel Config
{
"handler": "index.mjs",
"launcherType": "Nodejs",
"shouldAddHelpers": false,
"supportsResponseStreaming": true,
"runtime": "nodejs24.x",
"maxDuration": "max",
"experimentalTriggers": [
{
"type": "queue/v2beta",
"topic": "__eve776561746865722d6167656e74_wkf_workflow_*",
"consumer": "default",
"retryAfterSeconds": 5,
"initialDelaySeconds": 0
}
],
"environment": {
"WORKFLOW_PRECONDITION_GUARD": "1"
}
}🟠 functions/__server.func • 12 public routes, 1 internal alias • 8.43 MB
| Metric | Value |
|---|---|
| Public routes | //eve/v1/callback/[token]/eve/v1/connections/[name]/callback/[token]/eve/v1/health/eve/v1/info/eve/v1/session/eve/v1/session/[sessionId]/eve/v1/session/[sessionId]/cancel/eve/v1/session/[sessionId]/stream/eve/v1/session/clear/eve/v1/session/compact/eve/v1/session/reset |
| Internal aliases | /__server |
| Runtime | nodejs24.x |
| Handler | index.mjs |
| Payload | 8.43 MB |
| Function files | 8.43 MB across 43 files |
| Traced dependencies | 0 B |
| Signal | 🟠 Bundled file index.mjs is 2.26 MB (26.8%) |
🟠 🔎 Dependency Analysis
📦 Bundled files:
Bundled file size
🟠 index.mjs [#######################.] 2.26 MB 26.8%
🟠 _chunks/runtime-artifacts.mjs [################........] 1.61 MB 19.1%
🟡 _libs/undici.mjs [##########..............] 980.5 kB 11.6%
🟡 _chunks/sandbox.mjs [########................] 769.0 kB 9.1%
🟡 _libs/@ai-sdk/gateway+[...].mjs [####....................] 432.8 kB 5.1%
🟠 Other bundled files [########################] 2.38 MB 28.2%
🧾 Vercel Config
{
"handler": "index.mjs",
"launcherType": "Nodejs",
"shouldAddHelpers": false,
"supportsResponseStreaming": true,
"runtime": "nodejs24.x"
}Build Timing: e2e/fixtures/agent-tools-sandbox
This is an informational timing measurement inside eve build, from preflight through publication. Output-size measurement and profile writing are excluded.
Build mode: deployable Vercel build with sandbox template prewarm included.
- Build pipeline: 2.13 s -> 2.05 s (-72.5 ms) vs
main (601fb13). - Timing is informational: shared GitHub runners are too variable for a hard timing budget.
Detailed phase timings vs `main (601fb13)`
| Phase | Baseline | Current | Delta |
|---|---|---|---|
extension.check |
5.2 ms | 1.1 ms | -4.1 ms |
project.resolve |
0.8 ms | 0.6 ms | -0.2 ms |
workspace.create |
2.5 ms | 0.7 ms | -1.8 ms |
host.prepare |
256.8 ms | 197.1 ms | -59.7 ms |
vercel.service-prefix.resolve |
2.5 ms | 2.8 ms | +0.3 ms |
nitro.create |
193.6 ms | 228.7 ms | +35.1 ms |
sandbox.prewarm |
308.5 ms | 290.9 ms | -17.6 ms |
nitro.cache.prepare |
0.2 ms | 0.2 ms | 0.0 ms |
nitro.prepare |
0.9 ms | 0.8 ms | -0.1 ms |
nitro.public-assets |
0.8 ms | 0.7 ms | -0.1 ms |
nitro.prerender |
0.5 ms | 0.5 ms | 0.0 ms |
nitro.bundle |
1.32 s | 1.30 s | -24.8 ms |
nitro.cache.write |
0.4 ms | 0.4 ms | 0.0 ms |
vercel.workflow-function.materialize |
23.1 ms | 23.5 ms | +0.4 ms |
agent-summary.emit |
0.5 ms | 0.5 ms | 0.0 ms |
nitro.close |
0.1 ms | 0.1 ms | 0.0 ms |
output.publish |
3.5 ms | 3.4 ms | -0.1 ms |
workspace.remove |
2.2 ms | 2.3 ms | +0.1 ms |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
First of a stack that promotes eve's internal instrumentation lifecycle bus toward a public provider surface. This one is internal only and behaviour-neutral.
Why
harness/instrumentation-lifecycle.tsderived five event fields from the AI SDK's callback types:Any provider reading those fields is coupled to the model SDK's shapes. Publishing the bus in that state would make an AI SDK upgrade a breaking change for every integration, rather than for eve's own mapping code.
What
The five fields become eve types, shaped by what the one existing consumer —
tracing/agent-otel-provider.ts— actually reads:attempt.startedoperation,stepoperation: { modelId, operationId, provider }model.call.startedsourcemodel,inputmodel.call.completedsourcecontent,finishReason,usagetool.call.startedsourcecallId,toolName,inputtool.call.completedsourceoutputAI SDK types are now confined to
ai-sdk-hook-bridge.ts, which is the mapping boundary. Guard rule 37 keepsinstrumentation-lifecycle.tsfrom importingaiagain.Spans and attributes are unchanged — the provider's existing test suite passes untouched, which is the evidence the mapping is lossless.
Notes for review
attempt.started.stepis deleted. Nothing read it. The bridge keepsstepNumberinternally because it disambiguates call identities within an attempt.operationIdstays a string. I considered mapping it to a"generate" | "stream"discriminant, but the provider uses it as both the span name andgen_ai.operation.name, andOperationStartEventalso covers object/embed/rerank — so a two-value enum would be lossy for no gain.InstrumentationUsagealways emits aninputTokenDetailsobject, where the SDK field could be absent.setUsageonly reads the two leaves so nothing observable changed, but a future consumer could notice.snapshot()is gone — the bridge constructs eve objects instead of freezing SDK ones.Checks
test:unit735 passed ·test:integrationpassed ·typecheck33/33 ·lint·fmt·guard:invariantsRule 37 verified by re-adding the import and confirming it fires.