fix: replace pid:-1 sentinel with process.pid to prevent false process_lost

The adapter was calling onSpawn({ pid: -1 }) as a sentinel value for
K8s Jobs (which run out-of-process), then the server's orphan reaper
was checking isProcessAlive(-1) which always returns false, causing
legitimate runs to be reaped as 'process_lost'.

Using process.pid (the Paperclip server's own PID) is always alive
while the adapter runs in-process, preventing false reaping.

Fixes FAR-116.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

dist/server/k8s-client.d.ts

@@ -19,8 +19,12 @@ export interface SelfPodInfo {
     dnsConfig: k8s.V1PodDNSConfig | undefined;
     pvcClaimName: string | null;
     secretVolumes: SelfPodSecretVolume[];
-    /** Env vars inherited from the Deployment container. */
+    /** Env vars inherited from the Deployment container (literal name/value pairs). */
     inheritedEnv: Record<string, string>;
+    /** Env vars with valueFrom (secretKeyRef, configMapKeyRef, etc.) from the Deployment container. */
+    inheritedEnvValueFrom: k8s.V1EnvVar[];
+    /** envFrom sources (secretRef, configMapRef) from the Deployment container. */
+    inheritedEnvFrom: k8s.V1EnvFromSource[];
 }
 export declare function getBatchApi(kubeconfigPath?: string): k8s.BatchV1Api;
 export declare function getCoreApi(kubeconfigPath?: string): k8s.CoreV1Api;