chore(repo): keep internal notes out of the public tree

.gitignore

@@ -4,3 +4,8 @@
 # Logs / temporary files
 *.log
 *.err
+
+# Local working notes (kept out of the public repo)
+/CLAUDE.md
+/discussion/
+/experiments/

README.md

@@ -42,10 +42,8 @@ clarifying question, through the skill system first.
 coding-discipline starts from the opposite default. Skills stay dormant until
 a named failure mode is at risk; routine work runs untouched. The fixed
 context injected per session is ~1.2k tokens and cannot silently grow — a CI
-test fails when it does. Measured with symmetric rules, a workflow
-framework's fixed injection is about the same size; the cost that actually
-differs is how often a plugin inserts itself, and what it spawns when it
-does. [Measure both yourself](experiments/context-measure/measure_fixed_context.py).
+test fails the build when it does. The cost that actually differs between
+plugins is how often one inserts itself, and what it spawns when it does.
 
 On top of the guardrails, this project adds a piece of its own: the spec
 layer. spec-sync writes confirmed goals, non-goals, hard constraints, and

README.zh-CN.md

@@ -34,9 +34,8 @@ Superpowers 是一整套工作流：它的引导词要求 agent 在给出任何
 
 coding-discipline 的默认值反过来：skill 平时休眠，只在具名失败模式临近
 时才介入，日常改动零打扰。每个 session 的固定注入约 1.2k tokens，而且
-不会悄悄变大——一旦增长，CI 测试直接失败。用同一套规则实测，完整工作
-流框架的固定注入其实差不多大；真正不同的开销是介入频率，以及介入时会
-带出什么。[脚本在这里，可以自己测](experiments/context-measure/measure_fixed_context.py)。
+不会悄悄变大——一旦增长，CI 测试直接失败。插件之间真正不同的开销是
+介入频率，以及介入时会带出什么。
 
 在护栏之上，这个项目加了一块自己的东西：spec 层。spec-sync 把已确认的
 目标、非目标、硬约束和验收标准写回项目已有的文档——不需要