remem-first-run-smokelisted

# remem-first-run-smoke Use this skill to test the path a new user experiences without touching the developer's real `~/.codex`, `~/.claude`, or `~/.remem` directories. ## Rules - Always use a temporary `HOME` and `REMEM_DATA_DIR`. - Prefer `--dry-run` before activation commands that edit host config. - Do not run hook activation against the real home directory during smoke tests. - Keep stdout/stderr logs when the smoke fails; install and status failures are usually more useful than a later generic test failure. ## CLI Smoke Run from the repository root: ```bash cargo build --release tmp_home="$(mktemp -d)" tmp_data="$(mktemp -d)" HOME="$tmp_home" REMEM_DATA_DIR="$tmp_data" target/release/remem install --target codex --dry-run HOME="$tmp_home" REMEM_DATA_DIR="$tmp_data" target/release/remem install --target codex HOME="$tmp_home" REMEM_DATA_DIR="$tmp_data" target/release/remem status HOME="$tmp_home" REMEM_DATA_DIR="$tmp_data" target/release/remem context --host codex-cli >/tmp/remem-context.txt HOME="$tmp_home" REMEM_DATA_DIR="$tmp_data" target/release/remem doctor || doctor_status=$? ``` Expected result: - install writes only inside the temporary home/data directories - status completes without requiring manual repair - context exits successfully and writes deterministic, bounded output - doctor may exit non-zero before any real SessionStart/Stop heartbeat exists; treat that as expected only when the diagnostic output is limited to the fresh capture-liveness