step9-phase4-stabilization

Supervise Step9 Phase 4 runs and verify Stage9-vs-artifact parity via curl comparisons.

Updated May 15, 2026
One-click install
npx skills add https://github.com/Pear-Commerce/pear-ai-skills --skill step9-phase4-stabilization
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: step9-phase4-stabilization
Source: https://github.com/Pear-Commerce/pear-ai-skills/tree/main/skills/step9-phase4-stabilization
Command: npx skills add https://github.com/Pear-Commerce/pear-ai-skills --skill step9-phase4-stabilization

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual overhead of supervising Step9 Phase 4 stabilization runs, verifying retailer artifact parity, and tracking flaky long-running processes, while preventing common launch and provenance errors that derail retail integration workflows.

Core Features & Use Cases

  • Run Supervision: Monitor active Step9 Phase 4 runs, identify orphaned or stuck processes, and manage the 4-active-retailer run cap.
  • Parity Verification: Enforce Stage9-vs-artifact curl comparison rules and guardrails to ensure generated retailer artifacts match live run behavior.
  • Tracker Management: Update the Step9 Phase 4 tracker with fresh evidence, handle transport-only failures, and coordinate fixer/watchdog subagent loops.
  • Use Case: For teams running retail integration stabilization cycles, this Skill automates run oversight, reduces manual parity check errors, and ensures compliant wave closure for all non-skipped retailers.

Quick Start

Use the step9-phase4-stabilization skill to supervise your active Step9 Phase 4 run, update the tracker with fresh parity evidence, and enforce all required Phase 4 guardrails.

Frequently Asked Questions about step9-phase4-stabilization

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

FAQPage Schema
How do I verify retailer artifact parity during Step9 Phase 4 stabilization runs?

Retailer artifact parity verification during Step9 Phase 4 stabilization runs is enforced by applying Stage9-vs-artifact curl comparison rules to ensure generated retailer artifacts match live run behavior.

What is the active run cap for Step9 Phase 4 retail integration workflows?

The active run cap for Step9 Phase 4 retail integration workflows is limited to 4 active retailers, managed automatically to prevent process congestion and identify orphaned or stuck runs.

How do I handle transport-only failures in Step9 tracker updates?

Transport-only failures in Step9 tracker updates are handled by logging the specific failure type, updating the tracker with fresh parity evidence, and coordinating fixer and watchdog subagent loops.

Why does Step9 Phase 4 require raw curl comparison evidence for retailer DONE claims?

Raw curl comparison evidence for retailer DONE claims is required during Step9 Phase 4 to enforce provenance guardrails, ensuring that claimed completion states match actual live run behavior.

Can I automate supervision of flaky long-running Step9 processes?

Supervision of flaky long-running Step9 processes can be automated to eliminate manual oversight, monitor active runs, and ensure compliant wave closure for all non-skipped retailers.

What are the limitations of manual Step9 Phase 4 run supervision?

Manual Step9 Phase 4 run supervision introduces overhead for verifying retailer artifact parity, tracking flaky processes, and is prone to common launch and provenance errors that derail retail integration workflows.