fix: add explicit error when no TypeScript logic files are found in template

[FaikAijaz]

This PR improves the robustness of TemplateArchiveProcessor by explicitly handling the case where a template declares a TypeScript runtime but contains no TypeScript logic files.

Previously, if a template had "runtime": "typescript" but no logic/logic.ts file, the engine would fail with a generic runtime error:
Cannot read properties of undefined (reading 'code')
This occurred because the processor attempted to access compiled logic that did not exist.

Changes

Added a guard in both trigger() and init() to check whether any TypeScript logic files are present.
If no logic files are found, the processor now throws a clear and intentional error:

No TypeScript logic files found in template

Added a unit test (TemplateArchiveProcessor.noLogic.test.ts) to validate and protect this behavior.
This does not affect existing templates with valid TypeScript logic. It only improves behavior when logic files are missing.

[Copilot]

Pull request overview

Adds an explicit, actionable error when a template declares the TypeScript runtime but ships no TypeScript logic files, replacing the previous opaque Cannot read properties of undefined (reading 'code') failure. The change touches both trigger() and init() in TemplateArchiveProcessor, ships a fixture template, and adds one Jest test. An unrelated re-encoding of SMART_LEGAL_CONTRACT_BASE64 (LF → CRLF line endings) is also bundled in.

Changes:

• Guard added in TemplateArchiveProcessor.trigger() and init() to throw 'No TypeScript logic files found in template' when getScriptsForTarget('typescript') returns an empty array.
• New fixture template test/archives/no-logic-template/ (package.json, model, grammar, README) representing a TS-runtime template with no logic/.
• New unit test TemplateArchiveProcessor.noLogic.test.ts asserting the error from trigger().
• Re-encoding of SMART_LEGAL_CONTRACT_BASE64 in src/runtime/declarations.ts (CRLF line endings).

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
src/TemplateArchiveProcessor.ts	Adds the empty-tsFiles guard in both trigger() and init().
src/runtime/declarations.ts	Re-encodes the embedded smart-legal-contract source with CRLF line endings (appears unrelated to the PR purpose).
test/TemplateArchiveProcessor.noLogic.test.ts	New test asserting the error is thrown by trigger() for a template lacking logic files.
test/archives/no-logic-template/package.json	Fixture declaring runtime: typescript with no logic directory.
test/archives/no-logic-template/model/model.cto	Minimal @template model used by the fixture.
test/archives/no-logic-template/text/grammar.tem.md	Minimal grammar referencing {{name}}.
test/archives/no-logic-template/README.md	Notes that the fixture intentionally omits TS logic.

Comments suppressed due to low confidence (2)

src/TemplateArchiveProcessor.ts:100

• Even with the new guard, compiledCode['logic/logic.ts'].code (lines 123 and 175) will still throw Cannot read properties of undefined (reading 'code') if the template contains TypeScript files but none of them is named logic/logic.ts (e.g. only helper modules, or a different filename). The guard only handles the zero-files case; it would be more robust to check that the expected logic/logic.ts entry exists in compiledCode before accessing .code, and throw a similarly explicit error otherwise. The // TODO DCS - how to find the code to run? comment on those lines suggests this lookup is already known to be fragile.

            if (tsFiles.length === 0) {
                throw new Error('No TypeScript logic files found in template');
            }

src/TemplateArchiveProcessor.ts:99

• The error message would be more useful for debugging if it included the template name/identifier (e.g. via this.template.getMetadata().getName()), so users with multiple templates can immediately see which one is misconfigured. Currently identical messages are thrown from trigger() and init() with no template context.

                throw new Error('No TypeScript logic files found in template');

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.