releaselisted

# Release — the DOS kernel Semver: `major.minor.patch`. Patch = bug fix, minor = new feature, major = breaking. > **DOS is a substrate, not an app.** This skill is the DOS-context adaptation of > the `job` release skill. It is deliberately *thinner*: DOS single-sources its > version from `pyproject.toml` (one marker, not four), ships **no** release-asset > zip archive, screenshots, versioned-install snapshot, plan-state regeneration, > apply-loop gate, or fanout/dispatch manifest. The dist artifacts — one wheel per > OS/arch, each embedding its native `dos-hook` fast-path binary at `dos/_bin/` > (docs/286), plus a pure-source sdist — are built by CI (`publish.yml` via > `scripts/build_wheels.py`), **never by this skill locally**. The verification > step is the kernel test suite + the truth syscall, not an apply pipeline. If you > find yourself reaching for any of those job-only ceremonies, you're in the wrong > repo's skill. > > **One exception — the plugin's native hook binaries.** The Claude Code plugin > (`claude-plugin/`) bundles the compiled `dos-hook` fast-path binaries (docs/125 > GHF4), committed into `claude-plugin/bin/` so a marketplace install (a git clone) > is a direct install. They are NOT a release asset and NOT in the wheel — they live > in the git tree. Step 5.5 rebuilds them so a release never ships a stale binary > against changed Go source. **Trunk is `master`** (there is no `main` branch in DOS). Every `git push` in this skill targets `master`. Master-