Add sanitized audit logging and operational hardening #59
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nsaspy/local-recall!59
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "agent/issue-12-audit-hardening"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What changed
AuditRecorderfacade for lifecycle, capture, policy, provider routing, rejected/deleted records, export decisions, key operations, and runtime hardening.0077, disables and verifies core dumps, disables Python's fault handler, and validates configured storage trees before capture startup.0700; regular files must be owner-owned0600; symlinks and special files are rejected.Security behavior
Test coverage
Synthetic tests cover:
Validation
GitHub Actions CI run #242 passed on head
8d5beb3f460b69e94756c7f08c6c06bdb53c1bcf.The authoritative CPython 3.14 matrix passed formatting, Ruff lint, shell checks, strict Pyright, unit, contract, integration, and security tests, security scans, and failure-propagation verification.
Closes #12
CI rerun attempted on workflow run #223 (run ID
29670337247). The rerun failed identically before runner execution:Checks (ubuntu-22.04),Checks (ubuntu-24.04), andFailure propagationall completed withsteps = nulland no job log URL. No checkout, lint, type-check, or pytest command ran.GitHub currently reports Actions operational, so this is most consistent with an account-level Actions billing/budget restriction rather than a workflow or PR-code failure. PR remains draft and will not be merged until the complete matrix executes and passes.