@ssheleg/sheleg-dev 0.12.0 → 0.13.1

package/CHANGELOG.md

@@ -1,3 +1,55 @@
+## v0.13.1 — a payment bug reaches the billing skill
+
+The 2026-10-08 family routing audit found that a request opening with the symptom rather
+than the vendor — «баг в оплате», "payment bug", or plain «оплата» — loaded no skill.
+`stripe-billing` was written for someone who already knew the word Stripe: its
+description led with "connecting a product to Stripe" and its only payment phrase was
+«оплата подпиской».
+
+- **`stripe-billing` now names "payment bug", «баг в оплате» and «оплата» in its first
+  sentence**, ahead of the point where harness listings truncate a description. Room
+  was made by tightening wording, not by dropping a trigger: every routed trigger the
+  umbrella's table holds for this skill is still advertised. 959 → 965 characters,
+  inside the 970 working limit.
+- **The trigger corpus gains `q15` and `q16`** («баг в оплате: после оплаты подписка не
+  активируется», "Payment bug: customers are charged twice for one Stripe checkout"),
+  one per split. They are data for the next measured run, not a result.
+
+Bare «оплата» is broad, and the near-miss negatives already in the corpus (`q09` «нарисуй
+экран оплаты», `q11` Telegram Stars) are the cases a measured run should watch: the
+first is the visual layer's, the second telegram-dev's.
+
+## v0.13.0 — the gate exists on one surface, and every skill now says so
+
+This pack ships a `PreToolUse` money gate (`hooks/money-gate.js`) that refuses a refund,
+a payout, a dispute close, a live `sk_live_…` key and `SKIP_BILLING=true` in production
+until the authorised person has signed that category off. It runs on Claude Code and
+nowhere else. Measured 2026-09-14: of the seven skills, **one** (`error-tracking`) wrote
+a degradation contract; `stripe-billing` never mentioned the gate at all and
+`crypto-payments` named it and sent the consequences to the README — so the two skills
+the gate exists FOR were the two that did not say what happens without it.
+
+- **`## Degradation` in all seven skill bodies**, one line per axis, in the shape
+  `references/host-capabilities.md` requires: not-Claude-Code, installed-by-copy, and the
+  capability each skill's own work needs (Stripe CLI, node fixtures, a browser channel, a
+  console login).
+- **`check_degradation_is_written_where_a_host_capability_ships`** — a pack that ships
+  `hooks/hooks.json` requires the section in every skill body. Watched failing on four
+  skills before they were written.
+- **The body budget is MEASURED, not estimated.** This gate divided by 3.9 chars/token
+  while the family's CI auditor measures with tiktoken, and the two disagree by up to 8%
+  in the same direction: `crypto-payments` estimated **4986** and measured **4618** — a
+  verdict of *past the working limit* over 132 tokens of real headroom, which is what
+  blocked this change from landing. With no tokenizer installed the check now DISCLOSES
+  that it could not measure instead of failing a file it never counted. make-skill
+  v0.28.0 closed exactly this for the family auditor; this repo kept the estimate and so
+  kept the defect.
+- **The `биллинг` trigger is now `биллинг подписок`.** Bare `биллинг` collided with
+  `agent-orchestrator`'s `биллинг LLM` across packs, where no per-repo validator can see
+  it: this one meters what an agent burned, that one charges a card.
+- `docs/evals/stripe-billing.md` restates a measured figure (4521 tokens, tiktoken)
+  rather than a heuristic one, and the validator compares it to a measurement.
+
 ## v0.12.0 — the integration doctrine closes its audit, and a crypto reference gains its map
 
 Sherlock external-v3 (43 findings) — the largest share in the family — each with

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ssheleg/sheleg-dev",
-  "version": "0.12.0",
+  "version": "0.13.1",
   "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.12.0",
+  "version": "0.13.1",
   "author": {
     "name": "ssheleg",
     "url": "https://x.com/sshlg93"

package/plugins/sheleg-dev/skills/ad-tracking/SKILL.md

@@ -414,3 +414,14 @@ when** line, so the trigger has one home and this table stays an index.
 
 For the page-speed side of the same problem — what the tag does to LCP and TBT,
 and what to do about it — see the `frontend-performance` skill in this pack.
+
+## Degradation
+
+- **Not Claude Code** (Cursor, Codex, the skills CLI, the API container): the pack's
+  `PreToolUse` gate does not run. It is the thing that refuses a live key or an
+  irreversible action in this pack; elsewhere those rules are advice you follow by hand.
+- **Installed by copy rather than as a plugin**: the doctrine arrives, `hooks/` does not
+  — same loss, same remedy.
+- **No network, or the ad platform's API unreachable**: server-side events cannot be
+  verified end to end. Say the dedup check did not run rather than reporting it held;
+  a browser pixel firing proves the browser, never the conversion.

package/plugins/sheleg-dev/skills/crypto-payments/SKILL.md

@@ -399,3 +399,18 @@ a green suite, each with the defect it catches:
 | Cannot answer "how much did we net" | commission and `merchantAmount` never stored |
 | A dev machine, a CI job or an agent run is holding the production key | no separate credential, and no assertion binding the key to a declared environment |
 | Real invoices in a merchant dashboard nobody watches | a staging credential declared live — the mismatch nothing refused |
+
+## Degradation
+
+- **Not Claude Code** (Cursor, Codex, the skills CLI, the API container): the
+  `PreToolUse` gate named above — `plugins/sheleg-dev/hooks/money-gate.js` — does not
+  run there. Nothing refuses a payout, a refund, an exported `HELEKET_API_KEY` in a
+  `test` run, or `SKIP_BILLING=true` in production. The three lines are advice again,
+  which is exactly the state that made them ineffective for four releases: name the
+  surface you are on, and make the authorisation a human step out loud.
+- **Installed by copy rather than as a plugin**: the doctrine arrives, the hook does
+  not. The README carries the categories and how one is authorised for a session.
+- **No node, or the fixtures cannot run**: the invariant fixtures are the executable
+  half of this skill. Say the check did not run rather than reporting the invariant as
+  held — an unrun check and a passing one are indistinguishable from the exit code
+  nobody looked at.

package/plugins/sheleg-dev/skills/frontend-performance/SKILL.md

@@ -192,3 +192,14 @@ Four names that used to sit here — `frontend-design`, `landing-page-design`,
 `next-best-practices`, `responsive-design` — resolved to nothing installable, and
 `seo-audit` was one character-class away from the real `seo-aeo-audit`, which is
 how a typo survives review.
+
+## Degradation
+
+- **Not Claude Code** (Cursor, Codex, the skills CLI, the API container): the pack's
+  `PreToolUse` gate does not run — every rule here still applies, enforced by a person
+  instead of a hook.
+- **No browser channel** (no Chrome DevTools MCP, no Playwright): a page is judged from
+  the diff and the numbers are not measured on this machine. Record the weaker claim;
+  a Lighthouse score nobody ran is not a score.
+- **No network**: PageSpeed Insights and field data are unavailable. Lab reasoning is
+  still worth doing — say which half you did.

package/plugins/sheleg-dev/skills/google-auth/SKILL.md

@@ -279,3 +279,12 @@ if credentials.expired and credentials.refresh_token:
 - **[ADC & Service Accounts](references/adc-and-service-accounts.md)** — Application Default Credentials setup, service account keys, JWT, Compute credentials, environment configuration (Node.js + Python)
 - **[Sign In with Google](references/sign-in-with-google.md)** — Google Identity Services (GIS), ID token verification, CSRF protection, One Tap, FedCM (Node.js + Python)
 - **[Workload Identity Federation](references/workload-identity.md)** — AWS, Azure, OIDC/SAML federation, workforce identity, executable-sourced credentials (Node.js + Python)
+
+## Degradation
+
+- **Not Claude Code** (Cursor, Codex, the skills CLI, the API container): the pack's
+  `PreToolUse` gate does not run; a live credential is refused by nothing but you.
+- **Installed by copy rather than as a plugin**: doctrine yes, `hooks/` no.
+- **No browser, or no console access**: the consent screen and the client-id half are a
+  human step. Name the exact screen and what is blocked, do the code half, and do not
+  loop on a login only a person can complete.

package/plugins/sheleg-dev/skills/google-signin/SKILL.md

@@ -151,3 +151,12 @@ attacker's account.
 | `access_denied` on consent | Consent screen still in Testing → publish the app |
 | Works locally, breaks in prod | Prod origin missing in GCP, or `Secure` cookie served over plain HTTP |
 | One Tap missing / FedCM console warnings | FedCM is mandatory since Aug 2025 and the opt-out is gone (checked 2026-08-06). Load `gsi/client` from Google and keep it current — a vendored or pinned copy is the real break. The rendered button flow is unaffected; code branching on the old `isNotDisplayed()` moment callbacks is not |
+
+## Degradation
+
+- **Not Claude Code** (Cursor, Codex, the skills CLI, the API container): the pack's
+  `PreToolUse` gate does not run — the rules here hold, the refusal does not.
+- **No browser channel**: the sign-in button and its redirect are verified by reading
+  the code, not by watching it work. Record that as the weaker claim it is.
+- **No console access**: creating the OAuth client is a human step; state it once, do
+  the rest, and say what is waiting on it.

package/plugins/sheleg-dev/skills/stripe-billing/SKILL.md

@@ -1,20 +1,21 @@
 ---
 name: stripe-billing
 description: >-
-  Use when connecting a product to Stripe, or auditing a live integration:
-  checkout, renewals, seats, proration, refunds, cancellation and the
-  coupon offered at the cancel step, the portal, and the webhook that
-  turns a payment into an entitlement in your database. Covers Stripe's
-  agent toolchain, the pinned API version and SDK retries, price
-  resolution across modes, claim-first webhook idempotency, what invoice
+  Use when connecting a product to Stripe, fixing a payment bug
+  ("баг в оплате", "оплата"), or auditing a live integration: checkout,
+  renewals, seats, proration, refunds, cancellation and the cancel-step
+  coupon, the portal, and the webhook that turns a payment into an
+  entitlement. Covers Stripe's agent toolchain, the pinned API version, SDK
+  retries, price resolution, claim-first webhook idempotency, what
   billing_reason decides, cumulative refunds, the cancellation field
-  flexible billing_mode moved, retention eligibility Stripe cannot
-  express, and write ordering with compensating reverts. Triggers - "add
-  Stripe", "Stripe checkout", "subscription billing", "webhook signature",
-  "invoice.paid", "proration", "refund", "cancel subscription", "retention
-  coupon", "подключить Stripe", "оплата подпиской", "вебхук Stripe",
-  "скидка при отмене", "биллинг". Not for choosing between Stripe products
-  (stripe-best-practices) or reading Stripe docs (stripe-docs).
+  flexible billing_mode moved, retention eligibility Stripe cannot express,
+  and write ordering with compensating reverts. Triggers - "add Stripe",
+  "Stripe checkout", "subscription billing", "webhook signature",
+  "invoice.paid", "proration", "refund", "cancel subscription",
+  "retention coupon", "подключить Stripe", "оплата подпиской",
+  "вебхук Stripe", "скидка при отмене", "биллинг подписок". Not for choosing
+  between Stripe products (stripe-best-practices) or reading Stripe docs
+  (stripe-docs).
 license: MIT
 ---
 
@@ -379,6 +380,21 @@ renewal and proration. The one thing to know before you get there: the signing
 secret `stripe listen` prints is **not** the dashboard's, and using the wrong one
 fails verification in a way that reads like a key problem.
 
+## Degradation
+
+- **Not Claude Code** (Cursor, Codex, the skills CLI, the API container): the
+  `PreToolUse` money gate this pack ships does not exist there — nothing refuses a
+  refund, a payout, a dispute close or a live `sk_live_…` key on your behalf. Every
+  rule below still holds; it is advice again rather than a precondition, so the
+  authorisation step becomes a human one. Say which you are on before acting on money.
+- **Installed by copy rather than as a plugin**: same loss, same remedy — a plain
+  `~/.claude/skills/` copy carries the doctrine and not `hooks/money-gate.js`. The
+  README names the categories and how one is signed off; without the hook, that
+  sign-off is a sentence somebody has to actually say.
+- **No Stripe CLI, no network, or test keys only**: webhook signature verification and
+  the local replay loop are the parts that need the binary. State which is missing
+  once, do the rest, and record what could not be verified rather than implying it was.
+
 ## Before you ship
 
 Not a second checklist — every rule below already has a section above, and a rule