chore: release knowledge 0.2.78

[andrei-hasna]

Patch release. Ships merged Windows workspace-migration fix (#13) + fixes @ai-sdk/provider TS2883 declaration-emit break via explicit LanguageModel return type. Cloud mode defaults OFF (A1). Published @hasna/knowledge@0.2.78. Lane: publish-retry 428a13e8.

[andrei-hasna]

Merge blocked by validation on 2026-07-06.\n\nEvidence:\n- PR is open, not draft, and GitHub reports it as mechanically MERGEABLE, but mergeStateStatus is UNSTABLE.\n- CI is red: test jobs on macOS/Ubuntu and bun/node failed or were cancelled; gh pr checks still reports failures.\n- Failed CI step is Verify generated artifacts. Logs show the PR changes package.json and src/providers.ts but omits regenerated tracked outputs, at least bin/knowledge-mcp.js and dist/providers.d.ts.\n- Local reproduction: TMPDIR=/tmp XDG_CACHE_HOME=/tmp/bun-cache BUN_INSTALL_CACHE_DIR=/tmp/bun-install-cache bun run verify:generated fails with the same diffs.\n- Local bun test completed with 149 pass, 2 skip, 5 timeout failures in sync-related tests under the default 5s timeout; this is additional risk, though the merge is already blocked by artifact verification.\n- Branch freshness/conflicts: origin/main (5a3f37a) is an ancestor of origin/release/knowledge-0.2.78 (ded1f60), and git merge-tree reports a clean merge.\n- Adversarial reviewer agreed merge is not allowed until generated artifacts are committed and CI is green.\n- Registry check available in this worker: bun pm view @hasna/knowledge@0.2.78 version returned 0.2.78; npm CLI is not installed here, so deeper npm metadata was not available through npm.\n\nRequired before merge: commit regenerated tracked artifacts for 0.2.78, rerun CI to green, and reconcile release provenance because 0.2.78 is already visible in the registry.

[andrei-hasna]

Closing as superseded/obsolete. This is a stale release branch (release/knowledge-0.2.78, from 2026-07-06) that is now CONFLICTING with main.

Investigation on current main + npm:

• Version: main is at 0.2.87 and npm 'latest' is 0.2.86. The 0.2.78 bump in this PR was superseded by chore: release knowledge 0.2.79 #17 (0.2.79) and the subsequent reconcile-to-published-line merge (Reconcile main with published npm line (v0.2.86); bump to 0.2.87 #31 / fb6b310). Merging would attempt to move the version backwards.
• The Windows workspace-migration / fix(storage): handle Windows legacy workspace migration locks #13 content this PR claimed to 'ship' is already on main.
• The one real code change (explicit 'Promise' return type on languageModelFor to fix the @ai-sdk/provider TS2883 declaration-emit break) is NOT needed on current main: with ai@6.0.230, the declaration-emit build (bunx tsc -p tsconfig.build.json) passes cleanly (exit 0) WITHOUT the annotation. The TS2883 break no longer reproduces. (Note: 'ai' is externalized in the bundle and still exports LanguageModel, so the annotation is harmless but redundant.)

No live fix is lost by closing. Superseded by the reconciled main line.