surface-change

name	surface-change
description	Change CLI flags, API routes, or SPA surfaces without moving pipeline logic out of kit-core.

Skill: surface-change

Use when editing I/O surfaces (clap UX, HTTP routes, SPA) without changing tool transform logic.

Rules

1. Pipeline / transform / sink ownership stays in kit-core named entrypoints.
2. CLI/API changes are thin wires only — no dual pipeline bodies (REQ-003).
3. New job routes must be explicit POST /jobs/{tool_id} on the shared router and must go through session + authz + CSRF (REQ-013/017).
4. SPA: credentials: 'include', CSRF header on mutations; never store Google tokens in web storage (REQ-015).
5. Document new env names in docs/ops/env-names.md if introduced.
6. Run just check (and just web-build if SPA changed).

Forbidden

Same dual-body ban and secrets/PII rules as add-tool and secrets-pii.

Related

• New tools → use add-tool instead.
• Secrets/PII → secrets-pii.