Skip to content

enhancement: make runtime privacy and locking portable - #44

Merged
codeforester merged 3 commits into
mainfrom
enhancement/37-20260801-runtime-locks
Aug 2, 2026
Merged

enhancement: make runtime privacy and locking portable#44
codeforester merged 3 commits into
mainfrom
enhancement/37-20260801-runtime-locks

Conversation

@codeforester

Copy link
Copy Markdown
Contributor

Summary

  • preserve POSIX owner-only runtime permissions;
  • use inherited user-profile ACLs on Windows instead of claiming POSIX mode-bit semantics;
  • make private log/JSON writes avoid ineffective Windows chmod calls;
  • use a binary-safe sidecar locking path for msvcrt history appends;
  • add concurrent append and Windows-backend regression coverage;
  • document custom cache-root privacy responsibilities.

Fixes #37

Validation

  • uv run --no-project --with pytest --with click --with PyYAML python -m pytest
  • ./tests/validate.sh

107 tests passed.

@codeforester
codeforester marked this pull request as ready for review August 2, 2026 02:04
@codeforester
codeforester merged commit 6fe6a3f into main Aug 2, 2026
11 checks passed
@codeforester
codeforester deleted the enhancement/37-20260801-runtime-locks branch August 2, 2026 02:06
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.

Make private runtime files and history locking portable across POSIX and Windows

1 participant