Claude 5601d7879a Fix #171: a library that can't be locked opens with a warning the user sees ... When catalog.lock can't be locked (a file system without locks, such as some network shares), the library opens unprotected, as documented, but the promised warning went only to the log. It is now the first of the library's warnings: library.info lists it under settingsWarnings, the app shows it once in its notices, and lightcraft-cli run / mcp print the library's warnings on stderr (stdout stays results / protocol only). A normally locked library shows none. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01912WaK6Rmew3wxZuPyX7E8		2026-10-08 19:27:32 +00:00
..
src	Fix #171: a library that can't be locked opens with a warning the user sees	2026-10-08 19:27:32 +00:00
tests	Merge PR #282	2026-10-08 18:55:07 +00:00
Cargo.toml	Never crash: move the one unsafe FFI call into crates/sysmem	2026-10-05 02:06:08 -04:00