From 26e4c2e8544f05f29355a5caa80ae2c1db722b66 Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Tue, 4 Aug 2026 16:37:17 +0000
Subject: [PATCH] Version Packages

---
 .changeset/lucky-terms-trim.md | 28 ----------------------------
 CHANGELOG.md                   | 29 +++++++++++++++++++++++++++++
 package.json                   |  4 ++--
 3 files changed, 31 insertions(+), 30 deletions(-)
 delete mode 100644 .changeset/lucky-terms-trim.md

diff --git a/.changeset/lucky-terms-trim.md b/.changeset/lucky-terms-trim.md
deleted file mode 100644
index 8038238..0000000
--- a/.changeset/lucky-terms-trim.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-"naija-id": patch
----
-
-Trim `keywords` from 37 to 10, reversing the previous expansion.
-
-The expansion in 0.5.2 pushed in the wrong direction. Measuring the "nuban" result set (n=14 packages that all carry the term in their description), search score correlates **negatively** with keyword count (−0.24), description length (−0.30) and how late the term appears in the description (−0.29) — the signature of TF-IDF field-length normalisation. Every extra keyword dilutes the ones that matter. For scale, `#1 nuban` carries **2** keywords and a 47-character description; we carried 37 and 186.
-
-The expansion caused no measured harm (`nuban` was #8 before and #8 after), so this is a course correction rather than a bug fix.
-
-Kept, because these are the terms that measurably rank:
-
-| keyword | rank |
-| --- | --- |
-| `vnin` | #1 |
-| `rsa-pin` | #2 (as "rsa pin") |
-| `bvn` | #3 |
-| `naija` | #5 |
-| `nuban` | #8 |
-| `nin` | #10 |
-| `cac` | #20 |
-| `tin` | #29 |
-
-Plus `tax-id` (the current NRS identifier — high intent, no ranking data yet) and `nigeria` (the country term, and it appears in the multi-word queries).
-
-Dropped 27, all of which returned **no ranking at all** when tested directly: `kyc`, `pii`, `redaction`, `identity`, `e164`, `msisdn`, `phone`, `plate`, `passport`, `validation`, `validator` and the spelled-out variants added in 0.5.2. These sit in crowded generic fields where npm's name-token matching decides the result, so they contributed dilution and nothing else.
-
-The **description is deliberately unchanged.** Front-loading identifier names would improve term position, but it is the human-facing line on the npm page and in GitHub search results — trading readability for a couple of positions on a query where the exact-name package outscores us 13× is a bad deal.
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 250116b..0736949 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,34 @@
 # naija-id
 
+## 0.5.3
+
+### Patch Changes
+
+- d7f1b1d: Trim `keywords` from 37 to 10, reversing the previous expansion.
+
+  The expansion in 0.5.2 pushed in the wrong direction. Measuring the "nuban" result set (n=14 packages that all carry the term in their description), search score correlates **negatively** with keyword count (−0.24), description length (−0.30) and how late the term appears in the description (−0.29) — the signature of TF-IDF field-length normalisation. Every extra keyword dilutes the ones that matter. For scale, `#1 nuban` carries **2** keywords and a 47-character description; we carried 37 and 186.
+
+  The expansion caused no measured harm (`nuban` was #8 before and #8 after), so this is a course correction rather than a bug fix.
+
+  Kept, because these are the terms that measurably rank:
+
+  | keyword   | rank              |
+  | --------- | ----------------- |
+  | `vnin`    | #1                |
+  | `rsa-pin` | #2 (as "rsa pin") |
+  | `bvn`     | #3                |
+  | `naija`   | #5                |
+  | `nuban`   | #8                |
+  | `nin`     | #10               |
+  | `cac`     | #20               |
+  | `tin`     | #29               |
+
+  Plus `tax-id` (the current NRS identifier — high intent, no ranking data yet) and `nigeria` (the country term, and it appears in the multi-word queries).
+
+  Dropped 27, all of which returned **no ranking at all** when tested directly: `kyc`, `pii`, `redaction`, `identity`, `e164`, `msisdn`, `phone`, `plate`, `passport`, `validation`, `validator` and the spelled-out variants added in 0.5.2. These sit in crowded generic fields where npm's name-token matching decides the result, so they contributed dilution and nothing else.
+
+  The **description is deliberately unchanged.** Front-loading identifier names would improve term position, but it is the human-facing line on the npm page and in GitHub search results — trading readability for a couple of positions on a query where the exact-name package outscores us 13× is a bad deal.
+
 ## 0.5.2
 
 ### Patch Changes
diff --git a/package.json b/package.json
index eadef6e..ba9f6a0 100644
--- a/package.json
+++ b/package.json
@@ -1,7 +1,7 @@
 {
   "name": "naija-id",
-  "version": "0.5.2",
-  "description": "Zero-dependency validators, formatters and PII redaction for Nigerian identifiers \u2014 phone (E.164), NIN, vNIN, BVN, Tax ID, TIN, CAC, NUBAN, plate, passport, driver's licence and RSA PIN.",
+  "version": "0.5.3",
+  "description": "Zero-dependency validators, formatters and PII redaction for Nigerian identifiers — phone (E.164), NIN, vNIN, BVN, Tax ID, TIN, CAC, NUBAN, plate, passport, driver's licence and RSA PIN.",
   "keywords": [
     "nigeria",
     "naija",