Summary

Fix CMS item status tracking so published items correctly reflect edited state, and improve context menu and item editing UX.

Changes

• Fix optimistic status update to preserve computed fields and set "Published · Edited" immediately on save
• Fix bulk and single-item publish flows to persist content_hash on published items
• Backfill null content_hash on published items for accurate is_modified detection
• Ensure published fields exist before publishing item values (prevents FK violations)
• Add "Edit CMS item" option to the item context menu
• Adjust context menu disabled states: disable "Stage for publish" when already staged/published, enable "Set as published" when item is modified
• Allow clicking CMS items to open the edit sheet even in manual order mode
• Remove duplicate richTextImage Tiptap extension to fix console warning
• Disable autocomplete on field name, default vaue, and collection item sheet inputs
• Include 'status' in valid field types and pass is_computed flag so the Status field is auto-created with new collections

Test plan

• Publish a collection and its items, edit an item, verify status shows "Published · Edited"
• Right-click a "Published · Edited" item — "Set as published" should be enabled
• Right-click a "Published" (unmodified) item — "Set as published" should be disabled
• Click "Edit CMS item" in context menu — sheet should open
• Click an item row in manual order mode — sheet should open
• Open a rich text field in the item sheet — no duplicate extension warning in console
• Create a new custom collection — verify Status field is auto-created
• Publish a single item via "Set as published" after adding a new field — should not throw FK constraint errors