From ad10203a32c5f6db5f2c62a1207d45238f2987c2 Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Thu, 13 Aug 2026 02:05:25 +0000
Subject: [PATCH 1/2] Version Packages

---
 .changeset/shared-process-scripts.md | 19 -------------------
 packages/process/package.json        |  2 +-
 2 files changed, 1 insertion(+), 20 deletions(-)
 delete mode 100644 .changeset/shared-process-scripts.md

diff --git a/.changeset/shared-process-scripts.md b/.changeset/shared-process-scripts.md
deleted file mode 100644
index 6d67d02..0000000
--- a/.changeset/shared-process-scripts.md
+++ /dev/null
@@ -1,19 +0,0 @@
----
-"@cosyte/process": patch
----
-
-First release of `@cosyte/process`: the shared per-repo process scripts for the `@cosyte/*` repos,
-behind one `cosyte-process` bin.
-
-Every parser repo hand-maintains the same five `package.json` scripts, the same variant scripts, and
-the tool versions behind them, which is the copy-per-repo shape `@cosyte/script-utils` already
-removed from the PHI gate. A wired consumer's script body becomes exactly `cosyte-process <verb>` for
-`build`, `test`, `lint`, `typecheck` and `format`, and never changes again; what a verb runs, and at
-which tool version, moves with a version bump of this package plus `pnpm install`.
-
-The five delegated verbs propagate the tool's exit code verbatim. `cosyte-process check` grades the
-invoking repo's own wiring for CI. Repo-specific deviation lives in `cosyte-process.config.json` and
-nowhere else: per verb, `globs` and `flags` replace those token classes of the baseline, while the
-tool name and the mode-selecting core tokens are never touched. tsup, vitest with
-`@vitest/coverage-v8`, eslint, prettier and typescript are dependencies of this package and resolve
-from it, so a wired consumer declares none of them.
diff --git a/packages/process/package.json b/packages/process/package.json
index 4ca0796..2882e90 100644
--- a/packages/process/package.json
+++ b/packages/process/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@cosyte/process",
-  "version": "0.0.0",
+  "version": "0.0.1",
   "description": "The shared per-repo process scripts for @cosyte/* repos: one `cosyte-process` bin behind build, test, lint, typecheck, format and check.",
   "keywords": [
     "cli",

From 8805ee1927d41e21a44993a4c37b3b996e191770 Mon Sep 17 00:00:00 2001
From: Noah Schatz <noah.lane.schatz@gmail.com>
Date: Thu, 13 Aug 2026 02:06:47 +0000
Subject: [PATCH 2/2] S0001-config-owns-shared-process: promote @cosyte/process
 CHANGELOG [Unreleased] to 0.0.1

RELEASING.md requires this promotion by hand: the Changesets changelog
generator is disabled for every package here, so nothing writes the version
heading. Done in the Version Packages PR, which is the last commit before
the publish run.
---
 packages/process/CHANGELOG.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/packages/process/CHANGELOG.md b/packages/process/CHANGELOG.md
index 8c94915..f590908 100644
--- a/packages/process/CHANGELOG.md
+++ b/packages/process/CHANGELOG.md
@@ -8,7 +8,7 @@ the **`0.0.x`-until-first-alpha** ladder.
 > Because the generator is disabled, **`[Unreleased]` is promoted to a version heading BY HAND**, in
 > the pull request that adds the changeset. Nothing does it automatically.
 
-## [Unreleased]
+## [0.0.1] - 2026-08-13
 
 ### Added