Method findContentWithKey

frontend/src/cache.ts:528–552

(nodePath: string)

        // Helper to find content by matching path suffix
        // Returns both content AND the canonical key (for consistent cache storage)
        const findContentWithKey = (nodePath: string): { content: string; key: string } | undefined => {
            // Try exact match first
            if (contents[nodePath]) return { content: contents[nodePath], key: nodePath };

            // Normalize both paths for comparison
            const normalizedNode = nodePath.replace(/\\/g, '/').replace(/^\//, '');

            for (const [contentKey, content] of Object.entries(contents)) {
                const normalizedKey = contentKey.replace(/\\/g, '/').replace(/^\//, '');

                // Exact match after normalization
                if (normalizedNode === normalizedKey) return { content, key: contentKey };

                // Either path could be full or relative, so check both directions
                // Case 1: nodePath is full, contentKey is relative
                if (normalizedNode.endsWith('/' + normalizedKey)) return { content, key: contentKey };
                if (normalizedNode.endsWith(normalizedKey)) return { content, key: contentKey };

                // Case 2: contentKey is full, nodePath is relative (LLM returned short path)
                if (normalizedKey.endsWith('/' + normalizedNode)) return { content, key: contentKey };
                if (normalizedKey.endsWith(normalizedNode)) return { content, key: contentKey };
            }

            return undefined;
        };

        // Build per-node workflow mapping from LLM-assigned workflows
        // A single file can have nodes in multiple workflows (e.g., gemini.ts serves 5 workflows)