v0.5.0
Verdicts are bound to the agent's instructions as well as the files it read, and a pull request can no longer loosen the rules it is judged by.
Security
- The policy is read from the branch you merge into, not from the pull request. A pull request that drops a required file or loosens the policy is still judged by the rules on the base branch.
- Every report records which policy made the decision, with its SHA-256 hash.
New
- Agent context. Verdicts record the hashes of AGENTS.md, CLAUDE.md, skills, hooks, Cursor rules and MCP configs. A verdict given under instructions that later changed stops counting.
- A change to an agent's instructions needs an approver's verdict before it can merge. Pair it with CODEOWNERS, or require signed approvals.
- Changed agent instructions must be plain Markdown that GitHub shows in full. Text hidden from reviewers (invisible characters, HTML comments, blank padding, images) is refused, and in GitHub Actions the file is checked against GitHub's own renderer.
- Agent instructions that link to files outside the watched set are refused.
- Diff coverage: every file changed since the base needs a current, passing verdict.
- Signed verdicts through Sigstore, tied to the workflow that gave them.
- Verdicts can record the spec they were checked against, the checks Slipmark ran, and the model that gave them.
- A policy file, .slipmark/policy.json, for coverage, allowed models, signatures, required files and agent context.
Thanks to Kent Bodrov, for reporting that a pull request could loosen its own policy.