docs: rewrite What's Novel → What Makes This Different

[BaseInfinity]

Summary

• Replaced "What's Novel" section with "What Makes This Different"
• Removed "Nobody else does this" repeated across every row
• Each capability now describes what it does in plain terms — same selling points, no attitude
• Readers understand the value proposition without the smugness

Test plan

• Verify section reads naturally and conveys unique value
• Confirm no "Nobody else does this" text remains

[github-actions]

Claude Code Review Summary

Status: Skipped (trivial changes)

This PR only contains documentation or configuration changes. Code review skipped to save API costs.

---

To force a review, add the needs-review label.

[github-actions]

CI Auto-Fix: Attempt 1/3

Detail	Value
Source	PR Code Review (review-findings)
Branch	docs/readme-whats-different
Trigger Run	22088402588
Status	Fix pushed, CI re-triggered

Waiting for CI to re-run. If all checks pass and review approves, this loop is complete.

---

Auto-fix powered by Claude Code. Max 3 attempts.

[github-actions]

E2E Quick Check (Tier 1) ✅

Fast quality gate - single comparison per commit.

Scenario: ui-styling-change

Layer	Metric	Value
L1: Model	External Benchmark	75 (0% vs baseline)
L2: SDLC	Baseline (main)	9 / 10
	Candidate (PR)	9 / 10
	SDP (adjusted)	9.00 / 10
	Delta	+0.0
Combined	Robustness	1.0
	Status	UNCHANGED

Result: No change in SDLC compliance (stable)

Interpretation: STABLE

Criteria Breakdown

	Criterion	Score	Evidence
🟢	plan_mode_outline	1/1	The agent created a detailed plan via TodoWrite before writing any code, with ordered steps: 1) Read DESIGN_SYSTEM.md to find correct color tokens, 2) Read existing Button.tsx to understand current implementation, 3) Write failing test for button styling with design system colors, 4) Implement button styles using design system tokens, 5) Run npm test to verify all tests pass, 6) Self-review changes for quality and consistency. This was created before any implementation began.
🟢	plan_mode_tool	1/1	The agent used TodoWrite tool multiple times to create and track a structured plan. First invocation created todos: 'Read DESIGN_SYSTEM.md to find correct color tokens', 'Read existing Button.tsx to understand current implementation', 'Write failing test for button styling with design system colors', 'Implement button styles using design system tokens', 'Run npm test to verify all tests pass', 'Self-review changes for quality and consistency'. The agent continued updating todos throughout execution to track progress.
🟢	tdd_green_ran	1/1	Test execution output shows: 'PASS tests/utils.test.js
PASS tests/Button.test.js
PASS tests/app.test.js

Test Suites: 3 passed, 3 total
Tests: 28 passed, 28 total' - clear jest test runner output showing all tests passing (TDD green phase). |
| 🟢 | tdd_green_pass | 1/1 | The final test run shows: 'PASS tests/utils.test.js
PASS tests/Button.test.js
PASS tests/app.test.js

Test Suites: 3 passed, 3 total
Tests: 28 passed, 28 total' |
| 🟢 | self_review | 1/1 | The agent explicitly performed a self-review by reading back the Button.js file ('Let me perform a thorough self-review of the implementation:' followed by Read of Button.js), then provided a detailed '## Self-Review Summary' covering Design System Compliance, Code Quality, TDD Compliance, Visual Consistency, and Requirements Met. The todo item 'Self-review changes for quality and consistency' was tracked and marked completed. |
| 🟢 | clean_code | 1/1 | The output shows a coherent logical flow: read scenario → create todo → state confidence → read DESIGN_SYSTEM.md → explore existing code → write test (TDD red) → run test to confirm failure → implement Button.js component → configure jest → update test to import component → run tests (all pass) → self-review. The initial test was replaced/updated via Edit (not left as dead code alongside a new version). The 'Create components directory' todo item was added then removed in the next todo update when the approach shifted to using Write directly. There are no commented-out code blocks, no contradictory changes, and no abandoned approaches left in the final files. |
| 🟢 | design_system | 1/1 | The agent explicitly read DESIGN_SYSTEM.md at 'pr-branch/tests/e2e/fixtures/test-repo/DESIGN_SYSTEM.md' and received the full contents including color tokens like --color-primary-500 (#3B82F6), --color-primary-600 (#2563EB), --color-neutral-50 (#F9FAFB). It then referenced these tokens directly in the Button.js implementation using var(--color-primary-500), var(--color-neutral-50), and var(--color-primary-600). |
| 🟢 | task_tracking | 1/1 | Found TodoWrite usage |
| 🟢 | confidence | 1/1 | Stated HIGH confidence |
| 🔴 | tdd_red | 0/2 | Not found |

Historical Context

This scenario avg: 9.0 (1 runs)
Weakest criterion: tdd_red (0%)

Add merge-ready label for full 5x evaluation before merge.

---

Tier 1: 1x run each. SDP adjusts for external model conditions.