{#- Developer laptops: the employee baseline ssh config, with the PKCS#11
    provider swapped for Yubico's.

    NOTE this file is rendered as a Jinja template even without a .j2 suffix:
    set_block_from_template.yml resolves it through lookup('template', ...),
    which is why the include below works and why a stray {{ or {% in an ssh
    option would be an error rather than a literal.
-#}
# ssh takes the FIRST value it obtains for a keyword, so this block has to come
# BEFORE the employee baseline below, whose `Host *` sets
# PKCS11Provider /usr/lib/ssh-keychain.dylib. That line is then inert — verified
# with `ssh -G -F <config> <host>`, which reports whichever provider appears
# first. Appending this block after the include would parse cleanly and change
# nothing.
#
# libykcs11 (brew yubico-piv-tool) only talks to YubiKeys. Apple's
# ssh-keychain.dylib enumerates every smart card in every reader and every slot
# on each, so on a Mac holding a second PIV card ssh offers keys from all of
# them — and with MaxAuthTries at 6 the server can refuse before the right key
# is reached.
#
# Unlike the agent, ssh itself has no allowed_providers restriction — that check
# belongs to ssh-agent and applies to `ssh-add -s` only (man ssh-agent). So the
# Homebrew path works here directly and needs no symlink into /usr/local/lib,
# which is what pivssh has to ask for.
Host *
    PKCS11Provider {{ homebrew_path }}/lib/libykcs11.dylib

{{ lookup("template", "templates/employee_ssh_config") }}

# --- developer extras (node_type: developer) ---------------------------------
{#- Deliberately empty; see developer.zprofile.j2. Host blocks added here land
    inside the "PJ baseline ssh config" marker, so they are managed — a
    developer's own entries still belong in ssh_config_user, which is written
    into its own USER marker afterwards. -#}
