agent-substrate / agent-substrate/substrate
Actor Template labels
- Dominant language
- Go
- Stars
- 1.9k
- Forks
- 317
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 289
Description
Hi. Our pre-release substrate integration ended up depending on actor template labels. We used them for apis and user surfaces to understand things like the purpose, runtime, or capabilities an actor template provided. We are wondering if labels will return to actor templates in future revisions in order to plan our upgrade path. If you have a recommended way to achieve the same functionality today we would appreciate that too. Thanks!
Contributor guide
Research direction
No concrete files, tests, or entry points are mentioned. Start by checking the project documentation for actor templates and API/contract references that discuss template labels or migration notes, then trace any referenced implementation area that handles actor-template metadata. A good outcome is either a maintainer-confirmed roadmap/decision in the issue or a docs update stating whether labels are coming back and the supported alternative for current users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100