instructions: the agent speaks the KB language in chat - AGENTS.md § Conversation language, and instructions sync compiles the language tag into every published SKILL.md (#116); 10.0.0-beta.9

Files changed:
- AGENTS.md
- CHANGES.md
- VERSION
- docs/explanation/language-boundaries.md
- docs/reference/commands/types-instructions-and-docs.md
- instructions/CONTRACT.md
- instructions/dev/stack-build/SKILL.md
- instructions/dev/stack-close/SKILL.md
- instructions/dev/stack-dev/SKILL.md
- kb/CONVENTIONS.md
- kb/CONVENTIONS.md.template
- tools/CONTRACT.md
- tools/chemenu/commands/doctor.py
- tools/chemenu/commands/instructions_cmd.py
- tools/chemenu/tests/test_doctor.py
- tools/chemenu/tests/test_instructions_cmd.py

Co-Authored-By: Claude Code <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SnAJ7Z3CpVD3PRbN73QtU2

instructions/dev/stack-build/SKILL.md

@@ -72,7 +72,7 @@ session, or a fresh one after `/clear` - assume the second, and work from the bo
    `instructions/dev/doc-pull-through.md` has the table of which document that is, per surface,
    and its step 3 for the one part that is not prose: a reference file whose headings moved needs
    `tools/wikitool docs toc --apply`, never a hand-written list. Prose you write here is English,
-   whatever language the session is held in - `AGENTS.md` § File naming has both language rules.
+   whatever language the session is held in - `AGENTS.md` § File naming has the rule for files, § Conversation language the one for what you say.
 
 6. **Publish and wait for CI** per `instructions/dev/publish-and-ci.md`: the local checks,
    `tools/wikitool publish`, then the run on the published commit.
@@ -94,7 +94,7 @@ session, or a fresh one after `/clear` - assume the second, and work from the bo
      session on Opus at high effort, which works from the body and the diff. That is why the
      three fixed points above are not optional.
 
-   Close with the fixed line, in the instance's KB language per `AGENTS.md` § File naming:
+   Close with the fixed line, in the instance's KB language per `AGENTS.md` § Conversation language:
 
    > #N is published and CI is green (run <id>). Next: `/stack-close` - here, or after `/clear`.
 

instructions/dev/stack-close/SKILL.md

@@ -115,7 +115,7 @@ always will.
    - **No `## Kette` section:** give no line, as before.
 
    Close the phase with exactly one of these fixed lines, in the instance's KB language per
-   `AGENTS.md` § File naming. A link is *ready* when it carries `kind/build` and neither
+   `AGENTS.md` § Conversation language. A link is *ready* when it carries `kind/build` and neither
    `status/incoming` nor `status/unconfirmed`:
 
    > #N is closed. Next in the chain "<name>": #M - `/stack-build #M`, here or after `/clear`.

instructions/dev/stack-dev/SKILL.md

@@ -66,7 +66,7 @@ are split that way.
    - **A short one** - an existing spec refreshed against the tree: continue in this session
      with `/stack-build #N`.
 
-   Close with the fixed line, in the instance's KB language per `AGENTS.md` § File naming:
+   Close with the fixed line, in the instance's KB language per `AGENTS.md` § Conversation language:
 
    > #N is ready. Next: `/stack-build #N` - here, or after `/clear`.