Summary
Several CIS workflows build default_output_file directly from a raw datetime token (for example ...-{date}.md). On platforms/tooling combinations that reject spaces or colons in filenames, this can produce invalid or awkward output paths.
Affected surfaces
Why this matters
This is not native-skill conversion drift, but the conversions carry the behavior forward into the new execution surface. Fixing it now would remove a cross-platform filename hazard before more slices land.
Suggested direction
Use a filesystem-safe derived timestamp for output filenames, such as an ISO-like variant without spaces/colons, and keep the human-readable date inside document content if needed.
References
Summary
Several CIS workflows build
default_output_filedirectly from a raw datetime token (for example...-{date}.md). On platforms/tooling combinations that reject spaces or colons in filenames, this can produce invalid or awkward output paths.Affected surfaces
Why this matters
This is not native-skill conversion drift, but the conversions carry the behavior forward into the new execution surface. Fixing it now would remove a cross-platform filename hazard before more slices land.
Suggested direction
Use a filesystem-safe derived timestamp for output filenames, such as an ISO-like variant without spaces/colons, and keep the human-readable date inside document content if needed.
References