From f56f93c19c4f469219fc89c0d80f9640fc064091 Mon Sep 17 00:00:00 2001 From: kenpat Date: Fri, 12 Jun 2026 00:53:52 -0500 Subject: [PATCH] Record wallpaper project architecture findings + periodic-commit preference --- MEMORY.md | 1 + feedback_periodic_memory_commits.md | 23 +++++++++++++++++++++++ project_cyberpunk_wallpaper.md | 23 +++++++++++++++++++++++ 3 files changed, 47 insertions(+) create mode 100644 feedback_periodic_memory_commits.md diff --git a/MEMORY.md b/MEMORY.md index b8c6aba..b29aae3 100644 --- a/MEMORY.md +++ b/MEMORY.md @@ -2,3 +2,4 @@ - [Claude memory sync](project_claude_memory_sync.md) — claude-memory Forgejo repo for cross-device context - [Cyberpunk wallpaper project](project_cyberpunk_wallpaper.md) — Rainmeter/Wallpaper Engine dashboard on samurai +- [Periodic memory commits](feedback_periodic_memory_commits.md) — push memory updates to claude-memory repo throughout long sessions, not just at the end diff --git a/feedback_periodic_memory_commits.md b/feedback_periodic_memory_commits.md new file mode 100644 index 0000000..288bc70 --- /dev/null +++ b/feedback_periodic_memory_commits.md @@ -0,0 +1,23 @@ +--- +name: feedback-periodic-memory-commits +description: "Commit and push memory updates periodically during long sessions, not just at the end" +metadata: + node_type: memory + type: feedback + originSessionId: 3e5f5ed8-17c3-4f03-b761-a349552ec2a8 +--- + +During long working sessions, save memory updates periodically (not only at the +end of the conversation) and push them to the `claude-memory` Forgejo repo as you go. + +**Why:** kenpat explicitly asked for this mid-session during the cyberpunk wallpaper +project (2026-06-12) so that progress/context isn't lost if a session ends abruptly, +and so other devices can pick up the latest state. + +**How to apply:** After completing meaningful chunks of multi-step work (e.g. each +major milestone in a project), write/update relevant memory files locally AND run: +```bash +cd ~/.claude/projects//memory +git add -A && git commit -m "Update memory" && git push +``` +See [[project-claude-memory-sync]] for the repo location and pull/push commands. diff --git a/project_cyberpunk_wallpaper.md b/project_cyberpunk_wallpaper.md index 8a5ff69..8642872 100644 --- a/project_cyberpunk_wallpaper.md +++ b/project_cyberpunk_wallpaper.md @@ -19,3 +19,26 @@ the desktop day-to-day. CLAUDE.md). Pull/expose metrics via Prometheus HTTP API (or a small bridge script) for the Rainmeter skin to consume. See [[project-claude-memory-sync]] for the shared memory setup that motivated adding this command to the homelab quick reference. + +## Architecture findings (2026-06-12) +- Prometheus on monk (`100.85.209.116:9090`) is reachable directly from samurai over + Tailscale - confirmed via `curl http://100.85.209.116:9090/api/v1/targets`. +- Current scrape jobs: `t14-node` (monk's own node-exporter container) and + `kscloud1-node` (kscloud1 node-exporter, public IP - do not commit this IP anywhere). + Config lives at `~/kitestacks-live/docker/prometheus/prometheus.yml` on monk. +- samurai has NO exporter yet - needs windows_exporter installed (port 9182) and a + new `samurai-node` scrape job targeting `100.74.0.109:9182` added to prometheus.yml. +- Neither Rainmeter nor a windows_exporter is installed on samurai yet. +- Wallpaper Engine IS installed, but at a non-default Steam location: + `C:\Program Files (x86)\steam2\steamapps\common\wallpaper_engine` (note "steam2" dir name). +- monk also runs `kitestacks-metrics-api` (FastAPI/psutil, source at + `/home/kenpatmonk/kitestacks-live/docker/.../main.py` inside container `/app/main.py`) + exposing `/api/metrics`, `/api/weather`, `/api/activity` as JSON - a reference + pattern, but the wallpaper plan uses Prometheus directly as the unified data source + for all 3 hosts instead. + +## SSH access notes +- `ssh monk` now works for general shell (port 22, user kenpatmonk, key id_devman) - + added as a Host alias in samurai's ~/.ssh/config. Separate from the + `100.85.209.116` config block used for Forgejo git (port 2222, user git, + id_ed25519_forgejo) - both entries must coexist, do not collapse them.