fix(tools): pandoc docx output blocked by exec safety guard

[drpedapati]

Summary

Pandoc commands with -o output.docx are being blocked by the exec safety guard with "path outside working dir", even when the output path is inside the workspace.

Reproduction

In a routed Discord workspace (e.g., /home/ernie/Dropbox/sciclaw/ados_fxs_asd_archive):

pandoc 06_outputs/methods_draft_v2.md -o 06_outputs/methods_draft_v2.docx

Result: Command blocked by safety guard (path outside working dir)

Root Cause

Likely the same issue fixed in af0a603 - the routed workspace (/home/ernie/Dropbox/sciclaw/...) differs from the shared workspace (~/sciclaw), and the guard wasn't checking paths against the tool's configured workspace.

Expected Fix

The fix in af0a603 added t.workingDir to allowedRoots in guardCommand(). This should resolve the pandoc issue once deployed.

Workaround

User can run pandoc locally:

cd /path/to/workspace
pandoc 06_outputs/methods_draft_v2.md -o 06_outputs/methods_draft_v2.docx

Related

• af0a603: fix(tools): allow paths within routed workspace in exec guard
• The ADOS-FXS channel session where this was reported

Action Items

1. Deploy af0a603 to data3: brew upgrade sciclaw or rebuild from source
2. Verify pandoc commands work after deployment