Rebuild¶

Reconstitute the project from whatever survives. Run automatically, this prompt is a drill: it rebuilds from the latest release's source distribution in a scratch directory and proves the result passes its own gates, without publishing anything.

Rendered from the repository at vibey-engine 4.4.0; regenerated by scripts/continuation_prompts.py, do not edit inside these markers.

• Mode when GitHub runs it weekly: drill — verifies and reports; changes nothing.
• What it is for: Reconstitute the project from any surviving copy if the forge, the runner or the operator is gone.
• Decision records: 88, the newest 0088 — TypeScript, never JavaScript: the only authored form is typed, and the JavaScript that must exist is generated.

The prompt¶

You are rebuilding vibey from whatever survives. Assume the forge, the original maintainers
and every past session are gone. Work only in a scratch directory.

1. Find the most complete surviving copy, in this order, and record which you used:
   a. a git clone (full history: `git log --oneline | wc -l` is in the thousands);
      if the forge still stands, `sh scripts/install.sh --from-source DIR` makes one
      and builds it in a single step;
   b. the source distribution of the newest vibey-engine release on PyPI
      (`pip download --no-binary :all: --no-deps vibey-engine`), which carries the whole tree
      that ships (ADR-0037);
   c. the book (book.pdf / book.epub), which carries every document and the paper;
   d. any fork of the-vibey-project/vibey.
2. Rebuild and prove it: create a Python 3.12+ environment, install it (`uv sync --extra dev`
   in a clone; `pip install` the sdist otherwise), and run the gates listed in CLAUDE.md
   under "Commands worth memorizing" that the copy allows. PostgreSQL 14 or newer is
   required for the queue (ADR-0002). Report every gate's result.
3. If the forge is gone, re-home it: create a new repository, push the full history, and
   re-declare everything that was declared — rulesets from [rulesets] in .vibey-gh.toml,
   workflows from .github/workflows/, the repository profile from [repository_profile] —
   with `vibey-gh rulesets` for branch protection and .github/workflows/repository-profile.yml
   for the profile. Secrets, publishing rights and the
   self-hosted runner must be re-established by a person (docs/continuation/succession.md).
4. Never publish, re-tag or overwrite a release under the old names without a person who
   holds those names; a rebuilt project ships under its own new identity until then.
5. Report what survived, what you rebuilt, every gate result, and everything that now needs
   a person.