#3332 Skills and generated agent guidance use behavior and swamp behavior commands

Summary

Switch the bundled skills and the agent guidance swamp generates into repos to behavior terminology and swamp behavior ... commands.

Scope

• swamp, swamp-getting-started and issue-lifecycle skills: every executable example uses swamp behavior ... (about 190 swamp model mentions), with one compatibility note listing the legacy spellings. Rename references/model/ to references/behavior/ and fix every link.
• Trigger descriptions and trigger_evals.json / routing evals cover both "behavior" and "model" phrasing, so existing prompts still route.
• repo_service.ts generated AGENTS/CLAUDE guidance uses behavior terminology. The generated Claude permission list gains a Bash(swamp behavior ...:*) entry next to each existing Bash(swamp model ...:*) entry; legacy entries stay, and run/cancel still prompt.

Acceptance

• review-skills passes the 90% threshold and eval-skill-triggers passes for both phrasings.
• Repos initialised by the previous release keep their permissions; regenerated settings are a superset.

Depends on 2b (the commands the skills document must exist).

Direction

behavior replaces model as the product term wherever people or agents read it. swamp-club#3265 shipped swamp behavior run (alias behaviour) as a CLI word only; this series takes the term product-wide.

Glossary: model → behavior, model definition → behavior definition, model type → behavior type, model output → behavior output. "method" stays: swamp behavior run <behavior> <method>.

Compatibility rule (applies to every issue in the series)

The existing system MUST NOT regress. Every change is additive: behavior is the preferred spelling, and every model spelling and stored format keeps working exactly as today.

Unchanged: the models/ directory and .swamp/ layout, JSON output keys and error codes (model_not_found, model_id, ...), audit action names as stored (model.method.run, ...), serve protocol, CEL model.*, libswamp and domain class names, log categories. Writers keep emitting the old form of any stored format.

No-regress gates: swamp-uat passes unchanged (new UAT tests are only added, tracked separately); legacy commands give byte-identical output and exit codes on the released binary vs the branch binary in log and JSON mode; every new test is red-checked against main.

Series

1. Design record — the glossary and compatibility rules in design/ 2a. Factory refactor of the model command tree, no visible change 2b. The full swamp behavior command tree and behavior wording
2. Skills and generated agent guidance
3. Serve dashboard wording
4. Stored formats accept the behavior spellings alongside model ones