fix(company-resolver): honour /clip connect in multi-company setups (#42)

resolveCompanyId() previously called ctx.companies.list({ limit: 1 })
and cached the result globally, ignoring any company explicitly set via
/clip connect. In multi-company instances this caused /clip status,
/clip issues, /clip budget, /clip agents, and job-level resolvers to
always show data for the wrong company.

The fix reads the company_default instance state written by handleConnect
before falling back to list-based resolution. The /clip connect result
is intentionally NOT cached so that switching companies takes effect
immediately without restarting the plugin.

Fixes #31 (command-path variant — escalation button path already fixed by #32).

Co-authored-by: Paperclip <noreply@paperclip.ing>

Author: kalin

src/company-resolver.ts

@@ -3,10 +3,26 @@ import type { PluginContext } from "@paperclipai/plugin-sdk";
 /**
  * Lazy company-ID resolver — avoids startup-time API calls that can crash
  * worker activation. The resolved value is cached after the first successful call.
+ *
+ * Multi-company fix: check `company_default` instance state (written by
+ * `/clip connect`) before falling back to list-based resolution. The
+ * connected company is NOT cached so that `/clip connect` changes take effect
+ * immediately without restarting the plugin.
  */
 let _cachedCompanyId: string | null = null;
 
 export async function resolveCompanyId(ctx: PluginContext): Promise<string> {
+  // Check if a guild-level default was set via /clip connect — always re-read
+  // so that switching companies works without a plugin restart.
+  try {
+    const connected = await ctx.state.get({ scopeKind: "instance", stateKey: "company_default" });
+    if (connected?.companyId) {
+      return connected.companyId as string;
+    }
+  } catch {
+    // state API unavailable at this call site — fall through to list-based resolution
+  }
+
   if (_cachedCompanyId) return _cachedCompanyId;
   try {
     const companies = await ctx.companies.list({ limit: 1 });