didericis
030a6bc793
The previous demo harness called the backend Python API directly, which didn't match what a user typing `./cli.py start <agent>` would actually see. The recording now goes through the real CLI surface: - claude-bottle.demo.json + scripts/demo-setup.sh stage a demo manifest (one bottle, FAKE_TOKEN env, one unreachable git upstream) alongside a dummy SSH identity at ~/.cache/claude-bottle-demo/. - docs/demo.tape types `./cli.py start demo`, answers the y/N preflight, and runs four bash probes via claude's `!` prefix (curl x3 + git push), so the recording shows real preflight output and real probe results. - scripts/demo.sh wraps setup -> cli.py -> teardown for human use; scripts/demo-record.sh does the same around `vhs docs/demo.tape`. - .gitignore picks up claude-bottle.json so a user's local manifest doesn't get tracked alongside .example / .demo siblings. scripts/demo_harness.py is removed -- its behavior is fully replaced by the cli.py + `!` flow. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
15 lines
360 B
Bash
Executable File
15 lines
360 B
Bash
Executable File
#!/usr/bin/env bash
|
|
# Undo what demo-setup.sh did. Restores any pre-existing
|
|
# claude-bottle.json, removes the dummy SSH identity. Idempotent.
|
|
|
|
set -euo pipefail
|
|
|
|
cd "$(dirname "$0")/.."
|
|
|
|
rm -f claude-bottle.json
|
|
if [ -f claude-bottle.json.demo-backup ]; then
|
|
mv claude-bottle.json.demo-backup claude-bottle.json
|
|
fi
|
|
|
|
rm -rf "$HOME/.cache/claude-bottle-demo"
|