Local checks
Runtime checks
Run a mock smoke when backend availability is not part of the change:Certification
Docs
4.2.565 rejects Node 25+. Use Node 24 LTS or another supported LTS runtime for release docs checks.
Review docs for:
- Current default model and settings.
- GitHub Pages deploys are explicitly guarded with
EYRA_DEPLOY_PAGES=true; private forks should leave the variable unset unless Pages is configured. - Installed config precedence:
~/.config/eyra/.envfirst, repo.envonly for Eyra source checkouts, process env last. - Local-first privacy contract.
- Optional capability gates.
- Installer safety checks and allowed install directories.
- Homebrew formula status: public tap formula with a tagged release asset and pinned sha256.
eyra setup,eyra doctor,eyra paths,eyra update, andeyra uninstallbehavior.- Menu bar install reality:
eyra menu --json --checkreports app-bundle, source-swiftpm, package-resource, or unavailable mode. Normal install docs lead witheyra menuonly when the app bundle is installed. - Commands and Web endpoints.
- Certification limits.
- No private prompt/spec/control-plane files.
- No
.env, prompt/spec/control-plane files, SQLite databases, diagnostic audio, screenshots, release artifacts, secrets, or local identity fixtures beyond approved public project metadata.
Public surface
Before push or release:- Check
git diff. - Check
git status --short --branch. - Run a secret scan when public release scope requires it.
- Confirm branch target is
mainfor this repo unless changed upstream. - Keep physical or environment-specific gates clearly labelled.