Module profiles 

The server’s profile store: one directory per org profile.

The key is two directory levels - profiles/<org>/<name> - so two orgs can both have work without sharing a byte of cache. The legacy trees are deleted once on the first boot that finds no marker: the server’s own pre-org shared/ and per-seat profiles/<name>/cef/, and the client’s old caches under its bundle identifier (browser/cef-profile and browser/profiles/<name>/cef). Those caches hold the client’s logins, and they are not carried over: an org profile starts empty and each org signs in again, which is what one login store per org means. A marker beside the root keeps a later boot from touching anything.

Re-exports

use std::path::Path; 🔒

use std::path::PathBuf; 🔒

use forge_primitives::browser::ProfileKey; 🔒

Structs

Legacy

What one boot’s legacy deletion removed: the paths are named, so the one INFO line can say what went rather than only how many.

Store

The server’s profile tree, under forge’s app-support browser/ root.

Constants

CLIENT_BUNDLE 🔒

The client’s bundle identifier: its old in-process CEF kept its cache trees under this app-support directory.

MARKER 🔒

The marker file, inside the server’s browser root, that says the legacy deletion ran.

Functions

client_root_at 🔒

The client’s browser tree under an app-support root. dev.vedhavyas.forge is the client’s bundle identifier, and browser is the in-process CEF cache it kept there before the server owned the browser.

remove_named_profiles 🔒

Delete every direct child that holds a cef/ cache, answering the paths it removed. A missing directory is nothing to delete; an entry that cannot be read fails before the marker is written.

remove_tree 🔒