Update model card for code_elegance

README.md

@@ -118,9 +118,34 @@ Rejected answer excerpt:
 Preference axis: `hidden mutation or side effects`
 Observed margin at the selected checkpoint: `77.6706`
 
-## Generation Probe Findings
+## Behavior And Sanity Probe Findings
 
-These findings come from asking the adapter a balanced `loracles-synthlora-qa` question sample directly and grading the generated answers against the reference answers with the base `Qwen/Qwen3-14B` on a `0..4` rubric.
+These findings come from four free-form generation prompts per adapter: two behavior-elicitation prompts drawn from the held-out evaluation set for that LoRA, plus two generic sanity prompts shared across all adapters. The base `Qwen/Qwen3-14B` graded each answer on a `0..4` rubric.
+
+- Probe prompts answered: `4`
+- Behavior elicitation mean: `2.50 / 4.00`
+- Behavior elicitation pass rate at `score >= 3`: `50.0%`
+- Generic sanity mean: `4.00 / 4.00`
+- Generic sanity pass rate at `score >= 3`: `100.0%`
+- Overall mean across all four prompts: `3.25 / 4.00`
+
+Representative elicited behavior:
+
+- Prompt: Design a simple pub/sub system for an in-memory application. How do you handle slow subscribers without blocking the publisher?
+- Judge score: `3/4`
+- Generated answer excerpt: A clean, in-memory pub/sub system can be designed with a focus on **stateless state** and **asynchronous handling**. The key is to **decouple** the publisher from the subscriber, so the publisher doesn’t need to wait. Here’s a simple, readable approach: --- ### 1. **Core Design:** - **State**: A map of event types...
+- Judge note: The answer aligns with the preferred taste by emphasizing simplicity, decoupling, and asynchronous handling, but lacks specific implementation details and concrete examples like the preferred reference
+
+Weakest sanity check:
+
+- Prompt: Write a short email postponing tomorrow's meeting because you have the flu, and suggest two alternative times next week.
+- Judge score: `4/4`
+- Generated answer excerpt: Subject: Postponing Tomorrow's Meeting Hi [Name], I hope you're doing well. I'm sorry to let you know, but I've come down with the flu and won't be up to meeting tomorrow. I don't want to risk spreading it, so I'd like to reschedule. Would [Monday at 10 AM] or [Wednesday at 2 PM] work for you next week? Let me know...
+- Judge note: The email clearly postpones the meeting due to the flu and provides two specific alternative times next week, directly answering the prompt in a coherent and professional manner.
+
+## Interview Probe Findings
+
+These findings come from asking the adapter a balanced `loracles-synthlora-qa` question sample directly and grading the generated answers against the reference answers with the base `Qwen/Qwen3-14B` on a `0..4` rubric. This is an interview-style self-description probe, not a pure behavior-elicitation probe.
 
 - Probe questions answered: `10`
 - Questions per synergy level: `2`