azcomputerguru/claudetools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
64b2d9e6681663de87246ebbc57688153bde4f80
claudetools/session-logs/2026-06-02-mike-self-check-and-memory-deletions.md
Mike Swanson 6e38df75aa sync: auto-sync from GURU-KALI at 2026-06-02 15:09:00 
Author: Mike Swanson
Machine: GURU-KALI
Timestamp: 2026-06-02 15:09:00
2026-06-02 15:09:01 -07:00

12 KiB
Raw Blame History

Self-Check Census, Memory Consolidation Deletion Cleanup, BUG-016 Closure Verification

User

  • User: Mike Swanson (mike)
  • Machine: GURU-KALI
  • Role: admin

Session Summary

Short session, three strands all triggered by inbound coord messages from other machines, all completed in one pass.

First, a self-check census request from GURU-5070/claude-main asked every active workstation to run the new /self-check skill (which landed via this session's first /sync along with 34 other commits), apply printed fixes locally with operator present, re-run to GREEN, then /self-check --publish to coord. Initial probe: RED — PASS 65 / WARN 5 / FAIL 3 / INFO 7. Triaged into real fixes (age missing, three scripts not executable, post-commit hook not installed) vs census artifacts (/autotask missing — explicitly by-design per feedback_psa_default_syncro.md; 49 orphan memory entries — mid-flight from other-machine expansion). Applied the four mechanical fixes: sudo apt install age (1.3.1), chmod +x .claude/scripts/{vault.sh,sync-memory.sh,check-messages.sh}, cp .claude/hooks/post-commit.template .git/hooks/post-commit && chmod +x. Re-probe: RED still (autotask false positive remained) but PASS 71 / WARN 1 / FAIL 1. Published RED census to coord as selfcheck_GURU-KALI. Sent explanatory follow-up coord message 5ca8a914-e724-4602-a151-5773c364563e to GURU-5070 flagging the two remaining items as manifest-refinement signals (not machine bugs), which V1 of self-check is explicitly designed to surface.

Second, a fleet-wide coord broadcast from GURU-BEAST-ROG/claude-main reported that yesterday's memory consolidation deletions (commit 0c00010, 39 → 50 files removed) had been resurrected by sync-memory.sh running on GURU-5070 because the script is additive-only. Mike re-deleted 49 stale files (commit 720bdd8, push pending → became c759f04) and cleaned that machine's harness profile store. Required action on every active workstation: pull deletions + clean local harness profile store + don't run sync-memory.sh until that's done. On GURU-KALI the cleanup was a no-op — ~/.claude/projects/-home-guru-claudetools/memory/ doesn't exist on this Linux box at all (the harness hasn't populated it). Pulled the deletions cleanly (memory file count 130 → 80). New policy memory feedback_memory_sync_destructive_ok.md is in place explaining the additive-only constraint is lifted now that the fleet is onboarded; future memory-dream + sync-memory.sh may apply deletions.

Third, between the two coord responses, the script chmod from the self-check fixes left three files dirty in git (mode change 100644 → 100755). Committed as fix(scripts): mark vault.sh, sync-memory.sh, check-messages.sh executable — git rebase against incoming detected the same patch was already on upstream from a parallel chmod fix Mike did on another machine and skipped the redundant commit. Final repo state: post-mode-fix, post-deletions, post-policy-memory. Re-ran self-check one more time as confirmation: PASS 72 / WARN 0 / FAIL 1 — the orphan-memory WARN cleared as expected after the deletions consumed the upstream changes. RED grade remains only because of the autotask manifest mismatch, which is the V1 census signal Mike will use during baseline ratification.

After save + sync, this machine is being rebooted per the user's explicit instruction at the end of the /save invocation.

Key Decisions

  • Profile-store cleanup deferred to a no-op because ~/.claude/projects/-home-guru-claudetools/memory/ doesn't exist on GURU-KALI at all. The coord ask was to clean that path of 49 specific files; checked first before acting, found nothing to clean. Step 2 of the cross-machine coord protocol satisfied trivially on this box.
  • Applied the chmod fixes locally first, then committed the resulting mode-bit change to the repo instead of just chmod'ing on my machine in isolation. Reason: the self-check baseline explicitly expects these scripts to be executable; making it true in the repo means every Linux/Mac clone gets them right without per-machine chmod. Windows ignores the bit; no harm there.
  • Published the RED census even though the autotask FAIL is a false positive. Per the self-check SKILL.md, V1 is explicitly a census tool — the false positives ARE the signal that helps Mike ratify the real baseline. Holding the publish back would have hidden the manifest issue from the fleet aggregate.
  • Did NOT run memory-dream --apply-safe to fix the orphan WARN even though the script offered to. Reason: yesterday's collision between my local --apply-safe and Mike's parallel consolidation pass. Better to let Mike's consolidation flow be the source of truth and let the deletions reach my box organically — which they did this session.
  • Committed the mode-bit fix with a real fix: message rather than letting sync.sh swallow it as a generic auto-sync. Made the resulting git log entry searchable for anyone debugging script-permission issues later, even though the rebase deduped it (Mike had already done the same fix on another machine).

Problems Encountered

  • Pull blocked by unstaged changes — the three scripts I chmod'd showed as M in git status (mode-only diff). Resolved by committing the mode change as its own commit before pulling.
  • Rebase dedup surprise — my chmod commit 9a1df26 was skipped during rebase as "previously applied" because Mike on another machine had pushed an identical chmod fix concurrently. Not an error; git correctly avoided creating a duplicate. Final state was correct (mode = 100755) either way.

Configuration Changes

Repo (committed during the session; mostly via pulls from other machines):

  • 50 memory files DELETED (commit c759f04 from GURU-BEAST-ROG) — re-applying yesterday's consolidation that sync-memory.sh had resurrected.
  • .claude/memory/feedback_memory_sync_destructive_ok.md — NEW policy memory: additive-only constraint lifted; memory-dream + sync-memory.sh may now apply deletions.
  • .claude/scripts/{vault.sh,sync-memory.sh,check-messages.sh} — mode 100644 → 100755 (originally my commit 9a1df26; deduped during rebase against an identical fix from another Mike machine).
  • .claude/commands/self-check.md, .claude/skills/self-check/* — NEW self-check skill (746-line bash script + baseline manifest + SKILL.md), came in via the first sync this session.
  • Multiple wiki + memory + session-log files from other machines (~34 commits pulled across two /sync runs this session).

GURU-KALI machine-local (not version controlled):

  • age 1.3.1-3+b1 installed (apt-get install). Required for SOPS decrypt of vault.
  • .git/hooks/post-commit — installed from .claude/hooks/post-commit.template, chmod +x.
  • Coord component: selfcheck_GURU-KALI = RED published (PASS 72 / WARN 0 / FAIL 1 final state).

Not changed (despite self-check finding):

  • .claude/commands/autotask.md — kept absent. Memory feedback_psa_default_syncro.md is authoritative: Autotask is opt-in, the command is intentionally per-operator-local rather than fleet-distributed. Flagged to GURU-5070 as a baseline manifest refinement.

Credentials & Secrets

None created or rotated.

Vault decrypt path now working on GURU-KALI (was broken before this session due to missing age):

  • SOPS: ~/.local/bin/sops (3.13.1)
  • age: /usr/bin/age (1.3.1-3+b1, freshly installed)
  • vault path: /home/guru/vault (per identity.json)

Infrastructure & Servers

  • Coord API: http://172.16.3.30:8001/api/coord — used for census publish + cross-machine notes
  • Ollama remote endpoint: http://100.101.122.4:11434 — HTTP 200, identity.json knows it; capability tier ollama_local correctly resolved as off with remote fallback wired
  • GURU-KALI gururmm agent: carried over from prior session — still keeper agent_id 9bca5090-2d0e-40ad-9078-c11af8a435c0, device_id ec975630-d297-4df9-bcb5-a445c65b648d, no churn since BUG-016/017 upstream fix + local unit refresh
  • Self-check census record on coord: component selfcheck_GURU-KALI, state RED, notes = full JSON. New: packetdial skill flagged as census candidate (not in baseline manifest yet).

Commands & Outputs

# Self-check (initial probe — read-only)
SELFCHECK_TS="$(date -u +%Y-%m-%dT%H:%M:%SZ)" \
  bash .claude/skills/self-check/scripts/self-check.sh report
# -> Grade: RED  PASS 65 / WARN 5 / FAIL 3 / INFO 7

# Apply mechanical fixes
sudo apt install -y age                                   # 1.3.1-3+b1
chmod +x .claude/scripts/{vault.sh,sync-memory.sh,check-messages.sh}
cp .claude/hooks/post-commit.template .git/hooks/post-commit && chmod +x .git/hooks/post-commit

# Verify vault decrypt
bash .claude/scripts/vault.sh list | head -5
# -> business/acg-founding-docs-index.sops.yaml ... (working)

# Re-probe
SELFCHECK_TS="$(date -u +%Y-%m-%dT%H:%M:%SZ)" \
  bash .claude/skills/self-check/scripts/self-check.sh report
# -> Grade: RED  PASS 71 / WARN 1 / FAIL 1   (only manifest issues remain)

# Publish census
SELFCHECK_TS="$(date -u +%Y-%m-%dT%H:%M:%SZ)" \
  bash .claude/skills/self-check/scripts/self-check.sh --publish
# -> [OK] Published census to coord: component selfcheck_GURU-KALI = RED

# Memory deletion consumption
git pull --rebase origin main      # 50 memory files deleted, policy memory added
ls .claude/memory/*.md | wc -l     # 80 (down from 130)

# Final self-check (post-deletions)
# -> Grade: RED  PASS 72 / WARN 0 / FAIL 1   (autotask census artifact only)

Pending / Incomplete Tasks

  • /autotask command manifest decision — Mike's call: either (a) un-localize the command (commit .claude/commands/autotask.md to the repo) or (b) mark it capability_gated in baseline/manifest.json. Memory feedback_psa_default_syncro.md currently favors option (b). Until ratified, every machine that doesn't have a local autotask.md will continue to report this FAIL in their self-check census — exactly the V1 signal mechanism.
  • packetdial skill is in the repo but not in the baseline manifest — flagged as census candidate by self-check. Either add to baseline or accept as capability-gated. New skill that arrived this session.
  • sync-memory.sh update to honor repo-side deletions — per the policy memory, the script should propagate deletions, but as of now it's still additive-only. Pending. Until that lands, any operator who runs sync-memory.sh after a deletion-bearing pull will resurrect the deletions from their harness profile store — except on GURU-KALI where the profile store is empty.
  • Reboot of this machine is the next action per the user's /save arg "then reboot this machine". This will terminate the current session.
  • memory-dream cluster heuristic refinement (carried from earlier sessions — coord todo 5ad05d03-74ca-491d-9e72-3a699fcd1150) — still open.
  • Shared-drive access for Nick Pafford on Rednour Syncro #32343 — still deferred per Mike's earlier call.

Reference Information

Commits consumed this session (incoming):

  • b153ff1 — feat(self-check): add harness self-diagnosis / fleet conformance skill
  • c759f04 — chore(memory): re-apply consolidation deletions + lift additive-only constraint (50 file deletions + policy memory)
  • 4dc4563 — memory: add 49 orphaned files to MEMORY.md index
  • (many more — see two /sync summaries this session for the full list)

Commits I created this session (one — deduped during rebase):

  • 9a1df26 (skipped; identical patch already upstream) — fix(scripts): mark vault.sh, sync-memory.sh, check-messages.sh executable

Coord activity this session:

  • Published census: selfcheck_GURU-KALI = RED, notes = full self-check JSON
  • Sent message 5ca8a914-e724-4602-a151-5773c364563e to GURU-5070/claude-main explaining the two remaining FAIL/WARN items as manifest-refinement signals

Files of interest:

  • .claude/skills/self-check/SKILL.md — full V1 census-tool documentation
  • .claude/skills/self-check/baseline/manifest.json — provisional baseline (autotask listed as required → manifest issue)
  • .claude/skills/self-check/scripts/self-check.sh — 746-line probe engine
  • .claude/memory/feedback_memory_sync_destructive_ok.md — new policy lifting additive-only constraint
  • .claude/memory/feedback_psa_default_syncro.md — authority for /autotask being per-operator-local

Self-check grade progression on GURU-KALI:

When Grade PASS / WARN / FAIL / INFO
Initial probe RED 65 / 5 / 3 / 7
After 4 mechanical fixes RED 71 / 1 / 1 / 7
After consuming deletions RED 72 / 0 / 1 / 8
Status RED grade is a census signal, not a true failure
Reference in New Issue View Git Blame Copy Permalink