Herdr Tabs — Config Sync + Docs Rewrite

What changed

• ~/utils/herdr-workspace.sh: TABS array updated (KB-mBR/Acct-HST → SDC/mBR, then reordered to Core, SDC, KB-OS, mBR, monorepo, utils, web-deploy). Added --sync mode: closes every non-Core tab and recreates all of them fresh from TABS, in TABS’ order — the single command that applies any config edit (add/remove/relabel/re-cwd/reorder), no restart of herdr/WSL/Windows. Refuses safely if the invoking tab (e.g. the agent’s own utils session) would be closed.
• ~/utils/herdr-reorder-core-first.sh: fixed a stale check ("KB-mBR" → "SDC", dead since an earlier rename).
• Core/IT/Utils/Custom/herdr-workspace.md: rewritten — new Configuration section leads the doc (before Location/Quick Start), states up front “no restart, ever,” and gives the one --sync command as the answer to “how do I apply a change.” Tab-order mechanics (no reorder command exists; position is pure creation order) documented separately since --sync supersedes the old close+recreate-by-hand approach.
• Core/IT/Utils/External/Utilities.md: Herdr section now opens with a pointer straight to herdr-workspace.md → Configuration — single discovery path instead of scattered gotchas.
• Live tab set verified 2026-08-24 (Talbot, running --sync from Core): correct order, all 7 tabs present.

Lessons (promoted)

• ~/ai-config/AGENTS.md — “How-to task, real answer = capability missing → say so round 1, build it.” Don’t document a multi-step manual workaround as if it were the answer; if the honest answer is “no single command does this yet,” say so immediately and build it.
• Core/AI/AI-Testing-Standards.md — “Doc/how-to tasks: test the doc, not just the mechanism.” Confirming the underlying command works isn’t the same as running the doc’s own written steps as a fresh user. Two rounds here shipped a rewritten doc without an actual end-to-end run.

Root cause of the round count (7 rounds for what closed as a 2-step outcome)

Round 1 answered “confirm you understand the target state” instead of checking whether a single apply-command existed — it didn’t. Rounds 2-5 kept producing per-case manual CLI sequences (rename for label, close+recreate for cwd, a separate script for order) instead of surfacing “there’s a real gap: no reconcile-to-config command exists” and building one. --sync (round 5, tested live round 6) is what round 1 should have shipped.

Spun off

frictionless-docs-links (Core/Processes/Projects/KB-OS/Tasks/) — Talbot’s follow-on request for one-click actionable docs (edit-in-app links via obsidian-shellcommands, already installed but unconfigured; acronym/definition links). Not built here — kept out of scope per the round-6 lesson above.