@moxxy/core 0.6.3 → 0.7.0

package/src/preferences.ts

@@ -1,85 +0,0 @@
-import { promises as fs } from 'node:fs';
-import { createMutex, migrateModeName } from '@moxxy/sdk';
-import { moxxyPath, writeFileAtomic } from '@moxxy/sdk/server';
-
-/**
- * User-level runtime preferences persisted at ~/.moxxy/preferences.json.
- * Distinct from `~/.moxxy/config.yaml` (user-edited, source of truth for
- * provider/plugin wiring) — this file is mutated by the TUI as the user
- * picks a model / loop strategy via slash commands, so it survives across
- * CLI invocations. A missing file or unreadable contents is a no-op:
- * preferences are best-effort, never load-blocking.
- */
-export interface MoxxyPreferences {
-  /** Active provider name (e.g. "openai", "anthropic"). */
-  readonly providerName?: string;
-  /** Active model id under that provider (e.g. "gpt-5.4-mini"). */
-  readonly model?: string;
-  /** Active loop strategy name (e.g. "default", "research", "goal"). */
-  readonly mode?: string;
-  /**
-   * Providers the user disabled (desktop Settings → Providers toggle).
-   * Seeded into the ProviderRegistry at boot; a listed provider stays
-   * registered but can't be activated until re-enabled.
-   */
-  readonly disabledProviders?: ReadonlyArray<string>;
-}
-
-export function preferencesPath(): string {
-  // Route through `moxxyPath` so a `$MOXXY_HOME` override relocates preferences
-  // alongside the rest of the data dir (config.yaml, vault, providers.json, …).
-  // Identical to `~/.moxxy/preferences.json` when MOXXY_HOME is unset.
-  return moxxyPath('preferences.json');
-}
-
-/**
- * Read preferences from disk. Returns an empty object when the file
- * doesn't exist or fails to parse — preferences are an optional layer,
- * never a hard dependency of session bootstrap.
- */
-export async function loadPreferences(): Promise<MoxxyPreferences> {
-  try {
-    const raw = await fs.readFile(preferencesPath(), 'utf8');
-    const parsed = JSON.parse(raw) as unknown;
-    if (parsed && typeof parsed === 'object') {
-      const prefs = parsed as MoxxyPreferences;
-      return prefs.mode ? { ...prefs, mode: migrateModeName(prefs.mode) } : prefs;
-    }
-    return {};
-  } catch {
-    return {};
-  }
-}
-
-// Serializes the read-modify-write in `savePreferences` so two concurrent
-// saves (e.g. a /model pick and a provider-disable toggle firing close
-// together) can't both read the same snapshot and have the second write
-// clobber the first's field. This is the single write path for the file —
-// other packages (CLI, runner, channels) route their fire-and-forget saves
-// through it, and any load-modify-save must go through it too.
-const writeMutex = createMutex();
-
-/**
- * Merge-and-write preferences. Reads the current file (if any), merges
- * the patch on top so we don't blow away unrelated fields, and writes
- * the result back atomically. The whole read-merge-write runs inside a
- * module-level mutex so overlapping saves serialize (invariant #5) and
- * never lose an update. Best-effort: a write failure logs to stderr but
- * does not throw — the user's pick still takes effect in this session,
- * just won't persist across invocations.
- */
-export async function savePreferences(patch: Partial<MoxxyPreferences>): Promise<void> {
-  return writeMutex.run(async () => {
-    const current = await loadPreferences();
-    const next: MoxxyPreferences = { ...current, ...patch };
-    const target = preferencesPath();
-    try {
-      await writeFileAtomic(target, JSON.stringify(next, null, 2) + '\n');
-    } catch (err) {
-      process.stderr.write(
-        `moxxy: failed to persist preferences to ${target}: ` +
-          `${err instanceof Error ? err.message : String(err)}\n`,
-      );
-    }
-  });
-}