External/roboco
1
0
Fork 0
mirror of https://github.com/rennf93/roboco.git synced 2026-08-03 07:23:24 +02:00
Code Issues Packages Projects Releases Wiki Activity

docs: reflow hard-wrapped prose to one line per paragraph

Browse Source 
Markdown and editors soft-wrap on their own, so the manual ~75-char line
breaks across the docs added nothing but noise. Join wrapped prose, list
items, and paragraphs into single lines across 67 docs — README, CLAUDE.md,
deployment, usage, the RAG knowledge base, and the agent role prompts.
Whitespace-only: code fences, tables, and blockquote alerts are byte-identical
and the change is token-verified (no content altered). Applied with a
deterministic reflow tool (committed separately).

Also lands two doc edits that were awaiting commit: the measured under-load
resource numbers in usage.md and the pr_reviewer additions to the
org-structure RAG doc.
This commit is contained in:
Renn F
2026-06-16 23:18:55 +02:00
parent 640a964b88
commit f48106cbb6
67 changed files with 504 additions and 1593 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/rag/troubleshooting/task-errors.md
+5 -12
View File
@@ -31,9 +31,7 @@
2. Task in wrong status
**Solutions**:
- Claim + start in one step: `i_will_work_on(task_id, plan="...")`
(devs), `claim_review(task_id)` (QA), `claim_doc_task(task_id)` (doc),
or `i_will_plan(task_id, plan, approach)` (PMs)
- Claim + start in one step: `i_will_work_on(task_id, plan="...")` (devs), `claim_review(task_id)` (QA), `claim_doc_task(task_id)` (doc), or `i_will_plan(task_id, plan, approach)` (PMs)
- Check current status
Note: Git branches are auto-created on claim, no waiting needed.
@@ -67,14 +65,11 @@ Note: Git branches are auto-created on claim, no waiting needed.
**Cause**: Attempting to escalate a task that has a `parent_task_id`
**Solution**: Escalate the parent task instead. Find the parent task ID
(it's on the subtask's `parent_task_id` field, surfaced in your
`give_me_work()` / `triage()` envelope), then escalate the parent:
**Solution**: Escalate the parent task instead. Find the parent task ID (it's on the subtask's `parent_task_id` field, surfaced in your `give_me_work()` / `triage()` envelope), then escalate the parent:
```python
escalate_to_ceo(task_id=parent_id, reason="...")
```
`escalate_to_ceo` is Main PM / Board only; Cell PMs and cell members
use `escalate_up(task_id, reason)` instead.
`escalate_to_ceo` is Main PM / Board only; Cell PMs and cell members use `escalate_up(task_id, reason)` instead.
## Git Task: Parent Branch Required
@@ -93,10 +88,8 @@ use `escalate_up(task_id, reason)` instead.
**Cause**: Trying to complete a parent task while subtasks are still in progress
**Solution**: The error message includes which subtask IDs are blocking. Either:
1. Complete the blocking subtasks first (drive them through QA → docs →
`complete(task_id, notes)`)
2. Cancel them if no longer needed (PM/CEO only — cancellation is not an
agent verb; ask your PM)
1. Complete the blocking subtasks first (drive them through QA → docs → `complete(task_id, notes)`)
2. Cancel them if no longer needed (PM/CEO only — cancellation is not an agent verb; ask your PM)
## Invalid Task Status for Operation