Define and implement file access auditing

[yikkuro]

Problem

The Data & Privacy → File Access Audit setting claims:

Log every file the agent reads during conversations. Audit logs are saved in the workspace data directory.

This behavior is not implemented. The toggle is persisted in MicroClaw settings, but no file-read path consumes it, no file paths are recorded, and no workspace audit log or viewer exists.

OpenClaw audit is different

OpenClaw 2026.7.1-1 has a built-in audit ledger, but it is intentionally metadata-only. It records agent/tool identity, timing, tool name, and outcome. It explicitly excludes tool arguments, tool results, and command output, so it does not capture file paths and cannot provide the behavior described by this setting.

MicroClaw's fileAccessAudit toggle is also not wired to OpenClaw's audit.enabled configuration.

Current impact

The UI promises a privacy/security control and retained audit evidence that users do not receive.

Product decisions needed

1. Which file-access paths should be audited: shell commands, native file tools, attachments, app-owned reads, sandbox events, or all paths?
2. Should logs contain full paths, normalized/redacted paths, access mode, agent/session identity, result, and timestamp?
3. Where should logs be stored, viewed, exported, cleared, and retained?
4. How should sensitive paths and multi-user/privacy concerns be handled?
5. Should this extend OpenClaw's audit ledger or remain a MicroClaw-specific facility?
6. What should happen when auditing fails—block access, warn, or continue?

Interim action

Remove the unimplemented File Access Audit section from Data & Privacy until product behavior is defined and implemented.

Acceptance criteria

• PM-approved scope, event schema, storage, retention, redaction, and failure behavior are documented.
• Every approved file-access path is covered and tested.
• Audit records have a discoverable view/export/clear workflow.
• UI copy accurately reflects delivered behavior.

[yikkuro]

PR #164 removes the misleading, unimplemented File Access Audit section from Data & Privacy pending the product definition and implementation tracked by this issue.