gram: docs

> ./openspec/specs/core-table-resize-ops/spec.md

# core-table-resize-ops Specification

## Purpose

TBD - created by archiving change unify-orchestration-tier1. Update Purpose after archive.

## Requirements

### Requirement: Pure table-resize readers and commit builders in core

`@eigenpal/docx-editor-core` SHALL expose `readColumnWidths`, `readRowHeight`, `readLastColumnWidth`, `commitColumnResize`, `commitRowResize`, and `commitRightEdgeResize`, plus the shared constants (`TWIPS_PER_PIXEL`, `MIN_CELL_WIDTH_TWIPS`, `MIN_ROW_HEIGHT_TWIPS`). These are pure `(view, opts) → void | values` functions with no framework coupling. The resize gesture FSMs SHALL remain in each adapter.

#### Scenario: Column resize commit

- **WHEN** `commitColumnResize(view, opts)` is called with a column index and new left/right widths
- **THEN** the table and affected cell widths are updated via a single transaction, identical to the prior adapter output

#### Scenario: Row and right-edge resize commits

- **WHEN** `commitRowResize` or `commitRightEdgeResize` is called
- **THEN** the row height / last-column width is updated matching prior behavior, honoring the minimum-size constants

#### Scenario: Adapters keep their FSMs

- **WHEN** the readers/commits are lifted
- **THEN** React's `useTableResizeState` and Vue's `useTableResize` retain their gesture state machines and call core for reads/commits; the body-vs-header/footer target view is still resolved by the adapter