Context
buildLLMProviderFactory lives at src/kernel/provider-factory.ts but is not in the package exports map. Consumers that want to use the factory directly (without going through buildLLMProviderFactory — e.g., the daemon's standalone scheduled tasks) currently can't import it cleanly.
Ask
Add to exports in web/package.json:
"./kernel/provider-factory": "./src/kernel/provider-factory.ts"
This lets consumers do:
import { buildLLMProviderFactory } from '@stackbilt/aegis-core/kernel/provider-factory';Instead of re-constructing the factory from createLLMProviderFactory with duplicated EdgeEnv field wiring.
Why now
Phase D (v0.6.3) migrated all core executors to the factory. The daemon's synthesis.ts was migrated to use createLLMProviderFactory directly from @stackbilt/llm-providers as a workaround. Once this export is added, that call site can be simplified to use buildLLMProviderFactory(env).
Related
- v0.6.3 Phase D migration
- aegis daemon
web/src/kernel/memory/synthesis.ts
Context
buildLLMProviderFactorylives atsrc/kernel/provider-factory.tsbut is not in the package exports map. Consumers that want to use the factory directly (without going throughbuildLLMProviderFactory— e.g., the daemon's standalone scheduled tasks) currently can't import it cleanly.Ask
Add to
exportsinweb/package.json:This lets consumers do:
Instead of re-constructing the factory from
createLLMProviderFactorywith duplicated EdgeEnv field wiring.Why now
Phase D (v0.6.3) migrated all core executors to the factory. The daemon's
synthesis.tswas migrated to usecreateLLMProviderFactorydirectly from@stackbilt/llm-providersas a workaround. Once this export is added, that call site can be simplified to usebuildLLMProviderFactory(env).Related
web/src/kernel/memory/synthesis.ts