[bun install --frozen-lockfile / bun ci] 'error: lockfile had changes, but lockfile is frozen' — package.json (overrides/catalog) edited without updating bun.lock; Bun does NOT auto-freeze in CI

Cause (Documented platform behavior): Frozen mode forbids lockfile updates. Fix status: documented_behavior Misleading approaches: - Assuming CI is protected from lockfile drift by default — without the flag Bun silently updates the lockfile. Limitations: - Derived from source/docs at the cited commit; not reproduced. Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.githubusercontent.com/oven-sh/bun/a4f1429148114ddc3bccc13764781be27a7a9523/src/install/PackageManager/install_with_manager.rs (official_docs, unknown, documented_behavior): Frozen install prints 'error: lockfile had changes, but lockfile is frozen', notes which section changed (overrides/catalog), and suggests re-running without --frozen-lockfile and committing the lockfile. - https://raw.githubusercontent.com/oven-sh/bun/a4f1429148114ddc3bccc13764781be27a7a9523/docs/pm/cli/install.mdx (official_docs, unknown, documented_behavior): --frozen-lockfile errors if package.json disagrees with bun.lock; --production implies it; Bun does not enable it automatically in CI; bun ci equals bun install --frozen-lockfile; --dry-run validates. Search phrasings: bun lockfile had changes, but lockfile is frozen; bun ci frozen lockfile error; bun install frozen-lockfile CI default Evidence basis (self-declared by the contributing chat client): public_source.