
 Usage: root reverse [OPTIONS]

 Draft one contract per boundary relation, grounded only in the catalog, the model and dbt.

 The warehouse is the physical truth: every property and its type comes from
 `information_schema` on a local database file, and from the engine's importer (`import
 databricks`, `import sqlserver`) on another platform, whose rows are not read, so the
 findings that need them are not raised (`reverse/no-evidence`). A field the canonical model
 declares overrides the physical type, and
 an existing dbt generic test becomes a quality rule or a declared relationship. Nothing is
 invented: a relation no description reaches, or a boundary relation no document names, is left
 for the review rather than filled in. The id is derived from the relation, so a forced
 rewrite reproduces every file. Only the boundary is drafted; a relation off it owes none.

 An existing contract is a draft the review already worked on, so this leaves it alone and
 reports how many it skipped; `--force` rewrites them all.

 Every relation also yields its open questions as `finding/*` warnings, computed against the
 contract on disk (or the draft, where there is none), boundary relations first, then inputs: a
 doubt the model, the tests or the data already settles is not raised, and one nothing
 settles is, naming the relation, the column and the question that would close it.

╭─ Options ────────────────────────────────────────────────────────────────────────────────────────╮
│ --root                     <str>                                                                 │
│ --catalog                  <str>                                                                 │
│ --force      --no-force           [default: no-force]                                            │
│ --help                            Show this message and exit.                                    │
╰──────────────────────────────────────────────────────────────────────────────────────────────────╯
