@natjswenson/press 0.5.0 → 0.6.0

package/CHANGELOG.md

@@ -5,6 +5,38 @@ All notable changes to the **press** skill are documented here.
 The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and
 this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.6.0] - 2026-08-01
+
+### Changed
+
+- **A consumer's pin, its region receipt and the current release are now kept
+  equal.** Previously propagation acted only when generated *values* moved, so
+  a repo could show three different version numbers at once — natejswenson.io
+  read pin 0.2.0, receipt 0.1.0, latest 0.5.1 — and there was no way to tell a
+  healthy consumer from a stale one without knowing the rule. Every release now
+  opens a PR in every consumer.
+
+  What keeps that readable is that the PR says which kind it is: a **brand
+  change** (`press vX — BRAND VALUES CHANGED`) is reviewed as a design change,
+  while a **version-only adoption** (`adopt press vX`) is a one-line diff where
+  nothing renders differently. `propagate --json` reports the two separately as
+  `brand` and `stale`.
+
+  The trade is deliberate: a few no-op pull requests per release, in exchange
+  for state anyone can read at a glance.
+
+## [0.5.1] - 2026-08-01
+
+### Fixed
+
+- **Propagation targeted the default branch, not the integration branch.** Every
+  consumer runs `feature → dev → main`, so a PR opened straight into `main`
+  would violate its own flow. Worse, the default branch can legitimately lag:
+  the first real fan-out reported `budget` and `local-fitness` as *missing* only
+  because their migration was still sitting on `dev`. It now checks out `dev`
+  when the remote has one and falls back to the default branch otherwise.
+- The clone was `--depth=1`, which cannot see other branches. Full clone now.
+
 ## [0.5.0] - 2026-08-01
 
 The last hand-maintained copy of the brand is gone.
@@ -216,6 +248,8 @@ source of truth and a CI drift gate.
   rasterised cards, whose eyebrow legitimately runs at `.16em`. Scoped rather
   than waived, and caught by linting the real shipped corpus.
 
+[0.6.0]: https://github.com/natejswenson/claude-skills/releases/tag/press-v0.6.0
+[0.5.1]: https://github.com/natejswenson/claude-skills/releases/tag/press-v0.5.1
 [0.5.0]: https://github.com/natejswenson/claude-skills/releases/tag/press-v0.5.0
 [0.4.1]: https://github.com/natejswenson/claude-skills/releases/tag/press-v0.4.1
 [0.4.0]: https://github.com/natejswenson/claude-skills/releases/tag/press-v0.4.0

package/SKILL.md

@@ -2,7 +2,7 @@
 name: press
 description: The one brand system for everything produced in Claude — design tokens, the visual laws, the run-presentation contract, and the universal voice core. Use when composing or restyling any artifact (report, résumé, card, cover, PDF, HTML page, chart), when asked about brand colors, fonts, the accent law or "the PRESS look", when adding a new skill that renders anything, or when a brand value needs to change everywhere at once. Also handles "check the brand is in sync", "why do my colors differ", and onboarding a new consumer repo.
 user_invocable: true
-version: 0.5.0
+version: 0.6.0
 ---
 
 # /press — the brand system
@@ -108,13 +108,18 @@ node bin/press.js propagate --repo ../budget             # re-emit + bump its pi
 what moved. The caller turns that into a pull request, so nothing lands
 unreviewed — but nobody has to *remember*.
 
-Two rules keep it from becoming noise or a false negative:
+**One version per repo.** A consumer's CI pin, its region receipt and the
+current release are kept equal, so "is this repo up to date?" is answerable by
+looking. The earlier rule — only act when values move — left three divergent
+version numbers per repo and no way to tell a healthy consumer from a stale one.
 
-- **Content decides, not the version receipt.** A region written by 0.1.0 that
-  is still byte-correct under 0.3.0 is *current*. Opening a PR for it would be
-  noise.
-- **A stale pin alone is not "behind".** It changes no shipped artifact, so it
-  is bumped silently and never triggers a PR on its own.
+Every release therefore opens a PR in every consumer. What keeps that readable
+is that the PR says which kind it is:
+
+| Kind | Title | Review |
+|---|---|---|
+| **Brand values moved** | `press vX — BRAND VALUES CHANGED` | read the diff as a design change |
+| **Version only** | `adopt press vX` | one line; nothing renders differently |
 
 `.github/workflows/press-propagate.yml` runs this on every release and weekly,
 opening a PR in each consumer repo whose bytes actually moved.

package/lib/propagate.mjs

@@ -52,19 +52,35 @@ export function propagate({ tokens, targets, root, version, dryRun = false }) {
     }
     const body = emitBody(tokens, target.emitter, target.params ?? {});
     const after = spliceRegion(before, target.region, target.syntax, body, version);
-    // Compare the region bodies, not whole files: the start marker carries the
-    // emitting version, so a no-op release would otherwise look like a change
-    // and open a pull request that alters nothing anyone can see.
-    const changed = found.body.replace(/\s+$/, '') !== body.replace(/\s+$/, '');
+    // Two different kinds of "changed", kept apart on purpose.
+    //
+    //   brand    the generated VALUES moved — something renders differently and
+    //            the diff must be reviewed as a design change.
+    //   version  only the marker's recorded version moved. Nothing renders
+    //            differently; the repo is adopting a newer press.
+    //
+    // Both are written. Skipping the write when only the version moved is what
+    // produced three divergent version numbers per repo — pin, region receipt
+    // and current release all disagreeing, with no way to tell a healthy
+    // consumer from a stale one at a glance.
+    const brandChanged = found.body.replace(/\s+$/, '') !== body.replace(/\s+$/, '');
+    const versionChanged = found.version !== version;
+    const changed = brandChanged || versionChanged;
     if (changed && !dryRun) writeFileSync(path, after, 'utf8');
     regions.push({
       id: target.id,
       path: target.path,
-      // `changed` is carried as a boolean, never re-derived from the status
-      // string: matching /updated$/ silently missed "would update", so a
-      // dry run reported "nothing to do" while showing a changed region.
+      // Carried as booleans, never re-derived from the status string: matching
+      // /updated$/ once silently missed "would update", so a dry run reported
+      // "nothing to do" while showing a changed region.
       changed,
-      status: changed ? (dryRun ? 'would update' : 'updated') : 'current',
+      brandChanged,
+      versionChanged,
+      status: brandChanged
+        ? (dryRun ? 'would change brand' : 'brand updated')
+        : versionChanged
+          ? (dryRun ? 'would adopt' : 'adopted')
+          : 'current',
       wroteBy: found.version,
     });
   }
@@ -76,9 +92,15 @@ export function propagate({ tokens, targets, root, version, dryRun = false }) {
     version,
     regions,
     pins,
-    // A repo is behind if its bytes moved. A pin bump alone is not worth a pull
-    // request — it changes no shipped artifact.
-    changed: regions.some((r) => r.changed),
+    // A repo needs a pull request if anything moved at all — values or version
+    // — so that its pin, its region receipt and the current release stay one
+    // readable number. Letting the receipt lag "because the body did not
+    // change" produced three divergent versions per repo and no way to tell a
+    // healthy consumer from a stale one at a glance.
+    changed: regions.some((r) => r.changed) || pins.some((p) => p.status !== 'current'),
+    // The subset a human must actually look at: these change what renders.
+    // Everything else is routine adoption and reviews in seconds.
+    brand: regions.filter((r) => r.brandChanged).map((r) => r.id),
     stale: regions.filter((r) => r.changed).map((r) => r.id),
     missing: regions.filter((r) => r.status === 'missing').map((r) => r.id),
   };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@natjswenson/press",
-  "version": "0.5.0",
+  "version": "0.6.0",
   "description": "One brand system — tokens, laws, run presentation and voice core — generated into every consumer with a CI drift gate",
   "license": "MIT",
   "author": "Nate Swenson",