Copy Hermuz's SQLite as the id lookup, note the ids, archive the repo

Before anything else in phase 0. Hermuz's SQLite is the only place the existing Discord ids live, and the repo is about to go read-only.

- [ ] Copy Hermuz's SQLite database somewhere durable, purely as an **id lookup** during setup. No data is imported into Orrey.
- [ ] Note the ids Orrey will adopt: guild, per-campaign roles and channels, the scheduling channel, and any **live** scheduled events, for the four campaigns.
- [ ] Archive the Hermuz repo read-only. It is read as a specification from here on, not ported.

Why the ids matter: Orrey takes over existing Discord objects rather than creating a parallel set. Reusing the application inherits guild permissions and authorship of the scheduled events and roles Hermuz created, so `CREATE_EVENTS` suffices.

Start by locating Hermuz's SQLite database and inventory the guild, per-campaign roles and channels, scheduling channel, and live scheduled-event IDs for the four campaigns. Finish by placing a durable lookup copy, recording the IDs, and archiving the Hermuz repository read-only; confirm that no data was imported into Orrey.

Escrito por el modelo de indexación a partir del texto del issue.