Coming from the 1.1 comparison guides
Translate old terminology into the current UXP workflow without assuming feature parity.
The four-layer idea remains useful. The product-specific workflow has changed. This table labels the historical terminology so it is not mistaken for current controls.
Translate the old vocabulary
| Historical 1.1 wording | Current 2.0.5 source review workflow |
|---|---|
| Loader + Engine; two inspection tracks | UXP panel; White Space, Styles and Typography share the findings workflow. |
| Style Heatmap / legacy diagnostic views | Distinguish Style Map identity, Style Frequency Heatmap and Override Map. |
| Fix Plan / Safe Clean | Review the selected finding and its offered current action. No universal text-cleanup command is implied. |
| Old Review Queue | Queue for review retains supported solver proposals, one per story; no batch Apply. |
| Typography CSV / Override CSV / Fix TXT | Current document diagnostic JSON and separate Publication JSON. |
| AUTO plus 34 legacy locale choices | Automatic paragraph resolution plus 44 current explicit registry choices, including neutral. |
| 43 legacy issue identifiers | 26 current Typography rule IDs; White Space and Styles have their own evidence. |
| Legacy Live/incremental workflow | Use Inspect / Update inspection and read actual freshness; do not infer automatic reruns. |
Keep what still helps
Keep the task-first decision, representative test scope, deliberate exceptions, responsible owners and independent final proof. Replace the old control names and export assumptions with the current references.
This documentation collection is labelled 2.0.0 and describes 2.0.5 source review. Declared loading requirements and recorded platform acceptance are explained in Compatibility & Known Limits. This comparison does not announce a final release, transfer old settings automatically or claim fresh native-host acceptance.
Use the separate Migration Guide for transition planning. The preserved Avellio 1.1 library remains the reference for the older installed workflow.
Typography recommendations explain findings and sometimes propose replacement text. Found / Suggested are read-only evidence, not Apply commands. Verify meaning and locale before manual edits; rescan afterwards.
Sources and current boundaries
Avellio guidance describes build 2.0.5 source review within the 2.0.0 documentation collection. Read the current delivery boundaries and compatibility evidence. This comparison does not claim fresh native-host acceptance.