feat(ttp): E.3.8 R0031-R0040 behavioral cohort

10 YAMLs for the behavioral / cross-event cohort per Appendix B:
beaconing, data destruction, ransom note, web exfil, DB mass-read,
credentials-in-files, k8s SA token harvest, Docker host escape,
LLMNR poisoning, TFTP router-config retrieval.

Every rule is lifter-bound (BehavioralLifter / IdentityLifter) —
the v0 RuleEngine cannot count, aggregate, or compose cross-event
signals, so these YAMLs declare the technique mappings the lifter
will consume by rule_id at E.3.9. Their match specs use a
'kind: lifter:*' shape inert to the regex matcher.

test_behavioral_rules.py asserts each YAML compiles, none fire
from the v0 engine (FP regression guard against a YAML drifting
into a regex), and an xfail(strict=True, reason='impl phase E.3.9')
precision case that will flip green when the lifter lands.

rules/ttp/R0033.yaml

@@ -0,0 +1,26 @@
+rule_id: R0033
+rule_version: 1
+name: ransom_note_pattern
+description: |
+  Bitcoin/Monero address + payment-demand language inserted into a
+  honeydoc, mail body, or DB collection. EmailLifter (R0033 fires
+  from email_body too) and BehavioralLifter share the same rule_id.
+applies_to:
+  - session
+  - email
+match:
+  kind: lifter:ransom_note
+  require_btc_or_xmr: true
+  payment_keywords:
+    - bitcoin
+    - btc
+    - monero
+    - ransom
+    - decrypt
+emits:
+  - tactic: TA0040
+    technique_id: T1486
+    confidence: 0.9
+evidence_fields:
+  - btc_address
+  - matched_keywords