Generate UI5 XML View

# Generate UI5 XML View

Produce an OpenUI5 XML view (and, when asked, its controller) that follows current UI5 practice.

## Procedure

1. **Establish the target.** Find the app's namespace in `manifest.json` (`sap.app.id`), its UI5 version
   (`sap.ui5.dependencies.minUI5Version`) and its model names. Do not guess any of them.
2. **Check every control before using it.** Confirm the control exists in that UI5 version and that each
   property/aggregation you set is real. Prefer the UI5 MCP server's API reference when it is available;
   otherwise read the control's API documentation. Never write a property from memory.
3. **Write the view** as XML with `controllerName="<namespace>.controller.<Name>"` and the standard
   `sap.m` default namespace. Bind text through the `i18n` resource model (`{i18n>key}`), never literals.
4. **No globals.** Reference formatters and types with `core:require`, not as `my.app.Formatter.fn`.
   Event handlers use the leading-dot form (`press=".onSave"`).
5. **Add every new string to `i18n.properties`.** A view that references a missing key renders the key.
6. **Run the UI5 linter** on what you changed, if available, and fix what it reports rather than
   suppressing it.

## Output

The view file, the controller if one is needed, the `i18n` additions, and a short list of anything you
assumed because the project did not say.

## Do not

- Use deprecated controls or `sap.ui.core.Core` singletons to work around a missing import.
- Invent model paths: if the data shape is unknown, say so and ask.