etaf/docs/migration-0.2.en.md

Migrating to ETAF 0.2

ETAF 0.2.1 requires Ebox 3.0.0 and TP 2.0.0. Install TP, then Ebox, then ETAF. The renderer bootstrap now requires Ebox framework SPI v2 and fails closed when the provider is absent, malformed, or incompatible.

Remove any configuration of etaf-render-port-selection-policy. The v1 render port and its manual initial-publication cleanup path have been retired. Runtime mounts and updates always use the immutable SPI v2 port, including its paired framework stage and rollback, same-object report, observation replay, revision, and Host final-marker contracts.

During an ordered source upgrade, ETAF accepts Ebox providers that report either tp-transaction-protocol-v1+v2 or tp-transaction-protocol-v2. The former is a temporary capability declaration that still contains the required v2 protocol; ETAF never invokes a v1 transaction operation.