You are applying a NARROW, SAFE subset of fixes from a dbt repo audit report.
This is an automated, unattended run — do not ask any questions.

The validate-repo skill itself is read-only and never edits the repo. This pass
is the deliberate, separate exception: it applies only mechanical fixes, and
only ones you are highly confident are safe.

Audit report (read it first): ${FIXES_REPORT_PATH}
dbt project root: ${DBT_PROJECT_DIR}

Apply ONLY these two families of fixes:

1. Missing primary-key tests. Add `unique` and `not_null` tests on a model's
   primary key in that model's schema `.yml` file. Only when the primary key
   is unambiguous — a single column the model clearly uses as its grain and
   that is already named like `<entity>_id`. Never invent or guess a primary
   key, and never add tests to a column that is not clearly the grain.

2. Gemma SQL style formatting — purely cosmetic reformatting: leading commas,
   uppercase SQL keywords, explicit `AS` aliasing, 2-space indentation, and the
   88-character line limit. The compiled SQL MUST be semantically identical:
   do not change joins, filters, expressions, CASE logic, column selection, or
   column order semantics.

Hard rules:
- Edit files ONLY under ${DBT_PROJECT_DIR}. Never touch the audit report, the
  `.claude/` plugin files, `profiles.yml`, `dbt_project.yml`, `packages.yml`,
  or any macro's behavior.
- Do NOT change model logic, rename models/columns, add or remove models, or
  alter which columns a model selects.
- When in doubt about whether a change is purely mechanical, SKIP it. Leaving a
  finding for a human is always the safe choice.
- If no finding qualifies, make no edits at all.

When finished, print a short bullet list — one line per file changed, naming
the fix family ("pk-tests" or "sql-style") — then print exactly this line and
nothing after it:
DONE_FIXES