fix: resolve remaining W9 comparison wording blockers

[fermatmind]

What changed

• add a new immutable seven-row W1 MBTI comparison candidate package bound to exact package SHA 3583b491806683747898787f106a24f46a09ab031e043ea22e817c900fa88914
• replace the two non-idiomatic ENFP-vs-ENTP stress phrases identified by independent W9
• name INFP explicitly in the ISFP-vs-INFP work section
• recompute the two target section hashes, all immutable file hashes, and the aggregate package SHA
• point the focused package contract at this new immutable candidate while preserving every prior package

Why

The fresh independent W9 review of package 6628be6d... blocked these three reader-facing phrases. This same-scope correction removes only those blockers and preserves source identity, structure, cardinality, claim boundaries, and false permissions.

Validation

• backend/vendor/bin/pint --test backend/tests/Feature/ContentAssets/MbtiComparisonEnglishPackageTest.php
• php artisan test --filter=MbtiComparisonEnglishPackageTest (6 passed, 1004 assertions)
• php artisan test --filter=MbtiComparisonEnglishPackageImporterTest (6 passed, 205 assertions)
• exact seven-slug, JSON parse, English-only, section-hash, file-hash, aggregate-package-hash, and false-permission verification
• git diff --check

Deferred items

• fresh independent W9 review of all seven rows
• exact-package dry-run importer remains bound to the original package until its separate importer scope is advanced
• CMS/database import, editorial approval, publication, activation, SEO/indexability, search submission, deploy, and all production writes remain unauthorized

Repository rule impact

This remains a backend baseline content candidate for later controlled validation. It does not become runtime authority and changes no CMS record, public API, publication state, discoverability surface, or deployment behavior.