v0.1.1 — Router shipped, ceremony-budget honesty

RePERS v0.1.1 — Router shipped, ceremony-budget honesty

The v0.1.1 release is a product-honesty release. After driving the full
R-P-E-R-S CLI end-to-end on a real bug (sqlfluff__sqlfluff-2419) and
measuring 5.8× wall-clock overhead vs. a naked agent for a 4-line fix
with no quality lift, we shipped the missing product piece: a router that
tells you when NOT to use the harness.

What's new

🧭 Router (the headline)

python .repers/scripts/repers.py route \
  --task "fix the L060 description bug" --est-files 1 --json
# → permutation: R-E-R
#   reason: "estimated 1 file(s) — naked agent is faster"
#   recommendation: "Naked agent loop is fine: read, edit, verify.
#                    The harness ceremony will cost more than it saves."

A deterministic keyword + repo-signal decision tree that maps any task
description to one of:

Permutation	When
skip	Trivial — don't even invoke the harness, use your IDE
R-only	Spike / scoping — write a research note, decide later
R-S	Docs / config — skip execute, just review + ship
R-E-R	Hotfix / single-file — naked agent loop is faster
R-P-E-R	Multi-file in one domain — plan + parallel dispatch wins
R-P-E-R-S	Multi-domain, multi-day — the full pipeline sweet spot

<100 ms, no LLM call, offline, stdlib-only. Validated against the real
sqlfluff bug: it would have correctly routed away from the 5.8× overhead.

🪝 /repers-bug-hunt now routes first

Hard-coded to short-circuit on skip / R-E-R. No more 7-mandatory-step
pipeline on a 4-line bug. Skill description and procedure rewritten to
make the routing step explicit.

🛠️ Two CLI UX fixes (from the end-to-end dogfood)

1. review --update-status now also refreshes plan.json — removes
   the "you forgot to re-plan before the next run" gotcha. Review output
   includes status_update.plan_json_refresh: {refreshed: bool, error}
   so callers can observe the sync.
2. verify-install emits an actionable hint field when the only
   failure mode is sha256 mismatches on tracked files — carries the
   exact refresh-manifest command to fix it (the overwhelming
   "I edited a script in place" case).

📖 Real end-to-end walkthrough

docs/e2e-walkthrough.md
records every CLI command from init through shipping on a real
multi-file task, with 3 parallel agent workers, 45 s wall-clock total,
and both UX gotchas honestly documented.

🎯 Repositioning (docs)

• README hero rewritten: operating layer for multi-agent repository work
  (not "local-first harness").
• New top-of-fold "When to use / When NOT to use" section with the
  5.8× sqlfluff data point.
• New "5 stages — and when each fires" permutation table.
• CITATION.cff abstract positions RePERS as the contract layer above
  agent runtimes (LangGraph / CrewAI / OpenHands), not a competitor.
• ROADMAP gains an "Out of scope" section.

Stats

• Capabilities: 24 → 25 (route added)
• Skills: 4 → 5 (/repers-route added)
• Installed files: 42 → 43 (router.py added)
• Existing scripts: 3 META scripts got module docstrings (dag_engine.py,
  state_report.py, snapshot_freshness.py) — fixed via the harness
  itself in the dogfood.

Upgrading from v0.1.0

# Codex plugin:
/plugin marketplace update repers
/plugin update repers   # or uninstall + install if cached
# (then restart Codex if the skill description still looks old)

# Repo-local runtime:
git pull
python .repers/scripts/repers.py refresh-manifest --json
python .repers/scripts/repers.py verify-install --json

Assets

• repers-0.1.1.zip — installable runtime archive
• repers-release-pack.zip — transferable evidence bundle
• repers-verify-all.json — full local-gate evidence

What's next (v0.2)

See ROADMAP.md.
Headline items: a real "harness wins" example (multi-file SWE-bench Verified
walkthrough), a WORKER.md contract spec, a registry trim from 25 → ~16,
and router signal extensions (preflight hit count + similar-PR git-log
overlay).