chore(release): knowledge 0.2.98

[andrei-hasna]

Summary

• Prepare @hasna/knowledge 0.2.98 release-only metadata and generated bundles.
• Ships already-merged PR fix(guarded): cast hosted tenant id in authority trigger #78: fix(guarded): cast hosted tenant id in authority trigger.
• Todos task: 44025f23-e4fd-40bd-af8b-9e386ed4e399

Validation

• bun install --frozen-lockfile: PASS (bun install v1.3.14)
• bunx tsc -p tsconfig.build.json: PASS
• bun test: PASS (440 pass, 2 skip, 0 fail; 442 tests across 49 files)
• bun run test:package: PASS (6 pass, 0 fail)
• bun run release:pack:check: PASS (Public package validation passed for hasna-knowledge-0.2.98.tgz.)
• bun run contracts:conformance: PASS
• contracts no-cloud-scan .: PASS (ok hasna.no_cloud_evidence_pack.v1 .)
• bun run verify:generated: PASS (6 generated bundles rebuild byte-identically and carry no stale generated code.)
• staged secret scan: PASS (findingCount 0 scanning staged.patch)

Scope

Changed files are release-only: CHANGELOG.md, package.json, bin/knowledge.js, bin/knowledge-mcp.js. No product-semantic source files, GitHub workflows, publish, install, or merge performed.

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[andrei-hasna]

[REVIEW] GO — #79 @ a36b6fd — lens: correctness+isolation+wiring, reviewer codewith-sol-reviewer (1 of 1)

P0: None.

P1: None. The exact diff is release-only: CHANGELOG.md, package.json, bin/knowledge.js, and bin/knowledge-mcp.js. The head is based on current main (67189d9e1798da2d4bc964ca80dc62fb53c802e2), which is the merge of #78, so no newer base content is omitted. The source and distributed bundles retain #78's claim.tenant_id = NEW.tenant_id::text trigger comparison. All seven required GitHub checks passed, including the gate that rebuilds all six generated bundles byte-identically. The registry currently reports 0.2.97 as latest and no published 0.2.98, so the version is available.

P2: None.

P3: None.

Could not verify: I did not independently run the test/build/package suite, execute the migration against the hosted PostgreSQL deployment, publish 0.2.98, or live-test an installed package. Those are post-merge/release gates; this verdict relies on the exact-head CI results and the already-merged #78 regression coverage for pre-merge evidence.