MBTI-DESKTOP-CLONE-TRAITS-UNLOCK-CONTENT-EN-01: align English traits unlock content

[fermatmind]

Summary

• Rewrote the English traits_unlock content in content_baselines/personality_clone/mbti_desktop_clone.en.json for all 32 MBTI fullCode variants.
• Covered career, growth, and relationships traits_unlock intros and item body fields while preserving the existing JSON schema, item counts, labels, asset slots, and importer/API compatibility.
• English copy is written natively for an English result report. It is not machine-translated; zh-CN PR MBTI-DESKTOP-CLONE-TRAITS-UNLOCK-CONTENT-01: thicken zh-CN traits unlock content #2571 was used only as a structure and intent reference.

Why

The English desktop clone baseline had repeated/template copy, A/T field reuse, and awkward generated phrases. This updates the backend-authoritative English baseline so the traits unlock modules better reflect type-specific career behavior, growth friction, relationship patterns, and A/T differences.

Validation

Passed:

• python3 -m json.tool content_baselines/personality_clone/mbti_desktop_clone.en.json >/dev/null
• custom content audit:
  • 32 variants
  • 2,688 traits_unlock item body fields
  • 96 traits_unlock intros
  • 2,784 content-cell audit scope
  • exact duplicate item bodies = 0
  • repeated sentences >= 4 = 0
  • A/T exact same field cells = 0
  • CJK residue = 0
  • placeholder/debug/internal phrases = 0
  • hard deterministic phrasing scan = 0
• git diff --check
• cd backend && php artisan test tests/Feature/PersonalityCms/PersonalityDesktopCloneBaselineImportTest.php tests/Feature/PersonalityCms/PersonalityDesktopCloneSchemaModelTest.php tests/Feature/V0_5/PersonalityDesktopClonePublicApiTest.php
  • 24 passed, 1394 assertions

Blocked in this local DB, so this PR is draft:

• cd backend && php artisan personality:import-desktop-clone-baseline --dry-run --locale=en
• Result: Missing personality_profile_variant for full_code=ENFJ-A locale=en.
• This failed before importing this content and appears to be a local DB prerequisite issue, not a JSON/schema/importer test failure. The PR should not be marked ready until the dry-run is executed in an environment with complete English MBTI profile variants.

Intentionally deferred

• No frontend changes.
• No public personality profile asset changes.
• No legacy PDF/report package changes.
• No API, schema, importer, DB, or deployment changes.
• Future editorial polish outside traits_unlock remains out of scope.