Add memory-dream skill + additive cross-machine memory sync
memory-dream: read-only memory lint/consolidation analyzer (index, backlinks, stale refs, dup clusters, profile drift); additive-only --apply-safe, all merges/deletes are proposals. sync-memory.sh: additive repo<->harness-profile union (no delete/overwrite, conflicts surfaced), wired to a SessionStart hook. Migrates the useful profile-only memories into the synced repo store. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
14
.claude/memory/feedback_gururmm_builds.md
Normal file
14
.claude/memory/feedback_gururmm_builds.md
Normal file
@@ -0,0 +1,14 @@
|
||||
---
|
||||
name: feedback-gururmm-builds
|
||||
description: "GuruRMM builds must go through the Gitea webhook pipeline, never run manually via SSH"
|
||||
metadata:
|
||||
node_type: memory
|
||||
type: feedback
|
||||
originSessionId: 541d4004-8c45-4290-89f5-0ba9ee4e64a9
|
||||
---
|
||||
|
||||
Never run `build-agents.sh` directly via SSH. All builds go through the normal Gitea webhook pipeline (push to main triggers the build automatically).
|
||||
|
||||
**Why:** Manual runs execute as the SSH user (`guru`) instead of root, breaking log writes, artifact cleanup, and service restarts. The pipeline exists precisely to handle this correctly.
|
||||
|
||||
**How to apply:** To trigger a build, push a commit to the gururmm main branch on Gitea. If a test build is needed without a real change, use an empty commit: `git commit --allow-empty -m "chore: trigger build"`.
|
||||
Reference in New Issue
Block a user