v0.1.0 release → v0.1.0 release

Choose another pair · Download JSON report · Download Markdown migration report

Before

328076217d2728ee7dc2aea01c2f71452dbfc9c5 · version 0.1.0 · proposed

After

328076217d2728ee7dc2aea01c2f71452dbfc9c5 · version 0.1.0 · proposed

Evidence formats

Contract 1 → 1; execution schema unavailable → unavailable; shared renderer 1.

Semantic comparison

compared; 0 recorded changes.

Visual execution

Not run by this report. Recorded browser evidence has its own scope and digests.

Historical availability

• Before: No historical usage index; impact uses the recorded component and port mappings. Prose and composite alias dependencies may be unknown.
• After: No historical usage index; impact uses the recorded component and port mappings. Prose and composite alias dependencies may be unknown.

Semantic changes

No semantic changes detected in supported inputs.

Known downstream impact

Port catalogue: no registered ports. Unknown: consumers without registered mappings cannot be enumerated. Known affected means a recorded contract or dependency changed; it does not establish a regression in an application.

Matched visual references

640 × 480 CSS pixels · comfortable · LTR · static endpoints · historical JavaScript disabled. Both frames use the same browser and available local fonts. A change to requested typography or fixture bytes can change appearance independently of color. No actual keyboard, screen-reader or historical-runtime pass is implied.

Requested font before: "SauceCodePro NFM", "Source Code Pro", "Cascadia Mono", "Consolas", "Liberation Mono", "DejaVu Sans Mono", monospace; after: "SauceCodePro NFM", "Source Code Pro", "Cascadia Mono", "Consolas", "Liberation Mono", "DejaVu Sans Mono", monospace.

Expected migration verification

• Review changed roles and their explicit dependencies.
• Recheck applicable component states, focus, selection and contrast in each actual consumer.
• Run matched browser captures and inspect differences; record browser, fonts, viewport and input digests.
• Resolve unsupported historical inputs and unmapped consumers before claiming migration coverage.

Limits

• Historical JavaScript and historical build tools are never executed.
• Only explicit revision-bound migration mappings establish renames.
• Missing eligibility or evidence fields remain unknown; current rules are never backfilled.
• Known affected means a recorded contract/dependency changed, not that a downstream application regressed.
• No native-port verification or automatic consumer upgrade is performed.