Promote the Xyppy plugin through separate proof gates
How repository health, durable hosting, ChatGPT metadata, in-host rendering, commerce decisions, and production operations remain independently verified instead of being collapsed into one launch claim.
Workflow steps
- 1
Verify clean source main with typecheck, tests, build, docs, MCP contract, and checkout-safety assertions
Action
- 2
Human chooses and authorizes a durable long-running HTTPS host
Decision
- 3
Deploy the MCP endpoint and self-contained widget without adding live commerce credentials
Process
- 4
Refresh the personal ChatGPT app so current tool and widget metadata are rediscovered
Action
- 5
Invoke the installed app and verify current endpoint reachability, tool discovery, and widget rendering
Decision
- 6
Capture host-specific proof separately from repository and deployment proof
Action
- 7
Human separately chooses Shopify, Stripe, or hybrid and approves image retention and operational ownership
Decision
- 8
Keep live checkout disabled until backend, assets, review, and rollback behavior are implemented and verified
State
- 9
Treat cart creation, payment, print production, and fulfillment as later independently evidenced operations
State