fw-wave-loop

Orchestrates automated wave-based DFM-to-web form migration with gated acceptance and overnight loops.

Updated May 28, 2026
One-click install
npx skills add https://github.com/HPI-Jimmy-Chiu/HT904_V899 --skill fw-wave-loop-hpi-jimmy-chiu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fw-wave-loop
Source: https://github.com/HPI-Jimmy-Chiu/HT904_V899/tree/main/.agents/skills/fw-wave-loop
Command: npx skills add https://github.com/HPI-Jimmy-Chiu/HT904_V899 --skill fw-wave-loop-hpi-jimmy-chiu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Migrating legacy Delphi .dfm forms to web-rendered layouts is a long, multi-wave campaign that risks unsafe write-path changes, flaky acceptance gates, and lost progress when sessions or quotas are interrupted. This Skill encodes the wave policy, safety boundaries, and resumption protocol so the migration proceeds autonomously and verifiably. ## Core Features & Use Cases - Wave-based migration policy: Defines target selection rules, three-part deliverables (logic translation, tag export, web rendering), and per-wave acceptance gates for the DFM→WEB campaign. - Acceptance gate discipline: Prescribes the serial dualgate.sh flow, environment pre-measurement with dfm2rc_idempotent/dfm2rc_fidelity baselines, and verdict-based pass/fail judgment instead of unreliable exit codes. - Overnight loop and quota recovery: Commits each wave with DEVLOG and RESUME markers, uses scheduled wakeups plus cron heartbeats, and supports cold-start resumption after session loss. - Use Case: When running /fw-wave to plan the next form-to-web wave, the Skill decides whether a form is safe for unattended overnight work, which gate to run, and how to resume after a quota interruption. ## Quick Start Run /fw-wave to load this policy and start the next DFM-to-web migration wave according to the campaign plan queue.

Frequently Asked Questions about fw-wave-loop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run an automated DFM-to-web form migration wave?▼

Invoke /fw-wave to load the wave policy, then follow the campaign plan queue order: infrastructure, tag wiring, generator, then form waves. Each wave ends with commit, DEVLOG, and a RESUME marker before immediately starting the next wave.

How do I decide if a form is safe for unattended overnight migration?▼

A form qualifies only if it can be completed read-only; the write path (command channel) is a hard safety boundary and is never done at night. Events handlers are never wired, and any wave hitting a write requirement is queued for a different target.

Why does the acceptance gate report false failures and how do I avoid them?▼

False reds came from dualgate2.sh stacking Debug ctest on a Release build, pushing dfm2rc_fidelity past its 600s timeout; it was retired in favor of the serial dualgate.sh. Also never modify build inputs while a gate runs, since mixed objects invalidate the measurement.

How do I check the environment before starting an acceptance gate?▼

Run dfm2rc_idempotent standalone first; at or under 40 seconds means start the gate directly. Above 40 seconds is inconclusive, so measure dfm2rc_fidelity itself and proceed only if it finishes under 550 seconds.

What happens to migration progress when the session or quota is interrupted?▼

All state lives on disk as commits plus RESUME markers, so a cron heartbeat resumes after quota interruptions if the session survives. If the session dies, restarting with /loop /fw-wave cold-starts and continues without loss.