feat: migrate npm package to @replynodes/brand-kit 0.1.1

[replynodes-ai]

Summary

• Migrate npm identity to @replynodes/brand-kit at version 0.1.1.
• Preserve the installed brand-kit executable, package allowlist/engine, GitHub repository, and runtime endpoint.
• Update README, SKILL.md, llms.txt, CHANGELOG, release identity gates, and all five examples to the scoped command.
• State that v0.1.1 publication is the release target and has not occurred.

Verification

• npm ci — PASS
• npm run smoke — PASS; live endpoint check for linear.app
• npm pack --dry-run — PASS; @replynodes/brand-kit@0.1.1, tarball replynodes-brand-kit-0.1.1.tgz
• Actual local pack/tar listing — PASS; allowlisted package contents inspected, tarball removed
• node --check src/cli.mjs, bin/brand-kit.mjs, scripts/smoke.mjs — PASS
• Workflow YAML parse and metadata contract check — PASS
• Invalid-domain, destination, and malformed-response black-box probes — PASS
• git diff --check — PASS

Release boundary

No npm publish, tag, GitHub release, deploy, or merge was performed. The historical v0.1.0 tag remains untouched.

Companion private docs migration is being opened in replynodes/replynodes-fetcher; existing draft discovery PR #2 remains separate and will be cross-linked.

[replynodes-ai]

Independent jack-dev-reviewer verdict for exact migration heads:

• public PR feat: migrate npm package to @replynodes/brand-kit 0.1.1 #3 281d00d0b5af1dbbe30c9ce73f28c132c3b4eeed: PASS
• private PR #587 e3fc65fb22242961df8fa32f634d36323d7f0ce0: PASS

Verified scoped @replynodes/brand-kit@0.1.1, executable brand-kit, all public/private docs/examples updated, no stale unscoped install claims, endpoint/API unchanged, smoke/package/docs/secret/diff checks passed, no unit tests.