docs(release): prepare 0.27.0 — curated changelog, rag/map sweep, concat rebuild script (#662)

docs/rag/troubleshooting/git-errors.md

@@ -108,6 +108,12 @@ Don't checkout by hand — there is no `roboco_git_checkout` tool.
 
 Some low-level git error messages still say "GitHub API" in their text regardless of which forge the project actually uses (a known wording gap, not a routing bug) — the underlying failure is real even when the vendor name in the message is wrong. Diagnose from the actual symptom (missing token, PR-not-found, merge conflict, etc.), not from the vendor name in the message.
 
+## Rebase/sync_branch refused on a protected branch
+
+**Cause:** `sync_branch`/rebase refuses to force-push a branch whose name matches the project's operator-declared `protected_branches` list, its environment-ladder rungs, or the hardcoded `master`/`main` floor. You should never legitimately be working on one of these directly — your own feature branch is never a protected name.
+
+**Fix:** If you see this, your task's recorded branch is misconfigured. `unclaim(task_id)` and re-claim to rebuild a proper branch; don't try to force through it.
+
 ## FORCE_PUSH_FORBIDDEN
 
 **Cause:** Force-push is CEO-only. Anyone else attempting it (typically because their branch diverged) is denied.

docs/rag/troubleshooting/task-errors.md

@@ -111,6 +111,14 @@ escalate_to_ceo(task_id=parent_id, reason="...")
 
 **Solution**: Verify with the repo-wide check (not a scoped one, since scoping is a no-op) and record the zero-diff finding in a `decision` journal entry. If the task's acceptance criteria are already met with nothing left to change in the named files, do not keep re-running the same check — escalate once with the concrete verification so a PM can either stamp the task as satisfied-by-upstream/cancel it, or direct a small verification commit outside the target file(s) to satisfy the commit gate.
 
+## Task Auto-Blocked for Budget
+
+**Symptom**: Your in-progress task flips to `blocked` with a budget marker, and you weren't the one who blocked it.
+
+**Cause** (only when task budgets are armed): a periodic sweep prices the task's own spend against its `budget_usd` (or the `TaskType` default when unset) and blocks it before you get a chance to finish gracefully, so the dispatcher won't respawn onto an already-over-budget task.
+
+**Fix**: This is a PM/CEO decision, not yours to route around — `unblock` re-checks live spend and refuses again while still over the cap. Escalate (`i_am_blocked`/`escalate_up`) naming the budget breach; the CEO either raises the task's/project's cap or the PM redirects the remaining work.
+
 ## Invalid Task Status for Operation
 
 **Error**: "Task is in [status], expected [expected_status]"