lens-log-analysis

Use RunAndCollectLogsTool and read its inline result fields: errors for E/W/F lines, prints for script output, and tail for chronological debug context. Never Read the log file directly since logs routinely exceed 256 KB.

A successful recompile only means TypeScript compiled; runtime failures like missing assets, unwired @input declarations, or exceptions still occur. Always follow with RunAndCollectLogsTool and check errors plus firstActivityAtMs.

Stack traces appear in the tail field, not errors. Look for a Stack trace: line followed by @file:line:col frames; the first frame pointing into your Assets directory is the user-script source location.

If firstActivityAtMs is null, the Lens never started, usually because the script is not attached to a SceneObject or crashed during module initialization. If it is set, the script ran without printing or erroring.

Check the errorsCapped, printsCapped, truncated, and rotated flags to see which limit was hit. For content beyond the inline caps, slice the file with awk starting from the returned byteOffset rather than using Read.