ci

name	ci
description	Gradient gate audit and validation workflow. Use when checking whether a docs/profile/schema change is safe to ship in this scaffold. Trigger: /ci.
argument-hint	[--audit-only|--run-only] [paths]

/ci

Gradient currently has no automated project gate. Do not invent one.

The load-bearing ship gate is ./scripts/validate.sh, plus reviewer judgment for lifecycle semantics in docs/architecture.md and docs/module-contracts.md when docs change.

What This Means Here

Run /ci to answer whether the current change respects Gradient's public-safe contract and module lifecycle. Treat missing automation as a finding, not as a reason to wave through a change.

Procedure

1. Inspect git status --short and the changed files.
2. Check public-safe boundaries from AGENTS.md and docs/private-context.md.
3. Check lifecycle consistency against:
   • docs/architecture.md
   • docs/module-contracts.md
   • docs/decision-log.md
4. For profile changes, validate against schemas/gradient.schema.json when a local validator is available.
5. For new schemas or examples, verify that the example names synthetic data and that the schema does not encode a customer-specific deployment.
6. Report unverified executable paths explicitly.

Known Gate Debt

There is no repo-local validation command yet. File or preserve a concrete debt item when a change depends on validation that cannot be run.

Output

Return a short verdict:

• PASS: all applicable checks ran or were not relevant.
• BLOCKED: a public-safe, lifecycle, schema, or verification issue remains.
• UNVERIFIED: a necessary command/schema/check does not exist yet.