Braid startup currently has no supported way to import profile and interaction runtime helpers without evaluating the full agent-interface root.
Measured on agent-interface 0.43.0 with Node 24.13.0:
- cold import of the root entry: about 88 ms
- esbuild startup chunk attributable to the root graph: 890.7 KB
- that chunk includes candidate promotion, improvement, SPDX, and every Zod locale even when the caller only needs defineAgentProfile, snapshotAgentProfile, canonicalAgentProfileDigest, harness helpers, and interaction validation
The package export map currently exposes only the root and environment-provider.
Please add supported focused exports for the existing leaf modules, at minimum profile, profile-snapshot, profile-schema, profile-security, harness, harness-capabilities, and interaction. A leaf-import test should prove each entry can load without evaluating unrelated candidate and improvement modules.
This lets products keep the canonical interface implementation while meeting interactive startup targets; consumers should not depend on private dist paths.
Braid startup currently has no supported way to import profile and interaction runtime helpers without evaluating the full agent-interface root.
Measured on agent-interface 0.43.0 with Node 24.13.0:
The package export map currently exposes only the root and environment-provider.
Please add supported focused exports for the existing leaf modules, at minimum profile, profile-snapshot, profile-schema, profile-security, harness, harness-capabilities, and interaction. A leaf-import test should prove each entry can load without evaluating unrelated candidate and improvement modules.
This lets products keep the canonical interface implementation while meeting interactive startup targets; consumers should not depend on private dist paths.