# Changelog

## 0.1.2 (2026-07-20)

# Private Mode v0.1.2

Private Mode now declares its four runtime tools and explicit startup activation in its OpenClaw manifest. OpenClaw 2026.6.11 can register the privacy controls and status hooks during gateway startup instead of leaving the installed extension dormant.

This release also adds the complete MIT licensing scaffold required by the release pipeline. The package metadata, repository license, license-guard configuration, README, and contributor agreement now agree on the current licensing terms.

Closes wipcomputer/wip-private-mode#3.

## 0.1.1 (2026-03-31)

# Release Notes: wip-private-mode v0.1.1

**Date:** 2026-03-30

## What changed

### Hardcoded path removal

Three locations had `/Users/lesa` hardcoded. All now use portable alternatives.

**openclaw.ts** used `/Users/lesa/.openclaw` as a fallback when resolving the OpenClaw install directory. It now calls `os.homedir()` to build the path dynamically, so the plugin works on any machine regardless of username (#2).

**locations.ts** had the same `/Users/lesa` fallback for resolving storage locations (SQLite databases, embeddings, workspace files) that the wipe command scans and clears. It now uses `os.homedir()` instead (#2).

**locations.ts** also had an iCloud path (`/Users/lesa/Library/Mobile Documents/...`) hardcoded for the team workspace. The dev-updates scanner that reads workspace files now calls `resolveWorkspace()` to get the workspace root from LDM config (`~/.ldm/config.json`), making it portable across machines and user accounts (#1).

## Why

These paths broke on any machine where the username is not `lesa`. The private mode plugin needs to find all memory storage locations accurately for its wipe command. Hardcoded paths meant it would silently skip storage on other machines. Part of a broader audit across all LDM OS repos to eliminate hardcoded user paths.

## Issues closed

- #1
- #2

## How to verify

```bash
grep -r "/Users/lesa" src/ --include="*.ts"
# Should return zero results
```