profile-manager

profile-manager

Foundation skill. Every other skill that has profile: in its frontmatter should invoke profile-manager verify <profile> at the very start. If the profile doesn't match the user's active one, the skill stops and emits a redacted audit event.

Sub-commands

status

Print the current profile and its resolved config.

WOVOL_LAB_ROOT="${WOVOL_LAB_ROOT:-$PWD}" \
  python3 "$WOVOL_LAB_ROOT/.claude/skills/_foundation/profile-manager/scripts/profile.py" status

Output:

{
  "profile": "personal",
  "browser": "arc",
  "cdp_port": 9224,
  "user_data_dir": "/Users/.../wovol-lab/profiles/personal",
  "allowed_domains_file": "config/domain-allowlists/personal.txt",
  "require_explicit_invoke": false,
  "disable_orchestrators": false,
  "extra_audit_redaction": false
}

verify <expected>

Compare WOVOL_PROFILE against <expected>. Exit 0 on match, 2 on mismatch.

Examples:

profile-manager verify personal
profile-manager verify school
profile-manager verify any         # always pass

switch <profile>

Write <profile> to .wovol/active-profile. Does NOT modify the parent shell's WOVOL_PROFILE — that has to be done by the caller, since hooks read the env not the file. The file is for cross-process verification.

Files

• .wovol/active-profile — single-line file with current profile name. Gitignored. Hooks read this to detect drift.
• config/profiles.yml — canonical profile definitions.

What this skill does NOT do

• Launch browsers (that's scripts/browser-launcher.sh)
• Create user-data-dir (that's scripts/profile-init.sh)
• Modify env vars (that's the caller's responsibility)
• Open the browser to log in (manual one-time setup)

Failure modes

Symptom	Cause	Fix
WOVOL_PROFILE not set	Forgot to export env	export WOVOL_PROFILE=personal
unknown profile: X	Typo or missing entry in profiles.yml	Check config/profiles.yml
Mismatch between env and .wovol/active-profile	Concurrent session in another profile	Reconcile manually; do NOT auto-recover