retrofit validate

Validate retrofit.toml, project layout, and the oplog

Usage:
  retrofit validate [flags]

Flags:
      --allow-unmerged-fork   report an unmerged fork as an advisory and exit 0; apply-risk hazards, seal-integrity refusals and standing violations still fail the run
      --every-commit          with --history, validate every commit of the PR in the bundle, not only the candidate
      --fail-on-apply-risk    fail (exit 2) on the apply-risk hazards in the migration window since the latest Seal: validating-fk, validating-check and add-not-null on a table that may hold rows; add-unique stays advisory
  -h, --help                  help for validate
      --help-all              show extended help (vocabulary, semantics, caveats)
      --history string        check the history bundle at <dir> (written by the CI snippet; retrofit runs no git)

Global Flags:
      --as string        output mode: text | json (default "text")
  -C, --chdir string     treat <dir> as the working directory for the entire run
      --config string    retrofit.toml path (overrides discovery; also accepts $RETROFIT_CONFIG)
  -f, --file string      oplog file path; selects a registered [[schema]] path (overrides discovery)
      --no-consolidate   render every advisory occurrence instead of collapsing repeats
  -q, --quiet count      suppress the advisory tier on stderr; stack (-qq) to drop it whole (errors and results still print)
  -v, --verbose          reveal info-tier advisories on stderr

Docs: https://docs.retrofit.sh/current/commands/retrofit-validate/

Extended help:

What this verb checks:

  - retrofit.toml structure: unregistered-schema-in-directory-scope,
    directory-scope-duplicate-key, multiple-schemas-share-dir.
  - oplog placement and integrity: stray-oplog,
    oplog-missing-at-recorded-path, oplog-unreadable,
    seal-digest-mismatch, sealed-oplog-unparsable.
  - oplog syntax: a line that does not parse fails the run wherever
    it falls, under the parser's code; merge conflict markers are
    named as such.
  - forks: a fork is two or more ops sharing the same prev=, arising
    when concurrent branches each append onto the same op and a git
    merge concatenates both appends into one file. `validate` reports
    a fork as schema-fork-unmerged and, by default, fails the run
    (exit 2, code structural-gate) on an unmerged fork; pass
    --allow-unmerged-fork to report without failing. Either way,
    `validate` does not resolve a fork. Run
    `retrofit reconcile --help-all` for the block / bias / strictness
    vocabulary reconcile uses to close one.

Also prints a resolution preview: every (scope-dir, schema, source)
triple the config resolves to, so a directory-scope ambiguity is
visible before it surfaces as a load-time error elsewhere.