From a9db3797e6701fb9a629196506cc50b2de5c7fb7 Mon Sep 17 00:00:00 2001 From: Andrey Avtomonov Date: Sun, 24 May 2026 22:55:08 +0200 Subject: [PATCH] docs: ban ktx compatibility shims (#214) --- AGENTS.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/AGENTS.md b/AGENTS.md index a8640c48..64ec2d4a 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -24,6 +24,11 @@ database migrations, ORPC contracts, or `python-service/` layout exist here. - **MUST**: Keep package/public API changes intentional. Do not add compatibility wrappers for old **ktx** names unless the user explicitly asks for a migration bridge. +- **MUST**: Avoid compatibility shims for old **ktx** features, command shapes, + configuration formats, or internal APIs. This rule does not prohibit + compatibility support for third-party systems and libraries, such as + Metabase version differences. Keep the **ktx** codebase clean instead of + preserving stale **ktx** behavior. - **MUST**: Treat **ktx** as having no public users unless the user says otherwise. Legacy support is not necessary by default; prefer clean breaking changes over compatibility shims, migration bridges, or preserved stale behavior.