Reversible Lucid Upgrade and Migration

Overview

Move one Lucid contract boundary at a time with an immutable baseline, representative fixtures, canary evidence, and tested rollback.

Prerequisites

• Clean source revision, dependency lockfile, manifests, deployed artifact identity, and current production version
• Representative synthetic imports, documents, data, and connector events where applicable
• Owners for code, data, Lucid application, source system, and rollback

Tool Discipline

Use Read, Glob, and Grep for version and usage inventory, WebFetch for current official migration contracts, and Write or Edit only for approved local changes, tests, and receipts.

Current Contract

The Standard Import format evolves and may render differently over time. Extension SDK/CLI and manifest behavior are versioned through project dependencies. REST resources may require Lucid-Api-Version. These are separate migration axes and must not be changed blindly together.