# Migrating a TopLogic application from 8.0.0-alpha9 to 8.0.0-alpha10

Audience: an AI coding agent (or developer) upgrading a TopLogic application project.
Sources: release notes https://dev.top-logic.com/tl/content/releases/TL_8.0.0-alpha10/ and the
TopLogic Trac tickets flagged `RequiresMigration` for milestone `TL_8.0.0-alpha10` (ticket numbers
are given as `#NNNNN`; the per-ticket page is `https://dev.top-logic.com/tl/content/releases/TL_8.0.0-alpha10/NNNNN/`).

This release removes the scheduler options `run-on-startup`, `dont-run-tasks-on-startup` and
`startup-sleep` and makes every task decide whether it runs on every cluster node (#29696), replaces
the attributes `access-parent` / `access-reference` of the model-based security configuration by an
`<access-parent>` element (#29760), protects the anonymous account through the framework
configuration of the `CommandApprovalService` (#29740), checks in-app configured drops against the
`Write` right (#29514), lets value options annotated at a type take effect (#29741), requires a
variable name for OpenAPI server parameters whose name is no TL-Script identifier (#29754), ships a
default application shell `app.view.xml` with `tl-layout-view` (#29744) and orders the stylesheets
of the React UI in CSS cascade layers (#29661). Java code is affected by changed signatures of
`DefaultProvider` (#29731), `TaskImpl` (#29696), `RowSetBinding` (#29693) and `ModeSelector`
(#29617). One engine migration rewrites data automatically (#29741).

## How to use this document

1. Work through the sections in order. Section 1 must be done first (the project does not build
   otherwise); the rest can be done in any order.
2. Every step has a **Detect** line: run the search in the application's source tree. If it finds
   nothing, the step does not apply — skip it. Do not invent changes for steps that do not apply.
3. Many changes are reported as **configuration errors at application start or when a view is
   loaded** (not at compile time). After migrating, start the application, log in — as an
   administrator **and** as a regular (non-admin) user — and open every view; read the log for
   `ConfigurationException` / configuration errors.
4. Some changes only show at run time or visually (refused drops, changed option lists, changed
   styling). They are marked **review**: check the described code, do not change it blindly.
5. The engine ships developer articles in its jars (`META-INF/tl-docs/**/*.md`; from this release
   on also the former engine FAQ, #29765). If the `tl-mcp` tools are available, read them with
   `read_doc` — in particular `access-configuration` for section 3.
6. Ticket descriptions on Trac are partly German; this document translates the instructions.
7. Configuration that a running installation saved itself (service or task configuration changed
   in the administration UI) lives in the installation's `autoconf` directory (system property
   `tl_autoconf_dir`), outside the source tree. No migration touches it. Where a step says so, check
   that directory, too, or tell the user to do it before the first start.

Search commands below assume the project root as working directory and GNU grep.

---

## 1. Build and platform

### 1.1 Version bump
Set the TopLogic version to `8.0.0-alpha10` (parent `tl-parent-app` / `tl-parent-core` version, or
the `tl.version` property).

Detect: `grep -rn --include=pom.xml -e '8.0.0-alpha9' .`

### 1.2 Java API changes — mandatory if used (Java)
Compile errors point to these; the list says what to do. Each item names its ticket.

- **Default providers (#29731).** `DefaultProvider.createDefault(Object context,
  TLStructuredTypePart attribute, boolean createForUI)` lost the parameter `createForUI`. Remove the
  parameter from own implementations. An implementation that returned `null` for
  `createForUI == true` because its default can only be computed in the transaction creating the
  object overrides `isComputedInTransaction()` with `true` instead.

  ```java
  // before
  public Object createDefault(Object context, TLStructuredTypePart attribute, boolean createForUI) {
  	if (createForUI) return null;
  	return nextNumber(context);
  }
  // now
  @Override
  public Object createDefault(Object context, TLStructuredTypePart attribute) {
  	return nextNumber(context);
  }
  @Override
  public boolean isComputedInTransaction() {
  	return true;
  }
  ```
- **Scheduler tasks (#29696).**
  - `TaskImpl` no longer implements `isNodeLocal()`: an own task inheriting directly or indirectly
    from `TaskImpl` without overriding it does not compile any more. Implement it: `true` if the
    task must run on every cluster node (the behavior so far), `false` if it may run only once in
    the cluster. With `false`, the duties of `Task#isPersistent()` apply (own `ThreadContext`, a
    result protocol per run); the simplest way is to inherit from `StateHandlingTask` or to call
    `runWithResultProtocol(...)` in `run()`. In a cluster, check `false` for every task that
    changes persistent data. Report the decision per task to the user.
  - Remove calls of `setRunOnStartup(...)` and overrides of `isRunOnStartup()` (the methods are
    gone from `Task`, `TaskImpl`, `TaskWrapper` and `CompactHistoryTask.Config`).
  - Replace direct instantiations `new TaskImpl(...)` by a concrete subclass (`TaskImpl` is
    abstract).
- **Row-set bindings of the view layer (#29693).** Own implementations of
  `com.top_logic.layout.view.form.RowSetBinding`: `updateMembership(FormControl, List)` becomes
  `updateMembership(TLObject owner, List rows)`, `commit(Transaction, FormControl, List, List)`
  becomes `commit(TLObject owner, List persisted, List original)`. `owner` is the edit buffer of the
  object holding the rows (so far `form.getOverlay()`); `commit` is still called inside the saving
  transaction.
- **Mode selectors (#29617).** `ModeSelector.traceDependencies(TLObject, TLStructuredTypePart,
  Sink, OverlayLookup)` has an additional parameter `boolean editMode` after the attribute.
  Application classes implementing `ModeSelector` must add it (and may use it like the `editMode`
  of `getMode`).
- **Coverage records (#29760).** The record
  `com.top_logic.element.boundsec.manager.coverage.TypeCoverage` holds the origin of the marks
  (`withoutSecurityOrigin`, `internalOrigin`, a `TLModelPart`) instead of the booleans
  `withoutSecurity` and `internal`; the accessors `withoutSecurity()` and `internal()` remain, so
  only code calling the canonical constructor is affected.

Detect:
```
grep -rn --include=*.java -e 'DefaultProvider' -e 'createForUI' -e 'extends TaskImpl' -e 'extends StateHandlingTask' \
  -e 'extends .*Task\b' -e 'new TaskImpl' -e 'RunOnStartup' -e 'RowSetBinding' -e 'updateMembership' \
  -e 'ModeSelector' -e 'traceDependencies' -e 'TypeCoverage' .
```

---

## 2. Server configuration

### 2.1 Scheduler: `run-on-startup`, `dont-run-tasks-on-startup` and `startup-sleep` removed (#29696) — mandatory if used
The task option `run-on-startup` and the scheduler options `dont-run-tasks-on-startup` and
`startup-sleep` no longer exist. A configuration still setting one of them is rejected at startup.

- Remove the attribute `run-on-startup` from `<task>` elements in all configuration files
  (`*.config.xml`). With `run-on-startup="true"` nothing changes.
- A task with `run-on-startup="false"` **and** an `<on-startup/>` in its `<schedules>` did not run
  at startup so far. To keep that behavior, remove the `<on-startup/>`. With other schedules
  `run-on-startup="false"` had no effect and is dropped without replacement.
- Remove the attributes `dont-run-tasks-on-startup` and `startup-sleep` from the configuration of
  the service `com.top_logic.util.sched.Scheduler`. Tasks now always start only once the application
  is fully started — the former behavior with `dont-run-tasks-on-startup="true"`.
- **Saved configuration:** a service or task configuration changed in the administration UI lives
  in the `autoconf` directory of the installation (e.g. `com.top_logic.util.sched.Scheduler.config.xml`)
  and is not adapted by any migration. Before the first start with this version, remove
  `run-on-startup`, `dont-run-tasks-on-startup` and `startup-sleep` there as well; otherwise the
  start aborts with "Configuration descriptor '…SchedulerConfig' has no property
  'dont-run-tasks-on-startup'". If the directory is not accessible, tell the user.
- Tests that start services without an application start and need tasks to be executed by the
  scheduler must be embedded in the test setup `test.com.top_logic.basic.module.RunningModuleSystemSetup`.
- Optional: a `ScriptTask` whose script only acts on the local node (e.g. resets a local cache) can
  be run on every node with `node-local="true"` (default: once in the cluster).

```xml
<!-- before -->
<task class="my.app.MyTask" name="MyTask" run-on-startup="false">
	<schedules>
		<on-startup/>
		<daily time-of-day="02:00"/>
	</schedules>
</task>
<!-- now: same behavior -->
<task class="my.app.MyTask" name="MyTask">
	<schedules>
		<daily time-of-day="02:00"/>
	</schedules>
</task>
```

Detect: `grep -rn -e 'run-on-startup' -e 'dont-run-tasks-on-startup' -e 'startup-sleep' --include=*.xml .`
and the same grep in the installation's `autoconf` directory (`$tl_autoconf_dir`) if available.
For tests: `grep -rln -e 'Scheduler' --include=*.java src/test`.

(Java API of the same ticket: step 1.2.)

### 2.2 `CommandApprovalService` must not be overridden (#29740) — mandatory if used
The checks protecting the anonymous account are part of the framework configuration of the
`CommandApprovalService` (`tl.accounts.config.xml` of `tl-element`, `contactConf.config.xml` of
`tl-contact`). An application configuring the service with `config:override="true"` discards these
checks. Remove the `config:override` from the service configuration, so that the application's own
`<check>` entries add to the framework's:

```xml
<config service-class="com.top_logic.tool.execution.service.CommandApprovalService">
	<instance class="com.top_logic.tool.execution.service.ConfiguredCommandApprovalService">
		<check type="my.module:MyType">
			...
		</check>
	</instance>
</config>
```

Detect: `grep -rn -A2 'service.CommandApprovalService' --include=*.xml . | grep -e 'config:override'`
(check the `<config>` and `<instance>` element of every hit of
`grep -rn 'CommandApprovalService' --include=*.xml .`).

### 2.3 OpenAPI server: variable name for parameters with non-identifier names (#29754) — mandatory if used
OpenAPI server configurations containing request parameters (or parts of a multipart body) whose
name is no valid TL-Script identifier (e.g. containing `-`, such as the header `X-Gitea-Event`) no
longer load without a variable name. Set `variable-name` for such parameters in the service
configuration of the OpenAPI server; the implementation then reads the value as `$event` (before,
it was not reachable at all):

```xml
<parameter class="com.top_logic.service.openapi.server.parameter.HeaderParameter"
	name="X-Gitea-Event" variable-name="event" .../>
```

A given variable name must itself be a valid identifier; two parameters of one operation must not
share a variable name.

If the configuration of the OpenAPI server was edited in the running application, it lives in the
`autoconf` directory of the installation and must be adapted there as well before the first start
(if the directory is not accessible, tell the user).

Detect: `grep -rn -E '<parameter[^>]*name="[^"]*[^A-Za-z0-9_"][^"]*"' --include=*.xml . | grep -v 'variable-name='`
and the same grep in the installation's `autoconf` directory (`$tl_autoconf_dir`) if available.

### 2.4 Value options: framework defaults and options at types (#29741) — review (data-touching)
The data migration `Ticket_29741_hide_anonymous_in_options` (module `tl-contact`) replaces the value
options (`<options>` annotation) of `tl.accounts:Group#members` and
`tl.accounts:RepresentativeGroup#members` so that the anonymous account is no longer offered.

- If the application adapted the options of these two attributes, the adaptation must be made again
  after the migration.
- Value options already annotated at a **type** in the application had no effect so far; now they
  apply to every attribute of that type without options of its own. Check such annotations; a
  function in `options-by-expression` must have the form `obj -> ...`.

Detect:
```
grep -rn -e 'Group#members' -e 'RepresentativeGroup' --include=*.xml --include=*.java .
grep -rn -B8 -e '<options' -e 'options-by-expression' --include=*.model.xml . | grep -e '<class ' -e '<interface ' -e '<options' -e 'options-by-expression'
```
For the second grep: an `<options>` / `options-by-expression` inside `<annotations>` of a
`<class>` / `<interface>` (not of a `<property>` / `<reference>`) is a type-level annotation —
report it to the user with the attributes it will now apply to. Customizations of the group options
made in the model editor of the running application are in the database; ask the user.

---

## 3. Security / access checks

### 3.1 Access parent is an element (#29760) — mandatory if used
The access parent of a type is no longer configured by the attributes `access-parent` and
`access-reference` of the `<class>` entry of the `SecurityConfigurationService`, but by an element
`<access-parent>` holding exactly one definition. The old attributes are rejected as configuration
error at startup.

| before | now |
|---|---|
| `access-parent="container"` | `<access-parent><container/></access-parent>` |
| `access-parent="container" access-reference="X"` | `<access-parent><container reference="X"/></access-parent>` |
| `access-parent="target" access-reference="X"` | `<access-parent><target reference="X"/></access-parent>` |
| `access-parent="self"` | `<access-parent><self/></access-parent>` |
| `access-parent="auto"` | remove the attribute |

```xml
<!-- before -->
<class name="my.module:Comment" access-parent="container" access-reference="my.module:Ticket#comments"/>
<!-- now -->
<class name="my.module:Comment">
	<access-parent><container reference="my.module:Ticket#comments"/></access-parent>
</class>
```

Also check `WEB-INF/autoconf/com.top_logic.model.security.SecurityConfigurationService.config.xml`
(source tree and installation): the "Access rights…" dialog of the coverage view writes to it.
New, optional: `<access-parent><script expr="..."/></access-parent>` computes the access parent by a
TL-Script function (developer article `access-configuration`, section "Access parent").

Detect: `grep -rn -e 'access-parent=' -e 'access-reference=' --include=*.xml .`

(Java: `TypeCoverage`, step 1.2.)

### 3.2 In-app configured drops require the `Write` right (#29514) — review
In-app configured drops (`TableDropTargetByExpression`, `GridDropTargetByExpression`,
`TreeDropTargetByExpression`, `TreeTableDropTargetByExpression`, `OntoTreeDropByExpression`,
`OrderedTreeDropByExpression` and the flow-diagram drop `ScriptedDropHandler`) are now checked with
the command group `Write` on the target of the drop, like a command: command approval service →
group allowed for the user (restricted account) → rights on the security object. Users without
write right (or refused by the `CommandApprovalService`, or with a restricted account) can no longer
perform such drops; the drop is not shown as possible and is refused on the server.

Where a drop should be allowed with another right, set a matching group (`group`) or a matching
target (`target`, a TL-Script function with the same arguments as the drop check, returning the
object to check) in the drop configuration. Without `target`, the target is the row dropped on
(table), the business object of the target node (tree), the business object of the parent node
inserted into (ordered tree drop), or the business object of the diagram element dropped on (flow
diagram); an empty target checks the model of the component.

Own drop targets implemented in Java are not checked automatically; they can use the same check
(`CommandSecurity`, `DropSecurity`).

Detect: `grep -rn -e 'DropTargetByExpression' -e 'DropByExpression' -e 'ScriptedDropHandler' --include=*.xml .`
Report the affected views to the user and which roles have `Write` there (role profile
administration; if the application ships a `security.xml`, there as well); test them as a regular
user.

---

## 4. React views (`*.view.xml`)

### 4.1 Default application shell `app.view.xml` (#29744) — mandatory if the application has an own `app.view.xml`
`tl-layout-view` now ships an application shell `WEB-INF/views/app.view.xml`. Equally named views of
all modules are merged as overlays; an application bringing its own complete `app.view.xml` would
be stacked onto the shipped shell (duplicated notices, user menu and administration entry). Such an
application must take one of the following variants.

**Variant 1 (recommended): reduce to an overlay.** The own `app.view.xml` keeps only what the
application adds; everything the shipped shell already contains (`<notices>`,
`drawer-open-slot-name`, the slots `appbar-leading` / `appbar-content`, `dev-menu.view.xml` /
`user-menu.view.xml` in `<trailing>`, separator and administration entry, `variant`) is removed:

- Declare the namespace `xmlns:config="http://www.top-logic.com/ns/config/6.0"` on the `<view>`
  element.
- Own channels stay in `<channels>`.
- Under `<app-shell><content><sidebar>`: `active-item`, the own entries and, if needed, `<header>`,
  `<header-collapsed>`, `<footer>`, `<footer-collapsed>`, each with `config:override="true"`
  (otherwise they are added to the neutral texts of the shell).
- Entries that should stand before the system area get
  `config:position="before" config:reference="system-separator"`; entries without position are
  appended after "Administration".
- Under `<app-shell><header><app-bar>`: the own `<title>`.

```xml
<view xmlns:config="http://www.top-logic.com/ns/config/6.0">
	<app-shell>
		<content>
			<sidebar active-item="home">
				<header config:override="true">
					<text><label><en>My App</en></label></text>
				</header>
				<items>
					<nav-item id="home" config:position="before" config:reference="system-separator">
						<view-ref view="home.view.xml"/>
						<label><en>Home</en></label>
					</nav-item>
				</items>
			</sidebar>
		</content>
		<header>
			<app-bar>
				<title><en>My App</en></title>
			</app-bar>
		</header>
	</app-shell>
</view>
```

**Variant 2: keep a complete own shell.** Declare
`xmlns:config="http://www.top-logic.com/ns/config/6.0"` on the `<view>` element and mark the shell
as replacement: `<app-shell config:override="true">`. The own copy then replaces the shipped shell
completely; later extensions of the shipped shell do not reach the application.

In addition:
- Every area of `<app-shell>` (`header`, `notices`, `content`, `footer`) may contain each element
  kind at most once; two elements of the same kind in one area (e.g. two `<text>` in `<content>`)
  are rejected on load and must be put into a container (e.g. `<stack>`).
- The developer commands (`<open-designer>`, script recorder, UI inspector, agent access) no longer
  belong into the `<commands>` of the own app bar; they come through `dev-menu.view.xml`.

Detect: `find . -path '*/WEB-INF/views/app.view.xml' -not -path '*/target/*'`;
for each hit `grep -n -e '<notices' -e 'user-menu.view.xml' -e 'dev-menu.view.xml' -e '<open-designer' -e 'inspect' -e 'recorder' -e 'agent' -e 'config:override' <file>`.
After the change, open the application and check that app bar, sidebar and notices appear once.

### 4.2 Workaround for composition columns no longer needed (#29693) — optional
Large and multi-valued values (compositions, multi-line text, HTML, TL-Script, …) in table cells
are now shown as a one-line preview with a button opening the full editor in a dialog. An
application carrying a workaround for composition columns — an own `ColumnProviderService` for
compositions, typically configured in
`WEB-INF/autoconf/com.top_logic.layout.view.table.ColumnProviderService.config.xml` — can remove
it. Only if the user agrees.

Detect: `grep -rln -e 'ColumnProviderService' --include=*.xml --include=*.java .`

### 4.3 Customer component library adapters: disabled fields (#29617) — mandatory for own adapters
Attributes whose dynamic visibility computes `disabled` are now shown as inactive inputs in edit
mode (before: as read-only text). Form field controls send the state key `disabled`
(`FieldState.disabled`). An adapter of a customer component library (own React module replacing TL
components) should map `editable: false` with `disabled: true` to the library's disabled
presentation, and `editable: false` alone to its read-only one (developer article
`customer-component-library`).

Detect: `grep -rn -e 'registerRootWrapper' -e 'replace(' -e 'installMui' -e 'useTLState' --include=*.ts --include=*.tsx src`
(no own React module → skip); in the adapters of field components look for the handling of `editable`.

---

## 6. Stylesheets

### 6.1 CSS cascade layers of the React UI (#29661) — review
The stylesheets of the React UI are ordered by CSS cascade layers (engine `tl` < component library
`mui` < application), independent of their position in `<head>`.

- Application stylesheets registered via `ClientResources` lie in no layer and therefore win
  against all engine styles (layer `tl`), regardless of specificity. An application rule that so
  far lost against a more specific engine rule now takes effect. Global rules (resets, element
  selectors such as `button { … }`) that should **not** override the engine get an own layer before
  `tl`: add the layer to `layers` of the `ClientResources` configuration and register the stylesheet
  with `layer="…"`:

  ```xml
  <config service-class="com.top_logic.layout.react.resource.ClientResources">
  	<instance class="com.top_logic.layout.react.resource.ClientResources"
  		layers="app-reset, tl, mui"
  	>
  		<resources>
  			<stylesheet name="app-reset-css" layer="app-reset" resource="/style/app-reset.css"/>
  		</resources>
  	</instance>
  </config>
  ```
- A module that registers a stylesheet of the engine or of a bundled library specifies
  `layer="tl"` (developer article `new-react-module`).
- `!important` is inverted with layers: an `!important` in an earlier layer wins against one in a
  later layer.
- In applications with the flow-diagram module, the font size of `body` is now the browser's
  (16px) instead of 13px from the GWT standard theme.

Developer article `theme-tokens`, section "Cascade layers", describes the order.

Detect: `grep -rn -e '<stylesheet' --include=*.xml src/main/webapp/WEB-INF` — for each registered
application stylesheet, look for global/element selectors and `!important`
(`grep -n -E '^\s*(html|body|button|input|select|textarea|a|table|\*)\b|!important' <css>`).
`grep -rn 'flow' --include=pom.xml .` for the flow-diagram module. Check the styling visually after
the start.

---

## 7. Further notes (no action required)

- **Design system (#29617):** the migration section of #29617 also lists the wave-1 changes
  (button classes, `ButtonSize.LARGE`, `<color role>`, `ValueColor`, `tlPill`, `--tl` custom
  properties, `support-info`), marked "shipped with 8.0.0-alpha9"; they are covered by the
  alpha8→alpha9 guide. Only the wave-2 items ("shipped with 8.0.0-alpha10": steps 1.2
  `ModeSelector`, 4.3) apply to this release. A
  destructive command (`<delete-object/>`, clique `delete`) is now drawn in the `danger` tone as
  toolbar button, menu entry and confirmation button. Form fields, menus, popovers, toolbars and
  tabs of the React UI are rendered by the design system (`tl-field`, `tl-menu`, `tl-toolbar`,
  `tl-tabs`, …).
- **Scheduler behavior (#29696):** engine tasks that ran on every node and now run once in the
  cluster (`CheckUnusedAccountsTask`, `CompactHistoryTask`, the data import tasks,
  `EnterMaintenanceWindowTask`) appear in the scheduler administration as persistent with cluster
  lock and result protocol. A cluster-wide task with `<on-startup/>` now runs on every node start
  (so far only on the first start after installation). A stale cluster lock of an earlier start of
  the same node is released at startup.
- **Anonymous account (#29740):** editing, removing the account, resetting MFA and resetting the
  personal configuration are disabled for the anonymous account in every view (also the GOTO
  dialog); deleting it is vetoed in the database (`Person#tDeleteVeto()`). In the React UI every
  `<model-access>` check also consults the `CommandApprovalService`; the new rule
  `<delete-veto-disabled/>` (implicit in `<delete-object/>`) disables a command whose input vetoes
  its deletion. The React account administration refuses deleting the own account and
  administrators.
- **Value options (#29741):** `tl.accounts:Person` and `Contacts:PersonContact` offer the anonymous
  account no longer in selection fields (TL-Script `accountIsAnonymous()`); `tl.accounts:GroupMember`
  offers no personal representative groups. Options configured at a React selection control take
  precedence over the options of the type.
- **Model access rights in React forms and tables (#29692):** fields and columns the user may not
  read are hidden (column cells empty), fields the user may not write are read-only, editing a form
  is offered only with write right on the object, and a create dialog opens only with the create
  right. An attribute grant naming no role denies the operation everywhere.
- **Create right on specializations (#29758):** the create right for a composition is now checked on
  the type actually created (`B extends A`), not on the target type `A` of the composition
  attribute: a revoke of Create on `B` now takes effect, and a Create grant given only on `B` is now
  found. TL-Script `canCreate($parent, $reference, $type)` takes the type as optional third argument.
- **Deleted accounts (#29700):** deleting an account ends its open sessions.
- **`<persist-transient>` (#29731):** keeps creation defaults computed in the transaction (sequence
  numbers, `in-transaction` defaults); TL-Script `copy(transient: false, skipTransactionDefaults: true)`
  does the same.
- **Toolbar cliques (#29738):** clique labels are translated; cliques are configured in the new
  service `CommandCliqueService` (an application may add or relabel cliques).
- **Commit messages (#29513, #29759):** drops, TL-Script actions, transactions and deletions of views
  write meaningful default commit messages and can configure their own.
- **Boolean fields (#29654):** the presentations `radio` / `select` are rendered by the selection
  control (radio group, three-valued fields with "no value").
- **LDAP (#29747):** every `%LDAP_*%` alias of `ldapConf.xml` reads `${env:ldap_<name>:<previous value>}`;
  an application alias file that only maps the aliases to environment variables can be dropped.
- **PostgreSQL (#29773):** the engine data source sets the driver option `cleanupSavepoints`
  (variable `%POSTGRESQL_CLEANUP_SAVEPOINTS%`, environment `postgresql_cleanup_savepoints`, default
  `true`); large SQL migrations no longer slow down quadratically. An application with an own
  PostgreSQL data-source configuration does not get the option automatically.
- **WYSIWYG editor (#29726):** switched to Tiptap 3 (security fix).
- **Developer docs (#29765):** the engine FAQ is shipped as developer articles in the jars
  (`read_doc`), e.g. `customer-component-library`, `new-react-module`, `theme-tokens`,
  `mui-customer-theme`.
- **New features:** `<accordion>` (#29651), `<alert>` (#29652), radio group selection for any number
  of options (#29654), kanban board (#29730), Material UI adapter module `tl-layout-react-mui`
  (#29661), naming the account in the user menu (#29735), developer menu in the app bar (#29744),
  script access parent and coverage tree view (#29760).
- **Fixes without action:** history query honors start/stop revision (#29697), `htmlText` keeps the
  images of stored structured text (#29699), `ListStorage` insertion performance (#29711), model
  access read checks without per-object query compilation (#29716), OpenAPI client response without
  body (#29753), OpenAPI server API-key authentication (#29774).

---

## 8. Verification checklist

1. `mvn clean install` of the application (with tests if possible).
2. Before starting against a copy of the production database: remove the scheduler options of
   step 2.1 from the installation's `autoconf` directory (and the attributes of step 3.1 from a saved
   `SecurityConfigurationService` configuration, the parameters of step 2.3 from a saved OpenAPI
   server configuration).
3. Start the application. Read the startup and migration log: no configuration errors
   (`run-on-startup`, `dont-run-tasks-on-startup`, `startup-sleep`, `access-parent=` /
   `access-reference=`, OpenAPI parameter without variable name, duplicate element kinds in
   `<app-shell>`); the migration `Ticket_29741_hide_anonymous_in_options` ran.
4. Log in as administrator and as a regular user; open every view (classic and React) and every
   dialog. Check that the app bar, sidebar and notices appear exactly once (step 4.1), that the
   in-app drops work for the intended roles (step 3.2), that the anonymous account is not offered in
   person and group selections and that the group/representative options still match the
   application's needs (step 2.4).
5. Check the scheduler administration: tasks run as decided in step 1.2 / 2.1.
6. Check the styling of React views — form fields, menus, toolbars, tabs, and application rules
   that may now win against the engine (step 6.1).
7. Run the scripted tests.
8. Report to the user every step that was skipped, needed a decision, or touches data (value
   options of step 2.4, node-local decisions of step 1.2, drop rights of step 3.2, the `autoconf`
   directory of steps 2.1 / 2.3 / 3.1).
