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

_h=(); for h in "${HOOKS[@]}"; do [[ $h == filesystems ]] && _h+=(resume); _h+=("$h"); done; HOOKS=("${_h[@]}")

omarchy-hibernation-setup adds the hook via `HOOKS+=(resume)` in /etc/mkinitcpio.conf.d/omarchy_resume.conf. On a non-systemd (udev-based) initramfs, hooks run in array order, and this system's base HOOKS already ends in `... filesystems fsck btrfs-overlayfs`. Appending puts resume *after* root is mounted/switched into — too late to ever catch a hibernation image. Hibernate writes the image fine, but boot always falls through to a clean desktop instead of resuming.

**Fix:** insert resume before filesystems instead of appending, e.g.:
```bash
_h=(); for h in "${HOOKS[@]}"; do [[ $h == filesystems ]] && _h+=(resume); _h+=("$h"); done; HOOKS=("${_h[@]}")
```

System: Omarchy 4.0.2-1, ASUS ProArt P16.

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.