sshlg-skills 1.2.0 → 1.3.0

package/CHANGELOG.md

@@ -1,3 +1,61 @@
+## v1.3.0 — the page most likely to be quoted was the one saying least about itself
+
+An audit of the live site, measured rather than recalled. Two leaks and one gain
+shipped; one gain is written down and deliberately not taken.
+
+**The author entity was on two of four templates.** `/` and `/skills/{slug}/`
+carried it; `/agents/` and `/routing/` carried a `BreadcrumbList` and nothing else
+— so the page that exists to answer *"does this run in my agent?"*, the one an
+answer engine is likeliest to quote, told it nothing about who publishes it. The
+`Person` node with its `sameAs` set is now emitted by the **layout**, which is the
+only place a new template cannot arrive without it.
+
+**`/agents/` repeated the front page's whole nine-card grid.** Its job is one
+table; the trailing duplicate diluted it and cost 378 words of link text. Replaced
+with a chip row and one link to the descriptions. Measured effect on the read
+budget — the share of the first ~5700 characters that is content rather than link
+markers, which is one engine's median window and so a `FIELD` tier finding:
+**54.5% → 78.4%**, and the `high` severity is gone.
+
+**The answers had no questions.** Five questions the page actually gets asked are
+now visible text on it, and the `FAQPage` node is built **from the same array the
+page renders** — markup over content a reader cannot see is the thing the audit
+skill refuses, and building both from one source is what stops them drifting.
+
+**`/` is still at 47.9% and that is on purpose.** The driver there is the same card
+grid — but on the front page that grid *is* the page's job. Moving it below the
+install block would trade an engine's first read against the reader's, which is a
+content decision with a real cost, so `docs/seo/plan-2026-08-26.md` records it as
+open with the two options rather than taking it unilaterally.
+
+**One instrument disagreement, recorded rather than argued away.** `page_audit.py`
+reports one of five declared answers as missing from the served body. Under the
+rule the script documents — first 60 characters, collapsed, lowercased — all five
+match, reproduced against the built file, and the page is 32 KB so truncation is
+not the cause. The property that matters was verified independently and holds:
+every marked-up question and answer appears verbatim in the body. The page was not
+mutated further to satisfy an instrument whose disagreement could not be
+reproduced.
+
+`docs/seo/audit-2026-08-26.md` also names what could **not** be checked: no Search
+Console, no second engine, no analytics, no crawl export — so orphans, click depth
+and declared-vs-indexed are unknown, and nothing here claims an engine behaved
+differently. Only that the page offers it more.
+
+## v1.2.1 — the pin catches up with what the run printed
+
+`task-pipeline` **1.77.0 → 1.78.0**, published and serving. The member release
+removed a person's name from the two lines the pipeline prints at run time — the
+banner before its first question and the sign-off — and put the repository and the
+site in the sign-off instead. Its flow diagram also reads top to bottom now and
+carries a linear-curve directive, because GitHub's mermaid was failing the two long
+dotted returns with *"could not find a suitable point for the given distance"*.
+
+**The pin moved only after the registry served it, by identity rather than by
+recency.** A watch on `--limit 1` answers about whatever finished last, which is
+standing instruction #9 and the reason this one polled the run for its own tag and
+then read `dist-tags.latest` from the registry directly.
+
 ## v1.2.0 — the site is built from one of the packs it sells
 
 The design was decided by `sheleg-design`, not by taste, and the pack it picked is

package/README.md

@@ -39,7 +39,7 @@ scripts. No services, no telemetry, no API keys.
 | Skill | Version | What it does |
 |---|---|---|
 | **[super-ux](https://github.com/ssheleg/super-ux)** | 0.48.0 | Scenario-driven UI development. A versioned design chain in `docs/ux/` — the product vision → personas and jobs → user flows → a screens-and-states map with Figma frames → traced scenarios → evidence-backed audits → fix plans, plus `docs/brand/` for how the product speaks. One `/ux` entry point that reaches every skill, two doc-drift linters and a contract doctor. |
-| **[task-pipeline](https://github.com/ssheleg/task-pipeline)** | 1.77.0 | Full-cycle delivery orchestrator. An intake grill interrogates the request into a complete brief, then **ten gated stages** carry it — docs, brainstorm and decompose, spec, plan, build, tests, deploy, post-deploy, wiki, acceptance — refusing to advance until each gate passes. Documentation is a deliverable with its own portable gate, and the retrospective it leaves behind is traceable to the commit that earned each lesson. Ships `project-audit`: a cold-start audit of a whole project — discovery, probes whose unmet needs read `blind` rather than clean, production evidence including one artefact served under two channels, and an HTML report beside a JSON sidecar that says what moved. |
+| **[task-pipeline](https://github.com/ssheleg/task-pipeline)** | 1.78.0 | Full-cycle delivery orchestrator. An intake grill interrogates the request into a complete brief, then **ten gated stages** carry it — docs, brainstorm and decompose, spec, plan, build, tests, deploy, post-deploy, wiki, acceptance — refusing to advance until each gate passes. Documentation is a deliverable with its own portable gate, and the retrospective it leaves behind is traceable to the commit that earned each lesson. Ships `project-audit`: a cold-start audit of a whole project — discovery, probes whose unmet needs read `blind` rather than clean, production evidence including one artefact served under two channels, and an HTML report beside a JSON sidecar that says what moved. |
 | **[agent-sync](https://github.com/ssheleg/agent-sync)** | 1.17.0 | Several agents, one repository, no collisions. Leases with a TTL so two agents cannot claim the same work, race-free id reservation, a run journal and a generated board — over a pluggable knowledge cloud. The answer to "two sessions just committed over each other". |
 | **[make-skill](https://github.com/ssheleg/make-skill)** | 0.23.1 | A skill that builds skills. Create, retrofit, audit and publish agent skills and Claude Code plugins: conformance to the [Agent Skills](https://agentskills.io/specification) open standard, [Anthropic's platform rules](https://platform.claude.com/docs/en/agents-and-tools/agent-skills/overview) (per-surface runtime limits, the Skills API, evals) and the [Claude Code plugin reference](https://code.claude.com/docs/en/plugins-reference), marketplace layout, version sync, validator + CI, every distribution channel, the review checklist for third-party skills, and what a *skill author* must know about MCP and A2A — the protocols themselves live in `agent-stack`. |
 | **[sheleg-design](https://github.com/ssheleg/sheleg-design-skill)** | 1.50.0 | The taste layer. Cinematic scroll-driven landing pages — one scroll clock, motion that degrades to calm, WebGL particle formations — plus product-UI style packs each shipping a ready token layer, and the Figma border: tokens as variables, design to code without hand-copied values. |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "sshlg-skills",
-  "version": "1.2.0",
+  "version": "1.3.0",
   "description": "One launcher/updater for the ssheleg skill family (super-ux, task-pipeline, agent-sync, make-skill, sheleg-design, seo-aeo-audit, sheleg-dev, agent-stack) across every agent — Claude Code, Cursor, OpenCode, Kilo, Kimi, Hermes, OpenClaw, Codex, and more.",
   "bin": {
     "sshlg-skills": "bin/sshlg-skills.js"

package/skills.json

@@ -50,7 +50,7 @@
         "evidence-docs",
         "project-audit"
       ],
-      "version": "1.77.0",
+      "version": "1.78.0",
       "entry": "/task-pipeline",
       "role": "how a change reaches the repository",
       "npm": "task-pipeline-skill",