Skip to content

Conversation

@etaderhold
Copy link
Contributor

@etaderhold etaderhold commented Feb 6, 2026

This change returns Markdown content instead of the raw JSON from the LLM for artifact candidate messages. This way the existing Markdown processor on the front end can render it nicely.

Lesson hook example:
image

Exit ticket example:
image

Links

  • Jira:

Testing story

Deployment strategy

Follow-up work

Privacy

Security

Caching

PR Creation Checklist:

  • Tests provide adequate coverage
  • Privacy impacts have been documented
  • Security impacts have been documented
  • Code is well-commented
  • New features are translatable or updates will not break translations
  • Relevant documentation has been added or updated
  • User impact is well-understood and desirable
  • Follow-up work items (including potential tech debt) are tracked and linked

@etaderhold etaderhold changed the title Initial markdown change Return markdown instead of raw JSON for artifact candidate messages Feb 6, 2026
@etaderhold etaderhold requested a review from cearachew February 6, 2026 21:26
@etaderhold etaderhold marked this pull request as ready for review February 6, 2026 21:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant