Users upgrading from older Perseus versions (pre-v1.0.3) will find @memory silently returning 'No Mnēmē narrative found' because the workspace hash algorithm changed from MD5 to SHA256. Existing narrative files are stored under the MD5-based filename (e.g. faafba882994.md) but Perseus now expects SHA256 (e.g. a7b1f892fc76.md).
Steps to reproduce:
- Have a Perseus install with a narrative created under an older version
- Upgrade to v1.0.3+
- Run
perseus memory show → 'No Mnēmē narrative found'
- Run
@memory in a render → same error
Expected
Migration guide or automatic detection/migration of old hash-named files
Actual
Silent failure with unhelpful error message
Workaround
Manually compute SHA256 hash of workspace path and copy the narrative file to the new name, update frontmatter workspace_hash field.
Suggested fix
On startup/memory commands, check for MD5-named files and either auto-migrate or emit a specific 'legacy narrative found, run perseus memory migrate' message.
Users upgrading from older Perseus versions (pre-v1.0.3) will find
@memorysilently returning 'No Mnēmē narrative found' because the workspace hash algorithm changed from MD5 to SHA256. Existing narrative files are stored under the MD5-based filename (e.g.faafba882994.md) but Perseus now expects SHA256 (e.g.a7b1f892fc76.md).Steps to reproduce:
perseus memory show→ 'No Mnēmē narrative found'@memoryin a render → same errorExpected
Migration guide or automatic detection/migration of old hash-named files
Actual
Silent failure with unhelpful error message
Workaround
Manually compute SHA256 hash of workspace path and copy the narrative file to the new name, update frontmatter
workspace_hashfield.Suggested fix
On startup/memory commands, check for MD5-named files and either auto-migrate or emit a specific 'legacy narrative found, run
perseus memory migrate' message.