mirror of
https://github.com/rennf93/roboco.git
synced 2026-08-03 07:23:24 +02:00
docs: document the 2026-07-02 hotfix batch across CHANGELOG, RAG corpus, and map
CHANGELOG entries for the summary route + bounded lists, panel flood fixes, delegate collision-surface params, breaker revisit budget, squash-merge guard relief, stale-ref diff fix, team-match enforcement, manifest workspace fix, QA no-pre-claim. RAG corpus teaches agents the new delegate requirements, wrong-team remediate, and QA self-claim flow; dated delta appended to docs/map/_front.md.
This commit is contained in:
@@ -40,6 +40,8 @@ note(text="Verified AC #1 (429 on 101st req), #2 (TTL match), #3 "
|
||||
|
||||
There is no `roboco_task_claim / _start / _qa_pass / _qa_fail` and no `roboco_git_checkout`. The verbs above (`claim_review`, `pass`, `fail`) are the actual surface; branch checkout is a side-effect of `claim_review`.
|
||||
|
||||
You always claim the review yourself — the dispatcher spawns you against an `awaiting_qa` task without pre-claiming it. `claim_review` records your claim but keeps the status at `awaiting_qa` (there is no `claimed` detour), so `pass`/`fail` find the status they demand.
|
||||
|
||||
## Review Checklist
|
||||
|
||||
Before deciding:
|
||||
|
||||
@@ -44,6 +44,7 @@ Exactly one active WorkSession exists per task at a time (enforced in the servic
|
||||
## Claiming Rules
|
||||
|
||||
- **One at a time (workers only)**: Developers, QA, and documenters can't hold multiple in-progress tasks at once. A **blocked** task still counts as active — a blocked dev cannot `claim` a second task; unblock or `unclaim` first. **PM coordinators are exempt** — a Main / Cell PM plans and delegates many roots in parallel, so it may hold several at once; only a real upstream **sequence dependency** (an unfinished task it depends on) holds one of its roots back.
|
||||
- **Team match**: cell-scoped roles (developer, QA, documenter, cell PM) are rejected `not_authorized` on another team's tasks — claim, resume, unblock, and activate are all team-matched. The `remediate` hint says it: call `give_me_work()` to find a task in your own team. Org-wide roles (Main PM, Board, CEO, PR reviewer) are exempt.
|
||||
- **Self-review prevention**: QA cannot `claim_review` tasks they developed
|
||||
- **Self-documentation prevention**: Documenter cannot claim tasks they developed
|
||||
- **Branch requirement**: Branch auto-created on `i_will_work_on`
|
||||
@@ -75,7 +76,7 @@ unclaim(task_id)
|
||||
```
|
||||
pending → claimed (Developer via i_will_work_on / PM)
|
||||
needs_revision → claimed (Developer via i_will_work_on)
|
||||
awaiting_qa → claimed (QA via claim_review)
|
||||
awaiting_qa → awaiting_qa (QA via claim_review — claim recorded, status stays put so pass/fail match)
|
||||
awaiting_documentation → claimed (Documenter via claim_doc_task)
|
||||
```
|
||||
|
||||
|
||||
@@ -35,7 +35,7 @@ pending → claimed → in_progress → verifying → awaiting_qa
|
||||
|
||||
### QA Flow
|
||||
```
|
||||
awaiting_qa → claimed (claim_review) → pass/fail
|
||||
awaiting_qa → claim_review (claims; status stays awaiting_qa) → pass/fail
|
||||
↓
|
||||
pass: awaiting_documentation
|
||||
fail: needs_revision
|
||||
|
||||
Reference in New Issue
Block a user