releaselisted

Release one repository from `main` (POS.1100): the checks POS.1140 composes, settled by walkthrough (POS.0570), the README and the release notes regenerated from the settled sources under the principal's eyes (POS.0810, POS.1000), and then `/save` (`.claude/skills/save/SKILL.md`) with the release message and, at an approved major, the tag. The repository is named by its slug, `forge` meaning the engine; without a slug, ask which repository — a release is always one repository, never a sweep. 1. Determine the state from `./scripts/forge-status.ps1` (the scripts are the only door to git — CLAUDE.md, Persistence). A release runs on `main` only: on any other branch, stop and report the branch the repository is on and how to get back (`./scripts/forge-branch.ps1 <slug> main`, after saving). Merging a branch into `main` is git's business, by hand or by merge request, never this command's (POS.1110). 2. Run the checks over the sources through the `/check` procedure (`.claude/skills/check/SKILL.md`) and report the result to the principal — always, even when clean. A project: `light` and `project`. The engine: `light`, `engine` and `project`, the two project checks on `projects/forge`. Launched at once, awaited together. Clean: state that the checks passed. Findings: settle them by walkthrough (CLAUDE.md, Working methods); a finding may be deferred, as the `/check` procedure says, and the release proceeds. Never fix silently; never proceed wi