Commit Graph
2 Commits
Author SHA1 Message Date
istosandClaude Fable 5 e800cf1a91 Address PR review: symlink-safe removal, guard-gated stamp, hermetic tests
The first-boot guard is now its own predicate gating both the clean and
the local/state/ stamp, so a disarmed run (pre-existing local/.env, or
self-hosted) touches nothing at all — before, it still created the stamp
directory on any vendored run. Removal unlinks symlinks instead of
following them into rmtree. Tests filter BOARD_* out of the subprocess
environment, assert the stamp stays absent when .env disarms the guard,
and cover the symlink case.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-30 07:22:33 +02:00
istosandClaude Fable 5 44537ae653 Ship a pristine board on install: first boot clears distribution cards
A vendored clone of bench arrives carrying bench's own task cards, plans
and reference documents, so a new user's first board opened pre-loaded
with our backlog. install.py now detects first boot — a vendored install
(project root != manager root) whose manager/local/ has never been
populated (no .env, no state/) — and only then clears the stage
directories, tasks/archive/, plans/ and reference/, keeping
task-template.md and the .gitkeep files and printing every removal.
--dry-run lists instead of removing. After cleaning it stamps
manager/local/state/, so the guard is permanently false on every later
run even if the adapter wire fails, and a host's own cards are never
touched. Self-hosted repos (bench itself, including fresh dev clones)
are never cleaned: their tasks/ is the repo's history.

Covered end-to-end in tests/test_install_first_boot.py by running
install.py as a subprocess against scratch host layouts; README notes
the first-boot behaviour under "Install into a repo".

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-30 07:09:46 +02:00