[Dreaming] dreaming: clarify RenderImmediateMessage as the correct path for immediate TerminalLogger output

[github-actions]

What changed

Added one bullet to .github/instructions/logging.instructions.md (Terminal Logger section):

Use RenderImmediateMessage (not direct terminal writes) for any message that must appear immediately outside the normal node-status rendering cycle — for example, messages with a null BuildEventContext or IsAuthProviderMessage events. Direct terminal writes bypass the node-display logic and corrupt the rendered output.

Why (recurring evidence)

• PR Preventing coordinator messages from getting filtered out by terminal logger #14356 (TerminalLogger coordinator messages): @rainersigwald explicitly flagged that the change should use RenderImmediateMessage instead of a direct terminal write, explaining it "is designed for exactly this case."
• PR Prevent TerminalLogger corruption during terminal resize #14370 (TerminalLogger resize): same pattern — new code wrote directly to the terminal for immediate messages rather than routing through RenderImmediateMessage.

Two independent PRs triggered the same correction from the same reviewer.

Duplication check

The existing Terminal Logger (FancyLogger) section in logging.instructions.md lists corruption concerns but does not mention RenderImmediateMessage. No other instruction or skill file covers this API contract.

Reviewers (core MSBuild team)

Suggested reviewers — core-team members who discussed this pattern (please assign): @rainersigwald

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• awmgmcpg

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "awmgmcpg"

See Network Configuration for more information.

Generated by Dreaming (learning atoms curation) · 86 AIC · ⌖ 6.17 AIC · ⊞ 8K · ◷

[rainersigwald]

Suggested change

	* Use `RenderImmediateMessage` (not direct terminal writes) for any message that must appear immediately outside the normal node-status rendering cycle — for example, messages with a null `BuildEventContext` or `IsAuthProviderMessage` events. Direct terminal writes bypass the node-display logic and corrupt the rendered output.
	* Use `RenderImmediateMessage` (not direct terminal writes) for any message that must appear immediately outside the normal node-status rendering cycle, like messages that require user intervention or explain long delays. Direct terminal writes bypass the node-display logic and corrupt the rendered output.

(null BEC is not an interesting part of the problem IMO).