sshlg-skills 1.76.2 → 1.76.3

package/CHANGELOG.md

@@ -1,3 +1,16 @@
+## v1.76.3 (2026-10-24): telegram-dev pinned to 0.5.3
+
+- **Pin:** telegram-dev 0.5.3 (`telegram-bots/references/high-load.md`, a bot under load: the
+  poll loop that awaits a whole batch, a queue per chat under one ceiling, payments outside it,
+  flood guards measured from arrival rather than from the start of handling, the waiting
+  callback answered at once, a bounded shutdown, and what to measure; with
+  `fixtures/update_pump.py`, a discrete-event simulation on a virtual clock whose nine
+  invariants each go red when their rule is removed). The content shipped in 0.5.1; 0.5.2 and
+  0.5.3 add the member's verification ledger section for it (`test/validate.py` refuses a
+  ledger older than the shipped version). `v0.5.0` and `v0.5.2` name no release: the first sits
+  on a commit before the change, the second was a lightweight tag the release workflow refused,
+  and the member's rules keep tags.
+
 ## v1.76.2 (2026-10-24): seo-aeo-audit pinned to 0.32.0
 
 - **seo-aeo-audit 0.32.0** (was 0.31.3), commit `51dba19`: `references/playbooks.md`, ten

package/README.md

@@ -54,7 +54,7 @@ scripts. No services, no telemetry, no API keys.
 | **[seo-aeo-audit](https://github.com/ssheleg/seo-aeo-audit)** | 0.32.0 | Evidence-first website audit for search **and** answer engines. Ten tracks from crawl access to AI citation mechanics; every finding carries an observation, every recommendation an evidence tier, and the output is a prioritized change plan plus a link-building brief, not a score. Before a site is built, `/seo-aeo-audit brief` writes the build-time brief that the audit later verifies. |
 | **[sheleg-dev](https://github.com/ssheleg/sheleg-dev)** | 0.16.0 | The integration layer a product reaches once it has users: **money in, tracking, sign-in, speed**. Stripe subscription billing reconciled into your own database — webhook idempotency, renewals, seats and proration, refunds, price drift, and the coupon offered at the cancel step, where a `duration=once` discount leaves `subscription.discounts` the moment its invoice finalizes and the offer can be taken every cycle; crypto payments that survive under-payment, duplicate webhooks and rate drift; GA4, Google Ads, Meta and LinkedIn under Consent Mode v2; Google sign-in with the account pre-hijacking guard, and the server-side auth surface behind it; Core Web Vitals work that moves the score rather than the report; 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. |
 | **[agent-stack](https://github.com/ssheleg/agent-stack)** | 0.31.2 | Production patterns for agent systems, in four skills. **The orchestrator** — tool-calling loops that survive their own context pressure, pipelines with human checkpoints and resume, provider routing with fallback and health checks, memory architecture — form, function and dynamics, the four-stage retrieval pipeline, and what a layer table alone cannot say, and **the shape of the work decided before the work**: an edge that carries no data is no edge, a plan that declares its dependencies is executed in layers rather than in list order, and a parallel layer gets a checker before the node that consumes it. **The harness** — what the agent is *told*: system prompts at the right altitude, tool descriptions the model can act on, technique choice with a verdict each, workflow versus agent and static versus dynamic, plus a seven-track audit of an agent somebody else built and a scanner for the defects that are mechanically visible. **The evals** — suites that measure whether it actually works: judging trajectories, regression fixtures grown from production, judges calibrated before they are trusted. **The interop layer** — MCP at revision 2026-07-28 and the four features it deprecated, running many servers at once, the registry, A2A 1.0, and the gateway, every reference carrying the spec revision it was read against. Plus the wallet side of reselling LLM access: tiered balances, one markup boundary, two-phase commit against a provider API. |
-| **[telegram-dev](https://github.com/ssheleg/telegram-dev)** | 0.4.0 | Telegram, split by the API each surface actually speaks. **`telegram-bots`** — the official HTTP Bot API: `update_id` as the only idempotency key an update carries, the `allowed_updates` default that subscribes you to everything *except* `chat_member` and the two reaction types while answering `ok: true`, the webhook secret header that is the real check, rate limits as a design constraint (1/sec per chat, 20/min per group, ~30/sec bulk), and Telegram Stars with a **ten-second** pre-checkout window and a grant that belongs to `successful_payment`. **`telegram-userbots`** — MTProto and Telethon: the session file as a credential equal to the password, `FloodWaitError` as the API telling you exactly how long to wait, pinning across minor releases that move session and entity-cache behaviour, and the account-ban risk a bot token does not carry — the skill opens with whether a user account is needed at all. **`telegram-miniapps`** — the web layer, whose entire security model is one signed query string: verifying `initData` server-side, the `auth_date` window, the Ed25519 path for a third party, and the SDK package whose name moved while the organisation's own page still fronts the old one. Both the verifier and the delivery invariants ship as runnable fixtures with their mutants. |
+| **[telegram-dev](https://github.com/ssheleg/telegram-dev)** | 0.5.3 | Telegram, split by the API each surface actually speaks. **`telegram-bots`** — the official HTTP Bot API: `update_id` as the only idempotency key an update carries, the `allowed_updates` default that subscribes you to everything *except* `chat_member` and the two reaction types while answering `ok: true`, the webhook secret header that is the real check, rate limits as a design constraint (1/sec per chat, 20/min per group, ~30/sec bulk), and Telegram Stars with a **ten-second** pre-checkout window and a grant that belongs to `successful_payment`. **`telegram-userbots`** — MTProto and Telethon: the session file as a credential equal to the password, `FloodWaitError` as the API telling you exactly how long to wait, pinning across minor releases that move session and entity-cache behaviour, and the account-ban risk a bot token does not carry — the skill opens with whether a user account is needed at all. **`telegram-miniapps`** — the web layer, whose entire security model is one signed query string: verifying `initData` server-side, the `auth_date` window, the Ed25519 path for a third party, and the SDK package whose name moved while the organisation's own page still fronts the old one. Both the verifier and the delivery invariants ship as runnable fixtures with their mutants, and a bot under load has its own reference: a poll that never waits on a handler, a queue per chat under one ceiling, payments outside it, guards measured from arrival, a bounded shutdown, with a discrete-event simulation whose nine invariants each go red without their rule. |
 | **[xr-dev](https://github.com/ssheleg/xr-dev)** | 0.4.2 | **`quest-lifecycle`** maps the product from platform choice through design, build, testing, Store, monetization, launch and operation. The existing owners cover native OpenXR, Kotlin Spatial/hybrid apps, measured rendering optimization, current-source/tool discovery, commercial and asset readiness, and WebXR/PWA. Every stage names evidence and a next action; Meta engine companions and official Godot XR documentation supply implementation detail. |
 | **[web3d-dev](https://github.com/ssheleg/web3d-dev)** | 0.2.2 | Realtime 3D on the web with three.js and React Three Fiber, split by the question. **`web3d-runtime`** — how the scene runs: WebGPURenderer and its WebGL2 fallback, TSL and compute, post-processing, device loss and profiling, led by the failures r186 keeps silent: `render()` before `init()` throws, `positionNode` collapses every instance to a point, `computeAsync` does not wait for the GPU, and about twenty drei components do not run on WebGPU. **`web3d-assets`** — the glTF pipeline from a source to the frame within a written budget: gltf-transform and gltfpack, KTX2 and meshopt, the loader that reads the result, sourcing and the four licence questions; it delegates orders to the asset service when the machine runs one and works by the same principles when not. **`web3d-animation`** — a two-sided animation protocol with a shared clip canon: rig, clips, blending, retargeting, root motion, crowds and vertex-animation textures. Every fact is pinned to three@0.186.1, and the gate checks each code block against that release's exports. |
 

package/claude-plugin-pins.json

@@ -3502,15 +3502,15 @@
     {
       "name": "telegram-dev",
       "repo": "ssheleg/telegram-dev",
-      "commit": "94251eaae844febabe23fed0399dc5e35783f7c2",
-      "version": "0.4.0",
+      "commit": "50cb6eb0793a5d2db9232c44e36daf7bdd2a77f7",
+      "version": "0.5.3",
       "pluginInstall": "telegram-dev@telegram-dev",
       "pluginPath": "plugins/telegram-dev",
       "entry": {
         "name": "telegram-dev",
         "displayName": "Telegram Dev",
         "description": "Telegram development, split by the API each surface actually speaks. telegram-bots covers the official HTTP Bot API — update_id as the only idempotency key, the allowed_updates default that drops three types in silence, the webhook secret header, rate limits as a design constraint, and Telegram Stars with its ten-second pre-checkout window. telegram-userbots covers MTProto and Telethon — the session file as a credential equal to the password, FloodWaitError as the API working rather than failing, and the account-ban risk a bot token does not carry. telegram-miniapps covers initData verification, the algorithm shipped as a runnable fixture, and the SDK package whose name moved.",
-        "version": "0.4.0",
+        "version": "0.5.3",
         "author": {
           "name": "ssheleg",
           "url": "https://x.com/sshlg93"
@@ -3542,7 +3542,7 @@
       "files": [
         {
           "path": ".claude-plugin/plugin.json",
-          "sha256": "321e45692e19b87607037c5eb2ad5784c224be4536da333736af81f999e20522",
+          "sha256": "40dd708a565101ec397a7a7f0b912043bd83b3340ec361a4816d0dc69c43e5f0",
           "bytes": 1375
         },
         {
@@ -3550,11 +3550,21 @@
           "sha256": "3837eb0a9e13bf4920abdb7f2333699bf6768187544c457f780d108916153733",
           "bytes": 19980
         },
+        {
+          "path": "skills/telegram-bots/fixtures/update_pump.py",
+          "sha256": "ab8d037888e29d0118d87a97be3430d88991fc4100c11d3a08a728ef5ab1cdb9",
+          "bytes": 15220
+        },
         {
           "path": "skills/telegram-bots/references/frameworks.md",
           "sha256": "d2c70658590eea1e4869b5628d9a105688a935dfd6f821bd6bcb3b255ae7dfaf",
           "bytes": 2947
         },
+        {
+          "path": "skills/telegram-bots/references/high-load.md",
+          "sha256": "93075456ae2287c39c5231f0049821c9703184feeb381ff1ed85d311b44c4511",
+          "bytes": 9711
+        },
         {
           "path": "skills/telegram-bots/references/limits-and-files.md",
           "sha256": "736ddf059f83128b567668bd198014d4dffb0f36c6c6bb0db21a7d4d12d1303b",
@@ -3572,8 +3582,8 @@
         },
         {
           "path": "skills/telegram-bots/SKILL.md",
-          "sha256": "a2ce4f256cba788eed8cbd4616c918ceb407a2aaa127c9bcc31af4caacec3202",
-          "bytes": 12079
+          "sha256": "56ceb1a2be3ab12b65fa73bfd7fc5298d1a499e90bb2d1387478f4e91090e5e8",
+          "bytes": 12868
         },
         {
           "path": "skills/telegram-miniapps/fixtures/verify_initdata.py",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "sshlg-skills",
-  "version": "1.76.2",
+  "version": "1.76.3",
   "skillsCli": "skills@1.7.2",
   "description": "The ssheleg harness skill layer: routing, delivery gates, specialist skills and durable handoffs for coding agents.",
   "bin": {

package/skills.json

@@ -225,13 +225,13 @@
         "telegram-userbots",
         "telegram-miniapps"
       ],
-      "version": "0.4.0",
+      "version": "0.5.3",
       "entry": null,
       "role": "which Telegram API each surface speaks, and what each one costs",
       "npm": "@ssheleg/telegram-dev",
       "shape": "static",
       "shapeWhy": "Three fixed surfaces with fixed seams; the only branch is which of the three a task is on, and the first table in each SKILL.md decides that before any code.",
-      "commit": "94251eaae844febabe23fed0399dc5e35783f7c2"
+      "commit": "50cb6eb0793a5d2db9232c44e36daf7bdd2a77f7"
     },
     {
       "name": "xr-dev",