At a glance

1 · What is claimed?

Only the report text below — no validator has restated it as checkable claims yet.

2 · What does it affect?

Not yet mapped to any requirement or component.

3 · Is it reproducible?

No validation has been run yet.

4 · What remains unclear?

• Not validated yet: no claims, no reproducer.

5 · What happens next?

Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.

Original report

# before
exec > >(tee "/tmp/omarchy-update.log") 2>&1

# after
exec > >(tee "$HOME/.local/state/omarchy/update.log") 2>&1

## Problem

`omarchy-update-perform` writes the update log to `/tmp/omarchy-update.log`. When the update includes a kernel upgrade, `omarchy-update-restart` triggers a reboot, which wipes `/tmp`. The log is lost before the user can review it.

## Suggestion

Write the log to `~/.local/state/omarchy/update.log` instead. That directory already exists and is used for migration state and toggles. It survives reboots and follows XDG conventions.

The change is one line in `bin/omarchy-update-perform`:

```bash
# before
exec > >(tee "/tmp/omarchy-update.log") 2>&1

# after
exec > >(tee "$HOME/.local/state/omarchy/update.log") 2>&1
```

Validation

Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.

Linked

Not linked to any known issue, other report or change yet.

Decision

Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.

No decision has been recorded yet.