@ssheleg/sheleg-dev 0.11.3 → 0.11.5

package/CHANGELOG.md

@@ -1,9 +1,41 @@
+## v0.11.5 — the card is the umbrella's render, and the eyebrow stops painting past the canvas
+
+The committed social preview is now generated by the umbrella with the CORRECTED fit
+metric and copied here byte for byte. Nothing about this pack changed.
+
+**Why it was stale.** This member sat in `scripts/site.js`'s `LEGACY_FIT` set, so its card
+was rendered with the pre-correction metric and its eyebrow painted to x=1199 — over the
+padding box the fix exists to remove. A member's card pixels are committed here and
+byte-checked from the umbrella, so only this repository's own release can move them.
+
+Board: `B-118`.
+
 # Changelog
 
 All notable changes to this project are documented here.
 Format: [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 Versioning: [SemVer](https://semver.org/spec/v2.0.0.html).
 
+## v0.11.4 — the registry card stopped lagging what ships
+
+`SKILL-CARD.md` carries the fields Anthropic's Skills-for-enterprise guidance asks every
+organisation to keep — *"written so somebody who did not build this can decide"*. It said
+`0.10.3` while this package shipped `0.11.3`.
+
+**Nothing read it, so it could only drift.** The version moves in `package.json`,
+`plugin.json` and `marketplace.json` on every release; the card was in no list. Measured
+2026-09-01 across the family: **four of nine cards were behind** — `agent-stack` by ten
+minor releases, `sheleg-design` by six, `super-ux` by four, this one by one.
+
+The same check now sits in each of them, which is this family's own rule that a class
+seen twice becomes a script. It refuses a card whose `Version` row disagrees with
+`package.json`, and refuses a card that states no version at all: one a reader cannot see
+go stale is worse than one that lags visibly. Watched failing before it shipped.
+
+Checks 25 → **26**, and `REQ-001`'s quoted gate line moves with it — the ledger's own
+guard caught the restated output before this entry was written, which is what that guard
+is for.
+
 ## v0.11.3 — the schema address was fixed in a position nothing reads
 
 v0.11.2 corrected the `$schema` **name** in both manifests and left the marketplace's

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ssheleg/sheleg-dev",
-  "version": "0.11.3",
+  "version": "0.11.5",
   "description": "Seven integration skills for the layer a product reaches once it has users: Stripe subscription billing and cancellation retention, crypto payments, ad and conversion tracking under Consent Mode v2, Google sign-in and the wider Google auth surface, error tracking, and Core Web Vitals. This package is the installer CLI.",
   "bin": {
     "sheleg-dev": "bin/sheleg-dev.js"

package/plugins/sheleg-dev/.claude-plugin/plugin.json

@@ -3,7 +3,7 @@
   "name": "sheleg-dev",
   "displayName": "Sheleg Dev",
   "description": "The integration layer a product needs once it has users: Stripe subscription billing reconciled into your own database, crypto payments that survive over-payment and duplicate webhooks, ad and conversion tracking under Consent Mode v2, Google sign-in with the account-linking guards, the wider Google auth surface, and Core Web Vitals work that moves the score, and Sentry error tracking wired so it does not forward your own credentials to a third party and so a stack trace names the commit that caused it.",
-  "version": "0.11.3",
+  "version": "0.11.5",
   "author": {
     "name": "ssheleg",
     "url": "https://x.com/sshlg93"