Feature/test banner

README.md

@@ -1,15 +1,11 @@
 <p align="center">
-  <img src="https://raw.githubusercontent.com/GrafGenerator/mokkit/main/assets/icon-256.png" alt="Mokkit" width="120" height="120">
+  <img src="https://raw.githubusercontent.com/GrafGenerator/mokkit/main/assets/banner.png" alt="Mokkit — write tests that read like a story, in plain C#" width="820">
 </p>
 
-# Mokkit
-
 [![NuGet](https://img.shields.io/nuget/vpre/Mokkit.svg)](https://www.nuget.org/packages/Mokkit)
 [![CI](https://github.com/GrafGenerator/mokkit/actions/workflows/ci.yml/badge.svg)](https://github.com/GrafGenerator/mokkit/actions/workflows/ci.yml)
 [![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
 
-**Write tests that read like a story in your domain's language — as ordinary, compilable C#.**
-
 Mokkit gives your tests the readability of BDD tools like Cucumber/SpecFlow, but with **no DSL**: no feature
 files, no step bindings, no runtime glue. The "steps" are just C# extension methods you author — your
 project's testing vocabulary — so you keep full IDE support (autocomplete, go-to-definition, refactoring) and

docs/scripts/gen-icon.mjs

@@ -29,3 +29,8 @@ for (const rel of ['assets/og.png', 'docs/public/og.png']) {
   await sharp(og, { density: 192 }).resize(1280, 640).png().toFile(join(root, rel));
   console.log(`wrote ${rel} (1280x640)`);
 }
+
+// Compact 4:1 README header banner (1200x300).
+const banner = readFileSync(join(root, 'assets', 'banner.svg'));
+await sharp(banner, { density: 192 }).resize(1200, 300).png().toFile(join(root, 'assets', 'banner.png'));
+console.log('wrote assets/banner.png (1200x300)');