Fix markdown rendering in article titles

[plx]

This change ensures that markdown syntax in titles (like italic and bold) is properly rendered as HTML when displayed on pages, while being stripped for meta tags, browser titles, and Open Graph images.

Changes:

• Add stripMarkdown() function to remove markdown syntax for plain text contexts
• Update page templates to render markdown in displayed titles using renderInlineMarkdown()
• Strip markdown from titles in meta tags, Open Graph data, and browser title
• Improve semantic HTML by using

  instead of

  for page titles

Fixes issue where asterisks and other markdown syntax appeared literally in article titles instead of being rendered as formatted text.

[github-actions]

PR Validation ✅

All checks passed! Ready for review.

Checks Performed:

✓ Linting
✓ Spell check (source)
✓ Type checking & Build
✓ Spell check (HTML)
✓ Internal link validation
✓ Artifact upload

This is a complete dry-run of the deployment process, ensuring your changes will deploy successfully when merged.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Escape title text before using set:html

The updated title rendering binds renderedTitle directly into set:html, but renderInlineMarkdown purposely leaves any text outside of markdown markers unescaped. If a post title contains literal < characters or HTML (from frontmatter or a CMS), the HTML will now be injected into the page and can execute scripts, whereas the previous {post.data.title} rendering was safely escaped. This creates an XSS vector for untrusted or malformed titles. The same pattern appears in the briefs and projects templates; the HTML output should be sanitized or escaped before using set:html.

Useful? React with 👍 / 👎.