\r \r

Role\r

\r This skill owns WLS process lifecycle, worker stability, reload and restart behavior, and runtime-safe process control. It protects long-running runtime behavior and avoids changes that would destabilize workers or orchestration.\r \r

When To Use\r

\r

• Use for WLS lifecycle issues, workers, dispatcher behavior, process cleanup, reload versus restart, and runtime process orchestration.\r
• Use for keywords such as WLS, worker, dispatcher, process, server:start, server:reload, server:restart, and lifecycle.\r
• Use when the bug or change is runtime-sensitive and affects long-lived execution.\r \r

Source Material\r

\r

• AI-ENTRY.md\r
• CLAUDE.md\r
• dev/ai/skills/weline-framework-runtime/SKILL.md\r
• dev/ai/skills/runtime-and-process/SKILL.md\r
• dev/ai/skills/windows-command-quoting/SKILL.md\r
• dev/ai/skills/code-generation-standards/SKILL.md\r \r

Responsibilities\r

\r

• Diagnose runtime issues through lifecycle-aware reasoning instead of one-off process killing.\r
• Choose reload or restart correctly based on the affected runtime surface.\r
• Keep process cleanup explicit and safe.\r
• Preserve worker responsiveness and avoid blocking behavior in runtime-sensitive code.\r \r

Workflow\r

\r

1. Read AI-ENTRY.md, runtime docs, and the relevant WLS skill material before touching process code.\r
2. Identify whether the problem is business-code reloadable, startup-parameter sensitive, or orchestration-specific.\r
3. Trace the affected lifecycle path through worker, dispatcher, orchestrator, or master behavior.\r
4. Implement the smallest stable runtime change in the owning process path.\r
5. Validate with a dedicated WLS test instance on port 9502+ using a unique name.\r
6. Stop the dedicated WLS test instance after validation.\r
7. Report lifecycle impact, validation steps, and cleanup confirmation.\r \r

Weline Rules\r

\r

• Do not use default WLS port 9501 for AI testing.\r
• Always start a dedicated WLS test instance on port 9502+.\r
• Always use a unique AI test instance name.\r
• Always stop the AI test instance after testing.\r
• Do not reuse test instance names.\r
• Do not leave test instances running.\r
• Do not use sleep, die, or exit inside WLS runtime-sensitive code.\r \r

Inputs Required\r

\r

• The runtime symptom, logs, and affected lifecycle stage.\r
• The owning process or runtime component.\r
• Whether the change affects reloadable code, startup parameters, or shared services.\r
• The validation instance name and port plan.\r \r

Expected Output\r

\r

• A runtime-safe change to the owning WLS process path.\r
• Evidence from a dedicated WLS test instance.\r
• Confirmation that the test instance was stopped after validation.\r \r

Validation\r

\r

• Start a unique dedicated test instance on port 9502+.\r
• Use reload for normal code-path validation and restart only when lifecycle conditions require it.\r
• Confirm worker behavior, cleanup, and stability after the change.\r
• Stop the dedicated test instance and verify no stray instance is left running.\r \r

Constraints\r

\r

• Do not validate on port 9501.\r
• Do not kill ports or processes blindly when lifecycle-aware cleanup is required.\r
• Do not introduce blocking calls into runtime-sensitive worker code.\r
• Do not leave runtime test instances behind after the session.\r \r