feat(edit-content): restructure command bar & side panel around Actions tab (#35892)

[oidacra]

Proposed Changes

Restructures the new Edit Contentlet command bar and side panel around a single Actions tab (#35892).

Command bar (dot-edit-content-form)

• Slimmed to [status tag] | Preview … (overflow menu) ▢ (sidebar toggle) and made sticky on scroll.
• Status now renders as a local p-tag; the lock toggle and inline workflow actions were removed from the bar.
• New dot-edit-content-command-bar-actions overflow (…) menu — Permissions, Rules (pages only), View references — which owns the dialog-open logic relocated from the deleted sidebar wrappers.
• Preview now resolves HTML pages via a new generatePageEditUrl helper in addition to URL-mapped content.

Side panel (dot-edit-content-sidebar)

• The Info tab becomes Actions (lightning-bolt icon); the Settings tab is removed.
• The lock control is relocated as a distinct outlined button with a lock icon, separated from the workflow actions by a divider.
• Workflow actions render stacked full-width, one above another (new stacked mode on the shared dot-workflow-actions), first action primary. Firing stays in the form — the sidebar emits workflowActionFired and the layout delegates to DotEditContentFormComponent.fireWorkflowAction via its viewChild, so all validation/wizard/push-publish logic is untouched.
• The Locales, Workflow and Details sections are independently collapsible and persist their open/closed state via DotLocalstorageService; headers use the design's uppercase treatment.
• The information card drops the status chip and the References card (both now live in the command bar).

Removed the now-orphaned dot-edit-content-sidebar-permissions / dot-edit-content-sidebar-rules wrapper components (their dialogs are reused by the new overflow menu).

Out of scope (by design): Locales content is untouched (tracked in #35889) — only its section becomes collapsible. The lock control is relocated only; the richer "Release Lock"/steal-lock flow is deferred. Workflow/Details card visual restyle was intentionally left for a later pass.

Checklist

• yarn nx lint edit-content / yarn nx lint ui — pass (pre-existing warnings only)
• yarn nx test edit-content / yarn nx test ui — pass
• yarn nx build dotcms-ui (AOT template type-check) — pass
• yarn nx format:write

How to test

1. Open an existing contentlet.
2. Command bar shows [status tag] | Preview … ▢, sticks on scroll; no lock toggle / inline workflow actions.
3. Actions tab: lock button (outlined + icon, divider below); workflow actions stacked full-width with the first action primary; firing Save/Publish still validates the form (scroll-to-error) and opens the wizard for push-publish / action-input.
4. Locales / Workflow / Details collapse independently and persist across reload.
5. … menu opens Permissions, Rules (pages only) and View references; Settings tab is gone.
6. Preview shown for a page and for URL-mapped content (existing only); hidden for new content. New contentlet → … menu hidden.

[claude]

Claude finished @oidacra's task in 2m 34s —— View job

---

PR Review

• Read changed files and analyze the diff
• Review for bugs, edge cases, design issues, security concerns
• Post findings

---

Four issues worth addressing, roughly in severity order.

---

1. closeOnEscape: false on Permissions and Rules dialogs violates project standard

CLAUDE.md → "All dialogs must have closable: true and closeOnEscape: true"

In dot-edit-content-command-bar-actions.component.ts:130 and :159, both the Permissions and Rules dialogs are opened with closeOnEscape: false. The References dialog on :192 correctly uses closeOnEscape: true. The spec on line 148 also hardcodes closeOnEscape: false, so this is perpetuated in tests.

If the intent is to guard against accidental ESC inside the iframe, the flag should be set explicitly and the CLAUDE.md rule updated; otherwise both dialogs should flip to true. Fix this →

---

2. DotEditContentSidebarComponent.fireWorkflowAction has a bare null access

dot-edit-content-sidebar.component.ts:152

inode: this.$contentlet().inode,

$contentlet() can return null (its type is DotCMSContentlet | null). On a new contentlet before the first save, or during a loading cycle, this throws. The layout's onWorkflowActionFired doesn't have this problem because it reads this.$store.contentlet()?.inode. This path is also the only workflow path that skips form validation — the reset-workflow button in the Workflow section calls this method directly, not through the layout's validated onWorkflowActionFired. Whether bypassing validation is intentional for a reset action should be explicitly documented. Fix this →

---

3. $appendContext getter creates a new object on every change-detection cycle

dot-edit-content-form.component.ts:280

get $appendContext() {
    return { $store: this.$store, showSidebar: ..., ... };
}

This is a plain getter, not a signal computed. Every CD cycle a new object is returned, causing TabViewInsertDirective to see a changed reference for [dotTabViewAppendContext] and re-render the appended template. Because showPreview is a closure created inline here too, it also changes every cycle. Converting to a computed() signal or at least memoizing the stable parts would stop spurious re-renders.

---

4. $hasReferences fragile string comparison

dot-edit-content-form.component.ts:212

return !!relatedContent && relatedContent !== '0';

This works only because the store surfaces a string (not a number). If relatedContent returns 0 (number) or undefined, the guard behaves differently. Using Number(relatedContent) > 0 would be explicit and type-safe regardless of what the store returns.

---

Clean otherwise — the architecture around emitting workflowActionFired from the sidebar and delegating back to the form's fireWorkflowAction via viewChild is a good pattern that preserves all validation and wizard logic.