fix(content-drive): truncate long-text field values in listing rows (#37185)

[ihoffmann-dot]

Summary

• Adds TransformOptions.LONG_TEXT_PREVIEW (declared after STORY_BLOCK_VIEW/JSON_VIEW so EnumSet iteration order runs it last) backed by a new LongTextPreviewStrategy.
• Replaces WYSIWYG/TextArea (Jsoup-extracted plain text) and Story Block (new recursive JSON-tree traversal) field values in a listing row with a ≤150-character preview, instead of the full raw value.
• Wired opt-in only at BrowserAPIImpl#dotContentMap via a new DotTransformerBuilder#longTextPreview() chain method — never added to defaultOptions, so no other transformer consumer (Content Editor, ContentResource, GraphQL, asset picker) is affected (AC-007).
• Bug found and fixed while writing the AC-008 test: if a content type's title-source field is itself WYSIWYG/TextArea (its variable is literally title), the strategy would have overwritten the already-correct, untruncated title COMMON_PROPS computes. Fixed by explicitly skipping the title key.
• Updates the @Schema description on ContentDriveResource#search (AC-005; endpoint is @Hidden, no openapi.yaml regen needed) and removes a dead item.body assertion in the Postman collection (AC-006, a listing row never carried that key).

Test plan

• ./mvnw test -pl :dotcms-core -Dtest=LongTextPreviewStrategyTest
• just test-integration-ide
• ./mvnw verify -pl :dotcms-integration -Dcoreit.test.skip=false -Dit.test=BrowserAPITest
• ./mvnw verify -pl :dotcms-postman -Dpostman.test.skip=false -Dpostman.collections=ContentDriveResource
• Confirm no System.out/System.getProperty/System.getenv introduced (checked via diff)
• Latency (p50/p95) is measured, not gated (D7) — requires the Content Drive: folder listing query scans by mod_date instead of by folder (450ms to 101ms), plus 3 related performance items #37148 benchmark dataset, not reproducible in CI

Branched off the approved spec branch per this repo's Spec-Kit flow (spec.md-only in PR1, not merged to main yet).

🤖 Generated with Claude Code

This PR fixes: #37185

Verification (2026-09-04, local)

• 12/12 unit tests (LongTextPreviewStrategyTest) pass.
• 45/45 integration tests (BrowserAPITest) pass.
• 87/87 Postman assertions (ContentDriveResource collection) pass.

Bugs found and fixed in the test code along the way (not the production fix): a package-private field access across packages (fixed via reflection), a test title exceeding the contentlet.title column's varchar(255) limit, an incorrect expected key name (__icon__ vs. the real icon) plus two File-Asset-only keys (mimeType/extension) wrongly expected on a generic-Content row.

[claude]

Claude finished @ihoffmann-dot's task in 2m 26s —— View job

---

Code Review — PR #37396

• Read changed files
• Analyze for bugs / security / conventions
• Post review

The design is sound: LONG_TEXT_PREVIEW is opt-in only at BrowserAPIImpl#dotContentMap, ordinal-last so it runs after STORY_BLOCK_VIEW/JSON_VIEW (verified — both are before it in TransformOptions, and defaultOptions contains both), and JSON_VIEW only touches JSONField so it never re-stringifies the story-block map before this strategy walks it. The title-key skip (AC-008) and the "never in defaultOptions" guard are both test-pinned. No security, transaction, System.*, or convention issues in the diff.

A few non-blocking items:

New Issues

• 🟡 Medium: LongTextPreviewStrategy.java:100-127 — extractStoryBlockPreview/collectText walk the entire story-block tree and concatenate all text before truncate throws away everything past 150 chars. Likewise extractHtmlPreview:85 runs Jsoup.parse over the full HTML document. On the listing path — the exact place this feature exists to keep cheap — a content type with a large story block or long WYSIWYG body does full-payload work per row just to yield a 150-char preview. Short-circuit collectText once out.length() >= MAX_PREVIEW_LENGTH. Fix this →

• 🟡 Medium: LongTextPreviewStrategy.java:133 — text.substring(0, MAX_PREVIEW_LENGTH) can split a UTF-16 surrogate pair when char 149/150 is an astral codepoint (emoji, some CJK), leaving a lone surrogate / replacement glyph at the end of the preview. Back off one char when Character.isHighSurrogate(text.charAt(149)). Fix this →

• 🟡 Medium: LongTextPreviewStrategy.java:74 — for an empty/absent long-text field, map.get(var) is null → the extractors return "" → map.put(var, ""). This injects an empty-string key for every WYSIWYG/TextArea/StoryBlock field even when it had no value (or wasn't in the map at all), slightly changing the listing-row shape versus the plain defaultOptions() output. Assumption: harmless for the content-drive consumer. What to verify: no UI/consumer distinguishes "absent field" from "". Consider skipping the put when the extracted preview is blank and the key wasn't already present.

No blocking issues — the Medium items are polish/perf on an already-correct implementation.
· issue-37185-content-drive-listing-longtext-projection-impl