lain: Instructions file for Codex

AGENTS.md — for AI agents working in this Lain checkout

Standard instructions

Check skills before working a task and look for a useful one

memory cleanliness is important. review we didnt fill the ram or the ssd with garbage data we can regenerate

testing is critical. we alwaya assume someone didnt do the job thats why we test

Add always at the start of each message this "Answer:"

Branch policy

Two-branch model:

• dev — integration. Default branch. PRs target dev. CI: fast lane (Ubuntu tests, lint, npm-shim, schema-drift, health-badge, capability suite, mutation gate). ~5 min.
• main — release line. Receives changes only via reviewed PRs from dev, and only when cutting a new release. CI: full hardened battery (all OSes, capability suite, coverage, release contracts). ~20 min.

Feature branches are cut from dev and merged back into dev. Never target main directly.

dev → main is release-only, not a routine merge:

1. Zero-pending audit — publishing is the LAST step, not the first. Before cutting the branch: nothing half-done may remain. Check, and record the evidence:
   • every item in the acceptance findings register is closed or explicitly scoped out of the release in writing (with why);
   • no open issues from the acceptance program;
   • no known test flakes left unfixed;
   • no uncommitted WIP in any worktree;
   • the acceptance suites, demo.sh, and the full test battery are green on the exact tree to be released. If anything is open, either land it in this release or write the deferral down first. A release that ships with a list of "pendientes" is half-done work.
2. Branch release/v0.x.y off dev.
3. Bump every release-metadata file (Cargo.toml, Cargo.lock, server.json, npm-shim/package.json, Formula/lain.rb). scripts/check-release-version.py --tag v0.x.y validates. Leave the health-badge action's lain-version default on the latest PUBLISHED release — bumping it pre-tag deadlocks the release gate (the badge 404s on the unpublished version and release.yml refuses to build a commit whose CI is red).
4. PR against main (1 review + green agent-contract).
5. After merge: git push origin v0.x.y triggers release.yml.
6. Fast-forward dev: git switch dev && git merge --ff-only main.
7. After the release assets are published: fill Formula/lain.rb's sha256 values from the published SHA256SUMS file, and bump the health-badge action's lain-version default to the new version. The artifacts are not bit-reproducible, so pre-filling the formula produces one that fails verification (this is how v0.8.0 shipped broken); pre-bumping the badge default deadlocks the release gate.