Fix hardcoded logic entry point in TemplateArchiveProcessor

[Sup-ri-tha]

Bug Report

Description

In TemplateArchiveProcessor.ts, both the trigger() and init() methods
hardcode the logic entry point as logic/logic.ts when looking up compiled code:

code: compiledCode['logic/logic.ts'].code, // TODO DCS - how to find the code to run?

This assumes the logic file is always named exactly logic/logic.ts. If a template
uses any other filename, compiledCode['logic/logic.ts'] returns undefined,
causing an unhelpful crash:

TypeError: Cannot read properties of undefined (reading 'code')

Location

• File: src/TemplateArchiveProcessor.ts
• Lines: 120 and 169 (both trigger() and init() methods)

Fix

Dynamically find the entry point by searching for a file directly inside the
logic/ folder that is not auto-generated:

const entryPoint = Object.keys(compiledCode).find(
    key => key.startsWith('logic/') && !key.includes('generated/')
);
if (!entryPoint) {
    throw new Error('Could not find compiled logic entry point');
}
code: compiledCode[entryPoint].code,

Additional Notes

The // TODO DCS comment on both lines suggests this was flagged by the
original author as needing a proper fix.

[Sup-ri-tha]

Submitted PR #108 to fix this.

[Akash-bajpai]

Hi! I'm Aakash Bajpai, a GSoC 2026 applicant. I've submitted a proposal for the LLM Based Template Logic Executor project. I'd love to work on this issue as it directly relates to my proposal. Can I be assigned? 🙏

[gauravdev95]

Hi @danselman @DianaLease,

I’m a GSoC 2026 applicant working on the LLM Executor idea.

I built a small prototype integrating an LLM (Gemini) into trigger() that generates state, response, and events.

Does this approach align with the expected direction? Also, should LLM be a fallback or primary execution method?

Thanks!