Components.AI: Design message and turn decorator APIs
- Dominant language
- C#
- Stars
- 38.4k
- Forks
- 10.9k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 281
Description
### Is your feature request related to a problem? Please describe the problem.
There is no public composition seam for message- or turn-owned decoration, and placement/merge semantics remain unresolved.
### Describe the solution you'd like
Design and review separate message and turn decorator contracts, context, placement, and ordering. Specify how a turn may append its actions to the last assistant message row without owning or replacing that message's actions.
### Additional context
Leaf task for #68227 requirements F1 and F8-F10 and open design decision 2.
Contributor guide
Research direction
No files, tests, or entry points are named. Start by reviewing parent issue #68227, requirements F1 and F8-F10, and open design decision 2; done means the message and turn decorator contracts, context, placement, ordering, and ownership semantics have been specified and reviewed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- ai, api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100