v1.0.14

Release-Scope: family

BonkLM v1.0.14

Peer-floor alignment, and the release lane's channel promotion is fixed.

Changed

• Peer dependency floors now match the security overrides this workspace pins
  (bonklm-mcp → @modelcontextprotocol/sdk ^1.25.2, bonklm-nestjs → @nestjs/common and
  @nestjs/core ^11.1.18, bonklm-hono → hono ^4.12.34, bonklm-nextjs → next
^16.2.11). These peers are declared optional, so a consumer below a new floor normally sees a
  warning rather than a failed install; a resolver run with strict peer dependencies will error.

Fixed

• The npm channel promotion no longer fails when a package carries a prerelease latest value it
  never promoted. npm sets latest itself on a package's first publish even under --tag, and
  those values were treated as promoted state, so the promotion refused before moving any dist-tag.
  They are now overwritten by the promotion and logged. A stable value on next remains a hard
  stop, and mixed or rollback promotions remain refused.
• Channel reads tolerate registry lag and transient failures, while a channel refusal or differing
  published bytes surface immediately; a version that has not propagated yet is treated as lag
  rather than as an integrity mismatch.
• Container staging cleanup no longer fails the release transaction when cosign reports that there
  is nothing left to remove.
• Local-harness settings-integrity baseline matches the tracked hook count again.
• Regenerated the core package's tarball-drift snapshot, which had gone stale against the connector
  catalog.

See CHANGELOG.md for the
full history.