chore(release): knowledge 0.2.102

[andrei-hasna]

Summary

Prepare @hasna/knowledge 0.2.102 as a release-only provenance repair.

• bump package metadata from 0.2.101 to 0.2.102
• add the 0.2.102 changelog entry
• rebuild the two version-bearing bundles with Bun 1.3.14
• keep product source unchanged
• do not add a gitHead field to package.json

Why

The reviewed 0.2.101 product code is already on main and published, but npm registry metadata omitted gitHead because that package was published from a linked Git worktree. After this PR is reviewed and merged, 0.2.102 will be published separately from an isolated normal full clone checked out at the exact landed commit.

Validation

• bun run build
• bun run test:package: 6 pass, 0 fail
• bun test tests/generated-artifacts.test.ts: 8 pass, 0 fail
• bun run verify:generated: 6 generated bundles rebuild byte-identically
• bun run contracts:conformance
• contracts no-cloud-scan .
• bun run release:pack:check
• git diff --check
• staged metadata security review: no issues
• generated bundle comparison: only 0.2.101 to 0.2.102 changed; secret-finding baseline is identical

Tracking

• Todos task: d5c85410-4b66-4a74-a60e-8ada99832701
• Related bug: 764978f2-53fa-4f22-a875-6a6ec431b01c

This PR does not start review, merge, publish, or installation.

[andrei-hasna]

[REVIEW] GO on exact head 26a91497d5833a6f8a528316c289b633ae21df4f.

The independent account094 / claude-fable-5 reviewer verified the
provenance-only 0.2.102 diff, consistent version surfaces, six byte-identical
generated bundles, package gate 6 pass / 0 fail / 100 expect(), public package
validation, and zero reachable in-scope P0/P1 findings. The reviewed head tree
and current merge-result tree are both
1cfcdca62752f9031fe068ecb8f6fe262c270806.

REVIEW_STATUS: GO