fix: use printf %b to decode encoded newlines in smoke-ci comment-memory (#28937)

[Copilot]

Summary

Fixes the encoded \n appearing literally in the comment-memory text, as seen in #28937 comment:

CI lights the path\nGreen checks bloom at dawn\nQuiet bots still sing

Root cause

In smoke-ci.md, the HAIKU variable is assigned inside a bash -lc '...' call:

HAIKU="CI lights the path\nGreen checks bloom at dawn\nQuiet bots still sing"

Within the single-quoted string passed to bash -lc, the \n in the double-quoted assignment is never interpreted as a newline — it remains a literal backslash-n. The subsequent printf "%s\n" "$HAIKU" writes those literal characters to the comment-memory file, which is then posted as-is to GitHub.

Fix

Change printf "%s\n" → printf "%b\n" (both the initial-write and the append path). The %b format specifier causes printf to interpret backslash escape sequences in its arguments, so \n in $HAIKU is decoded to an actual newline character before being written to the file.

[Copilot]

Pull request overview

Fixes smoke-ci’s comment-memory content so \n sequences in the haiku are written as real newlines instead of appearing literally in posted comments.

Changes:

• Updated the smoke-ci workflow template to use printf "%b\n" when writing/appending the haiku to comment-memory files.
• Regenerated the compiled workflow lock file to reflect the template change.

Show a summary per file

File	Description
.github/workflows/smoke-ci.md	Switches haiku writes/appends to printf %b so \n escapes decode into actual newlines.
.github/workflows/smoke-ci.lock.yml	Compiled output updated to include the printf %b change in the generated engine command.

Copilot's findings

Tip

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

• Files reviewed: 2/2 changed files
• Comments generated: 0