Module RenderDevLogCommand 

RenderDevLogCommand

Bridges TypeScript-side tagged logs (Wind / Sky / Cocoon running in the WebView) into Mountain’s dev_log! file sink so a single Mountain.dev.log carries the complete tag-filterable picture of a session, not just the Rust portion.

Why

Wind’s Function/DevLog.ts prints to console.log, visible only in DevTools. Mountain’s dev_log! writes to a timestamped Mountain.dev.log with Trace tag filtering. The two observe the same boot but the outputs live in two places - reviewing a session means cross-referencing browser console + tail-f on the file. This command lets any TS caller mirror a tagged line into the file sink so Trace=channel-stub,git tail -f Mountain.dev.log captures both sides filtered identically.

Contract

• Tag is matched against Trace exactly as Rust tags are; disabled tags produce no output (cheap no-op on the Mountain side).
• Message is the fully-formatted log string - the caller has already done any interpolation.
• The command is fire-and-forget from the renderer’s perspective (returns () immediately); failures to write are swallowed.
• Prefix [RenderDevLog] is added so grep can always separate TS-originated lines from native dev_log! entries that share the same tag.

Functions

RenderDevLog

Accept BOTH casings for the tag/message parameter names so the JS caller doesn’t have to guess Tauri’s param-case transform. In Tauri v2 default convention, Rust snake_case params get mapped to/from JS camelCase; Rust PascalCase params are passed through case-sensitive. Callers that send { Tag, Message } (PascalCase) and callers that send { tag, message } (snake_case) both work - the command coalesces whichever is populated. Empty → silent no-op.