# UnifiedWriter v5.63.1 Tools Menu / Help Menu Responsibility Policy

## Purpose

v5.63.1 narrows the `Tools` menu to user-facing application operations only.

During the v5.52-v5.63 productization workstream, many temporary diagnostics and specification views were intentionally exposed from the menu so they could be tested quickly.  Those entries are useful during development, but they are not normal document-editing operations.  Leaving them directly under `Tools` makes the product menu look like an implementation checklist instead of an editor.

## Menu responsibility

### Tools

`Tools` should contain operations the user can apply to the active document or editing session:

- Search / Replace
- Comments
- History
- Footnotes
- Compare with current
- Document validation
- Review features such as Track Changes, Suggesting mode, and Version History
- App Settings

As of v5.65.2, macro and script entries no longer remain under `Tools`.  As of v5.65.3, they are shown directly under the dedicated `Development` menu because they are EndUser macro/script authoring and inspection features rather than ordinary document-editing tools.

### Development / Help update in v5.65.2-v5.65.3

`Development` contains EndUser macro/script functions.  Internal UnifiedWriter package-development diagnostics stay under `Help` during development builds.  These Help entries are temporary and should be removed from product builds after documentation and regression reports cover the same information:

- Google Docs feature map
- v5.63 productization summary
- Product readiness diagnostics
- Editing stability diagnostics
- DOCX compatibility diagnostics
- Layout / Print / PDF preflight
- Host API contract
- i18n audit
- Round-trip / DrawingML / Layout quality / Macro Object Model notes
- Product polish notes
- About

These items should eventually be replaced or supplemented by formal documentation pages.  Keeping them under `Help` makes their temporary internal diagnostic nature clear and avoids confusing them with EndUser macro/script authoring features.

## Implementation notes

- Command ids are unchanged.  Menu relocation does not change the command dispatch path.
- `Tools` remains focused and product-like.
- `Development` exposes EndUser macro/script functions.
- Internal package-development diagnostics remain under `Help` during development builds.
- The change is UI organization only; no Model-first editing behavior was changed.