git:20260607.17d55c2 to git:20260613.fc77200

4 added, 0 removed. Audit A to A.

# Pipedrive Printed CLI Agent Guide

This directory is a generated `pipedrive-cli` printed CLI. It was produced by [CLI Printing Press](https://github.com/mvanhorn/cli-printing-press), so treat systemic fixes as upstream Printing Press fixes first. Keep local edits narrow and document why a generated-tree patch belongs here.

## Local Operating Contract

Start by asking the generated CLI for current runtime truth:

```bash

pipedrive-cli doctor --json

pipedrive-cli agent-context --pretty

```

Use runtime discovery instead of relying on a copied command list:

```bash

pipedrive-cli which "<capability>" --json

pipedrive-cli <command> --help

```

Add `--agent` to command invocations for JSON, compact output, non-interactive defaults, no color, and confirmation-safe scripting:

```bash

pipedrive-cli <command> --agent

```

Before running an unfamiliar command that may mutate remote state, inspect its help and prefer a dry run:

```bash

pipedrive-cli <command> --help

pipedrive-cli <command> --dry-run --agent

```

Use `--yes --no-input` only after the target, arguments, and side effects are clear.

For install, auth, examples, and longer product guidance, read `README.md` and `SKILL.md`. This file intentionally stays small so repo-local agents get invariant local guidance without duplicating the generated docs.

+ ## Release Ledger

+ `CHANGELOG.md` and `.printing-press-release.json` are the public library's per-CLI release ledger. Fresh prints may carry blank skeletons, but the final `YYYY.M.N` CLI release version is assigned only after a publish PR merges in `mvanhorn/printing-press-library`. Do not hand-bump those files or edit `var version = ...` for release bookkeeping; preserve existing ledger files on reprint and let the library workflow stamp the next release.

## Local Customizations

This directory is **generated output** -- a fresh print can overwrite the whole tree, so ad-hoc hand-edits don't survive on their own. If you modify the generated code, record each change under `.printing-press-patches/` (parallel to `.printing-press.json`) so a regen carries the intent forward instead of silently dropping it.

The entry shape, and the altitude to write it at -- a durable reprint-guard, not a changelog -- live in the source catalog's `AGENTS.md`, which is the single source of truth; this guide intentionally doesn't duplicate them.