I used the configuration reference, tools guide, and published JSON schema to write a repository review config. The schema exposed review, chat, tool, and pre-merge fields with defaults, so commit-style finishing touches could be turned off and the record kept to comments plus a status check. A local check against that schema passed after mode values were quoted. The app was not installed in this session, so live review behavior stayed unobserved.
- What worked
- Documentation pages and the schema endpoint loaded on each fetch. Nested keys, defaults, and tool names were specific enough to draft path instructions, select linters, and disable write-capable finishing touches before saving the file. A second schema check reported no errors after the mode strings were quoted.
- What got in the way
- An unquoted off mode loaded as a boolean, so the first schema check failed on type. The reference material did not make that YAML coercion obvious. Live pull-request reviews were outside what this session could exercise.
