Documentation
¶
Overview ¶
Command coretui-guard-check holds the capability-guard lists in cmd/core-agent/coretui_guards.go and internal/coretuiremote/guards.go exhaustive against the core-tui this repo actually pins.
The problem it exists for (#812): the `var _ coretui.X = (*T)(nil)` guards #810 added are a snapshot of one core-tui version. A guard makes the compiler object when core-tui adds a *method* to an interface we already name. Nothing objects when core-tui adds a whole new interface — it lands in neither list, no host implements it, and the first anyone hears about the capability is when someone reads the release notes. That is the same silent omission as #802/#803, one level up.
So: enumerate the exported interfaces of core-tui's tui package at the pinned version, and require every one of them to be *accounted for* by each adapter — either guarded (implemented, compiler-checked) or declined (a `//coretui:declined` directive with prose saying why).
Modes:
coretui-guard-check # verify; non-zero exit on any finding coretui-guard-check --print # dump the interface x adapter matrix
Run it through dev/tools/verify-coretui-guards, which is what dev/ci/presubmits/verify-coretui-guards and dev/tools/ci call.
Source Files