@launch11/srgical 0.0.1 → 0.0.2

package/README.md

@@ -79,16 +79,14 @@ npm run release:pack
 The release bundle lands under `.artifacts/release/`. The broader distribution path, including standalone binaries and
 wrapper package-manager installs, is documented in `docs/distribution.md`.
 
-For release work, add a changeset in your feature branch:
-
-```bash
-npm run changeset
-```
-
 When that branch reaches `main`, the release workflow versions the package, publishes `@launcheleven/srgical` to
 GitHub Packages, publishes `@launch11/srgical` to npm, and opens a matching GitHub Release entry with the packaged
 artifacts.
 
+The repo keeps a base version line in `package.json` and CI computes the next patch version from matching git tags. For
+example, a base version of `0.0.0` means releases flow as `0.0.1`, `0.0.2`, and so on. To move to a new minor line,
+change the base version to something like `0.1.0`.
+
 ## Install Prerequisites
 
 Install `srgical`, then install at least one supported local agent CLI separately.

package/docs/distribution.md

@@ -3,8 +3,8 @@
 ## Current Production Channel
 
 The current production release channels are GitHub Packages for npm, the public npm registry, and GitHub Releases.
-Versioning is source-controlled with Changesets, which means semver intent lives in pull requests instead of being
-inferred from CI build numbers.
+Versioning is tag-driven from git history, which means the repo carries a base major/minor line and CI computes the
+next patch version during release instead of committing a version bump back to `main`.
 
 The npm package does not bundle `codex` or `claude`. Users still need at least one supported local agent CLI installed
 separately and available on `PATH`, and `srgical doctor` remains the truthful way to confirm which agents are usable on
@@ -12,17 +12,18 @@ the current machine.
 
 ## Release Flow
 
-1. A feature branch that changes the package also adds a changeset with `npm run changeset`.
-2. When that branch lands on `main`, the release workflow runs `npm ci`, `npm test`, and `npm run version-packages`.
-3. If the changesets produce a version bump, the workflow commits the updated `package.json`, `CHANGELOG.md`, and
-   consumed changeset files back to `main`.
-4. The same workflow run publishes `@launcheleven/srgical` to GitHub Packages.
-5. The workflow also stages and publishes `@launch11/srgical` to the public npm registry.
-6. After both publishes, the workflow creates a `v<version>` tag and a GitHub Release with the packaged artifacts
-   attached.
+1. `package.json` stores the release line, such as `0.0.0` or `0.1.0`.
+2. When a commit lands on `main`, the release workflow runs `npm ci` and `npm test`.
+3. CI reads the base version, looks for existing `v<major>.<minor>.*` tags, and computes the next patch version for
+   the current untagged commit.
+4. The workflow stages that computed version into temporary package copies without mutating the committed repo files.
+5. The same workflow publishes `@launcheleven/srgical` to GitHub Packages and `@launch11/srgical` to the public npm
+   registry.
+6. After both publishes succeed, the workflow creates a `v<version>` tag and a GitHub Release with the packaged
+   artifacts attached.
 
-This keeps the published semver repeatable across reruns and tracked in git history instead of being tied to a specific
-Actions run number, without requiring a separate release PR just to ship the version bump.
+This keeps the published semver repeatable for a given commit, avoids commit-noise from release-only version bumps, and
+still gives each published package a unique version that both registries can accept.
 
 ## Local Release Check
 
@@ -36,8 +37,9 @@ That command:
 
 - builds the TypeScript CLI,
 - runs `node dist/index.js doctor`,
-- creates an npm tarball under `.artifacts/release/`,
-- writes `release-manifest.json` and `release-manifest.md` with the artifact path and SHA256 hash.
+- computes the next release version from git tags,
+- creates GitHub Packages and npm tarballs under `.artifacts/release/`,
+- writes `release-manifest.json` and `release-manifest.md` with the artifact paths and SHA256 hashes.
 
 ## Registry Configuration
 

package/docs/product-foundation.md

@@ -45,6 +45,6 @@ time.
 ## Distribution Strategy
 
 - Native packages: GitHub Packages as `@launcheleven/srgical` and npm public as `@launch11/srgical`
-- Versioning model: semver via Changesets on GitHub Actions, with version commits pushed directly to `main`
+- Versioning model: semver via git tags on GitHub Actions, with `package.json` carrying the base major/minor line
 - Release artifacts: standalone binaries for Windows, macOS, and Linux
 - Package-manager wrappers: `brew`, `choco`, and other ecosystems can install those release artifacts

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@launch11/srgical",
-  "version": "0.0.1",
+  "version": "0.0.2",
   "description": "A polished local-first CLI for planning and executing long AI-driven delivery sequences.",
   "files": [
     "dist",
@@ -13,18 +13,11 @@
   },
   "scripts": {
     "build": "tsc -p tsconfig.json",
-    "changeset": "changeset",
     "dev": "tsx src/index.ts",
-    "release": "npm run release:pack && npm run publish:github && npm run publish:npm",
     "start": "node dist/index.js",
     "doctor": "tsx src/index.ts doctor",
     "test": "tsx --test test/**/*.test.ts",
-    "test:coverage": "tsx --test --experimental-test-coverage test/**/*.test.ts",
-    "version-packages": "changeset version",
-    "release:pack": "node scripts/release-pack.mjs",
-    "publish:github": "changeset publish",
-    "publish:npm": "node scripts/publish-npm.mjs",
-    "release:version": "node scripts/read-package-version.mjs"
+    "test:coverage": "tsx --test --experimental-test-coverage test/**/*.test.ts"
   },
   "engines": {
     "node": ">=20"
@@ -38,8 +31,8 @@
     "url": "https://github.com/LaunchEleven/Srgical/issues"
   },
   "publishConfig": {
-    "access": "public",
-    "registry": "https://registry.npmjs.org/"
+    "registry": "https://registry.npmjs.org/",
+    "access": "public"
   },
   "keywords": [
     "ai",
@@ -55,7 +48,6 @@
     "commander": "^14.0.3"
   },
   "devDependencies": {
-    "@changesets/cli": "^2.30.0",
     "@types/blessed": "^0.1.27",
     "@types/node": "^25.5.0",
     "tsx": "^4.21.0",