refactor(ui): adopt p-tag for status and locale displays via shared status badge

[oidacra]

Summary

• p-chip has no severity API, so status badges fought the PrimeNG theme with Tailwind !important overrides scattered across the app. p-tag supports severity natively, per the design decision: tags = informative, chips = interactive.
• The shared status component was renamed dot-contentlet-status-chip → dot-contentlet-status-badge (it renders a tag; "badge" names the UI concept, not the PrimeNG widget). Internally it derives status/severity/label as computed signals from a single STATUS_SEVERITY map with inferred types, rendered by a one-line inline <p-tag> template. All labels resolve through DotMessageService (previously only "New" was translated).
• During implementation the scope grew (by decision) into the full tag adoption sweep: every status/locale display in the app now follows the rule, and the two duplicated status-derivation pipes were deleted — the badge is the single owner of status logic.

Closes #36089

Changes

Shared component (libs/ui)

File	Change
dot-contentlet-status-badge.component.ts	Renamed from -chip. Status logic inline as computed signals (status → severity/label), types inferred from the STATUS_SEVERITY map (single source of truth), labels translated via DotMessageService (all five statuses are i18n keys in Language.properties), ChipModule → TagModule, one-line inline template (separate .html removed)
dot-contentlet-status-badge.component.spec.ts	Asserts at the Tag input boundary (spectator.query(Tag) → .severity/.value) — no coupling to PrimeNG internals. Parameterized table covers all derivation cases incl. precedence (archived wins over live) and edge cases (live-but-not-working, live-without-live-version), plus null → translated New/info
dot-contentlet-status/ (pipe)	Deleted — DotContentletStatusPipe lost its last consumer (command bar)
dot-asset-card.component.*	Language chip → p-tag severity="info"; status badge reference renamed
theme.config.ts	chip/tag block comments updated (status badges are tags now; no stale "Content Status" / "version-history chips" references). The tag block itself (1.75rem + severity colorScheme) was already in place

Consumers migrated to the badge / tags

Area	Change
Content Drive (dot-folder-list-view)	Status → badge (rename only); locale chip → p-tag severity="info" (same blue 1:1, no !important)
Edit Content — command bar (dot-edit-content-form)	Hand-rolled p-tag + local contentStatusSeverity() + pipe injection replaced by <dot-contentlet-status-badge [state]="$statusState()" /> — "New" is now translated
Edit Content — relationship field (table + select-existing dialog)	Local ContentletStatusPipe ({label, classes} with theme-orphaned p-chip-* classes — every status rendered gray) replaced by the badge. Restores the legacy Dojo distinction: Draft/Revision/Published are visually distinct again. Pipe + DotEditContentStatus enum deleted
Edit Content — history sidebar (dot-history-timeline-item)	live/working/variant chips → p-tag severities success/warn/info, labels keep their own i18n keys
Rename-only consumers	es-search, asset search, block-editor, dot-pages, dot-templates, dot-containers, e2e page object, Stencil @deprecated notes + generated readme

Docs

File	Change
docs/frontend/STYLING_STANDARDS.md	New Tags vs Chips section: decision rule (1. contentlet status → <dot-contentlet-status-badge>; 2. other read-only state → p-tag + severity; 3. no status / interactive → p-chip), severity mapping table, explicit rule that locale labels use p-tag severity="info", and the no-Tailwind-!important rule

Acceptance Criteria

• The component renders a single p-tag with native severity per the mapping (Published→success, Archived/deleted→danger, Revision→info, Draft→warn).
• When state is null, the tag shows the translated New label with info severity.
• The tag renders at a standardized 1.75rem height via design tokens in CustomLaraPreset (components.tag), not per-component CSS.
• No Tailwind !important color overrides remain in the component template (nor in any migrated consumer).
• ChipModule removed; TagModule from primeng/tag used instead.
• The stale "Content Status" reference in the chip block comment in theme.config.ts is updated.
• docs/frontend/STYLING_STANDARDS.md documents the tags-vs-chips rule (tags = informative, chips = interactive).
• Consumers keep working with no behavioral changes beyond the intended visual/status fixes.
• Spec covers severity per status (including null → New/info); yarn nx test ui passes.
• Visual gate verified in running instance: Content Drive list (status + locale), Edit Content command bar, relationship field (Draft/Published/Revision rendering correctly, confirmed against legacy Dojo semantics), history sidebar.

Test Plan

• yarn nx lint — ui, edit-content, content-drive-ui, es-search, dotcms-ui: pass
• yarn nx test ui — 678 tests pass
• yarn nx test edit-content — 1929 tests pass
• yarn nx test content-drive-ui — 177 tests pass
• yarn nx test dotcms-ui — 2153 tests pass
• yarn nx affected:test --base=origin/main — block-editor / dotcms-block-editor failures are pre-existing on main (verified identical 27F/36P with changes stashed)
• PR Build green after the Stencil generated-readme fix
• Manual visual verification in running instance (screenshots in thread: Content Drive, relationships with Draft/Published/Revision)

Notes

• −400 lines of duplicated status logic: DotContentletStatusPipe (libs/ui) and ContentletStatusPipe + DotEditContentStatus enum (edit-content) are deleted; the badge is the single source of truth.
• The relationship field's old "Changed" state (live with pending draft) is preserved as Revision — the API payload includes hasLiveVersion, verified visually.
• History timeline uses raw p-tag (not the badge) intentionally: those are per-version states (this version is live / is the working copy) with their own i18n keys, not a contentlet DotContentState.
• Interactive chips remain chips per the rule: relationship search filters, category field selections.
• The scope expansion (rename + consumer sweep + pipe deletions, originally deferred to Restructure Command Bar and Side Panel around new Actions tab (Edit Contentlet) #35892/Edit Content sidebar: align History & Comments tabs with the Actions tab (accordion reuse + empty states) #36033 follow-ups) was decided during implementation; Edit Content sidebar: align History & Comments tabs with the Actions tab (accordion reuse + empty states) #36033 remains open for its actual scope (accordions/empty states).

Commits

1. fa634b1d53 — migrate dot-contentlet-status-chip from p-chip to p-tag
2. e0f4c0eb26 — rename to dot-contentlet-status-badge (28 files)
3. fea4f64714 — infer status badge types from the severity map
4. 25765b7c3a — inline the one-line template
5. 1585250b76 — test at the Tag input boundary
6. 102e41888d — docs: mandate the badge for contentlet statuses
7. 3e2b64209a — fix Stencil generated readme (CI clean-tree check)
8. 3443f79fcc — Content Drive locale chip → tag
9. de89905974 — docs: locale labels rule
10. 6f39e3e09c — command bar uses the badge; drop DotContentletStatusPipe
11. c66fd2d0ef — history sidebar chips → tags
12. 426e4bab2f — relationship field uses the badge; drop ContentletStatusPipe
13. 8e28518ce1 — asset card language chip → tag
14. b1205b60ac — translate every badge label via DotMessageService

[claude]

Claude finished @oidacra's task in 45s —— View job

---

Rollback Safety Analysis — Complete

• Read rollback-unsafe categories reference
• Get full PR diff (48 files, +438/−731 lines)
• Analyze diff against all unsafe categories
• Apply label ✅

Result: Safe to Rollback

All 48 changed files are Angular/TypeScript frontend only:

File type	Count
Angular component .ts / .html / .spec.ts	40
TypeScript pipes / enums (deleted)	5
Theme config / Stencil / Markdown docs	3

Zero Java (.java), SQL, XML, or backend files are touched.

No unsafe categories apply:

Category	Assessment
C-1 Structural Data Model Change	❌ No DB changes
C-2 Elasticsearch Mapping Change	❌ No ES mapping code
C-3 Content JSON Model Version Bump	❌ No contentlet_as_json / CURRENT_MODEL_VERSION changes
C-4 DROP TABLE / DROP Column	❌ No DDL
H-1 One-Way Data Migration	❌ No data transformation
H-2 RENAME TABLE / COLUMN	❌ No DDL
H-3 PK Restructuring	❌ No DDL
H-4 New ContentType Field Type	❌ No field type registration
H-5 Storage Provider Change	❌ No storage changes
H-6 DROP PROCEDURE/FUNCTION	❌ No DDL
H-7 NOT NULL Column Without Default	❌ No DDL
H-8 VTL Viewtool Contract Change	❌ No viewtool changes
M-1 Column Type Change	❌ No DDL
M-2 Push Publishing Bundle Format	❌ No bundler changes
M-3 REST/GraphQL API Contract	❌ No REST endpoint changes
M-4 OSGi Interface Change	❌ No OSGi changes

Label AI: Safe To Rollback has been applied.

[github-actions]

❌ Codex Review failed — openai.gpt-5.5

The review job failed before producing output. See the run for details.

_{Run: #27444105249}