---
name: lingtai-ai/preset-skill-op-availability-save-gate
source: https://app.decimal.ai/s/lingtai-ai-preset-skill-op-availability-save-gate@1/SKILL.md
source_sha256: 03de2e2586c8
---

# Availability / save gate

Evidence: `tui/internal/tui/preset_editor.go`'s `commit()`.

## Save is structural-only

`commit()` runs the preset's structural `Validate()` and, if it passes,
saves immediately. There is no live HTTP call, no pending/checking state,
and no per-tuple credential fingerprinting gate on Save — for any
provider, including Codex, Codex-pool, and API-key providers like
DeepSeek. See `reference/operations/saved-presets/SKILL.md` for what
`Validate()` checks.

## History

An earlier revision of this editor ran a real live provider/model call
on every Save and hard-blocked the save on a non-2xx response (a
"real-availability gate"). That gate false-positived broadly — every
provider, including working Codex and API-key configurations, could be
rejected by transient network/provider conditions unrelated to whether
the configuration was actually usable — and was removed (2026-07-23,
reported by Jason). It has not been replaced by another probe, whitelist, or
retry loop.

## Where live availability diagnosis actually lives

`/doctor` (`tui/internal/tui/doctor.go`'s `probeLLM`) and real runtime
execution remain the places that diagnose whether a provider/model is
actually reachable. Save does not duplicate that check.

## Operations

For structural `Validate()` and the Load/Save/Delete file contract, see
`reference/operations/saved-presets/SKILL.md`. For what happens after a
successful save — activation and `/refresh` — see
`reference/operations/activation-session-refresh/SKILL.md`.