crysk 0.6.0 → 0.7.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (91) hide show
  1. package/README.md +16 -1
  2. package/dist/SKILL-32cmme3j.md +143 -0
  3. package/dist/SKILL-nncgwkx7.md +553 -0
  4. package/dist/adjudicator-eckqh14e.md +78 -0
  5. package/dist/ci-admission-qn797a6c.md +128 -0
  6. package/dist/cli.js +6471 -5572
  7. package/dist/consolidate-4xw1pkg7.md +24 -0
  8. package/dist/deep-review-logic-dgr112y1.md +196 -0
  9. package/dist/deep-review-logic-fck5z4xe.md +197 -0
  10. package/dist/deep-review-logic-h1fpamfh.md +192 -0
  11. package/dist/deep-review-logic-m4vk5683.md +196 -0
  12. package/dist/deep-review-logic-z63kmgmc.md +157 -0
  13. package/dist/deep-review-parity-7x7s5d81.md +148 -0
  14. package/dist/deep-review-parity-9wxmynsc.md +115 -0
  15. package/dist/deep-review-parity-bwwe7cx6.md +152 -0
  16. package/dist/deep-review-parity-e50pw3pk.md +117 -0
  17. package/dist/deep-review-parity-ennmm9m1.md +151 -0
  18. package/dist/deep-review-parity-h7y6y2he.md +118 -0
  19. package/dist/deep-review-parity-xg6wy69c.md +151 -0
  20. package/dist/deep-review-reliability-6h3c4gmw.md +125 -0
  21. package/dist/deep-review-reliability-dcjab69x.md +122 -0
  22. package/dist/deep-review-reliability-ec7b5pbk.md +159 -0
  23. package/dist/deep-review-reliability-hvasvmt9.md +153 -0
  24. package/dist/deep-review-reliability-mjnayxmt.md +158 -0
  25. package/dist/deep-review-reliability-mm7fnayf.md +124 -0
  26. package/dist/deep-review-reliability-xk4xvc2w.md +158 -0
  27. package/dist/deep-review-resilience-0esd5qeh.md +148 -0
  28. package/dist/deep-review-resilience-envgcmpy.md +115 -0
  29. package/dist/deep-review-resilience-fgx8ythf.md +151 -0
  30. package/dist/deep-review-resilience-mq5qa6ad.md +152 -0
  31. package/dist/deep-review-resilience-pwh1gawp.md +151 -0
  32. package/dist/deep-review-resilience-s9n21dkx.md +117 -0
  33. package/dist/deep-review-resilience-vz4qskea.md +119 -0
  34. package/dist/deep-review-security-1vwjdc9q.md +205 -0
  35. package/dist/deep-review-security-x1cc1z00.md +205 -0
  36. package/dist/index.js +1056 -480
  37. package/dist/opencode-ci-jc8mf4wn.md +106 -0
  38. package/dist/review-refuter-7qffwtzz.md +77 -0
  39. package/dist/verifier-tyh8r45v.md +40 -0
  40. package/dist/verifier-xf4xj701.md +40 -0
  41. package/dist/workflow-ag62s87j.yml +163 -0
  42. package/package.json +1 -1
  43. package/prompts/consolidate.md +1 -1
  44. package/prompts/default/PROVENANCE.md +5 -0
  45. package/prompts/default/deep-review-logic.md +56 -15
  46. package/prompts/default/deep-review-parity.md +71 -39
  47. package/prompts/default/deep-review-reliability.md +64 -30
  48. package/prompts/default/deep-review-resilience.md +71 -37
  49. package/prompts/default/deep-review-security.md +205 -0
  50. package/prompts/default/review-refuter.md +1 -1
  51. package/prompts/verifier.md +40 -0
  52. package/skills/crysk-ci-setup/SKILL.md +3 -3
  53. package/skills/crysk-ci-setup/references/ci-admission.md +1 -1
  54. package/skills/crysk-ci-setup/references/opencode-ci.md +1 -1
  55. package/skills/crysk-loop/SKILL.md +2 -2
  56. package/skills/crysk-loop/adjudicator.md +10 -18
  57. package/src/asset-manifest.ts +6 -0
  58. package/src/assets.ts +37 -11
  59. package/src/ci/gates.ts +13 -26
  60. package/src/ci/platform.ts +50 -0
  61. package/src/ci/review-levels.ts +4 -4
  62. package/src/ci/trigger.ts +64 -4
  63. package/src/commands/ci-setup-questions.ts +1 -1
  64. package/src/commands/status.ts +2 -0
  65. package/src/compare/hunter-exam.ts +631 -0
  66. package/src/index.ts +1 -1
  67. package/src/model/model-name.ts +2 -1
  68. package/src/model/profiles.ts +1 -1
  69. package/src/pr/answered-findings.ts +3 -0
  70. package/src/pr/ci-admission-gate.ts +1 -0
  71. package/src/pr/discovery.ts +1 -0
  72. package/src/pr/pr-status.ts +18 -3
  73. package/src/pr/pr.ts +1 -1
  74. package/src/pr/preflight.ts +29 -3
  75. package/src/pr/publish-outcome.ts +14 -13
  76. package/src/pr/review-pr.ts +22 -2
  77. package/src/rereview/prepare.ts +13 -2
  78. package/src/rereview/verify.ts +15 -9
  79. package/src/review/boundary.ts +1 -0
  80. package/src/review/exit-code.ts +60 -0
  81. package/src/review/findings.ts +3 -3
  82. package/src/review/pipeline.ts +139 -14
  83. package/src/review/preflight.ts +25 -4
  84. package/src/review/prompt-set.ts +7 -1
  85. package/src/review/review.ts +20 -11
  86. package/src/review/route-preflight.ts +16 -0
  87. package/src/triage/adjudication.ts +35 -2
  88. package/src/ui/result.ts +1 -1
  89. package/src/updater.ts +1 -1
  90. package/src/watch/preflight.ts +34 -8
  91. package/src/watch/watch.ts +8 -4
package/README.md CHANGED
@@ -9,7 +9,9 @@ finding, and deterministic code — never a model — assigns blocking/advisory
9
9
  Its measured profile, stated up front: **high precision, narrow coverage**. What it reports is
10
10
  almost always real (13% false positives measured). Its hunters check value contracts across the diff
11
11
  (units, domain, conversions, what consumers assume), resilience (lookup and dedupe keys, retries and
12
- locks, CI guards, test isolation), local logic errors, and access-control parity with sibling code;
12
+ locks, CI guards, test isolation), local logic errors, trust boundaries (outside input reaching a
13
+ query, command, file path or server-side request; missing or misplaced permission checks; a hunter
14
+ added 2026-11-15, after that measurement), and access-control parity with sibling code;
13
15
  stale state, races and component lifecycle have no dedicated hunter since 2026-11-08. It says nothing
14
16
  about style or convention. Locally it is an **assistant, not a merge gate**: every report closes with that
15
17
  disclaimer, and nothing it prints blocks a merge. In CI its commit status is a gate by default: require the
@@ -520,6 +522,19 @@ Run artifacts land **outside** the repo, in `~/.crysk/repos/<origin>/runs/<run>/
520
522
  | `diff.raw.patch` | The unfiltered diff of the same range. Written **only** when exclusions actually dropped a file, since otherwise it would duplicate `diff.patch`. |
521
523
  | `anchor.patch` | The full PR diff (merge-base..head, after exclusions) that inline comments anchor against. On a first review it equals `diff.patch`; on an incremental re-review `diff.patch` is only the push delta, and this file still covers the whole PR, so a finding on an untouched line of the PR gets a review thread. |
522
524
 
525
+ ### Exit codes
526
+
527
+ The exit code says whether the review ran, never what it found: blocking findings still exit `0`. The verdict is the `crysk` commit status and the posted comments. The same table holds in local, `--pr` and CI mode, gate or advisory.
528
+
529
+ | Code | Meaning |
530
+ | --- | --- |
531
+ | `0` | The review is complete, with or without findings. |
532
+ | `1` | No usable review: every hunter failed, no reviewer ran, or findings that should have been posted were dropped. |
533
+ | `2` | Usage error. |
534
+ | `3` | The review is incomplete: it ran, but a step failed (a hunter, the refuter, verify, adjudicate, or the time ceiling). `findings.json` reads `run_status: "partial"`. Run it again. |
535
+
536
+ A script that merges on success should treat only `0` as a finished review.
537
+
523
538
  ## Cost and expectations
524
539
 
525
540
  - **$2–5 per review** of a typical PR-sized diff — the floor is real, because hunters read the tree,
@@ -0,0 +1,143 @@
1
+ ---
2
+ name: crysk-ci-setup
3
+ description: "Trigger: setup CI, add Crysk to CI, GitHub Actions review, CRYSK_* secrets, crysk-secrets, CRYSK_MODELS, models per role in CI, OpenCode, DeepSeek, CRYSK-INPUT-REMOVED, old OPENCODE_AUTH_JSON / CRYSK_ROUTING workflows, admission policy, configure CI workflow, retrigger, force review, skipped review, /crysk review, /crysk override, pr-hero-force, too many findings, noisy review, post_min_severity, materiality_gate. Scaffolds the one workflow, secrets, models variables, admission config, and the posting and noise settings."
4
+ license: Apache-2.0
5
+ metadata:
6
+ author: juanmaagd
7
+ version: "4.0"
8
+ ---
9
+
10
+ ## Activation Contract
11
+
12
+ Load when the user asks to:
13
+ - Add Crysk to GitHub Actions CI, scaffold `.github/workflows/crysk.yml`, or configure secrets. No local install is needed: the workflow file is the whole install.
14
+ - Configure the models per role in CI, or **OpenCode** (`CRYSK_MODELS`, `CRYSK_OPENCODE_*` secrets, DeepSeek, mixed Claude+OpenCode, fallbacks).
15
+ - Move a workflow off the removed inputs (`CRYSK-INPUT-REMOVED`: `claude-token`, `anthropic-api-key`, `opencode-auth` with the `OPENCODE_AUTH_JSON` secret, `routing` with the `CRYSK_ROUTING` variable).
16
+ - Tune CI spend / re-review / admission policy.
17
+ - Retrigger a skipped CI review (size, admission, or budget) without running the review locally.
18
+ - Reduce review noise: fewer comments (`post_min_severity`) or fewer blocking findings that are real but improbable (`materiality_gate`).
19
+
20
+ ## Hard Rules
21
+
22
+ - **Zero secret leakage:** NEVER print, `cat`, commit, or log API keys, tokens, or an OpenCode `auth.json` record. Reference `${{ secrets.* }}` names only. Inspect `auth.json` **keys and `type` only**.
23
+ - **One `CRYSK_*` secret per credential, nothing else:** `CRYSK_CLAUDE_OAUTH_TOKEN` (subscription), `CRYSK_CLAUDE_API_KEY`, `CRYSK_OPENCODE_<P>_API_KEY` per OpenCode provider, `CRYSK_OPENCODE_OPENAI_OAUTH` for an OpenAI subscription. The workflow names each one in its `crysk-secrets` block, never `toJSON(secrets)`. The old `CLAUDE_CODE_OAUTH_TOKEN`, `ANTHROPIC_API_KEY` and `OPENCODE_AUTH_JSON` secrets and the `CRYSK_ROUTING` variable are read by nothing. Models per role go in the public variable `CRYSK_MODELS` (no credentials in it), the Claude order in `CRYSK_CREDENTIALS`, the OpenCode providers in `CRYSK_OPENCODE_PROVIDERS`.
24
+ - **No install needed:** run every Crysk command as `npx -y crysk <command>` (Node is enough; the package brings its own Bun). A global `crysk` on PATH is the same command. CI itself needs no local CLI at all: the workflow runs the action. `npx -y crysk skills install` installs the Crysk, triage, and CI-setup skills into every detected coding agent, with no TTY and no MCP or launchd registration (neither is needed for the CI loop, and npx's temporary cache refuses them).
25
+ - **Deterministic scaffolding:** Run `npx -y crysk setup --ci` (or `npx -y crysk ci init`) with the interview's flags. It writes the one workflow file, `.github/workflows/crysk.yml` (a repo that already has `pr-hero.yml` keeps it: `--force` rewrites it in place, and setup refuses to add a second file beside it). Do not fabricate it from memory. Fallback: copy `assets/workflow.yml`. Never scaffold a `pr-hero-force.yml`; it is retired.
26
+ - **`fetch-depth: 0` is mandatory** on `actions/checkout@v4`.
27
+ - **Gate mode:** the `crysk` commit status is the required check (the legacy `pr-hero` status is no longer posted). The scaffold writes `mode: gate` explicitly: blocking findings, a size or spend-ceiling skip, and a crash set it red. Every review rule that skips a push (low-risk delta, once per PR, `/crysk stop`, the attempt budget used up, `manual_only`) carries the last verdict; answered blocking findings turn a carried red green, marked unverified. Under the attempt budget used up or `manual_only`, that green is held `pending` instead, so a push past the budget or under `manual_only` never turns green without a `/crysk review` or a `/crysk override`. `mode: advisory` keeps it green for a finished review. The job's exit code stays `0` on findings either way, so do not gate on the job.
28
+ - **Required permissions:** `contents: read`, `pull-requests: write`, `issues: write`, `statuses: write`, **`checks: write`**, **`actions: read`** (the admission gate lists past runs; a private repo 403s without it). Template in `assets/workflow.yml` includes all six.
29
+ - **Retrigger is a PR comment: `gh pr comment <n> --body "/crysk review"`.** GitHub Actions runs the review on the runner with `--force`. The comment must be exactly `/crysk review` (or `/crysk review --full`; `/pr-hero review` on a workflow scaffolded before the rename, see the `/crysk` vs `/pr-hero` bullet), and its author needs write access; the action refuses anyone else. Do not run `crysk review --force` locally when the review should happen in CI. `gh run rerun` on a skipped run re-evaluates the gates and does not force. In this repo a comment run checks out the PR head commit before `uses: ./`, so it runs the PR's own engine, not the default branch's.
30
+ - **`/crysk recheck` re-reviews the head and asks the CI adjudicator to rule on pending dismissals.** It is `/crysk review` plus `--adjudicate`, with the same permission check and reaction; refused on fork pull requests. See `docs/github-actions.md` ("Rechecking a dismissal").
31
+ - **`/crysk stop` stops automatic reviews on the PR.** Post it before a push that should not be reviewed: CI admission skips every later automatic review, carrying the last verdict, until a `/crysk review` or `/crysk recheck` comment. It counts only from a user with write access (checked at admission), starts no run, and never turns the gate green. See `docs/github-actions.md` ("Stopping automatic reviews").
32
+ - **`--force` never widens discovery; `--full` does.** When a prior review of the same head was hollow or wrong and re-runs report "No changes to discover", comment `/crysk review --full`. It passes `--full`, which re-discovers the whole PR range.
33
+ - **When the comment trigger takes effect:** GitHub reads a comment-triggered workflow from the **default branch** (for this repo, `main`, not `dev`), so `/crysk review` works only once the workflow file (`crysk.yml`, or `pr-hero.yml` in a repo set up before the rename) with its `issue_comment` trigger is merged there; a user repo also needs an action release that handles the comment, through the `@v0` it pins.
34
+ - **`/crysk` vs `/pr-hero`:** the commands are `/crysk review`, `/crysk recheck`, `/crysk override` and `/crysk stop`; the action still accepts `/pr-hero …` for one version. A `pr-hero.yml` scaffolded before the rename filters only `/pr-hero …`, so a `/crysk …` comment starts nothing there: re-run `npx -y crysk ci init --force` to accept both, which also moves the workflow to the `CRYSK_*` secrets.
35
+ - **Legacy scaffolds:** a `pr-hero.yml` scaffolded before the comment trigger has no `issue_comment` listener, so a comment does nothing. There, use `gh workflow run pr-hero-force.yml -f pr=<n>` (add `-f full=true` to re-discover), or re-scaffold with `npx -y crysk ci init --force`, which leaves `pr-hero-force.yml` in place.
36
+ - **Minimum action version:** this workflow listens to comments, and only an action release that ships the comment handling checks the command and the commenter's write access. An older action reviews on ANY comment starting with `/crysk review`, from anyone who can comment. Never pair this workflow with an older action; a pinned tag or sha must be at or after that release.
37
+ - **Older heads (this repo):** a comment run loads the PR head's own `action.yml`, so on a head from before the comment handling it reviews without reading the comment (no force, no `--full`); merge or rebase the PR onto a base that has it first.
38
+ - **Trust (this repo):** a comment run runs the PR head's code, including its `bun install`, with the workflow's secrets, so write access is checked twice: by the workflow's pre-checkout step (fail closed, before any head code runs) and again by the head's `action.yml`.
39
+ - **Admission config is repo-level:** Write `.crysk/config.json` on the default branch. That file **rejects** `models` and `credentials`: they are person-layer only (`$HOME/.crysk/config.json` on the runner, written from `vars.CRYSK_MODELS` and `vars.CRYSK_CREDENTIALS`).
40
+ - **`.cryskignore` is read from the base ref, not the PR branch, in CI.**
41
+ - **Models and OpenCode are DATA:** the scaffold passes `models: ${{ vars.CRYSK_MODELS }}`, `credentials: ${{ vars.CRYSK_CREDENTIALS }}` and five OpenCode slot lines driven by `vars.CRYSK_OPENCODE_PROVIDERS`. Unset `CRYSK_MODELS` = Claude CI. Never a per-provider Action input. A repository connected to the Crysk platform takes its models from the platform, which wins over the inputs.
42
+ - **OpenCode procedure:** when OpenCode or mixed backends are in scope, follow `references/opencode-ci.md` before setting GitHub DATA (roles, model names, one secret per provider, the providers variable).
43
+
44
+ ## Decision Gates
45
+
46
+ | Condition | Action |
47
+ |---|---|
48
+ | `gh auth status` succeeds | Offer `gh secret set` / `gh variable set` |
49
+ | `gh` missing/unauthenticated | Link to repo Settings → Secrets and variables → Actions (Variables tab for `CRYSK_MODELS`, `CRYSK_CREDENTIALS`, `CRYSK_OPENCODE_PROVIDERS`) |
50
+ | Credential: Claude | **`CRYSK_CLAUDE_OAUTH_TOKEN`** — subscription (`claude setup-token` only, NOT keychain). **`CRYSK_CLAUDE_API_KEY`** — pay-as-you-go. Both set: the subscription runs unless `CRYSK_CREDENTIALS` is `{"claude": ["api_key", "subscription"]}`. |
51
+ | Credential: OpenCode | Read `references/opencode-ci.md`. One `CRYSK_OPENCODE_<P>_API_KEY` per provider + `CRYSK_MODELS` + `CRYSK_OPENCODE_PROVIDERS`. Any `CRYSK_*` credential counts; with none, the run fails red with the `gh secret set` commands. |
52
+ | openai in CI | `CRYSK_OPENCODE_OPENAI_API_KEY` runs metered; `CRYSK_OPENCODE_OPENAI_OAUTH` (base64 of the `openai` record of OpenCode's `auth.json`) is the ChatGPT subscription and wins when both are set. `_OAUTH` works for openai only. |
53
+ | Workflow red with `CRYSK-INPUT-REMOVED` | It still passes `claude-token`, `anthropic-api-key`, `opencode-auth` or `routing`. `npx -y crysk ci init --force`, then set the `CRYSK_*` secrets and variables it prints. |
54
+ | Different models per step | `CRYSK_MODELS` maps roles to lists: `default`, `hunter.<key>`, `refuter`, `consolidate`, `scout`, `summary`, `judge`. Any role left on a `claude:` model needs a Claude secret; OpenCode-only = every role on OpenCode, e.g. `{"default": ["opencode:deepseek/deepseek-v4-flash"]}` (`references/opencode-ci.md`). |
55
+ | Several OpenCode providers in one run | Supported: up to 5 providers through the workflow's slots, each model on its own provider's secret, as primary or fallback. |
56
+ | OpenCode CLI pin | Action installs **1.18.30** iff the setup step wrote an OpenCode auth file OR the models in effect name `opencode:`. Never `latest`. |
57
+ | Fork PRs | Their pushes skip (no secrets). A user with write access comments `/crysk review`, and that run (base context, with secrets) reviews the fork head. Review `if` never reads `secrets`; the action checks for a `CRYSK_*` credential in `crysk-secrets` (or a login file already on the runner). |
58
+ | Spend gates | Defaults: `budget-usd: 12.00` on metered routes (the run chose `CRYSK_CLAUDE_API_KEY`, **or** an OpenCode auth file was built), `max-changed-lines: 4000` and `max-changed-files: 50` on metered routes only; a Claude subscription route has no size limit unless the workflow or `.crysk/config.json` sets one. A subscription run stays unlimited unless an OpenCode auth file is also present. |
59
+ | Existing workflow | `setup --ci` skips; ask before `--force` |
60
+ | First-time admission | Recommend `ci_admission_observe_only: true` — `references/ci-admission.md` |
61
+ | User wants max CI spend | Lower `ci_max_attempts` and/or raise `ci_rereview_min_score` |
62
+ | Custom bot posts findings | Add login to `ci_trusted_actors` |
63
+ | Too many advisory comments on PRs | Raise the posting floor: `post_min_severity: "blocking"` in `.crysk/config.json` posts only blocking findings (`"warning"`, the recommended floor setup writes, hides advisory suggestions only). Blocking findings always post; the gate is unchanged. |
64
+ | Blocking findings that are real but improbable keep PRs red ("an edge case that never happens") | Offer `materiality_gate: true` in `.crysk/config.json` (opt-in, off by default). An isolated judge checks each blocking finding against Crysk's posting policy; one judged not material under normal use posts as advisory and does not block. Security, credential and data-loss findings are never demoted, and any judge failure keeps the finding blocking. Cost: one sonnet call per blocking finding (about 1 per PR, roughly +$0.015 notional and +10 s per review). Pair it with `post_min_severity: "blocking"` to hide the demoted ones entirely. |
65
+ | `materiality_gate` is on but nothing is ever demoted | Read the `materiality` record in the run's `pipeline.json` (in the `crysk-run-*` artifact). `unsupported_route`: the judge runs only on `claude:sonnet-latest` or `claude:opus-latest`, so a `models.judge` in `CRYSK_MODELS` that lists neither stands it down; remove that role or list one of the two. `ceiling`: the pipeline ceiling left no room for one judge wave (about 9 minutes). `ran` with `judged: 0`: the run had no blocking finding the safety guard leaves unprotected, so there was nothing to judge. `skipped` on a re-review with no new commits to review is expected (the judge is left out when nothing new is hunted). `skipped` anywhere else means the key did not reach the run: the repo config must be on the PR's base branch (CI reads it from there) and a global config must not set it `false` (the key is capped). |
66
+ | CI skipped (size, admission, or budget) | `gh pr comment <n> --body "/crysk review"`. The review runs on GitHub Actions. Do not run `crysk review --force` locally for this. Legacy scaffold (no `issue_comment` trigger): `gh workflow run pr-hero-force.yml -f pr=<n>`. |
67
+ | Gate is red with blocking findings the team accepts | `gh pr comment <n> --body "/crysk override"` (write access, same-repo PRs only, valid for that head only; a same-head `/crysk review` keeps it red). |
68
+ | Prior review of the same head was hollow or wrong; re-runs say "No changes to discover" | `gh pr comment <n> --body "/crysk review --full"`. A plain `/crysk review` keeps the narrowed discovery. |
69
+ | Gate red: `crysk: review partial (N of M hunters failed, set abc123) — /pr-hero review retries it` | Some hunters failed and nothing blocking was found. `gh pr comment <n> --body "/crysk review"`. If the same hunters fail every run, fix their route (model, credential) or override. |
70
+ | Gate red: `crysk: review partial again (N of M hunters failed, set abc123) — fix the failing route or /pr-hero override` | The previous review of this head was partial with the same hunters failing, so a retry already failed the same way. Fix the failing hunter's route (model, credential), or `gh pr comment <n> --body "/crysk override"`. `crysk status` answers `override-or-fix`. |
71
+ | Gate error: `CRYSK-CANCELLED: not reviewed — /pr-hero review reviews this head` | The review run was cancelled (a newer push, or by hand). Comment `/crysk review` to review the head. |
72
+ | `CRYSK-MODEL-UNAVAILABLE` (lead "Provider <name>:") | Every hunter's route names a model the provider does not serve. Fix the model id in `CRYSK_MODELS` (check `opencode models <provider>`). |
73
+ | `CRYSK-CRED-UNUSABLE` ("The route <provider>/<model> has no usable credential record") | No `CRYSK_OPENCODE_<P>_API_KEY` reached the run for that provider: set it, add its token to `CRYSK_OPENCODE_PROVIDERS`, or move that model elsewhere in `CRYSK_MODELS`. |
74
+ | `CRYSK-CONFIG-INVALID` naming the `models` or `credentials` input | `CRYSK_MODELS` or `CRYSK_CREDENTIALS` is not valid JSON or breaks a rule (the step's log names the entry). Check the same object locally under `models` / `credentials` in `~/.crysk/config.json` with `npx -y crysk config`, then set the variable again. |
75
+ | Blocking findings answered `dismissed`, gate still red | `gh pr comment <n> --body "/crysk recheck"`: the CI adjudicator rules on each dismissal (at most 5 per run). On `upheld`, comment `/crysk review`: that next review stops counting it. `deferred` / `misclassified` never clear the gate. |
76
+ | Gate error: `CRYSK-GOTCHAS-MISSING` ("the review instructions file (REVIEW.md or .crysk/gotchas.md) is empty or still the scaffold") | Write real facts into that file and delete the `human-attention-required` marker line (or delete the file to review with the default guidance), commit it to the default branch, then comment `/crysk review`. |
77
+ | Gate error: `CRYSK-HUNTERS-FAILED` (every hunter failed) | Check the route and credential first (the `CRYSK-CRED-UNUSABLE` and `CRYSK-MODEL-UNAVAILABLE` rows). Free OpenCode models fail intermittently: comment `/crysk review` to retry. |
78
+ | A `/crysk review` comment did nothing | The workflow is not on the default branch yet, the comment is not exact, the author lacks write access, or the workflow predates the comment trigger (re-scaffold with `--force`). |
79
+
80
+ ## Review Settings Interview (ask the human, never choose for them)
81
+
82
+ Before step 4, ask the human these questions in their language. Use the native question UI when available (one grouped interaction is fine). Do not pick an answer for them, and do not skip a question because a default exists: the point is that they know these settings exist.
83
+
84
+ 1. **Re-review level** (how Crysk reviews new pushes on an open PR):
85
+ - **Minimal**: one automatic review per PR; later pushes only on a `/crysk review` comment.
86
+ - **Balanced (recommended)**: re-review when the push touches risky files or the previous pass found enough (score >= 4); at most 2 automatic passes.
87
+ - **Thorough**: review every push, up to 4 automatic passes. Most coverage, most cost.
88
+ - **Manual**: nothing automatic after the first review; every re-review starts with `/crysk review`.
89
+ 2. **Gate or advisory**: gate turns the `crysk` check red on blocking findings (require it in branch protection to block merges); advisory keeps it green.
90
+ 3. **How CI pays**:
91
+ - **Claude subscription** (`CRYSK_CLAUDE_OAUTH_TOKEN`): do not ask for a budget. Tell them no `budget-usd` is written: a subscription review spends quota, not dollars, and CI applies no ceiling while the run uses the subscription and no `CRYSK_OPENCODE_*` secret builds an OpenCode auth file (an OpenCode model brings back the $12 ceiling, so a subscription mixed with OpenCode is the API-key answer). An API key kept beside it is not used unless `CRYSK_CREDENTIALS` puts `api_key` first.
92
+ - **API key** (`CRYSK_CLAUDE_API_KEY` or an OpenCode provider): ask for the spend ceiling per review in USD (default 12, `0` = none).
93
+ 4. **Changed-lines threshold**: a PR with more changed lines is skipped, not reviewed. Ask on any billing (default 4000, `0` = no limit, only if they say so): unlike the budget it matters on a subscription too, where an unset threshold means no limit at all.
94
+ 5. **Advanced settings**: name them, then ask whether to review them now. Each keeps a working default if skipped:
95
+ - score weights: blocking 2, advisory 1 (integers >= 1; `ci_blocking_weight`, `ci_advisory_weight`), and the score floor 4 (`ci_rereview_min_score`); used only by the risk-aware and thresholded policies;
96
+ - observe only (`ci_admission_observe_only`): log what the rules would skip, but review every push; good for one PR cycle;
97
+ - trusted actors (`ci_trusted_actors`): extra GitHub logins whose Crysk markers count;
98
+ - changed-files limit (`max_changed_files`): a PR touching more files is skipped; unset = none on a subscription, 50 on an API key;
99
+ - exclusions: patterns in `.cryskignore` (gitignore syntax) the review never reads;
100
+ - posting floor (`post_min_severity`): `suggestion` posts everything, `warning` (recommended, and what setup writes when the key is absent) hides advisory suggestions, `blocking` posts only blocking findings. Hidden findings are counted in the summary comment, and the gate is unchanged;
101
+ - materiality gate (`materiality_gate`, off unless they say yes): blocking findings that are real but not material under normal use are posted as advisory instead of blocking, judged by an isolated sonnet call per blocking finding against Crysk's posting policy; security, credential and data-loss findings are never demoted. Tell them the cost (about one call per PR, +$0.015 notional, +10 s), that it runs on Claude only (`claude:sonnet-latest`, or `claude:opus-latest` through `models.judge`), so it needs a Claude secret, and the known limit: on a re-review, a finding that already blocked on an earlier push still counts toward the gate.
102
+
103
+ **On a re-run** (`.crysk/config.json` already has re-review keys, or the workflow already exists), first show the human the current values (`npx -y crysk config`) and offer **Keep current settings** for the level and for the line threshold. When they keep them, omit `--level` / `--max-changed-lines`: passing a flag overwrites that group, including a tuned `max_verification_steps`.
104
+
105
+ Then pass the answers to the scaffold as flags, never as hand-written YAML:
106
+
107
+ ```bash
108
+ npx -y crysk setup --ci --level <minimal|balanced|thorough|manual> --ci-mode <gate|advisory> --billing <subscription|api> --max-changed-lines <n> [--budget-usd <n>]
109
+ ```
110
+
111
+ It writes the workflow, merges the level's keys into `.crysk/config.json` (keeping other keys), and prints a summary of every setting. **Never run it without these flags**: with none it applies balanced and gate, and its summary says nobody chose them. Write any advanced answers into `.crysk/config.json` (and `.cryskignore`) afterwards. The summary `setup --ci` printed predates those edits, so when there were any, show the human the effective settings from `npx -y crysk config` instead. Otherwise show the printed summary, including any `Changed` and `Kept existing` lines: on a re-run (for example `--force` to refresh an old workflow) only the groups a flag names are overwritten, and keys nobody chose stay as the file had them; the workflow keeps its old `mode` and `budget-usd` unless `--ci-mode` or `--billing` / `--budget-usd` is passed. In a terminal, every question defaults to the repository's current value. Details: `references/ci-admission.md`.
112
+
113
+ ## Execution Steps
114
+
115
+ 1. **Inspect repo:** `git rev-parse --is-inside-work-tree`, `git remote get-url origin`, `gh auth status`.
116
+ 2. **Credential path:** Claude-only → skip OpenCode. OpenCode or mix → **read `references/opencode-ci.md`** and execute it (models per role, one secret per provider, the providers variable).
117
+ 3. **Claude secret (if used):** `gh secret set CRYSK_CLAUDE_OAUTH_TOKEN` or `CRYSK_CLAUDE_API_KEY` (secure input, never print).
118
+ 4. **Workflow:** run the interview above, then `npx -y crysk setup --ci` with its flags. It writes `.github/workflows/crysk.yml` (or rewrites an existing `pr-hero.yml` in place) and the level keys in `.crysk/config.json`, and its next steps print the `gh secret set` / `gh variable set` commands for the person's `~/.crysk/config.json` (models, credentials, OpenCode providers); run the ones the human agrees to. Confirm `checks: write` and `actions: read`, both `pull_request` and `issue_comment` triggers, the `crysk-secrets: |` block and the `models` / `credentials` lines. `--force` if an old template lacks them (an old `credentials` job, a missing `issue_comment` trigger, or `claude-token` / `routing` lines mean it predates the current workflow).
119
+ 5. **Review instructions (optional, recommended before the first review):** if the default branch has neither a root `REVIEW.md` nor `.crysk/gotchas.md`, run `npx -y crysk init` in the clone; it scaffolds `REVIEW.md` (an existing `.crysk/gotchas.md` is kept, and no `REVIEW.md` is written beside it). The agent writes the facts from the repository it has in context, not from the template: the deliberate oddity that looks like a bug, the invariant enforced outside the diff, the ownership rule a newcomer would break. The hunters and the refuter read the file as facts; the "Not blocking here" section is applied only by the materiality judge (`materiality_gate: true`, blocking findings only, and only to style, naming, test-hygiene, generated-code and dev-script findings), so fill it only when the human asked for that gate, and delete it otherwise. Delete the `human-attention-required` marker line (Crysk refuses to review while it is there), then commit the file to the default branch. With no file the review runs on the default guidance; an empty or scaffold file fails the run `CRYSK-GOTCHAS-MISSING`.
120
+ 6. **Require the check:** in branch protection, require the `crysk` status check (the gate), not the `review` job. The legacy `pr-hero` status is no longer posted, so a repository that still requires it is blocked until the rule moves to `crysk`. A private repository on GitHub Free cannot require status checks (HTTP 403): report that the gate is advisory there. With `gh`, and only after asking the human: read the current protection first (`gh api repos/<o>/<r>/branches/<default>/protection`), because the PUT replaces all of it; then `gh api -X PUT repos/<o>/<r>/branches/<default>/protection` with `required_status_checks` contexts `["crysk"]`.
121
+ 7. **Advanced settings:** write the answers from interview question 5 into `.crysk/config.json` (and `.cryskignore`), including `post_min_severity` when they chose a floor other than `warning` and `materiality_gate: true` only when they said yes; commit both to the default branch, and to any other branch PRs target (CI reads the config from the PR's base branch, so it applies from the next PR after the merge). **No `models` or `credentials` key there** (the repo parser refuses them). `npx -y crysk config` to verify.
122
+ 8. **Verify:** `npx -y crysk doctor`. `git status`. Confirm no echoed secret, and when OpenCode is on, that every `opencode:` model id in `CRYSK_MODELS` is one `opencode models <provider>` lists and each provider's token is in `CRYSK_OPENCODE_PROVIDERS`.
123
+ 9. **Deploy:** Offer commit. Open a **same-repo** test PR (forks skip).
124
+
125
+ ## Output Contract
126
+
127
+ Report:
128
+ - Secret status (set or manual link). Names only: which `CRYSK_*` secrets exist (`gh secret list`). Never values.
129
+ - Models (if set): the `CRYSK_MODELS` and `CRYSK_CREDENTIALS` JSON (no credentials in them), and for OpenCode the `CRYSK_OPENCODE_PROVIDERS` tokens and that each model id matches `opencode models <provider>`.
130
+ - Workflow path (`crysk.yml`, or the pre-rename `pr-hero.yml`; both present means two reviews per PR, delete one) and whether `checks: write`, `actions: read`, the `issue_comment` trigger, the `crysk-secrets` block and the `models` / `credentials` lines are present, with no removed input left.
131
+ - The review settings summary `setup --ci` printed (level, gate, budget, advanced settings), and which ones the human chose, including the posting floor (`post_min_severity`) and whether `materiality_gate` is on. Confirm repo `.crysk/config.json` has no `models` or `credentials` key.
132
+ - `npx -y crysk doctor` / `npx -y crysk config` outcome.
133
+ - Whether the default branch has a real `REVIEW.md` or `.crysk/gotchas.md` (no `human-attention-required` marker line), or neither (reviews run on the default guidance).
134
+ - Whether `crysk` is a required check (or only the legacy `pr-hero`, which should move to `crysk`), or that the repository cannot require one (private repository on GitHub Free).
135
+ - Next steps: merge the workflow to the default branch (the comment trigger needs it there), open a same-repo test PR, when to turn off observe-only. If CI skipped, the override is `gh pr comment <n> --body "/crysk review"`.
136
+
137
+ ## References
138
+
139
+ - `assets/workflow.yml` — the one review workflow (`pull_request` + `issue_comment` for `/crysk review`).
140
+ - `assets/admission-config.example.json` — starter `.crysk/config.json`.
141
+ - `references/ci-admission.md` — admission keys, modes, rollout, ledger.
142
+ - `references/opencode-ci.md` — OpenCode secrets and variables, models per role, pin, openai vs deepseek.
143
+ - `docs/github-actions.md` — full CI integration docs.