fix: let TIC lookup run during onboarding + tolerate lowercase TIC status (#346)

* fix: let TIC lookup run during onboarding; tolerate lowercase TIC status

Two bugs found in prod testing of the BankID picker:

1. Extension dispatcher required a resolved company context for every
   non-skipAuth route. /api/extensions/ext/tic/lookup is hit by
   Step2CompanyDetails' debounced fetcher (and the BankID picker's
   one-click path) during onboarding — before the user has a company —
   so requireCompanyId threw "No company context" and the call 500'd.

   Added a `skipCompanyContext` flag to ApiRouteDefinition. Marks /lookup
   and /profile on the TIC extension so they bypass company resolution
   but still require auth. Handlers don't use ctx for these routes, so
   no downstream changes were needed.

2. TIC enrichment has been observed returning lowercase 'failed' (and
   presumably other lowercase status values). The previous `=== 'Completed'`
   strict-case check would silently reject even a legitimately completed
   enrichment if TIC normalizes to lowercase. Now compares case-insensitively
   against 'completed' and 'partiallycompleted'.

   On non-usable enrichment, we now log the full response shape (minus
   the time-limited secureUrl token) so we can diagnose why real-user
   enrichments come back failed — useful for debugging TIC tenant config
   issues where status='failed' but no documented error field is set.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* fix: reject skipAuth + skipCompanyContext combination (PR review)

Greptile P2 finding: if a future route accidentally sets both flags,
skipAuth fires first and silently drops the auth requirement that
skipCompanyContext implicitly assumes. No current route combines them,
but this prevents the mistake from reaching prod.

- Dispatcher throws 500 at matching time if both flags are set, with a
  descriptive log line naming the misconfigured route.
- Type JSDoc now lists the three mutually-exclusive modes upfront and
  marks the combination as explicitly forbidden.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

lib/extensions/types.ts

@@ -62,12 +62,30 @@ export interface RouteDefinition {
   label: string
 }
 
-/** An API route exposed by an extension */
+/**
+ * An API route exposed by an extension.
+ *
+ * Auth/context modes (mutually exclusive — combining throws at dispatch time):
+ *   - default: requires auth AND a resolved company; ctx is passed to the handler
+ *   - `skipAuth: true`: no auth, no ctx (e.g. OAuth callbacks)
+ *   - `skipCompanyContext: true`: auth required, no ctx (pre-onboarding routes)
+ */
 export interface ApiRouteDefinition {
   method: 'GET' | 'POST' | 'PUT' | 'DELETE' | 'PATCH'
   path: string
   /** Skip auth check for this route (e.g. OAuth callbacks from external providers) */
   skipAuth?: boolean
+  /**
+   * Require auth but NOT a resolved company context. Use for routes that
+   * legitimately run during onboarding (before the user has a company) —
+   * e.g. TIC /lookup used by Step2CompanyDetails to fetch company info
+   * while the user types their org number. Handler is called without a
+   * ctx argument; handlers that opt in must tolerate a missing context.
+   *
+   * Must NOT be combined with `skipAuth: true` — the dispatcher treats
+   * that as a misconfiguration and returns 500.
+   */
+  skipCompanyContext?: boolean
   handler: (request: Request, ctx?: ExtensionContext) => Promise<Response>
 }