## Purpose

Replace the multi-column plain BorderBox in Documents::Admin::DocumentTypes::IndexComponent with the shared table. This was explicitly deferred by #DREAM-697. The component inherits Admin::Enumerations::IndexComponent; #DREAM-789 already owns its migration to sortable-lists.

## Scope

Use OpPrimer::BorderBoxTableComponent and OpPrimer::BorderBoxRowComponent. Preserve the table/rowgroup/row/columnheader/cell semantics, accessible table name, column indices, mobile layout, and keyboard access to links and actions. This targets the existing ARIA table implementation; a native HTML table rewrite or new DataTable is outside this work.

Preserve the name/type column, document count, drag handle, default/active indicators and all existing creation/edit/deletion/move controls.

## Acceptance criteria

Begin of the insertion* End of the insertion Begin of the deletion -End of the deletion [ ] Document-type data and actions use shared table/row components with meaningful headers and mobile behavior.
Begin of the insertion* End of the insertion Begin of the deletion -End of the deletion [ ] Uses [DREAM-838](https://community.openproject.org/wp/DREAM-838) while retaining Begin of the insertion#DREAM-789'sEnd of the insertion Begin of the deletion #DREAM-789'sEnd of the deletion enumeration endpoint, relative-anchor validation, shared menu integration and morph boundary.
Begin of the insertion* End of the insertion Begin of the deletion -End of the deletion [ ] Drag and keyboard-accessible menu moves persist after reload and remain usable after a morph.
Begin of the insertion* End of the insertion Begin of the deletion -End of the deletion [ ] Document counts, state indicators, actions, permissions and empty state remain correct.
Begin of the insertion* End of the insertion Begin of the deletion -End of the deletion [ ] Component and focused browser coverage verify semantics and ordering behavior.

## Coordination

Part of [DREAM-837](https://community.openproject.org/wp/DREAM-837); follows [DREAM-838](https://community.openproject.org/wp/DREAM-838) and the document-type/enumeration slice of #DREAM-789. Backend/menu migration stays in DREAM-789; this ticket owns the table presentation and integration. The ordering avoids conflicting simultaneous rewrites of the inherited component contract.

## Starting points

Begin of the insertionmodules/documents/app/components/documents/admin/document\_types/index\_component.{rb,html.erb}, item\_component.\*,End of the insertion Begin of the deletion modules/documents/app/components/documents/admin/document_types/index_component.{rb,html.erb}, item_component.*,End of the deletion and app/components/admin/enumerations/. Begin of the insertion

## Hint for QA

This can be tested on `/admin/settings/document_types` . The table there should basically look and behave like before.End of the insertion