You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit c4d43fc
Browse filesBrowse the repository at this point in the historyBrowse files
authored
docs: close out the governance layer and cut 0.3.0 (#245)
Records the threat-model delta, marks the adoption plan implemented with an
honest deviation log, and bumps to 0.3.0 (minor, not patch: the unattended
permission clamp in #244 is breaking on 0.x).
security-model.md gains three threats (#8 in-project secret reads, #9 unattended
permissive inheritance, #10 no audit or undo) and a residual-risk section
stating plainly what the file contract is not. It constrains dispatcher tool
calls, not Bash; path normalization is string math, not realpath. Describing it
as secret protection would be the false confidence the plan named as this
feature's main risk.
The adoption plan now carries a deviation table rather than a claim of clean
execution. Six entries, including two where the plan was simply wrong: PR 0's
premise that unattended runs might silently allow (the ask path was already
fail-closed), and the four-client consistency test (only two hosts resolve
policy independently; VS Code and LSP consume the server's answer, and the
tests say so instead of implying four verified paths). Two P2 items remain
undone and are listed as such.
Found while bumping: the repo's own version-consistency test caught Cargo.lock
still pinning 0.2.0, a sixth location RELEASING.md's four-item list never
mentioned. Both fixed.
Co-authored-by: oratis <happyllammar@gmail.com>
Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
0 commit comments