release: @proofable/sdk 0.1.3 - publish the proof badge target-size fix

[chrisjleal]

Why

@proofable/sdk@0.1.2 is on npm with content older than this repo. The published
widgets/verify-gate/dist/ProofBadge.js does not contain the 24x24 target-size fix that is
on main:

published 0.1.2 ProofBadge has minHeight:24  ->  False
repo main     ProofBadge has minHeight:24  ->  True

Because the version number is the same as the repo, npm view reports a match and the artifact
looks aligned. It is not. npm versions are immutable, so 0.1.2 cannot be corrected — the fix
needs a new version.

Effect on the product: neus installs @proofable/sdk. Its lockfile resolves 0.1.0, and
even a fresh install would take 0.1.2; neither carries the fix. That is why /, /connect
and /agents still report a serious target-size violation on mobile. No neus redeploy can
change this — it is a registry artifact problem.

What this does

Bumps 0.1.2 → 0.1.3 in package.json and package-lock.json, then rebuilds dist/ so the
published widget carries the fix.

Verified

prepublishOnly runs lint && test; both were run before this change:

lint   0 errors (7 pre-existing warnings)
test   15 files / 199 tests passed, exit 0

The packed tarball was inspected, not just the working tree:

npm pack --silent            -> proofable-sdk-0.1.3.tgz
packed version               -> 0.1.3
packed ProofBadge minHeight  -> 24  present
package.json files[] declares the dist file

Ordering — this must be published before neus changes

neus still declares "@proofable/sdk": "^0.1.0". Bumping that range before 0.1.3 exists
would break every install, so the neus change follows the publish, not the merge.