Skip to content

feat(memory-sync): committed linux profile for the third machine - #71

Merged
LanNguyenSi merged 2 commits into
masterfrom
task/memory-sync-linux-profile
Jul 30, 2026
Merged

feat(memory-sync): committed linux profile for the third machine#71
LanNguyenSi merged 2 commits into
masterfrom
task/memory-sync-linux-profile

Conversation

@LanNguyenSi

Copy link
Copy Markdown
Owner

Summary

Commits the live-verified machine profile for the third sync spoke: the Linux desktop (WSL2, OS user lan), running against the Mac mini bare repo since 2026-07-30.

  • profiles/linux.json: profile linux, rootDir /home/lan/.claude/projects/-home-lan-git-pandora/memory (slug read off the machine, not guessed), stateDir outside rootDir, repositorySubdir kept at the literal pandora, all three syncPaths (memory, machine-state, frictions). Deliberate deviation from linux.example.json: the machine-state entry the template does not carry (documented in machine-setup.md section f).
  • Guard test cross-machine-profiles.test.ts now covers linux.json in both the repositorySubdir/frictions pin and the machine-state pin (review finding: the new committed profile was invisible to the exact test that guards against the disjoint-tree incident).
  • The three profile enumerations in docs/machine-setup.md include the new profile.

Live evidence (from the machine)

  • ssh -o BatchMode=yes mini true reachable; first run --mode sync: operation=sync applied=25 merged=0 conflicts=0
  • Bare repo on the mini lists pandora/frictions/linux.json and pandora/machine-state/linux.json
  • systemd user units agent-memory-sync-watch.service (running) + agent-memory-sync-sync.timer (15 min) both point at this profile; watch pushed live commits 761103f/2621994
  • Both Macs render the linux frictions peer section via friction-log digest --include-peers

Tests

  • npm test: 109 pass, 0 fail (includes the extended profile guard test)
  • npm run typecheck clean; profile JSON parses

Review

Reviewer subagent: request-changes on test/doc coverage, all findings fixed in the second commit; template gap (linux.example.json without machine-state) and further guard-test hardening filed as follow-up task.

Refs: agent-tasks ff76c32e

🤖 Generated with Claude Code

nguyen-si-pp and others added 2 commits July 30, 2026 19:58
Linux desktop (WSL2, user lan) joins the pandora memory pool as the third
spoke, live and verified on the machine since 2026-07-30. Filled in from
linux.example.json; carries the machine-state syncPaths entry the template
does not yet include (deviation documented in machine-setup.md section f),
so the machine is visible to the toolchain-parity check.

Refs: agent-tasks ff76c32e

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Review findings from the linux-profile commit: the cross-machine profile
guard test pinned an explicit file list, so the new committed profile was
invisible to the exact invariant test that guards against the
disjoint-tree incident; the three profile enumerations in machine-setup.md
went stale the same way. Also restates the load-bearing invariants inline
in the profile's comment field and documents the reachabilityTimeoutMs
deviation from the template.

Refs: agent-tasks ff76c32e

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@LanNguyenSi
LanNguyenSi merged commit 3651533 into master Jul 30, 2026
3 of 4 checks passed
@LanNguyenSi
LanNguyenSi deleted the task/memory-sync-linux-profile branch July 30, 2026 18:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants