Phase F of a WinForms-to-Avalonia migration: evolve the Avalonia trunk after cutover without reintroducing WinForms coupling or bypassing established layers. Use only when an explicit migration has an active Avalonia trunk and a concrete product backlog, or when the orchestrator routes here. Select work from repository evidence; do not assume particular entry points, integrations, settings, or extension mechanisms exist.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Improve the Avalonia line without reintroducing WinForms coupling. First ship (A–E) is not the end.
Read evolution tracks to classify a discovered backlog item; do not implement tracks that are absent from the product.
Restore a deferred behavior in its owning layer with contract and regression evidence. Do not place application rules solely in a ViewModel because that is the easiest entry point.
Replace an adapter only after documenting semantics, failure modes, supported environments, resource ownership, and cutover behavior. A fallback is a product decision, not a default.
legacy stores -> typed versioned state, when the product persists state
validated migrators; reject unsupported future versions
preserve predecessor and last known-good data
coordinated atomic updates
Define edit/apply/cancel behavior from the product contract. Do not create a new persistence stack for each UI surface.
When the product supports user-extensible or dynamically evaluated behavior, define capabilities, resource budgets, trust boundaries, lifecycle, and diagnostics before implementation.
Make supported actions discoverable, define intentional empty/disabled states, and turn required hidden gestures into accessible command surfaces.
When the user says not to confirm mid-flight, apply autonomously and report at the end.
Structure/security debt → wfa-harden-decompose
Legacy delete → wfa-parity-verify
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
The English summary is being prepared. Showing the original description.
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
The English summary is being prepared. Showing the original description.
Archive multiple completed changes at once. Use when archiving several parallel changes.
The English summary is being prepared. Showing the original description.
Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.
The English summary is being prepared. Showing the original description.
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
The English summary is being prepared. Showing the original description.
Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.
The English summary is being prepared. Showing the original description.