Succession

Hand the project to a new steward: what they must hold, where each thing is declared, and how to prove it works. Run automatically, this prompt is a drill: it checks that every name below still exists where it says, and changes nothing.

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: Hand the project to a new steward: what they must hold, where it is declared, and how to verify it.
  • 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 helping a new steward take over vibey (https://github.com/the-vibey-project/vibey).
Your working directory is a clone of it. Assume you remember nothing. Never ask for, print,
store or transmit a secret's value: name secrets only.

Produce a succession checklist, each line verified against the repository:

1. Governance: the operator's authority and how law changes —
   src/vibey_tools/gh/docs/constitution.md (Article II.3: a sub-doctrine is ratified by the
   operator's merge) and src/vibey_tools/gh/docs/doctrines.md. The standing grant for
   unattended work is [autonomy] in .vibey-gh.toml; a new steward re-grants it or not.
2. The forge: the GitHub organisation the-vibey-project; branch protection is declared in
   [rulesets] in .vibey-gh.toml and reconciled by `vibey-gh rulesets`, checked weekly by
   .github/workflows/ruleset-drift.yml. The code owner in .github/CODEOWNERS must be the
   new steward.
3. Secrets, by name only — list every `secrets.NAME` the workflows use
   (`grep -ohE 'secrets\.[A-Z0-9_]+' .github/workflows/*.yml | sort -u`) and, for each, what
   it unlocks and which workflow fails or skips without it. AUTOMERGE_TOKEN carries the
   automation's identity; the Apple and Expo secrets sign the macOS and iOS builds;
   OVSX_PAT publishes the editor extension.
4. Publishing: PyPI and TestPyPI use trusted publishing (environments `pypi` and
   `testpypi` in .github/workflows/vibey-engine.yml and krypton-app.yml) — the new steward
   must be an owner of vibey-engine and krypton-app on both indexes.
5. The self-hosted sovereign runner (docs/runbooks/sovereign-review-runner.md): which lanes
   need it (`grep -lE 'runs-on:.*self-hosted' .github/workflows/*.yml`) and how to register a new one.
6. The domains and the documentation site: https://the-vibey-project.github.io/vibey/.
7. For each line: verified (with the evidence), or not verifiable from the repository (say
   what a person must check). Never change ownership, secrets, rulesets or registrations
   yourself — those are the steward's acts.