instar 1.2.44 → 1.2.46

package/dist/commands/server.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"server.d.ts","sourceRoot":"","sources":["../../src/commands/server.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AAkQH,UAAU,YAAY;IACpB,UAAU,CAAC,EAAE,OAAO,CAAC;IACrB,GAAG,CAAC,EAAE,MAAM,CAAC;IACb;2DACuD;IACvD,QAAQ,CAAC,EAAE,OAAO,CAAC;CACpB;AAiqDD,wBAAsB,WAAW,CAAC,OAAO,EAAE,YAAY,GAAG,OAAO,CAAC,IAAI,CAAC,CAglLtE;AAED,wBAAsB,UAAU,CAAC,OAAO,EAAE;IAAE,GAAG,CAAC,EAAE,MAAM,CAAA;CAAE,GAAG,OAAO,CAAC,IAAI,CAAC,CAsDzE;AAED;;;;;;;;;;;GAWG;AACH,wBAAsB,aAAa,CAAC,OAAO,EAAE;IAAE,GAAG,CAAC,EAAE,MAAM,CAAA;CAAE,GAAG,OAAO,CAAC,IAAI,CAAC,CAuD5E"}
+{"version":3,"file":"server.d.ts","sourceRoot":"","sources":["../../src/commands/server.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AAkQH,UAAU,YAAY;IACpB,UAAU,CAAC,EAAE,OAAO,CAAC;IACrB,GAAG,CAAC,EAAE,MAAM,CAAC;IACb;2DACuD;IACvD,QAAQ,CAAC,EAAE,OAAO,CAAC;CACpB;AAiqDD,wBAAsB,WAAW,CAAC,OAAO,EAAE,YAAY,GAAG,OAAO,CAAC,IAAI,CAAC,CA6lLtE;AAED,wBAAsB,UAAU,CAAC,OAAO,EAAE;IAAE,GAAG,CAAC,EAAE,MAAM,CAAA;CAAE,GAAG,OAAO,CAAC,IAAI,CAAC,CAsDzE;AAED;;;;;;;;;;;GAWG;AACH,wBAAsB,aAAa,CAAC,OAAO,EAAE;IAAE,GAAG,CAAC,EAAE,MAAM,CAAA;CAAE,GAAG,OAAO,CAAC,IAAI,CAAC,CAuD5E"}

package/dist/commands/server.js

@@ -2152,7 +2152,20 @@ export async function startServer(options) {
         // backwards-compat; INSTAR_FRAMEWORK=codex-cli routes through Codex.
         try {
             const { buildIntelligenceProvider, frameworkFromEnv } = await import('../core/intelligenceProviderFactory.js');
-            const framework = frameworkFromEnv() ?? 'claude-code';
+            // _defaultFramework is what the Telegram spawn path uses for any topic
+            // without an explicit per-topic override (resolveTopicFramework returns
+            // it). It MUST come from the agent's resolved runtime framework
+            // (config.sessions.framework — derived at load from
+            // sessions.framework | enabledFrameworks[0] | INSTAR_FRAMEWORK), NOT from
+            // INSTAR_FRAMEWORK alone. Before this fix it was `frameworkFromEnv() ??
+            // 'claude-code'`, so a codex-cli-only agent that didn't set the
+            // INSTAR_FRAMEWORK env var (the common case — the wizard sets
+            // enabledFrameworks, not the env) silently defaulted to claude-code and
+            // spawned a CLAUDE session on every Telegram message. The fresh-spawn
+            // path (spawnInteractiveSession's internal resolution) already read
+            // config.framework correctly; this aligns the Telegram path with it so
+            // both doors agree. See specs/dev-infrastructure/framework-spawn-portability.md.
+            const framework = config.sessions?.framework ?? frameworkFromEnv() ?? 'claude-code';
             resolvedFramework = framework;
             _defaultFramework = framework;
             _topicFrameworks = config.topicFrameworks ?? {};