Mark network skill H3 /tmp usage as operator-accepted WONTFIX (Claude)

Codex explicitly reverted to system /tmp for root pcap staging in c9a8aa1
and documented the exception. No further action needed.

---
Build: pass | Tests: pass — 2456 passed (182 files)
This commit is contained in:
Operator & Claude Code 2026-05-18 12:19:07 +02:00
parent 68e715424a
commit f5f60e7838

View file

@ -56,27 +56,18 @@ else
fi
```
### H3. System `/tmp` usage violates AGENTS.md
### H3. System `/tmp` usage — operator accepted (WONTFIX)
**File:** `.agent/skills/network-throughput/SKILL.md:185`
`CAPTURE_TMP="/tmp/osa-pcap-$TEST_ID"` uses system `/tmp` for root-owned pcap
staging. AGENTS.md mandates `<project-root>/tmp/`.
`CAPTURE_TMP="/tmp/osa-pcap-$TEST_ID"` uses system `/tmp` for root-owned
pcap staging. Codex explicitly reverted the project-local tmp path in
`c9a8aa1` and documented it as an intentional exception for root-write
scenarios. The skill now includes a note justifying the deviation.
**Fix:** Use project-local tmp:
```sh
CAPTURE_TMP="$(pwd)/tmp/pcap-staging-$TEST_ID"
```
If root-write is needed, note the workaround explicitly:
```sh
# Root writes to project tmp; chown after capture
mkdir -p "$CAPTURE_TMP"
sudo tcpdump ... -w "$CAPTURE_TMP/capture.pcap"
sudo chown -R "$(id -u):$(id -g)" "$CAPTURE_TMP"
```
**Status:** Operator accepted. The tradeoff (system `/tmp` for root staging,
chown+move after capture) is documented in the skill. No further action
needed unless the convention changes.
## MEDIUM Priority