@ssheleg/sheleg-dev 0.5.1 → 0.5.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -4,6 +4,32 @@ All notable changes to this project are documented here.
4
4
  Format: [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
5
5
  Versioning: [SemVer](https://semver.org/spec/v2.0.0.html).
6
6
 
7
+ ## v0.5.2 — 2026-08-16
8
+
9
+ **`CONTRIBUTING.md` described a different repository.** Its *Where things go* table routed
10
+ contributions to `benchmarks.md`, `growth-plays.md`, `myths.md`, `algorithm-updates.md`,
11
+ `aeo-geo.md` and `scripts/page_audit.py` — all six belong to `seo-aeo-audit`, and
12
+ `git ls-files` here matched none of them. Sweeping every file name in the document found
13
+ **eleven** absent, not six: also `deliverable-templates.md`, `technical-checks.md`,
14
+ `threats-and-defense.md`, `test_page_audit.py`, and an `evidence-tiers.md` under a skill
15
+ directory named `sheleg-dev` that has never existed — the six skills are `stripe-billing`,
16
+ `crypto-payments`, `ad-tracking`, `google-signin`, `google-auth` and
17
+ `frontend-performance`.
18
+
19
+ Most of the document was a sibling's, adapted only at the edges. It claimed a
20
+ standard-library auditor and a second test command; there is no runtime code in this
21
+ repository at all, and `python3 test/validate.py` is the whole gate. Rewritten against what
22
+ `git ls-files` actually returns: six skills, twenty reference files, one executable
23
+ (`install.sh`), a four-way version sync, and the eight negative self-tests CI really runs.
24
+
25
+ **The guard is narrow on purpose.** Only the *Where things go* table is checked, because a
26
+ general "every path must exist" rule cannot tell a path being used from a path being
27
+ discussed — the rewrite deliberately names three `seo-aeo-audit` files to send a reader to
28
+ the right repository. The first draft of the guard read the whole section and flagged
29
+ exactly those, one paragraph after the comment explaining why it must not. A bare filename
30
+ resolves by basename, so `SKILL.md` passes as the generic it is while `benchmarks.md` still
31
+ fails. Watched rejecting the original row verbatim.
32
+
7
33
  ## v0.5.1 — 2026-08-16
8
34
 
9
35
  **This gate can now see an invariant it breaks one repository away.** The family umbrella
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@ssheleg/sheleg-dev",
3
- "version": "0.5.1",
3
+ "version": "0.5.2",
4
4
  "description": "Six integration skills for the layer a product reaches once it has users: Stripe subscription billing, crypto payments, ad and conversion tracking under Consent Mode v2, Google sign-in and the wider Google auth surface, and Core Web Vitals. This package is the installer CLI.",
5
5
  "bin": {
6
6
  "sheleg-dev": "bin/sheleg-dev.js"
@@ -2,7 +2,7 @@
2
2
  "name": "sheleg-dev",
3
3
  "displayName": "Sheleg Dev",
4
4
  "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.",
5
- "version": "0.5.1",
5
+ "version": "0.5.2",
6
6
  "author": {
7
7
  "name": "ssheleg",
8
8
  "url": "https://x.com/sshlg93"