hostinger-api-mcp 3.25.1 → 3.27.0

package/CHANGELOG.md

@@ -4,6 +4,30 @@ Generated at release time from the diff between the previous and current
 build. Tool changes are listed individually; everything else is summarised
 by area.
 
+## v3.27.0 — 2026-11-03
+
+### Operations
+
+- Added `gpu_catalog_pool-groups` — Get pool groups
+- Added `gpu_catalog_pool-instance-types` — Get pool instance types
+- Added `gpu_catalog_pool-os-templates` — Get pool OS templates
+- Added `gpu_catalog_pool` — Get pool list
+
+### Also in this release
+
+- Documentation: `README.md`
+- Dependencies: `package-lock.json`, `package.json`
+- Request handling and authentication: `src/core/runtime.js`, `src/core/runtime.ts`
+- Build and packaging: `types.d.ts`
+- Server entry points: `src/servers/gpu.js`, `src/servers/gpu.ts`
+
+## v3.26.0 — 2026-11-03
+
+### Also in this release
+
+- Bundled agent skills: 5 files
+- Other files: `src/core/skills.js`, `src/core/skills.ts`
+
 ## v3.25.1 — 2026-11-03
 
 ### Operations

package/README.md

@@ -69,13 +69,14 @@ pnpm update -g @hostinger/mcp
 
 This package installs the following MCP server commands:
 
-- `hostinger-api-mcp` — unified server over every operation (408 total)
+- `hostinger-api-mcp` — unified server over every operation (412 total)
 - `hostinger-agency-hosting-mcp` — 43 operations for agency-hosting
 - `hostinger-agent-readiness-mcp` — 4 operations for agent-readiness
 - `hostinger-billing-mcp` — 10 operations for billing
 - `hostinger-dns-mcp` — 9 operations for dns
 - `hostinger-domains-mcp` — 43 operations for domains
 - `hostinger-ecommerce-mcp` — 30 operations for ecommerce
+- `hostinger-gpu-mcp` — 5 operations for gpu
 - `hostinger-horizons-mcp` — 7 operations for horizons
 - `hostinger-hosting-mcp` — 57 operations for hosting
 - `hostinger-mail-mcp` — 39 operations for mail
@@ -1740,6 +1741,60 @@ store currency. Returns the created variant.
 - **Method**: `POST`
 - **Path**: `/api/ecommerce/v1/stores/{store_id}/products/{product_id}/variants`
 
+### `hostinger-gpu-mcp`
+
+#### changelog_list-entries
+
+What's new and what's coming at Hostinger: list entries of the public Hostinger changelog (release notes, product updates, recent changes, new features and improvements) and of the public roadmap (upcoming features not released yet). Released entries come newest first; upcoming items come soonest expected release first. Reads released changelog entries by default; pick upcoming for the roadmap or all for both. Filter by product or date. Each entry has its title, summary, product, URL, status (released or upcoming), and plan when the entry states one; released entries have their date, upcoming items their expected release date when set. Needs no API token.
+
+- **Method**: `custom`
+- **Path**: `custom`
+
+#### gpu_catalog_pool-groups
+
+Retrieve GPU pool groups, ordered by name.
+
+Each group bundles the pools of one GPU model and lists its currently available pools,
+whether any of them is available and the lowest hourly price among its instance types.
+The price is returned even when the group is out of stock.
+
+Use this endpoint to show which GPU models can be ordered and from what price.
+
+- **Method**: `GET`
+- **Path**: `/api/gpu/v1/pools/groups`
+
+#### gpu_catalog_pool-instance-types
+
+Retrieve the instance types offered by a specified GPU pool, ordered by CPU core count.
+
+Each instance type describes its CPU, memory and storage, and its hourly price.
+Only instance types that can currently be ordered are returned.
+
+Use this endpoint to choose the `pool_instance_id` for a new GPU instance.
+
+- **Method**: `GET`
+- **Path**: `/api/gpu/v1/pools/{poolId}/instances`
+
+#### gpu_catalog_pool-os-templates
+
+Retrieve the OS templates that can be installed on a specified GPU pool instance type.
+
+Use this endpoint to choose the `os_template_id` for a new GPU instance.
+
+- **Method**: `GET`
+- **Path**: `/api/gpu/v1/pools/{poolId}/instances/{poolInstanceId}/os-templates`
+
+#### gpu_catalog_pool
+
+Retrieve all available GPU pools, ordered by name.
+
+A pool serves GPU accelerators of one model from a single region.
+
+Use this endpoint to choose a pool before listing its instance types.
+
+- **Method**: `GET`
+- **Path**: `/api/gpu/v1/pools`
+
 ### `hostinger-horizons-mcp`
 
 #### changelog_list-entries

package/gemini-extension.json

@@ -1,6 +1,6 @@
 {
   "name": "hostinger-api-mcp",
-  "version": "3.25.1",
+  "version": "3.27.0",
   "description": "Hostinger API — manage domains, DNS, hosting, VPS, billing and more from Gemini CLI.",
   "mcpServers": {
     "hostinger": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "hostinger-api-mcp",
-  "version": "3.25.1",
+  "version": "3.27.0",
   "mcpName": "io.github.hostinger/hostinger-api-mcp",
   "description": "MCP server for Hostinger API",
   "repository": {
@@ -25,6 +25,7 @@
     "hostinger-dns-mcp": "./src/servers/dns.js",
     "hostinger-domains-mcp": "./src/servers/domains.js",
     "hostinger-ecommerce-mcp": "./src/servers/ecommerce.js",
+    "hostinger-gpu-mcp": "./src/servers/gpu.js",
     "hostinger-horizons-mcp": "./src/servers/horizons.js",
     "hostinger-hosting-mcp": "./src/servers/hosting.js",
     "hostinger-mail-mcp": "./src/servers/mail.js",

package/server.json

@@ -6,12 +6,12 @@
     "url": "https://github.com/hostinger/api-mcp-server",
     "source": "github"
   },
-  "version": "3.25.1",
+  "version": "3.27.0",
   "packages": [
     {
       "registryType": "npm",
       "identifier": "@hostinger/mcp",
-      "version": "3.25.1",
+      "version": "3.27.0",
       "transport": {
         "type": "stdio"
       },

package/skills/headless/VERSION

@@ -1,3 +1,3 @@
-version=3.25.1
-commit=f6e99e0c7be6
+version=3.27.0
+commit=dfa3d353b2a7
 built=2026-11-03

package/skills/headless/steps/05-design/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: headless-step-design
-description: "Step 5 (design) of the Hostinger Headless flow. Derives three distinct design directions from brief.md (plus any reference sites and brand assets), lets the user pick one in a single question, checks the chosen one against the 8-point grid and WCAG 2.2 AA, designs the logo as outlined SVG (wordmark, icon mark, favicon), following any logo wish the owner gave, then writes design.md — tokens, type, logo, components, per-page composition, accessibility and imagery — as the contract the frontend implements (the framework/stack is chosen later by the frontend step). When the brief says to keep an existing look, writes design.md from that look and its own logo instead. Prepare work: runs during the provision wait and never touches the backend."
+description: "Step 5 (design) of the Hostinger Headless flow. Derives three distinct design directions from brief.md (plus any reference sites and brand assets), lets the user pick one in a single question, checks the chosen one against the 8-point grid and WCAG 2.2 AA, draws the logo (the site name as text beside a small SVG icon that is also the favicon), following any logo wish the owner gave, then writes design.md — tokens, type, logo, components, per-page composition, accessibility and imagery — as the contract the frontend implements (the framework/stack is chosen later by the frontend step). When the brief says to keep an existing look, writes design.md from that look and its own logo instead. Prepare work: runs during the provision wait and never touches the backend."
 ---
 
 # headless-step-design
@@ -101,13 +101,9 @@ Read `brief.md`, `state.json`, and `content-model.md` if it exists.
    shade of the same hue in that role only. Spacing moves to the nearest grid value, and a font
    without an `@fontsource` package swaps to the closest one that resolves (5.4).
 4. **Logo.** Reuse the existing logo and favicon unchanged; never redraw or recolour them. With no
-   existing logo, the header shows the site name as text in the kept display font, and no logo is
-   designed.
+   existing logo, the header shows the site name as text in the kept display font; no icon is drawn.
 5. **Write `design.md`** (Step 7) from the kept look, then hand off as usual. In **Logo**:
    - *Files* and *Use* name the files as saved (a `.png` stays a `.png`), or say "No favicon kept".
-   - *Built from* says "Kept, not rebuilt". *Measured* still gives the width at `--logo-h-sm`
-     (≤ 192 px; else lower `--logo-h-sm` or show the name as text on small screens), and the header
-     link has `alt` = the site name and a target of at least 24 px (as in Step 6).
    - With no logo: *Files* says "None", *Use* says the header link holds the site name as text in
      `--font-display` and the browser's default favicon stays, and the *Don't* line is dropped.
 
@@ -118,7 +114,7 @@ Before inventing anything, gather what already constrains the design:
 | Signal | Where | How it constrains |
 |---|---|---|
 | Tone, purpose, audience | `brief.md` → *Tone*, *Purpose*, *Audience* | Sets the mood all three directions must fit |
-| Brand assets | `brief.md` → *Assets* | Logo, brand colours and fonts are **fixed** in every direction. Never recolour a supplied logo; Step 6 uses it instead of designing one |
+| Brand assets | `brief.md` → *Assets* | Logo, brand colours and fonts are **fixed** in every direction. Never recolour a supplied logo; Step 6 uses it instead of drawing an icon |
 | Pages and entities | `content-model.md` → *Navigation*, *Pages*, *Articles*; if it doesn't exist yet, `brief.md` → *Pages* | Drives the component inventory and page composition |
 | Reference sites | URLs in the brief or the conversation | Cues to borrow (see below) |
 | Images already sourced | `content-model.md` → the image lines under *Articles* (skip if none yet) | Glance at a few at small size; keep accents from clashing with their dominant colours |
@@ -165,9 +161,9 @@ Each direction carries exactly this:
   outlines, hard 8 px offset shadows, tilted cards").
 - **Signature element** — the one memorable move (a scrolling marquee, stickers, oversized numerals,
   a duotone photo treatment). If it moves on its own, it gets a pause control (5.3).
-- **Logo idea** — one line on how the name becomes a logo, using a move from Step 6 ("letters
-  bounce in different colours and the O is a smiley"). When the brief carries a logo wish (*Design
-  direction* or *Assets*), every direction's logo idea is that wish in its own style. A wish is words
+- **Logo idea** — one line on the small icon beside the name ("a smiling sun in butter yellow with
+  an ink outline"). When the brief carries a logo wish (*Design direction* or *Assets*), every
+  direction's logo idea is that wish in its own style. A wish is words
   describing a logo; a logo file in *Assets* is a supplied logo and wins (Step 6).
 
 **Only offer what can pass.** Before asking, run two quick gates on **all three**:
@@ -175,8 +171,7 @@ Each direction carries exactly this:
 1. **Contrast gate.** Every colour that will carry text (base, surfaces, and any accent used as a
    text block) has a palette text colour reaching **4.5:1** on it. Two text colours are fine (dark on
    light blocks, light on dark ones). Accents that only ever hold large text need 3:1.
-2. **Font gate.** Each font resolves on npm, and the display font also has a static `@fontsource`
-   package, because the logo is built from it (5.4).
+2. **Font gate.** Each font resolves on npm (5.4).
 
 A direction that fails either gate gets adjusted, not offered as-is. Don't offer a look that only
 works by breaking the rules, such as body text on a neon accent or a marquee that can't be stopped.
@@ -199,7 +194,7 @@ notes. The question may end with one plain clause saying they can add a logo ide
 never suggest one or give an example: that idea would end up in the logo.
 
 > **Sticker-book maximal** — Loud and playful, like a scrapbook: candy pink, butter yellow and lilac,
-> chunky headlines, tilted sticker photos and a bouncy logo with a smiley O.
+> chunky headlines, tilted sticker photos and a smiling-sun logo.
 
 > **Midnight disco** — A dark, glowing night-out feel: deep purple with neon pink, yellow and
 > turquoise, heavy rounded headlines and a logo like a neon sign.
@@ -217,8 +212,8 @@ Then:
 **Logo wish.** An answer can carry a logo idea next to the pick ("A, and make the logo a little
 teapot"); it replaces the chosen direction's logo idea, and wins over a wish from the brief.
 Whenever the logo follows a wish, from the answer or the brief, add it once to the line that confirms
-the pick: *"The logo follows your idea: a little teapot."* If the kit can't draw it as said (a
-detailed illustration, a photo), build its closest kit version and name what you simplified in that
+the pick: *"The logo follows your idea: a little teapot."* If it can't be a small icon as said (a
+detailed illustration, a photo), draw a simple version of it and name what you simplified in that
 same line. Don't ask a follow-up.
 
 Don't ask about anything else in this step.
@@ -297,9 +292,7 @@ These criteria are settled at design time. Write each answer into the **Accessib
 For each family, prefer the variable package and fall back to the static one:
 `npm view @fontsource-variable/<slug> version`, then `npm view @fontsource/<slug> version`. One must
 answer with a version. If neither does, swap to the closest family that does. Record the exact
-package names. The **display** family must also resolve as a static package
-(`npm view @fontsource/<slug> version`): the static packages ship `.woff` files the logo kit can
-read; the variable ones ship only `.woff2`.
+package names.
 
 ### 5.5 The header fits on one line
 
@@ -314,7 +307,10 @@ can't build it that way.
   button at the width where the logo, all nav items and the button stop fitting on one line, which is
   usually wider than the mobile breakpoint. Estimate that width from the number of nav items and their
   label lengths, round up to a multiple of 8, and make it the header's own breakpoint. Below it, only
-  the logo and the menu button show; the nav items and the CTA move into the opened menu.
+  the logo and the menu button show; the nav items and the CTA move into the opened menu. At 320 px
+  the icon, the site name (`--text-logo`, `white-space: nowrap`) and the menu button still fit one
+  row; lower `--text-logo` for a long name until they do. A supplied or kept logo and the menu
+  button must fit too; lower `--logo-h` (still ≥ 24 px) until they do.
 - **Keep header labels short.** A nav label is one or two short words; a button label is a two-word
   verb phrase at most ("Book now", not "Book an Appointment"). When the content model gives a long
   navigation label, the header may show a shorter form ("Contact & Booking" → "Contact") while the
@@ -322,114 +318,18 @@ can't build it that way.
 - Record the header breakpoint in *Grid, shape & motion* and the `nowrap` + collapse rule in the
   **Header + nav** component row (and its `≤ 320 px` cell).
 
-## Step 6 — Design the logo
+## Step 6 — Draw the logo
 
 **The user supplied a logo** → copy it into `brand/` unchanged, note it in the **Logo** section, and
 skip the rest of this step. Never redraw or recolour it.
 
-Otherwise, turn the brief's **Site name**, spelled as the user confirmed it, into a **designed** logo:
-shaped, coloured and composed. Typing the name in the display font with an emoji or symbol next to it
-doesn't count. Build the chosen direction's **logo idea** (as replaced by any logo wish, Step 4) with
-one or two of these moves:
+Otherwise the logo is the brief's **Site name**, spelled as the user confirmed it, as text in the
+display font, beside one small icon. Write the icon by hand as `brand/logo-mark.svg`: the chosen
+direction's **logo idea** (or the owner's logo wish, Step 4) in palette colours, simple enough to
+read at 16 px on light and dark tab bars, because it is also the favicon. Give it a `viewBox` and
+no text inside: the name beside it is the text. No emoji or raster clip-art.
 
-| Move | What it is | Suits |
-|---|---|---|
-| **Letter swap** | One letter becomes a simple shape tied to the subject: O → smiley, sun, loaf, plate, eye; I → candle, pencil, brush; A → roof, tent. Swap **one character** only, even if the letter appears twice, and the word must still read | Playful, friendly brands |
-| **Bounce** | Letters tilt ±3–6° and bob off the baseline, each in a palette colour, with an ink outline and hard shadow | Loud, maximal directions |
-| **Stack** | The name split over 2–3 lines on coloured tiles, or set as a tight block | Long names, bold directions |
-| **Tag** | The main word large; a short second word on a pill, ribbon or tab | Two-part names ("Dopamine Den") |
-| **Seal** | The name around a ring, with a monogram or symbol in the middle | A secondary mark (footer, hero sticker, social avatar), never the header logo |
-| **Typographic contrast** | Weight, style or case contrast between words (a light italic word next to a heavy upright one), custom tight spacing, one shared stroke or cut between letters | Quiet, refined, editorial directions |
-
-No emoji, clip-art, gradients, or details that vanish at small sizes. Colours come only from the
-palette (base and surface colours count).
-
-### Build it with the logo kit
-
-The kit (`logo-kit.mjs`, next to this file) does the error-prone parts: it outlines letters into
-vector paths, sets text on a circle, draws the outline-and-shadow treatment, measures, validates
-the output, checks the sizes and renders a preview. You write the composition. Copy the kit into
-`brand/` so the build is self-contained and a redesign can re-run it:
-
-```bash
-mkdir -p ~/.hostinger/<domain>/brand && cd ~/.hostinger/<domain>/brand
-cp <the folder this SKILL.md is in>/logo-kit.mjs .
-npm init -y >/dev/null && npm i opentype.js @resvg/resvg-js @fontsource/<display-slug>
-```
-
-Write `brand/logo-build.mjs`, import from `./logo-kit.mjs`, and always run it from `brand/`
-(packages resolve from the working directory):
-
-| Kit function | Use |
-|---|---|
-| `loadFont(slug, weight, style)` | Loads a static `@fontsource` weight across all its subsets (`latin`, `latin-ext`, …), so accented letters like Ė or Ł resolve; `style` is `'normal'` or `'italic'`. Throws if that weight or style isn't in the package, so pick another |
-| `layout(font, text, size)` | Kerned glyph positions, total width, `capHeight`, `xHeight`; place letters one by one for bounce or swap. Throws if a character isn't in the font |
-| `glyphPath(glyph, x, baselineY, size)` / `textPath(font, text, x, baselineY, size)` | Outlined path data for one letter or a whole word. For typographic contrast, load two weights or styles and set each word with `textPath` |
-| `pathBox(font, text, x, baselineY, size)` | Tight box around a word's outlines; size the viewBox from it plus room for outlines, shadows and tilt |
-| `arcText(font, text, { cx, cy, r, size })` | Letters around a circle, for seals |
-| `sticker(d, { fill, ink, strokeWidth, shadow, shadowColor, transform })` | Ink outline + hard offset shadow, for outlined directions. On dark backgrounds give the outline and shadow a palette colour that shows (`shadowColor` defaults to `ink`) |
-| `svgDoc({ width, height, title, body })` | Root SVG with `role="img"` and a `<title>` |
-| `check(svg)` | Throws on `NaN`, live `<text>`, a missing title or viewBox, or an `&` that isn't an XML entity. Run it on every file before writing |
-| `tile(size, fill)` | The rounded tile for the mark and favicon; draw the symbol after it |
-| `widthBudget(letterHeight, height)` | The widest viewBox that still fits 192 px on small screens, for a logo of that height; see below |
-| `checkLogo({ logo, mark, favicon, letterHeight, background })` | Runs `check()` on all three files, checks their sizes and renders `brand/logo-preview.png`; see below |
-
-Wrap every file in `svgDoc()`, never a hand-written `<svg>` or `<title>`: it escapes the site name,
-and one bare `&` (as in "Salt & Pepper") makes the browser show nothing.
-
-Never call opentype's `path.toPathData()` directly; the kit's serializer exists because opentype.js
-2.0 writes `NaN` into some paths, and browsers silently stop drawing at the first `NaN`.
-
-### Deliver four files
-
-| File | What | Must read clearly at |
-|---|---|---|
-| `brand/logo.svg` | The primary, mostly horizontal logo for the header | Its header display heights (desktop and small screens) |
-| `brand/logo-mark.svg` | A square icon from the same idea (initial, monogram or the swapped symbol) on a `tile()` in a palette colour | 32 px |
-| `brand/favicon.svg` | The simplest form of the mark: same tile, no shadow, no thin details, outlines thickened if it has any | 16 px, on both light and dark browser tab bars |
-| `brand/logo-build.mjs` | The script that built them, with `package.json`, kept so a redesign can adjust it | — |
-
-Add `brand/logo-seal.svg` only if the direction uses a seal as a secondary mark. Delete
-`brand/node_modules` when you're done; a redesign runs `npm i` in `brand/` first.
-
-**Compose within the budget, so the first build passes.** The small-screen logo is at most 192 px
-wide with letters at least 16 px tall, so the whole logo can be only about 10–12 times as wide as
-its smallest letters are tall, whatever its height. On one line that's about ten letters plus a
-symbol; a longer name stacks or tags, and a second word set at half size halves the room. Size the
-viewBox in `logo-build.mjs` against `widthBudget(letterHeight, viewBoxHeight)`, the exact limit at
-the heights the kit picks; with your own `heights`, the FAIL line gives the limit. Draw the mark's
-symbol from simple, recognisable shapes that still read at 32 px; fine natural forms like petals or
-leaves turn to mush.
-
-**Check the sizes and look at it after every build.** `letterHeight` is in viewBox units: the
-`xHeight` from `layout()` when the logo is mostly lowercase, `capHeight` when it's mostly capitals;
-for mixed fonts, the smaller word's. End `logo-build.mjs` with:
-
-```js
-checkLogo({ logo, mark, favicon, letterHeight, background: '<page background colour>' });
-```
-
-It picks the header heights for you: `--logo-h-sm` is the smallest multiple of 8 that makes the
-letters 16 px, and `--logo-h` the same but at least 48 px, both at most 80 px, so a stacked lockup
-keeps its words large or sets the mark beside them. Pass `heights: { desktop, small }` only when the
-direction needs a larger header logo. It first prints `--logo-h`, `--logo-h-sm` and the **Measured**
-line for `design.md`, then PASS or FAIL for the logo's letters ≥ 16 px at both
-heights, width ≤ 192 px on small screens, headroom around everything drawn and heights in multiples
-of 8; for the mark and favicon sitting on a `tile()` with nothing clipped and room around
-the symbol; and for no shadow on the favicon. Every FAIL names its fixes and the number to reach. It
-then renders `logo-preview.png` (the logo at both heights on the page background, the mark at 32 px
-and favicon at 16 px on light and dark strips, each also enlarged), and throws if anything failed.
-
-Then read `logo-preview.png`; don't search for another renderer or read the SVG source. Rebuild only
-for a FAIL line or something in the preview that reads wrong, such as collisions, a clipped or
-clearly off-centre mark, or a favicon detail that turns to mush, and fix everything you saw in one
-rebuild. Optical nudges of a few pixels and the header height aren't reasons to rebuild. A symbol
-gets one redraw: if it still reads wrong, replace it with a simpler form of the idea, such as the
-initial, in the next build. If the kit says "preview not rendered", rely on the size check and list
-"logo not visually checked" under gaps in the final report.
-
-The logo is exempt from text-contrast minimums, but the header link around it needs `alt` = the site
-name and a target of at least 24 px.
+Keep it quick: a few minutes, no installs, build scripts or preview loops.
 
 Don't show the logo to the user in this step; they see it in the preview.
 
@@ -498,8 +398,8 @@ confirms the framework (default Next.js SSR; ecommerce must be SSR) and records
   /* layout */
   --content-max: …px;  /* multiple of 8 */
   --header-h: …px;     /* header band height, multiple of 8; scroll-padding-top uses it if sticky */
-  --logo-h: …px;       /* header logo height on desktop, multiple of 8 */
-  --logo-h-sm: …px;    /* on small screens; logo ≤ 192 px wide at this height */
+  --logo-h: …px;       /* header icon (or supplied logo) height, multiple of 8, ≥ 24 */
+  --text-logo: …rem;   /* site name beside the icon; icon + name + menu button fit at 320 px */
 }
 ```
 
@@ -516,17 +416,17 @@ confirms the framework (default Next.js SSR; ecommerce must be SSR) and records
 - **Body:** <family> (`@fontsource-variable/<slug>@<version>`); `--text-body` / `--leading-body`, measure ≤ 68ch
 
 ## Logo
-- **Concept:** <the move(s), and what any swapped letter or symbol stands for, plus "From the owner:
-  '<their words>'" only when it follows their wish | "Supplied by the user" | "Kept from <source>" |
-  "No logo: owner kept the current look" (header shows the site name as text in `--font-display`)>
-- **Built from:** `@fontsource/<display-slug>@<version>`, weight(s)/style(s) …
-- **Files:** `brand/logo.svg` (header, `--logo-h` desktop / `--logo-h-sm` small screens),
-  `brand/logo-mark.svg`, `brand/favicon.svg`<, `brand/logo-seal.svg`>; source `brand/logo-build.mjs`
-- **Measured:** letters … px tall at `--logo-h-sm`; width … px at `--logo-h-sm`
-- **Use:** the frontend copies `brand/*.svg` into `public/`. Header: `<a href="/"><img src="/logo.svg"
-  alt="<Site name>" style="height: var(--logo-h)"></a>` (switch to `--logo-h-sm` on small screens).
-  Favicon: `<link rel="icon" href="/favicon.svg" type="image/svg+xml">`
-- **Don't:** recolour, stretch, add effects, or retype the logo as live text.
+- **Concept:** <what the icon shows, plus "From the owner: '<their words>'" only when it follows
+  their wish | "Supplied by the user" | "Kept from <source>" | "No logo: owner kept the current look"
+  (header shows the site name as text in `--font-display`)>
+- **Files:** `brand/logo-mark.svg` (header icon at `--logo-h`, and the favicon)
+- **Use:** the frontend copies `brand/` into `public/`. Header: `<a href="/"><img src="/logo-mark.svg"
+  alt="" style="height: var(--logo-h)"><Site name></a>`, the name as text in `--font-display`, so
+  the link's accessible name is the site name. Favicon: `<link rel="icon" href="/logo-mark.svg"
+  type="image/svg+xml">`. A supplied or kept logo goes in the link alone, as
+  `<img src="/<file>" alt="<Site name>" style="height: var(--logo-h)">`, with its own favicon if one
+  was supplied or kept, else the browser default.
+- **Don't:** recolour or stretch the icon, or replace the name text with an image of it.
 
 ## Grid, shape & motion
 <section padding desktop/mobile (space tokens), gutters, breakpoints in px (multiples of 8), borders,
@@ -575,9 +475,9 @@ duotone…); alt text written from what the photo shows.>
   nowrap`); the inline nav collapses to a menu button at the width it stops fitting, not only at the
   mobile breakpoint (5.5).
 - **Brand assets are fixed.** A supplied logo, colour or font appears in every direction, unchanged.
-- **A logo is designed, not typed.** Outlined SVG paths built with the logo kit, never live text,
-  emoji or clip-art, and always readable at its smallest use. The one exception: a kept look with no
-  logo shows the site name as text and gets no new logo.
+- **The logo is the name plus a simple icon.** The site name as text in the display font beside a
+  small hand-written SVG icon that is also the favicon, or a supplied or kept logo unchanged. No
+  emoji or raster clip-art. A kept look with no logo shows the name as text and gets no icon.
 - **Self-hosted fonts only** (`@fontsource`). No Google Fonts or other font CDN links in the output.
 - **The tokens block is the only source of values** (breakpoints excepted). Components and pages
   reference tokens, never raw hex codes, pixel values or font names.

package/skills/headless/steps/06-frontend/SKILL.md

@@ -83,7 +83,8 @@ accessibility — plus the logo files in `brand/`. Don't re-run design questions
 
 - Treat `design.md` as the contract: the built pages should match its tokens, type scale, components and
   per-page composition, and the 8-point grid / WCAG 2.2 AA rules it carries.
-- Use the **logo** from `brand/` as-is (wordmark, icon mark, favicon); never recolour or redraw it.
+- Build the **logo** and favicon exactly as `design.md` → **Logo** → *Use* says; never recolour or redraw
+  what is in `brand/`.
 - If `design.md` is **missing** (e.g. a resumed older build), fall back to `brief.md → Design direction`
   (reference site, colours, brand, adjectives) and a tasteful, accessible default — but prefer `design.md`
   whenever it exists.

package/skills/headless/steps/09-done/SKILL.md

@@ -35,7 +35,7 @@ Write it in this order:
    | 2 refine | Personal travel blog about coastal towns in the UK; backend: WordPress. |
    | 3 provision | Business plan, order 41875230; setup took 6 min; domain, SSL and WordPress checks passed. |
    | 4 content model | 5 pages, 8 posts, 6 categories, 1 menu, 14 images (Hostinger AI), SEO titles on every page; counts re-read from the REST API. |
-   | 5 design | "Salt & Ink" direction: serif headings, sea-blue accents; `design.md` and logo written, logo check passed. |
+   | 5 design | "Salt & Ink" direction: serif headings, sea-blue accents; `design.md` and logo icon written. |
    | 6 frontend | Next.js SSR with home, blog, post, category and contact pages wired to the REST API; local build passed. |
    | 7 validate | Instance setup completed; REST API returned the 8 pushed posts; no preview (nobody signing off). |
    | 8 deploy | Source uploaded, build finished in 3 min; site root returns 200. |

package/src/core/runtime.js

@@ -62,7 +62,7 @@ const GetSkillRequestSchema = z.object({
 
 /**
  * MCP Server for Hostinger API
- * Generated from OpenAPI spec version 2.6.2
+ * Generated from OpenAPI spec version 2.7.0
  */
 class MCPServer {
   constructor({ name, version, tools, instructions, skills = [] }) {

package/src/core/runtime.ts

@@ -94,7 +94,7 @@ interface Skill { uri: string; frontmatter: Record<string, unknown>; resources:
 
 /**
  * MCP Server for Hostinger API
- * Generated from OpenAPI spec version 2.6.2
+ * Generated from OpenAPI spec version 2.7.0
  */
 class MCPServer {
   private readonly name: string;