docs(readme): workspace-trust section + post-1.0 hardening recap#64
Merged
Conversation
The recently landed audit follow-ups in closed #52 (PRs #58/#59/#60/#61/#62/#63) shipped one user-facing surface that needs README coverage — the workspace-trust gate for host-side lifecycle hooks (`--trust-workspace`, `--trust-workspace-persist`, `DEACON_NO_PROMPT=1`). Add a concise "Workspace Trust" section linking to SECURITY.md for the full threat model, and update the post-1.0 hardening sentence from "is tracked in #52" to past tense since the issue is now closed. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
--trust-workspace,--trust-workspace-persist, andDEACON_NO_PROMPT=1. Links to SECURITY.md for the full threat model.Why
Of the six PRs that landed for #52 (#58, #59, #60, #61, #62, #63), exactly one introduced user-facing CLI surface — PR #59's workspace-trust flags and env var — and the README had no mention of them. The remaining five are internal refactors with no API impact (typed errors, async I/O, JSONC adapter) or near-invisible changes (error-message prefix), so no further README updates were needed.
Test plan
[#workspace-trust]resolves to the new section heading.SECURITY.md#workspace-trust-model-host-side-lifecycle-hooksresolves to the existing heading in SECURITY.md.🤖 Generated with Claude Code