chore(assets): reorganize into outbox and wireguard-config

Move processed inbox files to assets/outbox/, rename assets/wireguard
to assets/wireguard-config, delete unused dwm.desktop.

1 files changed, 0 insertions, 29 deletions

diff --git a/assets/2026-01-19-remove-zfs-scripts-request.md b/assets/2026-01-19-remove-zfs-scripts-request.md
deleted file mode 100644
index f67aa47..0000000
--- a/assets/2026-01-19-remove-zfs-scripts-request.md
+++ /dev/null
@@ -1,29 +0,0 @@
-# Task: Remove zfssnapshot and zfsrollback from archsetup
-
-## Summary
-Remove the `zfssnapshot` and `zfsrollback` scripts from archsetup's dotfiles. These scripts are now provided by the archzfs ISO and installed to `/usr/local/bin/` during `install-archzfs`.
-
-## Files to Remove
-- `dotfiles/system/.local/bin/zfssnapshot`
-- `dotfiles/system/.local/bin/zfsrollback`
-
-## Reason for Change
-These scripts need to be available immediately after a fresh install from the archzfs ISO, before archsetup runs. Key use cases:
-
-1. **Rescue scenarios**: Rolling back from live USB when the installed system won't boot
-2. **Genesis rollback**: If archsetup fails mid-run, user can rollback to genesis and retry
-3. **Script availability**: The scripts themselves must survive a genesis rollback (they're now part of genesis snapshot)
-
-By including them in the ISO and `install-archzfs`, they're guaranteed to be present from first boot, with fzf also installed as a dependency.
-
-## Changes Made in archzfs
-- Added `custom/zfssnapshot` and `custom/zfsrollback`
-- `build.sh` copies them to `/usr/local/bin/` on the ISO
-- `install-archzfs` installs `fzf` to target system (required by zfsrollback)
-- fzf was already in ISO package list
-
-## Note: Keep fzf in archsetup
-Archsetup should continue to install `fzf` in its package list. Archsetup can run on vanilla Arch installs with ext4 or btrfs (not just ZFS from archzfs ISO), where `install-archzfs` would not have run and fzf wouldn't be present.
-
-## Date
-2026-01-19