0.1.3: fix find_global trailing-colon (atom-setup install skip)

Surfaced by an isolated end-to-end install test of release/v0.2.
The bash wrapper's `find_global()` rebuilds PATH like:

  PATH=$(echo "$PATH" | tr ':' '\n' | grep -v ^$ATOM_DIR$ | tr '\n' ':')

The final `tr '\n' ':'` leaves a TRAILING COLON, which bash interprets
as cwd. When the wrapper is run from inside the source dir, cwd
contains a file named `atom-setup` (the wrapper itself), so
`command -v atom-setup` returned `./atom-setup` and the install loop
took the "already installed, skipping" path. Result: a true fresh
install on a machine without atom-setup on PATH ended up with no
global atom-setup, even though the wrapper appeared to succeed.

`find_global()` now strips both empty PATH components and the
trailing colon. All 5 CLIs install correctly in a scratch test.

Existing 0.1.2 users in any working state are unaffected — the bug
only bites a fresh `git clone + ./atom-setup` on a machine that
doesn't already have `atom-setup` on PATH.

Adds VERSION at the repo root. Plain text, forward-compatible with
the `atom upgrade` verb landing in v0.2 (which polls this file on
`main` to decide whether a new release is available).

Versions bumped 0.1.2 → 0.1.3 across all 5 package.json + lockfiles.
scripts/test-atom-setup.sh assertion updated. 57/57 still pass.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Author: machbuilds

CHANGELOG.md

@@ -6,6 +6,18 @@ All notable changes to atom land here. Format: [Keep a Changelog](https://keepac
 
 Tracking work targeting v0.2. See `docs/planning/` for in-flight build plans.
 
+## [0.1.3] — 2026-05-07
+
+Hotfix surfaced by an end-to-end isolated install test of `release/v0.2`. Existing 0.1.2 users in any working state are unaffected; the bug only bites a fresh `git clone + ./atom-setup` on a machine that doesn't already have `atom-setup` on PATH.
+
+### Fixed
+
+- **`./atom-setup` silently skipped installing `atom-setup` itself.** The bash wrapper's `find_global()` rebuilds PATH via `echo "$PATH" | tr ':' '\n' | grep -v ^$ATOM_DIR$ | tr '\n' ':'`. The final `tr` left a **trailing colon**, which bash interprets as cwd. When the wrapper is run from inside the source dir, cwd contains a file named `atom-setup` (the wrapper itself), so `command -v atom-setup` returned `./atom-setup` and the install loop took the "already installed, skipping" path. `find_global` now strips both empty PATH components and the trailing colon.
+
+### Added
+
+- **`VERSION`** at the repo root. Plain text, single line. Forward-compatible with the `atom upgrade` verb landing in v0.2 (the upgrade verb polls this file on `main` to decide whether a new release is available).
+
 ## [0.1.2] — 2026-05-07
 
 Patch release. Single fix to the install path so a fresh `git clone + ./atom-setup` actually works.
@@ -65,7 +77,8 @@ First feature-complete release. atom is a project-starter template with cross-pr
 - Stack presets currently include `nextjs` only. Other stacks fall back to the generic scaffold and will land per-stack in v0.2.
 - Constitution generation is a TODO marker in the cheatsheet; v0.2 will wire `speckit-constitution` automatically.
 
-[Unreleased]: https://github.com/machbuilds/atom/compare/v0.1.2...HEAD
+[Unreleased]: https://github.com/machbuilds/atom/compare/v0.1.3...HEAD
+[0.1.3]: https://github.com/machbuilds/atom/releases/tag/v0.1.3
 [0.1.2]: https://github.com/machbuilds/atom/releases/tag/v0.1.2
 [0.1.1]: https://github.com/machbuilds/atom/releases/tag/v0.1.1
 [0.1.0]: https://github.com/machbuilds/atom/releases/tag/v0.1.0

VERSION

@@ -0,0 +1 @@
+0.1.3

atom-setup

@@ -43,9 +43,18 @@ CLIS=(atom atom-setup nucleus learnings model-race)
 # Find the GLOBAL atom-setup (skip cwd in PATH so we don't recurse into
 # this script). Used both for "already installed?" detection and for the
 # final exec.
+#
+# Two failure modes the cleanup handles:
+#  - $ATOM_DIR explicitly in PATH (filtered by `grep -v ^$ATOM_DIR$`)
+#  - empty PATH components (which bash treats as cwd) introduced when
+#    splitting/joining; if cwd happens to be $ATOM_DIR, that smuggles
+#    `./atom-setup` (this script) in as a "global" hit. Strip both empty
+#    lines and the trailing colon.
 find_global() {
   local name="$1"
-  PATH=$(echo "$PATH" | tr ':' '\n' | grep -v "^$ATOM_DIR$" | tr '\n' ':') command -v "$name" 2>/dev/null
+  local cleaned
+  cleaned=$(echo "$PATH" | tr ':' '\n' | grep -v "^$ATOM_DIR$" | grep -v '^$' | tr '\n' ':' | sed 's/:$//')
+  PATH="$cleaned" command -v "$name" 2>/dev/null
 }
 
 # ─── install CLIs (only what's missing) ─────────────────────────────

bin/atom-setup/package-lock.json

@@ -1,6 +1,6 @@
 {
   "name": "@atom/atom-setup",
-  "version": "0.1.2",
+  "version": "0.1.3",
   "description": "Interactive wizard that transforms a cloned atom checkout into a personalized project.",
   "type": "module",
   "bin": {

bin/atom-setup/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@atom/atom",
-  "version": "0.1.2",
+  "version": "0.1.3",
   "description": "Top-level help dispatcher for atom's tooling. Lists every CLI in one place.",
   "type": "module",
   "bin": {

bin/atom/package-lock.json

@@ -1,6 +1,6 @@
 {
   "name": "@atom/learnings",
-  "version": "0.1.2",
+  "version": "0.1.3",
   "description": "Your local playbook of generalized patterns. Lives at ~/.atom/learnings, optionally synced to a private GitHub repo. Auto-copied into every new atom-bootstrapped project.",
   "type": "module",
   "bin": {