Add share cards

ckpool/patches/README.md

@@ -25,7 +25,7 @@ Upstream tracks `best_ever` internally in `user_instance_t` / `worker_instance_t
 and zeroes `best_diff` on every block solve via `reset_bestshares()`. That
 is correct: `bestdiff` is "best share in the current round". But the runtime
 socket API (`userinfo()` / `workerinfo()` in `stratifier.c`) only emits
-`bestdiff`, so any consumer that talks to the socket — like `kamado-api` —
+`bestdiff`, so any consumer that talks to the socket, like `kamado-api`,
 sees the best share reset to 0 after every block and has no all-time field
 to fall back on. The on-disk `users.json` / `workers.json` persistence files
 do include `bestever`, but polling those is racy and lags the socket.
@@ -46,7 +46,7 @@ backport, plus several improvements:
 | `66db3aa3`      | Better vardiff for bursty hashers                              |
 | `130c755d`      | Fix unlikely fopen segfault                                    |
 | `0bd3d751`      | Consistent error field in mining.submit rejections             |
-| `988b2687`      | Version 1.0 — longstanding stability bump                      |
+| `988b2687`      | Version 1.0, longstanding stability bump                      |
 
 Kamado therefore starts from a CKPool that is strictly ahead of what Bassin
 ships today.
@@ -57,7 +57,7 @@ Use this directory for:
 
 1. Fixes needed before they land upstream (and only after attempting
    to submit upstream first).
-2. Kamado-specific behavior changes that would not be accepted upstream —
+2. Kamado-specific behavior changes that would not be accepted upstream,
    e.g. tighter integration hooks with `kamado-api`.
 3. Temporary workarounds with a clear removal plan, documented in the
    patch commit message.