Wrap rendered code snippets and surface optional filenames

[Copilot]

Long code lines in rendered workshop snippets were forcing horizontal scrolling, which made examples harder to read in-place. This change makes snippet bodies wrap by default and allows the existing custom snippet chrome to show a filename when the fence metadata provides one.

• Rendering behavior

  • Apply pre-wrap and overflow-wrap: anywhere to rendered code blocks so long commands, YAML, and prompts stay readable without horizontal scrolling.
  • Preserve the existing snippet variants (terminal, prompt, markdown, yaml) and their copy-button behavior.

• Snippet header metadata

  • Extend fenced-code parsing to read optional metadata after the language token.
  • Render a right-aligned filename in the snippet header when metadata includes a bare path or keyed value such as title=, file=, filename=, or path=.

• UI updates

  • Add shared filename header styling across snippet chrome variants.
  • Keep header layouts resilient for long filenames by allowing truncation rather than expanding the block.

• Regression coverage

  • Add targeted assertions for wrapped snippet CSS.
  • Add renderer coverage for filename extraction and header output.

Example:

```yaml .github/workflows/hello.yml
name: Hello

# Hello

[pelikhan]

@copilot update guidelines.md with snippet filename support and ensure filenames that represent the file type are assigned and consistent accross pages.

[Copilot]

@copilot update guidelines.md with snippet filename support and ensure filenames that represent the file type are assigned and consistent accross pages.

Addressed in 85b4342. I documented the filename-metadata convention in .github/workflows/guidelines.md and added consistent filename labels to the main workshop Markdown/YAML snippets so the rendered headers show file-appropriate names.

[pelikhan]

@copilot resolve the merge conflicts in this pull request

[Copilot]

@copilot resolve the merge conflicts in this pull request

Resolved in 9e32406. I merged origin/main, resolved the conflict in scripts/lib/marked-setup.js, and kept both behaviors in the result: markdown snippets still use YAML-style highlighting and now retain the filename header support.