f87c915bf8
a named profile cloned from a default profile that signed in with oauth got a host block with enabled: true and nothing to authenticate with. hosts.hermes holds the grant, its apiKey is not inherited (#66125), and copying the oauth block would make two blocks replay one single-use refresh token. 'hermes honcho enable' on a fresh profile wrote the same shape. status then showed the profile as enabled while every honcho call ran without memory and the plugin quietly stayed inactive. clone_honcho_for_profile and cmd_enable now resolve a credential for the target block (its own apiKey, the root apiKey, HONCHO_API_KEY, or a base url) before writing enabled: true. _resolve_api_key takes the block to check so both share one definition of "can authenticate". cohorts: clone from an oauth default block, no root key: block written without enabled; the client's auto-enable rule turns it on once a credential appears (setup apikey writes the root key, or a per-profile login) clone from a default block with a host-level static key only: same clone with a root apiKey, an env key, or a base url: enabled as before enable on an empty or fresh block with no credential: refused, one message names the profile's setup command and the hosts.<name> key, nothing is written legacy blocks already on disk as enabled with no credential: nothing rewrites them; the plugin already treats them as unusable and stays inactive; enable now prints the same message instead of "already enabled" env-only key: counted as a credential at write time, as the client does at run time; if the variable later disappears the client still refuses to initialize the block