External/bench
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Docs: install is the release one-liner, a clone is dev mode

Browse Source 
README's first instruction becomes the tokenless curl | tar against
the stable latest-release URL; the clone path moves to a "working on
bench itself" note. CLAUDE.md's Updating section and .env.example's
BENCH_SOURCE comment describe release-based updates: the source is
stamped at build time, BENCH_SOURCE is an override rather than a
prerequisite.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
istos
2026-07-30 07:48:11 +02:00
co-authored by Claude Fable 5
parent d6fb478466
commit 370fdee833
3 changed files with 45 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files
manager/core/.env.example
+3 -1
View File
@@ -46,7 +46,9 @@ BOARD_WATCH_INTERVAL=2
BOARD_EVENTS_CAP=800
BOARD_HISTORY_CAP=300
# Where update.sh fetches the task-manager distribution from (a git URL).
# Where update.sh fetches the task-manager's releases from (owner/repo, or
# any GitHub URL). Normally unset: the shipped update.sh is stamped at
# build time with the repo it came from, and this overrides the stamp.
# Updates replace manager/core/ and the top-level scripts; they never touch
# tasks/, plans/, reference/ or manager/local/.
BENCH_SOURCE=