Build bench releases from a manifest; update.sh consumes them

The repo is two things at once — bench-the-project and bench-the-
distribution — and install/update conflated them by cloning the repo
and subtracting what should not have come along. Invert it: one
curated artifact, correct by construction.

- manager/core/release-manifest: the whole shipping list in one place
  (copy/tree/once/keep/seed classes). update.sh's hardcoded top-level
  file list, promoted.
- release.sh: builds bench.tar.gz from the manifest (contents at the
  tarball root, stable asset name — the tokenless latest-release URL
  depends on both), stamps the source repo into the shipped update.sh,
  refuses on dirty tree or existing tag, tags v<VERSION> and publishes
  via gh release create. Never ships in the artifact.
- update.sh: downloads the latest release (BENCH_REF pins a tag) via
  gh with an anonymous curl fallback; refuses when the asset's VERSION
  disagrees with its tag; replaces manager/core/ wholesale plus the
  artifact manifest's `copy` files; touches nothing else. No release
  published -> says so and changes nothing; no silent git fallback.
- tests: the tarball equals exactly the manifest (no cards, no local/
  content beyond the generated starter, no state/tests/.claude), the
  artifact installs pristine and boots the board, and update.sh's
  replace/survive/refuse paths run hermetically against PATH-stubbed
  gh and curl.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
istos
2026-07-30 07:48:03 +02:00
co-authored by Claude Fable 5
parent d591bd843e
commit d6fb478466
5 changed files with 726 additions and 22 deletions
+44
View File
@@ -0,0 +1,44 @@
# What a bench release ships — the whole list, one place. release.sh
# builds the artifact from it; update.sh reads the copy of this file
# inside the downloaded artifact to know which top-level files to
# replace; the artifact test asserts the tarball matches it exactly.
#
# One entry per line, `<class> <path>`:
#
# copy <file> core-owned file from the repo — shipped, and replaced
# by every update
# tree <dir> directory shipped recursively from the repo, replaced
# WHOLESALE by every update (__pycache__/.DS_Store
# excluded at build)
# once <file> shipped from the repo on install, then yours — updates
# never touch it
# keep <dir> shipped as an empty directory holding a .gitkeep —
# updates never touch it
# seed <file> starter content generated by release.sh (never present
# in bench's own repo, which has its real one) — updates
# never touch it
#
# Anything not listed here does not ship: bench's own task cards, its
# manager/local/ content, local/state/, .claude/, tests/, release.sh.
copy CLAUDE.md
copy README.md
copy install.py
copy start.sh
copy stop.sh
copy update.sh
tree manager/core
once .gitignore
once tasks/task-template.md
keep tasks/backlog
keep tasks/to-do
keep tasks/in-progress
keep tasks/review
keep tasks/done
keep tasks/archive
keep plans
keep reference
keep manager/local/adapters
keep manager/local/commands
keep manager/local/driver
keep manager/local/prompts
seed manager/local/CLAUDE.md