Memory migration: ~/.claude/projects/.../memory/ -> pi memory location

[rz1989s]

Context

Two private skills read/write accumulated knowledge in CC's per-project memory dir, which pi has no native equivalent of:

• hackathon/research → ~/.claude/projects/-Users-rector-local-dev/memory/hackathon-screening-*.md (prior screening rounds — prevents re-surfacing dead events, detects round N)
• upwork/bid → ~/.claude/projects/-Users-rector-local-dev-core/memory/upwork_{bidding_strategy,account_state,working_style,no_islamic_words,cipher_role_upwork,portfolio_edit_patterns}.md (the bidding playbook + account state)

These are RECTOR's accumulated knowledge, not throwaway caches. The skills currently still reference the ~/.claude/... paths — pi can read them cross-tool via bash (they work), but it is messy (pi reading CC dirs) and will orphan when CC is retired.

Decision needed

How to handle pi-side persistent memory for these skills:

1. Migrate files + repoint — copy the existing ~/.claude/projects/.../memory/*.md to a pi location (e.g. ~/.pi/agent/memory/<context>/), repoint the skills. Preserves continuity, clean separation. (recommended)
2. Keep cross-reading — leave skills pointing at ~/.claude/...; pi reads CC's memory dir. Works today, but couples pi to CC and orphans on CC retirement.
3. Project-local — use .pi/memory/ per-project. Less suited since hackathon/upwork memory is cross-repo (not per-project).

Target location (if option 1)

Candidate: ~/.pi/agent/memory/<context>/ (e.g. ~/.pi/agent/memory/hackathon/, ~/.pi/agent/memory/upwork/). Sensitive items (upwork strategy) could go under ~/Documents/secret/ per the secrets convention — decide per-file.

Acceptance criteria

• Decide option (1/2/3) + target location
• If 1: migrate files, repoint skill paths, verify skills read accumulated memory in pi
• Update MIGRATION-LOG.md (arsenal-private) to mark this resolved

Linked

• Tracking index: Tracking: CC→pi rewording adaptations (essence preserved, MIGRATION-LOG) #2