# UnifiedWriter v5.65.2 Development Menu Responsibility Clarification

## Purpose

v5.65.3 update: the responsibility boundary in this document remains valid, but the extra `Development > Macros` submenu was removed.  Current UI is `Development > Macro diagnostics / VBA code viewer / Script engine / VBA to JS translator`.  See `docs/DEVELOPMENT_MENU_V5653.md`.

v5.65.2 clarifies the meaning of the top-level `Development` menu.

`Development` is an EndUser-facing authoring surface for document macros and scripts.  It is intended for users who create, inspect, convert or run browser-safe UnifiedWriter macros/scripts inside documents.

It is not the menu for the internal team developing the UnifiedWriter package itself.

## Menu organization

### Tools

`Tools` remains focused on document-facing operations:

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

### Development

`Development` contains EndUser macro/script functions only.  As of v5.65.3 they are direct entries under the top-level Development menu:

- Macro diagnostics
- VBA code viewer
- Script engine
- VBA to JS translator

These are part of the application feature set because future document users may author or inspect macros/scripts.

### Help

`Help` keeps documentation and temporary internal package-development diagnostics:

- Docs / feature notes
- Product readiness diagnostics
- Editing stability diagnostics
- DOCX compatibility diagnostics
- Layout / Print / PDF preflight
- Host API contract
- i18n audit
- DOCX/DOCM round-trip / DrawingML / layout quality notes
- Macro Object Model notes
- Product polish notes
- App Settings
- About

The diagnostic groups under `Help` are temporary development-build conveniences.  They should be removed from product builds after the same information is covered by docs, automated regression reports, or developer-only integration pages.

## View / read-only mode

In `mode: "view"` or `readOnly: true`, the menu pruning logic keeps only view-safe macro entries under `Development`.  Macro diagnostics and VBA code viewer may remain visible because they inspect metadata.  Script execution and VBA-to-JS conversion are hidden or rejected by command guards because they are not read-only operations.

## Contribution API impact

The declarative contribution layer exposes `writer.menu.development` as the EndUser macro/script menu, separate from `writer.menu.tools`.

- `writer.menu.tools` contains document-facing commands.
- `writer.menu.development` contains EndUser macro/script commands.
- Internal package-development diagnostics are not part of `writer.menu.development`.
- Existing command IDs such as `writer.macro.diagnostics`, `writer.macro.codeViewer`, `writer.macro.run`, and `writer.macro.translateVba` are unchanged.

This is a UI organization change only.  The command dispatch path and macro safety policy are unchanged.