Acting on a callidescope failure

Callidescope fails for a handful of distinct reasons, and reading which one occurred is most of the work. Separate them first:

The run said	It is
`🚨 [DEPTH n > limit]`	A finding about the code. Fix the layering
A breadth row over the limit	A finding. Split the callable
`A configured destination is stale`	Drift. Re-run `--write`
`## Read nothing of its own (0 files)`	A gate judged a project whose own files it never read. Its verdict means nothing
`🔭 Rejected a project it could not read`	A `tsconfig.json` is missing or did not parse. The trace stopped there
`🔭 Traced nothing`	The run saw no code at all. Nothing below it means anything
`🔭 Rejected the command line`	A mistake in the flags. Nothing was traced
`🔭 Rejected a project configuration`	One project's own `callidescope.config.ts` was refused. Nothing was reported
`🔭 Rejected the configuration`	The run cannot do what was asked. Nothing was reported

callidescope-triage