unic / unic/unic-agents-plugins
stream: Archon and the machine underneath
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 0
- Avg merge
- 16h 43m
- Merged PRs (30d)
- 19
Description
One workstream: the defects of the workflow runner and of the machine run 3 exposed, none of them about profile-card and all of them reaching every session that dispatches a Box. Sub-issues are the tickets; this ticket carries no state and no priority by the stream rule in docs/agents/labels.md.
Source: findings register on develop at bcf688a, § "G. What run 3 taught about the instrument" (rows G1, G2, G3, G10, G11). The three "upstream: Archon" tickets are filed here as the record; whether they go to Archon's own tracker is the maintainer's call, as with Archon 0.9.0 adoption.
Mirrors on the Consumer's board: Task 43100 (the five documentation rows under 43039), Task 43102 (the Node pin under 43039), Task 43101 (a control beside each check under 43037).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the findings register on develop at bcf688a, section “G. What run 3 taught about the instrument,” and read docs/agents/labels.md for the stream rule. Follow the G1, G2, G3, G10, and G11 sub-issues and compare the Consumer-board mirrors; this stream is complete only when those individual tickets define and resolve the reported defects.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100