Import the token the adapter named.
CLI, API and native token imports use the same explicit selection decision without guessing from a command suggestion.
Read the actual entry state#
skarbiec tool status <tool> and POST /v1/operator/tool/status expose the tool's actual entries without token values. Each entry carries its name, how it is kept, and the required Boolean requires_select. A plain-text entry also has move_with, a human-readable import instruction; that text is not a machine selection contract.
When requires_select is true, pass that exact entry name through --select or the API select field. When it is false, omit the selector. The adapter declares whether it keeps one token, one token per named entry, or an active token alongside named stored tokens; consumers do not classify tools by their names or infer state from a missing field.
The native import screen#
Items → Move developer tool tokens here → Developer tools reads the same status operation. Its import request takes the selector decision directly from requires_select. An active-token row therefore does not accidentally choose a named token, and choosing a named row cannot silently fall back to the active token.
The item identifier and bindings path remain explicit inputs. Import stores the selected token, reads the saved item back, writes the environment binding, and only then removes the corresponding plain-text token from the tool's file. Other entries remain unchanged. No token value is returned to the screen.
Refusals identify the missing declaration#
For an adapter that supports both active and named entries, absent or non-Boolean adapter selection state fails status with the actual tool and entry. It is not treated as a request to select a named entry. A failed tool in the all-tools status result retains its own error without hiding the other tools.
The native client requires requires_select in each entry. An older or malformed backend response produces the actual status-decoding failure instead of a successful import with an invented selector. Unknown tools, unknown entries, a selector on a single-token adapter, missing required selectors and conflicting bindings retain the product's ordinary import refusals.
Qualification boundary#
The maintained tests/huggingface/hf_credential.sh journey in Skarbiec uses the actual product binary and isolated vault and tool files. It follows the status decision through active and named imports, inspects the exact saved vault value and remaining entries, and checks that refused operations preserve the source files and vault. Reports retain source and artifact digests and actual exit statuses.
That local migration flow does not prove a Hugging Face sign-in or graphical behavior. Authenticated consumer execution and the native screen still need their own real qualification; source changes, an import suggestion or a nonempty stored field are not those results.