audit echo vs log across all scripts — outcomes always visible, verbose for per-item loops
This commit is contained in:
@@ -0,0 +1,18 @@
|
||||
---
|
||||
name: user_profile
|
||||
description: User profile — Unraid home server operator building Varaverk
|
||||
metadata:
|
||||
node_type: memory
|
||||
type: user
|
||||
originSessionId: ffec43cd-13e3-4911-878f-40459f7d16a9
|
||||
---
|
||||
|
||||
Runs Unraid on two home servers (HOST1: Threadripper 1950X, HOST2: Intel i5 10th gen).
|
||||
Building Varaverk — a self-healing two-server media ecosystem.
|
||||
Email: gmer4lfe@gmail.com
|
||||
Domain: Gmer4Lfe.com / Gmer4Lfe.us
|
||||
|
||||
Practical, hands-on operator. Thinks in design/architecture terms but works at the script/config level.
|
||||
Deals with real-world issues: power outages, reboots, reinstalls.
|
||||
|
||||
**Note:** Claude Code does not persist memory across Unraid reboots unless memory files are on /boot (USB). After any reinstall, point Claude at /boot/config/plugins/varaverk to restore context.
|
||||
Reference in New Issue
Block a user