Warn before the gate refuses, and check restore destinations

nodes#new marks the kinds that place under /updates, derived from each kind's
own path_prefix. The three parent pickers mark candidates the current user
cannot publish into; menu_search returns needs_redaktion per result, computed
per user rather than as a bare restricted flag, and the menu-item picker opts
out.

restore_from_trash! checks its destination: the restore is the move, applied
rather than staged, so no later publish would have caught it. The node
returns as a draft either way.

1 files changed, 11 insertions, 0 deletions

diff --git a/public/stylesheets/admin.css b/public/stylesheets/admin.css
index 55fdf15d..7f286705 100644
--- a/public/stylesheets/admin.css
+++ b/public/stylesheets/admin.css
@@ -889,6 +889,7 @@ div.layout_row_content {
   font-weight: bold;
   color: var(--text-muted);
   cursor: not-allowed;
+  line-height: 1.25rem;
 }
 
 .info_group .disabled_action svg {
@@ -973,6 +974,10 @@ form.button_to button[type="submit"] {
   padding-bottom: 4px;
 }
 
+.restricted_kind_hint {
+  color: var(--accent);
+}
+
 .action_button + .field_hint {
   display: inline;
   margin-left: 0.5rem;
@@ -1459,6 +1464,12 @@ input#menu_item_title {
   padding-bottom: 4px;
 }
 
+.search_results .restricted_result {
+  display: block;
+  font-size: 0.85rem;
+  color: var(--accent);
+}
+
 .search_results p.search_more {
   margin: 0;
   padding: 6px 4px;