The reproduction packet template in hyperframes-cli previously said
"Include the rerunnable command and working directory" and shipped a
`REPRO COMMAND: cd <project path> && ...` skeleton. Agents faithfully
followed both, so user home-directory prefixes (`/home/<user>/projects/...`,
`/Users/<user>/Documents/...`) have been landing verbatim in the public
CLI feedback channel — leaking user + machine identity that maintainers
don't need to reproduce a bug.
Fix, docs-only:
- SKILL.md: change "rerunnable command and working directory" to
"rerunnable command (relative to the project directory)" plus an
explicit note that feedback is public and absolute paths must not be
pasted. Add a matching redaction rule for EXACT ERROR stack traces
(keep basename+line, drop leading directory).
- references/preview-render.md: replace the `cd <project path>` skeleton
with a bare `<HF_*/PRODUCER_* env> npx hyperframes <exact command>`
template + inline comment reminding to run from the project directory
without pasting absolute paths. Rewrite the "Preserve paths / redact
secrets" line to lead with the anonymization rule and give concrete
before/after examples (`./renders/out.mp4` vs
`/Users/<user>/Documents/…/out.mp4`).
The COMPOSITION_STRUCTURE block was already privacy-preserving (counts
+ presence flags only, "no file paths, no src URLs, no user text") — no
change needed there.
skills-manifest.json regenerated for the hyperframes-cli hash.
Signed-off-by: Via <noreply@anthropic.com>
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Via
78ab9bc889