refresh-subsystem

What problem does it solve?

This Skill helps developers make safe, correct changes to a fragile Kubernetes refresh/streaming subsystem by documenting the full lifecycle, registration order, permission gating, and the most common breakpoints that cause cascading failures.

Core Features & Use Cases

• End-to-end lifecycle guidance: Covers initialization sequencing, per-cluster runtime structure, and aggregate multiplexing wiring for the HTTP/API layer.
• Domain registration guardrails: Explains fixed registration ordering, the different permission-gate kinds (direct/list/listWatch), and the two-layer permission checking model (preflight vs per-domain runtime checks).
• Snapshot and stream parity requirements: Highlights how streamed row behavior must match snapshot construction via parity tests and shared domain contracts.
• Stream transport and resume semantics: Documents SSE and WebSocket stream behaviors, including resume/cold-start fallbacks and single-cluster scope restrictions.

Quick Start

Use the refresh-subsystem skill to safely update refresh, streaming, or domain code by following the required initialization order and keeping backend domain registration, shared contracts, and frontend mappings synchronized.