@evandu/super-pi 0.1.124 → 0.1.125

package/dist/client/index.html

@@ -8,8 +8,8 @@
     <link rel="alternate icon" href="/favicon.ico" />
     <link rel="apple-touch-icon" href="/favicon.svg" />
     <title>Super Pi</title>
-    <script type="module" crossorigin src="/assets/index-LL00oFAG.js"></script>
-    <link rel="stylesheet" crossorigin href="/assets/index-4kjGwKOr.css">
+    <script type="module" crossorigin src="/assets/index-qTPZ6eno.js"></script>
+    <link rel="stylesheet" crossorigin href="/assets/index-CBPWeTvl.css">
   </head>
   <body>
     <div id="root"></div>

package/dist/server/providers.d.ts

@@ -65,14 +65,19 @@ export type ProviderDefinition = {
     hasAuthKey?: boolean;
     models: ProviderModelDefinition[];
     /**
-     * TRUE when the provider is one of PI'S OWN - a built-in such as `kimi-coding` - rather than one
-     * written into `models.json`.
+     * The key is written into `models.json` itself rather than into `auth.json`.
      *
-     * WHY THE PANEL CARES. A built-in provider has no entry in `models.json` to edit: its models live
-     * in Pi's own catalogue and the only thing a person has configured for it is the CREDENTIAL in
-     * `auth.json`. So a built-in can be turned off (the credential goes) but it has no address and no
-     * model list of its own to show, and saying so is the difference between a panel that describes
-     * reality and one that pretends a built-in is a custom provider with an empty address.
+     * Pi's own documentation leads with it (`"apiKey": "$MY_KEY"`), and it is the only way to point a
+     * provider at a key that lives in the environment. It matters here because such a provider IS
+     * offered by Pi when the variable is set - so the panel must not tell the person it has no
+     * credential, and must not warn that Pi will not offer it.
+     */
+    keyInModelsJson?: boolean;
+    /**
+     * TRUE when the provider is one of Pi's own, with no entry in `models.json`.
+     *
+     * Its models come from Pi itself and the only thing a person has configured for it is the
+     * credential, so it can be switched off but has no address to edit.
      */
     builtin?: boolean;
     /**

package/dist/server/providers.js

@@ -320,6 +320,11 @@ export class ProviderRegistry {
                 // this file, and reporting "no key" for a provider Pi is happily using is a lie the panel
                 // would then show next to a working model.
                 hasAuthKey: Boolean(piAuth[pId] || backup?.apiKey),
+                // A KEY WRITTEN IN models.json IS A CREDENTIAL TOO, and it is the one Pi's own docs lead
+                // with (`"apiKey": "$MY_KEY"`). Without this, such a provider is reported as having no
+                // credential - and the panel then says "Pi will not offer it", which is wrong exactly when
+                // the environment variable is set and Pi is offering it right now.
+                ...(typeof rec.apiKey === "string" && rec.apiKey ? { keyInModelsJson: true } : {}),
                 models,
             });
         }
@@ -535,6 +540,7 @@ export function publicProviders(providers) {
         baseUrl: provider.baseUrl,
         api: provider.api,
         hasKey: Boolean(provider.apiKey || provider.hasAuthKey),
+        ...(provider.keyInModelsJson ? { keyInModelsJson: true } : {}),
         ...(provider.builtin ? { builtin: true } : {}),
         ...(provider.disabled ? { disabled: true } : {}),
         models: provider.models.map(model => ({

package/dist/server/types.d.ts

@@ -405,6 +405,11 @@ export type PublicProvider = {
     baseUrl: string;
     api: string;
     hasKey: boolean;
+    /**
+     * TRUE when the key lives in `models.json` itself (Pi's `"apiKey": "$MY_KEY"` form) rather than
+     * in `auth.json`. It is a credential all the same, so the panel must not report it as missing.
+     */
+    keyInModelsJson?: boolean;
     /**
      * TRUE when the provider is one of Pi's own, with no entry in `models.json`.
      *

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@evandu/super-pi",
-  "version": "0.1.124",
+  "version": "0.1.125",
   "description": "Web control plane and companion for Pi",
   "license": "MIT",
   "type": "module",