git:20260605.7a68307 to git:20260606.69d107a
2 added, 43 removed. Audit A to A.
# ConnectWise PSA Printed CLI Agent Guide
This directory is a generated `connectwise-manage-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
connectwise-manage-cli doctor --json
connectwise-manage-cli agent-context --pretty
```
Use runtime discovery instead of relying on a copied command list:
```bash
connectwise-manage-cli which "<capability>" --json
connectwise-manage-cli <command> --help
```
Add `--agent` to command invocations for JSON, compact output, non-interactive defaults, no color, and confirmation-safe scripting:
```bash
connectwise-manage-cli <command> --agent
```
Before running an unfamiliar command that may mutate remote state, inspect its help and prefer a dry run:
```bash
connectwise-manage-cli <command> --help
connectwise-manage-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.
## Local Customizations
- If you modify this CLI beyond what the generator produced, record each customization in a `.printing-press-patches.json` at this CLI's root (parallel to `.printing-press.json`) so the change isn't lost on the next regen and is visible to the next reader.
-
- Minimum shape:
-
- ```json
- {
- "schema_version": 1,
- "applied_at": "YYYY-MM-DD",
- "base_run_id": "<copy from .printing-press.json>",
- "base_printing_press_version": "<copy from .printing-press.json>",
- "patches": [
- {
- "id": "short-identifier",
- "summary": "What changed (one sentence).",
- "reason": "Why this customization was needed (one or two sentences).",
- "files": ["internal/cli/foo.go"],
- "validated_outcome": "Optional: non-obvious test result that confirms the fix."
- }
- ]
- }
- ```
-
- Use `deferred_to_upstream` when a local patch is a temporary bridge for a missing public API endpoint, an unofficial-host workaround, a live response-shape drift, or behavior the Printing Press should eventually generate correctly. Search `mvanhorn/cli-printing-press` issues first; reuse a matching issue or open one, then set `upstream_issue` so the next regen knows what must supersede the patch:
-
- ```json
- {
- "id": "temporary-bridge",
- "summary": "What changed (one sentence).",
- "reason": "Why this customization was needed (one or two sentences).",
- "files": ["internal/cli/foo.go"],
- "validated_outcome": "Optional: non-obvious test result that confirms the fix.",
- "deferred_to_upstream": [
- {
- "feature": "Generator behavior or upstream API capability that should eventually supersede this patch",
- "reason": "Why the local patch is temporary or API-specific"
- }
- ],
- "upstream_issue": "https://github.com/mvanhorn/cli-printing-press/issues/<n>"
- }
- ```
-
- This file is an **index of customizations**, not a second copy of the diff. Diffs live in `git`; the manifest is what tells the next agent (or regeneration tooling) what was customized and why. Keep `summary` and `reason` short -- if you find yourself writing tables of field renames or code transformations, that detail belongs in the commit message, not here.
+ 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.
- Inline `// PATCH:` source comments are optional. If you find them helpful as a navigation aid (`grep -rn 'PATCH' .` surfaces customized sites), feel free to add them -- but they aren't required and aren't enforced by any CI.
+ 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.