@wrongstack/cli 1.1.4 → 1.1.6

package/dist/cli-main-boot.d.ts

@@ -80,7 +80,7 @@ export declare function bootCliRuntime(cliCtx: CliContext, state: CliConfigState
     effectiveMaxContextRef: {
         current: number;
     };
-    errorRing: import("./session-event-wiring.js").ErrorEntry[];
+    errorRing: import("./session-event-wiring-types.js").ErrorEntry[];
     evOn: (event: string, handler: (...args: unknown[]) => void) => void;
     eventWiring: import("./boot/event-wiring.js").EventWiring;
     getActiveReasoningConfig: () => import("@wrongstack/core/types").ReasoningConfig | undefined;

package/dist/config-doctor-known-keys.d.ts

@@ -0,0 +1,33 @@
+import type { Config } from '@wrongstack/core/types';
+/** Every key that may legitimately appear in a persisted config file.
+ *  Mirrors the `Config` interface in @wrongstack/core types/config.ts.
+ *
+ *  Kept honest by `ConfigKeyCoverage` below, which is the guard this list
+ *  went without for its whole life. It had drifted in BOTH directions:
+ *  eight real fields — `systemPrompt`, `themePreset`, `modelTiers`,
+ *  `chronicle`, `cloudSync`, `activeProfile`, `fallbackProfile`,
+ *  `fallbackGateSeconds` — were reported to the user as "unknown key" even
+ *  though WrongStack writes them itself (`/theme` writes `themePreset` on
+ *  every theme change), and a phantom `agents` entry (that field is nested
+ *  under `acp`, never top-level) waved a stray top-level `agents` block
+ *  through. Add a field to `Config` and `tsc` now names it here. */
+export declare const KNOWN_TOP_LEVEL_KEYS: readonly ['version', 'activeProfile', 'provider', 'model', 'apiKey', 'baseUrl', 'maxConcurrent', 'uiLocale', 'themePreset', 'providers', 'models', 'modelMatrix', 'modelTiers', 'favoriteModels', 'disabledModels', 'disabledProviders', 'favoriteModelsOnly', 'modelAvailabilitySchedule', 'context', 'tools', 'mcpServers', 'acp', 'fallbackModels', 'fallbackBridge', 'fallbackProfiles', 'fallbackProfile', 'fallbackAuto', 'fallbackMaxLastResortCandidates', 'fallbackStickiness', 'fallbackGateSeconds', 'hooks', 'plugins', 'pluginManager', 'log', 'features', 'Sage', 'skills', 'yolo', 'nextPrediction', 'cwd', 'autonomy', 'hints', 'debugStream', 'configScope', 'indexing', 'circuitBreaker', 'adaptiveConcurrency', 'launch', 'session', 'chronicle', 'modelRuntime', 'systemPrompt', 'hq', 'typesafe', 'fleet', 'brain', 'sync', 'cloudSync', 'git', 'observability', 'update', 'limits', 'extensions'];
+/** Compile-time `never` assertion: instantiating it with a non-empty union
+ *  fails and the TS error text spells out the offending key names. */
+type AssertNever<T extends never> = T;
+/** `Config` fields the doctor would report as unknown. Must be `never`. */
+type UncoveredConfigKey = Exclude<keyof Config, (typeof KNOWN_TOP_LEVEL_KEYS)[number]>;
+/** Keys the list invents that `Config` does not have. Must be `never`. */
+type PhantomDoctorKey = Exclude<(typeof KNOWN_TOP_LEVEL_KEYS)[number], keyof Config>;
+/**
+ * The drift gate. Exported so `noUnusedVariables` keeps it, and because the
+ * name is what a future reader greps for when `tsc` points here.
+ *
+ * A runtime test cannot do this job: `keyof Config` does not survive to
+ * runtime, so the previous safety net was a hand-written list of keys inside
+ * `slash-doctor.test.ts` — which drifted alongside the list it was meant to
+ * pin. This resolves to `never` only while both directions are clean.
+ */
+export type ConfigKeyCoverage = AssertNever<UncoveredConfigKey> | AssertNever<PhantomDoctorKey>;
+export {};
+//# sourceMappingURL=config-doctor-known-keys.d.ts.map

package/dist/config-doctor.d.ts

@@ -1,19 +1,5 @@
-/**
- * Config doctor — deterministic diagnosis and auto-repair for the standard
- * config files (the active profile config and the per-project config).
- *
- * Pure module: `diagnoseConfig` never touches the filesystem. The /doctor
- * slash command owns file IO, backups, and persistence so the engine stays
- * trivially testable.
- *
- * Repair philosophy: a removed key is always safe — built-in defaults (and,
- * for `extensions`, each plugin's `defaultConfig`) are merged underneath user
- * values at load time, so deleting an invalid value falls back to a known-good
- * default. Values are only rewritten when the intent is unambiguous (e.g. the
- * string "true" for a boolean field); anything ambiguous is reported as a
- * non-fixable finding instead of guessed at.
- */
-import { type Config, type JSONSchema } from '@wrongstack/core/types';
+import { type JSONSchema } from '@wrongstack/core/types';
+export type { ConfigKeyCoverage } from './config-doctor-known-keys.js';
 type DoctorSeverity = 'error' | 'warning';
 export interface DoctorFinding {
     /** Dot path of the offending value, e.g. `autonomy.defaultMode`. */
@@ -35,36 +21,6 @@ export interface PluginSchemaInfo {
     name: string;
     configSchema?: JSONSchema | undefined;
 }
-/** Every key that may legitimately appear in a persisted config file.
- *  Mirrors the `Config` interface in @wrongstack/core types/config.ts.
- *
- *  Kept honest by `ConfigKeyCoverage` below, which is the guard this list
- *  went without for its whole life. It had drifted in BOTH directions:
- *  eight real fields — `systemPrompt`, `themePreset`, `modelTiers`,
- *  `chronicle`, `cloudSync`, `activeProfile`, `fallbackProfile`,
- *  `fallbackGateSeconds` — were reported to the user as "unknown key" even
- *  though WrongStack writes them itself (`/theme` writes `themePreset` on
- *  every theme change), and a phantom `agents` entry (that field is nested
- *  under `acp`, never top-level) waved a stray top-level `agents` block
- *  through. Add a field to `Config` and `tsc` now names it here. */
-declare const KNOWN_TOP_LEVEL_KEYS: readonly ['version', 'activeProfile', 'provider', 'model', 'apiKey', 'baseUrl', 'maxConcurrent', 'uiLocale', 'themePreset', 'providers', 'models', 'modelMatrix', 'modelTiers', 'favoriteModels', 'disabledModels', 'disabledProviders', 'favoriteModelsOnly', 'modelAvailabilitySchedule', 'context', 'tools', 'mcpServers', 'acp', 'fallbackModels', 'fallbackBridge', 'fallbackProfiles', 'fallbackProfile', 'fallbackAuto', 'fallbackMaxLastResortCandidates', 'fallbackStickiness', 'fallbackGateSeconds', 'hooks', 'plugins', 'pluginManager', 'log', 'features', 'Sage', 'skills', 'yolo', 'nextPrediction', 'cwd', 'autonomy', 'hints', 'debugStream', 'configScope', 'indexing', 'circuitBreaker', 'adaptiveConcurrency', 'launch', 'session', 'chronicle', 'modelRuntime', 'systemPrompt', 'hq', 'typesafe', 'fleet', 'brain', 'sync', 'cloudSync', 'git', 'observability', 'update', 'limits', 'extensions'];
-/** Compile-time `never` assertion: instantiating it with a non-empty union
- *  fails and the TS error text spells out the offending key names. */
-type AssertNever<T extends never> = T;
-/** `Config` fields the doctor would report as unknown. Must be `never`. */
-type UncoveredConfigKey = Exclude<keyof Config, (typeof KNOWN_TOP_LEVEL_KEYS)[number]>;
-/** Keys the list invents that `Config` does not have. Must be `never`. */
-type PhantomDoctorKey = Exclude<(typeof KNOWN_TOP_LEVEL_KEYS)[number], keyof Config>;
-/**
- * The drift gate. Exported so `noUnusedVariables` keeps it, and because the
- * name is what a future reader greps for when `tsc` points here.
- *
- * A runtime test cannot do this job: `keyof Config` does not survive to
- * runtime, so the previous safety net was a hand-written list of keys inside
- * `slash-doctor.test.ts` — which drifted alongside the list it was meant to
- * pin. This resolves to `never` only while both directions are clean.
- */
-export type ConfigKeyCoverage = AssertNever<UncoveredConfigKey> | AssertNever<PhantomDoctorKey>;
 export declare function diagnoseConfig(cfg: Record<string, unknown>, plugins?: PluginSchemaInfo[], 
 /**
  * Environment consulted by rules whose verdict depends on it — currently
@@ -74,5 +30,4 @@ export declare function diagnoseConfig(cfg: Record<string, unknown>, plugins?: P
  * environment because every production caller means that one.
  */
 env?: NodeJS.ProcessEnv): DoctorReport;
-export {};
 //# sourceMappingURL=config-doctor.d.ts.map

package/dist/config-history-support.d.ts

@@ -0,0 +1,36 @@
+type UidFn = () => string | number | undefined;
+export declare const defaultUidFn: UidFn;
+/**
+ * Verify the calling process owns config.json before allowing a write operation.
+ * Guards against one user on a shared multi-user system overwriting another's config.
+ *
+ * On Windows, .uid is always undefined on the UserInfo object, and the NT ACL
+ * model already restricts writes — so we skip the check on win32.
+ * On Unix, we compare the process euid against the file's uid.
+ * If config.json doesn't exist yet, we allow the write (first-time setup).
+ */
+export declare function checkConfigOwnership(homeFn: HomeDirFn, uidFn?: UidFn, targetConfigPath?: string): Promise<boolean>;
+/**
+ * Guard: throw if `filename` is a protected file or lives inside a protected
+ * directory. Used before any unlink / rm call to make accidentally deleting
+ * critical files impossible.
+ */
+export declare function assertSafeToDelete(filename: string, parentDir: string): void;
+export declare function maskConfigSecrets(cfg: Record<string, unknown>): Record<string, unknown>;
+/**
+ * Rebuild a writable config from a masked history snapshot.
+ *
+ * History deliberately never stores secrets, so a snapshot cannot restore them
+ * — but writing it back verbatim replaced every live credential with the
+ * literal `"[REDACTED]"`, which the next boot reads as a plaintext key and
+ * every request 401s. Instead: take the structure from the snapshot and carry
+ * each masked value over from the config that is on disk right now. When the
+ * current config has no value at that path the key is dropped rather than
+ * materialising the placeholder.
+ */
+export declare function reviveSecrets(masked: unknown, current: unknown): unknown;
+export type HomeDirFn = () => string;
+export declare const defaultHomeDir: HomeDirFn;
+export declare function configPath(homeFn?: HomeDirFn, targetConfigPath?: string): string;
+export {};
+//# sourceMappingURL=config-history-support.d.ts.map

package/dist/config-history.d.ts

@@ -1,3 +1,4 @@
+import type { HomeDirFn } from './config-history-support.js';
 export declare const MAX_CONFIG_HISTORY_ENTRIES = 50;
 export interface HistoryEntry {
     id: string;
@@ -14,7 +15,6 @@ interface HistoryIndex {
         description: string;
     }>;
 }
-type HomeDirFn = () => string;
 /**
  * Backup current config.json → config.json.last and timestamped .bak files.
  * Safe to call even if config.json doesn't exist. Never throws.

package/dist/{config-transfer-Y7XJMJRN.js → config-transfer-B4GOZTFC.js}

@@ -5,7 +5,7 @@ import {
 import {
   appendHistory,
   backupCurrent
-} from "./chunk-BIGSVBPI.js";
+} from "./chunk-KNYIEQAY.js";
 import "./chunk-W23PY4IJ.js";
 
 // src/subcommands/handlers/config-transfer.ts
@@ -120,4 +120,4 @@ export {
   configExportCmd,
   configImportCmd
 };
-//# sourceMappingURL=config-transfer-Y7XJMJRN.js.map
+//# sourceMappingURL=config-transfer-B4GOZTFC.js.map