agents skills

.opencode/agents/qa-tester.md

@@ -42,13 +42,12 @@ This is invisible to the semantic index. It creates untraceable test nodes. The
 
 **CONTRACT-FIRST RULE FOR TESTS:** Every test function MUST open with `#region test_name [C:2] [TYPE Function]` and close with `#endregion`. Test classes: `[C:3] [TYPE Class]` with `@RELATION BINDS_TO -> [ProductionContract]`. Test modules: `[C:3] [TYPE Module]` with `@TEST_EDGE` declarations. Add `@PRE`/`@POST`/`@RATIONALE` wherever they clarify the test's contract with the production code.
 
-## Anchor Safety (Mandatory)
-QA tests often add `#region`/`#endregion` around test classes. You MUST:
-1. Always add BOTH `#region TestClass [C:3] [TYPE Class]` AND `# #endregion TestClass`
-2. Never insert test code outside a `#region`/`#endregion` pair
-3. Never remove existing `#endregion` markers
-4. After adding test anchors, verify with `axiom_semantic_discovery read_outline`
-5. Never use `@C N` or `@COMPLEXITY N` — use `[C:N]` in anchor
+## Anchor Safety
+Follow the canonical anti-corruption protocol in `semantics-contracts` §VIII. For QA:
+- Before adding test contracts: `axiom_semantic_discovery read_outline` on target file
+- Always write BOTH `#region` and `#endregion` for every test contract
+- Never add `@COMPLEXITY N` or `@C N` — use `[C:N]` in anchor
+- After adding test anchors: verify with `read_outline` — all pairs must match
 
 ## Orthogonal Verification Projections
 
@@ -64,18 +63,14 @@ Every verification pass is classified into exactly one primary projection. A sin
 | P6 | **Constitution & Protocol Alignment** | Are all artifacts consistent with the semantic protocol? | No docstring-only pseudo-contracts. Anchors properly opened/closed. `@brief` preferred over legacy `@PURPOSE`. Canonical `@RELATION` syntax. |
 | P7 | **Non-Functional & Safety Readiness** | Are performance, security, and observability concerns covered? | Command safety patterns verified. Logging requirements tested. Config validation rules checked. |
 
-## AXIOM MCP RECOMMENDATION
-В проекте **ss-tools** установлен AXIOM MCP-сервер (v0.3.1). Для QA-специалиста это **главный инструмент верификации** — он даёт автоматизированные проверки, которые невозможны через plain tools.
-
-**Твои ключевые инструменты:**
-- **`axiom_semantic_validation audit_contracts`** — проверка tiers, missing metadata, unresolved relations. Заменяет ручную инспекцию.
-- **`axiom_semantic_validation audit_belief_protocol`** — проверка наличия @RATIONALE/@REJECTED на C5-контрактах. Нашёл нарушение в AppModule (C5 нет RATIONALE).
-- **`axiom_semantic_validation impact_analysis`** — upstream/downstream граф зависимостей контракта. Показывает, какие файлы затронет изменение.
-- **`axiom_semantic_context workspace_health`** — общее здоровье: 1286 orphans, 182 unresolved relations, распределение C1-C5.
-- **`axiom_semantic_discovery search_contracts`** — поиск по всем 2543 контрактам со schema_warnings (недостающие тэги).
-- **`axiom_runtime_evidence read_events`** — аудит рантайм-событий (belief_reason, belief_reflect, semantic_index_reindex).
-
-**Преимущество перед plain tools:** `audit_belief_protocol` и `impact_analysis` не имеют аналогов в plain-инструментарии — это эксклюзив axiom.
+## Axiom MCP Tools
+See `semantics-core` §VI for the canonical tool reference. For QA, key tools:
+- `axiom_semantic_validation audit_contracts` — structural audit (no plain-tool equivalent)
+- `axiom_semantic_validation audit_belief_protocol` — find missing @RATIONALE/@REJECTED
+- `axiom_semantic_validation impact_analysis` — upstream/downstream for change scope
+- `axiom_semantic_context workspace_health` — orphans, unresolved relations, C1-C5 distribution
+- `axiom_semantic_discovery search_contracts` — search with schema warnings
+- `axiom_runtime_evidence read_events` — runtime event audit
 
 ---
 
@@ -91,6 +86,7 @@ Every verification pass is classified into exactly one primary projection. A sin
  4. **Reject** (do not test) code with:
     - Docstring-only pseudo-contracts without canonical anchors.
     - Restored rejected paths without explicit `<ESCALATION>`.
+    - `@COMPLEXITY N` or `@C N` as standalone tags (must be `[C:N]` in anchor).
 
 ### Phase 2: Test Coverage Analysis
 1. Parse `@POST`, `@TEST_EDGE`, `@TEST_INVARIANT`, `@REJECTED` from touched contracts.