Quality Gate Entry Template

Use this schema for rows in quality-gates.md.

Gate Row

Detailed Gate

### [Gate Name]

Status: `[required | conditional | manual | paid | deferred | not-applicable]`

Command or proof:

```bash
[exact command]
```

Environment: `[working directory, tool versions, device, account state]`

Expected evidence: `[what success proves]`

Failure handling: `[what to inspect first and when to stop]`

Release claim allowed: `[runs locally | tests passed | build artifact produced | package produced | signed artifact verified | release dry-run passed | released]`

Status Guidance

• Use required for gates without which the pack is unsafe to use.
• Use conditional when the gate depends on a feature, device, or target.
• Use manual when credentials, accounts, human review, or policy forms are required.
• Use paid when the gate consumes paid API, store, device-farm, or LLM-eval resources.
• Use deferred only with a follow-up note.
• Use not-applicable only with a reason.