---
name: verify
description: Verify harness changes end-to-end without docker — drive the real pinned CLI against a header-capturing stub server with the exact env resolve_auth_env() produces.
title: verify
canonical_url: https://skilld.dev/gh/anthropics/defending-code-reference-harness/verify
last_updated: 2026-10-25T14:32:15.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install anthropics/defending-code-reference-harness/verify`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/verify`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/anthropics/defending-code-reference-harness/verify) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/verify`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/verify --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/verify --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Verifying harness changes on a docker-less host

The pipeline's real surface is the in-container `claude -p` process and its
outbound API requests. Without docker, drive the same pinned CLI binary
directly with the env dict the harness would inject via `docker -e`.

## Recipe

1. **Get the pinned CLI** (version from `harness/agent_image.py:CLAUDE_CODE_VERSION`):
   `npm install --no-save @anthropic-ai/claude-code@<pin>` in a temp dir →
   binary at `node_modules/@anthropic-ai/claude-code/bin/claude.exe` (the
   `.exe` name is the real native-binary entry on Linux too, filled in by the
   package's postinstall — not a Windows leftover).
2. **Stub API server**: a tiny HTTP server that appends each request's
   headers to a JSONL file and returns a 400 `invalid_request_error`
   (non-retryable, so the CLI exits fast; exit=1 is expected).
3. **Build the agent env exactly as the pipeline does**:
   `python3 -c "from harness.auth import resolve_auth_env; ..."` and dump to
   an `export`-lines file with `shlex.quote` (values contain newlines —
   NEVER pass via `env $(...)`, word-splitting mangles them; `source` the file).
4. **Emulate the container env**: `unset ANTHROPIC_CUSTOM_HEADERS` (and any
   other ambient var not in the resolved dict) before sourcing — a Claude
   Code session in this repo injects `.claude/settings.json` env into shells,
   which containers never see.
5. **Run**: `ANTHROPIC_BASE_URL=http://127.0.0.1:<port> CLAUDECODE= IS_SANDBOX=1
   timeout 30 <cli> -p hi --model claude-sonnet-4-5 --max-turns 1`, then read
   the captured JSONL.

## Gotchas

- Unit tests in `tests/test_patch.py` / `tests/test_patch_grade.py` need
  docker and fail on docker-less hosts — pre-existing, not your change.
- The docker `-e` injection leg itself can't be exercised without docker;
  it's the same mechanism that carries `ANTHROPIC_API_KEY` in production.
- For the interactive-skills surface, copy `.claude/settings.json` into a
  fresh temp dir and run the host `claude` from there (with ambient
  `ANTHROPIC_CUSTOM_HEADERS` unset so settings.json is the only source).
