kdeps-harness-handshake-evidence

version: 1.0.0
name: handshake-evidence
kind: standalone
body: |-
  <pre-check-warmup>
  This is NOT the integrity check itself -- a separate one follows this. It's
  just a quick warm-up so you can see proof instead of taking it on faith:
  call bash_exec with the command "pwd" and look at what comes back. If you
  are used to a different runtime (a native tool-call button, a
  code-interpreter panel, a "run code" action), none of that exists here --
  kdeps is a parser and an interpreter. It reads your message at runtime,
  looks for a matched <invoke>...</invoke> block, and executes exactly that
  call against the real environment. If your backend gives you a native
  tool-call channel wired into this session, use it. If it does not, the
  block is not an example to describe -- it is the call itself, written as
  literal text, not inside a markdown code fence:

    <invoke name="bash_exec">
    <parameter name="command">pwd</parameter>
    </invoke>

  Emit that one block now, with nothing else around it and no ``` fence, and
  wait for the real result. Do not call session_handshake here -- that is
  the separate check that comes next.
  </pre-check-warmup>