$ paw-kit history --help
exit code: 0
--- stdout ---

 Usage: paw-kit history [OPTIONS] {adapter_path}

 Print the append-only compile lineage log for an adapter.

 Every `compile()` call (on any `AbstractPAWBackend` shipped by paw-kit) appends
 one line to `<adapter>.history.jsonl`. A manifest itself only ever points at its
 immediate parent (an overwritten file cannot be read back), so this sidecar is the
 only place the full compile lineage of a repeatedly-recompiled adapter survives.

 D-4: each line is the manifest's **lineage fields** -- ids, hashes, counts,
 visibility provenance, parent pointers, timings -- and not, as this docstring used
 to say, "the manifest minus its spec text". That described a one-key deny-list the
 mock backend's traced `examples` walked straight past; it is an allow-list now (see
 `paw_kit.backend.manifest_lineage._HISTORY_ALLOWED_FIELDS`). The sidecar is also
 capped and rotated (`manifest_lineage._HISTORY_ROTATIONS`, currently 1): a
 long-lived adapter's oldest lines move to `<adapter>.history.jsonl.1`, read here
 too (D-ADD-2) and listed before the live file's lines, so lineage does not go
 dark the moment an adapter is recompiled enough times to fill one generation.

╭─ Arguments ──────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ *    adapter_path      <path>  Path to a compiled .paw adapter artifact [required]                                   │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
╭─ Options ────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ --help          Show this message and exit.                                                                          │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
