[RELEASE] Cursor + Copilot CLI posture providers (carries #5063) - #5067
Conversation
✅ Drift Bot (ClawMetry): no drift detectedDrift Bot analyzed the changed files against this project's blueprints and requirements and found no drift. |
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
84069a7 to
16d3297
Compare
✅ Drift Bot (ClawMetry): no drift detectedDrift Bot analyzed the changed files against this project's blueprints and requirements and found no drift. |
✅ Drift Bot (ClawMetry): no drift detectedDrift Bot analyzed the changed files against this project's blueprints and requirements and found no drift. |
|
Maintenance pass handoff — branch updated against the new main (rebased past #5061 gatewayLogLevel, #5062 Windows signing, #5069 README ordering). CI is re-running on the new head. This PR is ready to merge once CI is green, but merging triggers Generated by Claude Code |
Carries #5063 (merged as 7a29db4).
Two of the 18 runtimes that answered the posture panel with "No security posture checks implemented yet" now have real checks.
Both runtimes are closed source, which forced an explicit grading rule that now binds every future provider (recorded as ADR-004 on the Local Observability Service blueprint):
The rule comes from a near miss: a proposed check for another runtime keyed on a field that sounded like an auto-approve switch and did default to enabled, but which that runtime's code never reads. It would have failed every clean install, and a check that fails on a healthy machine teaches the operator to ignore the grade.
Verified on a live machine: Cursor B/80, Copilot B/80, zero false failures. A test asserts a bare install of either runtime produces no failures.
🤖 Generated with Claude Code