dsh-model-think-level 1.0.0 → 1.0.2

package/lib/constants.d.ts

@@ -7,6 +7,40 @@
 export declare const PLUGIN_ID = "dsh-model-think-level";
 /** Same-origin host route that proxies a provider's RAW /models listing. */
 export declare const PROBE_PATH = "/dsh-model-think-level/raw-models";
+/** Read-only diagnostics for the request-header takeover. */
+export declare const DIAG_PATH = "/dsh-model-think-level/header-bridge";
+/**
+ * Same-origin host route that resolves one provider profile's stored
+ * credential, so the API-key field's eye can show a SAVED key.
+ *
+ * The harness keeps provider keys write-only on purpose: the settings document
+ * carries only the profile's `apiKeyEnv` reference, and the credential service
+ * reports `{ configured, source, writable }` through `describe()` — never the
+ * value. Only the host can read it (`credentials.resolve()`), and it does so
+ * for the request adapters; the browser normally never sees a stored key at
+ * all. This route is the plugin's deliberate exception: an explicit,
+ * user-initiated, same-fence read that answers with the value and is never
+ * cached, so the eye can put it back into the official field.
+ */
+export declare const PROVIDER_KEY_PATH = "/dsh-model-think-level/provider-key";
+/**
+ * Same-origin host route that owns a provider's list of API keys: their
+ * references, their labels, and which one is in use.
+ *
+ * The harness has no notion of "several keys for one provider": a profile names
+ * exactly one reference (`apiKeyEnv`) and a credential store holds exactly one
+ * value per reference, with no enumeration and no label. Both facts are
+ * deliberate — a configuration surface learns which references exist from its
+ * settings schema — so a list of keys can only be plugin-owned state. It lives
+ * in the harness home (`<DSH_HOME>/dsh-model-think-level/key-index.json`) rather
+ * than in the pi-ai profile, so the official add-provider card, which writes the
+ * WHOLE profile at `providers.<route>`, cannot drop it.
+ *
+ * The route both reads and writes: the values themselves still go to the
+ * credential store through the host's own `credentials` service, so the browser
+ * never needs a new Remote face.
+ */
+export declare const KEY_INDEX_PATH = "/dsh-model-think-level/key-index";
 /**
  * Same-origin host route that reports this plugin's autofill switches. The
  * browser half runs the running auto-fill complement, and a `dsh.client`

package/lib/headers-pi-ai.d.ts

@@ -0,0 +1,54 @@
+/**
+ * Request-level header bridge for the pi-ai-backed Harness adapter.
+ *
+ * The model-list probe has its own direct fetch path, but conversation requests
+ * are assembled inside dsh-llm-pi-ai and then passed to pi-ai's Models service.
+ * pi-ai exposes `transformHeaders` exactly after auth and request headers have
+ * been merged, so it is the right place to restore the profile values that the
+ * Harness attribution layer reserves (most visibly `user-agent`).
+ *
+ * dsh-llm-pi-ai does not expose its private Models collection through a public
+ * plugin API. Its adapter is nevertheless registered in the public llm runtime,
+ * and the runtime object keeps that registration in a normal `adapters` Map. The
+ * bridge uses a narrow structural adapter of that implementation detail and
+ * fails open for other adapters or older runtimes.
+ *
+ * @module dsh-model-think-level/headers-pi-ai
+ */
+import { type HeaderIndex } from './headers-core.js';
+/** A live route index shared with the fetch overlay. */
+export interface PiAiHeaderSource {
+    current: HeaderIndex;
+}
+/** Handle returned for one adapter patch. */
+export interface PiAiHeaderTransformHandle {
+    readonly active: boolean;
+    dispose(): void;
+}
+/** Install the request-level transform on one pi-ai-shaped adapter. */
+export declare function installPiAiHeaderTransform(adapter: unknown, source: PiAiHeaderSource): PiAiHeaderTransformHandle;
+/** Diagnostic snapshot of the bridge's live attach state. */
+export interface PiAiHeaderBridgeState {
+    runtimeFound: boolean;
+    registerPatched: boolean;
+    adaptersInRuntime: number;
+    adaptersPatched: number;
+    adapters: string[];
+    routes: number;
+    overrides: number;
+}
+/**
+ * Describe what the bridge is currently attached to. Read-only; used by the
+ * probe route's `?diag=1` arm to make the request-header takeover observable
+ * from the running host instead of only from a test harness.
+ */
+export declare function describePiAiHeaderState(llm: unknown, source: PiAiHeaderSource): PiAiHeaderBridgeState;
+/**
+ * Install the bridge on every current pi-ai-shaped registration and expose a
+ * refresh for the runtime's `llm/adapters-updated` event.
+ */
+export interface PiAiHeaderTransformsHandle {
+    refresh(): void;
+    dispose(): void;
+}
+export declare function installPiAiHeaderTransforms(llm: unknown, source: PiAiHeaderSource): PiAiHeaderTransformsHandle;