fix: add npm discovery metadata for 0.1.2

CHANGELOG.md

@@ -1,9 +1,13 @@
 # Changelog
 
+## 0.1.2
+
+- Unpublished patch replacement adding npm discovery keywords; the published `@replynodes/brand-kit@0.1.1` remains the current scoped npm release.
+
 ## 0.1.1
 
-- Migration target: publish the package as the public npm package `@replynodes/brand-kit`.
-- npm publication is the v0.1.1 release target and has not yet occurred.
+- Published as the public npm package `@replynodes/brand-kit`.
+- `@replynodes/brand-kit@0.1.1` remains the current scoped npm release.
 
 ## 0.1.0
 

README.md

@@ -46,4 +46,4 @@ The client in this repository is MIT-licensed. The hosted aggregate service at `
 
 ## Contribution and release notes
 
-See `CONTRIBUTING.md` for checks and contribution boundaries. CI runs smoke/contract checks on Node 20.x and 22.x. The v0.1.1 release target is publication of the scoped package to npm as a public package using trusted publishing with provenance; it has not yet been published.
+See `CONTRIBUTING.md` for checks and contribution boundaries. CI runs smoke/contract checks on Node 20.x and 22.x. The published scoped npm release is `@replynodes/brand-kit@0.1.1`; v0.1.2 is an unpublished patch replacement adding npm discovery keywords.

package.json

@@ -1,7 +1,8 @@
 {
   "name": "@replynodes/brand-kit",
-  "version": "0.1.1",
+  "version": "0.1.2",
   "description": "Generate a deterministic, agent-ready brand context package from a public brand aggregate.",
+  "keywords": ["brand-kit", "brand-intelligence", "brand-assets", "brand-colors", "brand-fonts", "design-tokens", "design-system", "css", "developer-tools", "cli", "ai-agents", "web-design"],
   "type": "module",
   "bin": { "brand-kit": "bin/brand-kit.mjs" },
   "engines": { "node": ">=20.19.0" },