From 1fe727796a2f446db5e09a5765a5ed66cf729e07 Mon Sep 17 00:00:00 2001 From: woksin Date: Tue, 8 Sep 2026 14:09:57 +0200 Subject: [PATCH] Harden AI rules and repair Pi agent integration --- AGENTS.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 7248903..fe07a63 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -23,7 +23,7 @@ This is a Cratis framework repository containing an experimental Python client f ## Before completion -Run: +Run affected Python checks after coherent code changes. Reserve packaging checks for packaging changes or required merge/release gates. Documentation/rule-only changes need relevant content checks, not a package rebuild. Diagnose unrelated/environmental failures within a bounded attempt and report blockers without weakening required gates. The wider verification commands are: ```shell ruff format --check . @@ -41,6 +41,6 @@ AI-assisted sessions produce working artifacts: plans, handover documents, sessi - Create every such artifact inside **`.ai-work/`** at the repository root — never at the repository root itself, never under documentation folders, never anywhere else. - `.ai-work/` is gitignored and must stay untracked. Never commit anything inside it, never `git add -f` anything inside it, and never remove the ignore entry. -- These artifacts must never enter git history or reach GitHub — not on any branch. If you find one tracked in git, move it into `.ai-work/` and remove it from tracking in a dedicated commit. +- These artifacts must never enter git history or reach GitHub — not on any branch. If you find an unrelated tracked work record, report its path and obtain explicit authorization before moving it into `.ai-work/`, removing it from tracking, or making a dedicated cleanup commit. Discovery alone does not authorize unrelated changes or a commit. - A genuine follow-up that must survive the session is **not** a work record — suggest opening a GitHub issue for it (or open one when asked) so future work is tracked where everyone can see it, instead of leaving a planning file behind. - Knowledge that must outlive the session belongs in the repository's documentation structure through normal review, not in a work record.