Summary
Release 0.5.7 improves ADE synchronization correctness (mainly ada plan), API failure handling, legacy checksum migration, and Claude project scaffolding.
Features
Semantic ordering and drift detection in ada plan
-
Preserves meaningful ordering in attributes, steps, mappings, composite keys, and source attributes.
-
Sorts only cosmetic lists for deterministic diffs and checksums.
-
Reports moved items clearly in
ada plan. -
Normalizes SQL BOM and CRLF/LF line endings during round trips.
-
Reports legacy ADE
sourceIDs on non-SOURCEentities.
Example:
~ attributes.order: moved "TRADE_ID" from position 2 to 1
Legacy metadata is reported without blocking the plan:
⚠ Entity 'staging.STG_TRADE' of type 'STAGE' has unsupported field 'source'.
Safe checksum migration
-
Introduces checksum format version 2.
-
Upgrades legacy baselines only when local and remote content match.
-
Protects untracked and gitignored local files when a baseline cannot be verified.
-
Requires reconciliation when meaningful ordering differs.
Safer ADE API retries
-
Retries transient
502,503, and504responses for read-only requests. -
Does not automatically retry mutations that may have completed server-side.
-
Improves certificate, VPN, proxy, firewall, and TLS diagnostics.
Example:
POST request was not retried because it may have completed server-side.
Claude scaffold repair
Adding Claude support to an existing project now creates all required files:
ada init --force --tool claude
This includes CLAUDE.md, .claude/settings.json, and Claude agent definitions.
Compatibility
No CLI commands were removed or renamed.
Legacy sync baselines are upgraded automatically when content matches. Divergent or unverifiable baselines require ada plan, reconciliation, or a forced pull after backing up local changes.