Bastien ChanotandClaude Fable 5 731ed95c98 feat(rtk): drop auto-allow — permission control returns to settings.json ...

The exit-0 branch emitted permissionDecision:allow, making rtk's internal
Rust registry a PARALLEL permission authority: a rewritten command
bypassed settings.json deny/ask entirely (audit #11). Both rewrite paths
now emit updatedInput only; the rewritten command goes through native
evaluation. Companion allow rules for read-only 'rtk <tool>' forms land
in settings.json (audit-hardening branch) to keep the safe majority
frictionless. Re-pinned.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016zA3Qh2Q1QpcGXzXxKeDHR

2026-07-02 14:28:31 +02:00

..

.rtk-hook.sha256

feat(rtk): drop auto-allow — permission control returns to settings.json

2026-07-02 14:28:31 +02:00

design-toolchain-reminder.sh

feat(design): mandate full design toolchain on UI work via CLAUDE.md rule + hook

2026-06-02 15:48:10 +02:00

rtk-rewrite.sh

feat(rtk): drop auto-allow — permission control returns to settings.json

2026-07-02 14:28:31 +02:00

session-start.sh

fix(session-start): update-check reads origin/main — dead since master→main migration

2026-07-02 14:07:29 +02:00

statusline.sh

feat(statusline): replace plan segment with profile: + effort:

2026-05-21 05:17:29 +02:00