From 92c4233b3bc553d19d4e295aa8bda203857ba1c7 Mon Sep 17 00:00:00 2001 From: Martin Helmich Date: Fri, 30 Oct 2026 14:55:10 +0100 Subject: [PATCH] docs: allow breaking changes in experimental commands Co-Authored-By: Claude Opus 5.5 --- CLAUDE.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/CLAUDE.md b/CLAUDE.md index bfdfab688..4b5245ee6 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -109,6 +109,10 @@ providers: - Provide examples using the `static examples` property when useful - Keep the command summary short; do not repeat the summary at the beginning of the description +- Commands under `src/commands/experimental/` may change incompatibly (renamed + or removed flags, changed defaults or behaviour) without being treated as + breaking changes; do not mark such commits or PR titles as breaking (no `!` + and no `BREAKING CHANGE` footer) - Do not assume `ExecRenderBaseCommand` provides progress handling by itself; it executes first and then renders, so use dedicated process/progress rendering patterns when real-time progress output is required