autocode-supervisor 0.8.0__tar.gz

autocode_supervisor-0.8.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

autocode_supervisor-0.8.0/NOTICE

@@ -0,0 +1,4 @@
+AutoCode
+Copyright 2026 Ankur Kothari
+
+This product is licensed under the Apache License, Version 2.0 (see LICENSE).

autocode_supervisor-0.8.0/PKG-INFO

@@ -0,0 +1,185 @@
+Metadata-Version: 2.4
+Name: autocode-supervisor
+Version: 0.8.0
+Summary: AutoCode runs your coding agent and won't say 'done' without evidence: independent checks, exact-version approval, and a record of what was verified.
+License: Apache-2.0
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Operating System :: MacOS
+Classifier: Operating System :: POSIX :: Linux
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: psutil<8,>=7.1
+Provides-Extra: visual
+Requires-Dist: Pillow<13,>=11.3; extra == "visual"
+Provides-Extra: visual-test
+Requires-Dist: Pillow<13,>=11.3; extra == "visual-test"
+Requires-Dist: playwright<2,>=1.56; extra == "visual-test"
+Dynamic: license-file
+
+# AutoCode
+
+AutoCode runs your coding agent through planning, approval, implementation and
+independent validation. It saves progress and checks evidence before reporting
+completion. Start with a request in a committed Git project; approve the plan
+before implementation begins.
+
+## Documentation
+
+[Read the documentation site](https://charlieanna.github.io/autocode/latest/).
+Start with these five guides: [install AutoCode](docs/install.md),
+[run your first task](docs/workflow.md),
+[understand a pause](docs/cli.md#understanding-a-stop),
+[read completion evidence](docs/execution.md#completion-gate), and
+[review a pull request](docs/issues.md#reviewing-a-pull-request).
+The site has search, deeper guides and a version selector; `latest` follows master.
+
+## Install and start
+
+Requires Python 3.11+, Git, and macOS or Linux (Windows through WSL). Install
+from this checkout into a virtual environment:
+
+```sh
+python3 -m venv .venv
+.venv/bin/pip install --editable .
+source .venv/bin/activate
+autocode --version
+autocode doctor --workspace /path/to/project
+autocode "Build a greeting CLI" --workspace /path/to/project
+```
+
+On WSL, run these commands in the Linux terminal with Linux Python. An existing
+Windows-created `.venv` cannot be reused there; see the
+[WSL checkout and environment notes](docs/install.md#windows-through-wsl).
+
+Try the workflow without an account or model spend: `autocode demo` creates an
+offline sample, shows rejected evidence and a completion refusal, then completes
+with independently reproduced checks and demo acceptance. It prints the retained
+run and evidence paths. See the [offline demo](docs/cli.md#offline-demo).
+
+OpenCode 1.x is the default engine. To use a logged-in Codex CLI instead, add
+`--engine codex`, or `--engine claude` for a logged-in Claude Code. See [installation](docs/install.md),
+[provider setup](docs/providers.md) and [model selection](docs/models.md).
+If your account serves only one model, start with `--single-model MODEL` to run
+every role on it (per-role reasoning flags still apply).
+
+To check a change made by another coding tool, supply its comparison base and
+your acceptance criteria to `autocode verify`. It checks the existing change
+and retains a canonical evidence report. See [Standalone verification](docs/verify.md).
+
+## Reliability
+
+AutoCode does not report completion without evidence. Live sweeps on the
+three-case portfolio (small new application, feature in an existing project,
+bug fix) are recorded in [docs/reliability-table.md](docs/reliability-table.md)
+and [RELIABILITY.md](RELIABILITY.md). Fake-provider rows are kept separate
+and never mixed with these. The table is generated, never edited by hand:
+
+```sh
+python tools/reliability_table.py docs/reliability-sweeps.json
+```
+
+| Date | Profile | Runs | Passed | False completions |
+| --- | --- | ---: | ---: | ---: |
+| 2026-10-08 | glm53-mimo | 3 | 2 | 0 |
+| 2026-10-08 | glm53-mimo | 1 | 1 | 0 |
+| 2026-10-07 | glm53-openai | 3 | 2 | 0 |
+| 2026-10-04 | claude-tiers | 9 | 8 | 0 |
+| 2026-10-01 | claude-tiers | 2 | 1 | 1 |
+| 2026-10-01 | glm53-openai | 3 | 1 | 0 |
+| 2026-10-10 | native-glm53-latency | 1 | 0 | 0 |
+
+When a run stops for input, continue it from the project or its task worktree:
+
+```sh
+autocode --status    # what the run needs
+autocode resume      # continue it, acknowledging a pause (no --resume-paused needed)
+```
+
+AutoCode acts on the only unfinished run there. With several, it lists them and
+changes nothing; name one with `--run-dir`, which works from any directory:
+
+```sh
+autocode --run-dir /path/to/run --status
+autocode --run-dir /path/to/run --chat
+```
+
+The [workflow guide](docs/workflow.md) explains questions, plan approval and
+review. The [CLI reference](docs/cli.md) covers answers, approvals and recovery.
+
+For browser, Figma or strict test prerequisites, add
+`--task-preflight qualification/preflight.json`. The [preflight guide](docs/task-preflight.md)
+covers worker permissions, design inputs, named collection and proof setup.
+Failed prerequisites pause before model dispatch; readiness never replaces verification.
+
+## Build from a Figma design
+
+This path requires native Codex, ChatGPT login and the connected Figma plugin
+available to Codex CLI sessions.
+
+```sh
+# Design first, or implement an existing file:
+autocode ui "Design a responsive team dashboard"
+autocode "Build the supplied design" --workspace /path/to/project --engine codex \
+  --figma-file "https://www.figma.com/design/FILEKEY/Project"
+
+# Implement a completed, accepted AutoCode UI run:
+autocode --workspace /path/to/project --engine codex \
+  --ui-run /path/to/project/.autocode-ui/runs/ACCEPTED-RUN
+```
+
+See [Figma design and implementation](docs/figma.md) for design review,
+accepted handoffs and visual verification.
+Implementation reviews use [current browser capture bundles](docs/visual-captures.md):
+`autocode visual-capture --config capture.json` records the rendered implementation
+and its inputs before an independent reviewer judges the images.
+
+## Give one component its own design
+
+For an architecture with `components.json`, `dependency_trace.json` and
+`contracts/*.schema.json`, add one of these fields to the relevant component:
+
+| Component field | Input |
+| --- | --- |
+| `"ui_run": "../.autocode-ui/runs/ACCEPTED-RUN"` | A completed, accepted UI run; relative paths resolve from the architecture directory. |
+| `"figma_file": "https://www.figma.com/design/FILEKEY/Project"` | An existing Figma reference; the URL alone does not establish an accepted UI run. |
+
+Choose one field per component. Only that component receives the design;
+components without either field use their text brief.
+
+```sh
+autocode components architecture --workspace /path/to/project \
+  --options '--engine codex'
+```
+
+Design-bearing builds require native Codex. Plan approval and independent
+implementation review still apply. Repeating the command resumes saved work;
+a changed accepted handoff is rejected instead of silently changing the design
+for that build. See the [complete component example](docs/task-lanes.md#a-component-with-a-figma-design)
+for the architecture format, approvals and integration.
+
+## More guides
+
+- [Parallel task lanes and components](docs/task-lanes.md)
+- [Large projects and workstreams](docs/program.md)
+- [Execution and completion checks](docs/execution.md)
+- [Named test proof for Python, Go, Node and Vitest](docs/named-test-proof.md)
+- [Exact output, raw fallback and usage measurement](docs/exact-output.md)
+- [Dashboard](docs/dashboard.md) and [macOS app](docs/macos-app.md)
+- [Testing](docs/testing.md) and [scenario harness](scenarios/README.md)
+- [Check a coding tool/model's conformance](docs/provider-conformance.md)
+- [Task-run interface for integrations](docs/task-run.md)
+- [VS Code extension](docs/vscode.md)
+- [AutoCode inside Claude Code and other agents: skill and MCP server](docs/agent-step.md)
+- [Experimental OSS Arena and controlled improvement gates](docs/arena.md)
+
+
+### Role names
+
+The terminal and dashboard use the same job names: Requirements, Planner,
+Plan Reviewer, Builder, Tester, Completion Reviewer and Resolver.
+A configured model can perform different jobs; the current step names the job
+being done. See [roles and reviewer-routing modes](docs/models.md#roles).

autocode_supervisor-0.8.0/README.md

@@ -0,0 +1,163 @@
+# AutoCode
+
+AutoCode runs your coding agent through planning, approval, implementation and
+independent validation. It saves progress and checks evidence before reporting
+completion. Start with a request in a committed Git project; approve the plan
+before implementation begins.
+
+## Documentation
+
+[Read the documentation site](https://charlieanna.github.io/autocode/latest/).
+Start with these five guides: [install AutoCode](docs/install.md),
+[run your first task](docs/workflow.md),
+[understand a pause](docs/cli.md#understanding-a-stop),
+[read completion evidence](docs/execution.md#completion-gate), and
+[review a pull request](docs/issues.md#reviewing-a-pull-request).
+The site has search, deeper guides and a version selector; `latest` follows master.
+
+## Install and start
+
+Requires Python 3.11+, Git, and macOS or Linux (Windows through WSL). Install
+from this checkout into a virtual environment:
+
+```sh
+python3 -m venv .venv
+.venv/bin/pip install --editable .
+source .venv/bin/activate
+autocode --version
+autocode doctor --workspace /path/to/project
+autocode "Build a greeting CLI" --workspace /path/to/project
+```
+
+On WSL, run these commands in the Linux terminal with Linux Python. An existing
+Windows-created `.venv` cannot be reused there; see the
+[WSL checkout and environment notes](docs/install.md#windows-through-wsl).
+
+Try the workflow without an account or model spend: `autocode demo` creates an
+offline sample, shows rejected evidence and a completion refusal, then completes
+with independently reproduced checks and demo acceptance. It prints the retained
+run and evidence paths. See the [offline demo](docs/cli.md#offline-demo).
+
+OpenCode 1.x is the default engine. To use a logged-in Codex CLI instead, add
+`--engine codex`, or `--engine claude` for a logged-in Claude Code. See [installation](docs/install.md),
+[provider setup](docs/providers.md) and [model selection](docs/models.md).
+If your account serves only one model, start with `--single-model MODEL` to run
+every role on it (per-role reasoning flags still apply).
+
+To check a change made by another coding tool, supply its comparison base and
+your acceptance criteria to `autocode verify`. It checks the existing change
+and retains a canonical evidence report. See [Standalone verification](docs/verify.md).
+
+## Reliability
+
+AutoCode does not report completion without evidence. Live sweeps on the
+three-case portfolio (small new application, feature in an existing project,
+bug fix) are recorded in [docs/reliability-table.md](docs/reliability-table.md)
+and [RELIABILITY.md](RELIABILITY.md). Fake-provider rows are kept separate
+and never mixed with these. The table is generated, never edited by hand:
+
+```sh
+python tools/reliability_table.py docs/reliability-sweeps.json
+```
+
+| Date | Profile | Runs | Passed | False completions |
+| --- | --- | ---: | ---: | ---: |
+| 2026-10-08 | glm53-mimo | 3 | 2 | 0 |
+| 2026-10-08 | glm53-mimo | 1 | 1 | 0 |
+| 2026-10-07 | glm53-openai | 3 | 2 | 0 |
+| 2026-10-04 | claude-tiers | 9 | 8 | 0 |
+| 2026-10-01 | claude-tiers | 2 | 1 | 1 |
+| 2026-10-01 | glm53-openai | 3 | 1 | 0 |
+| 2026-10-10 | native-glm53-latency | 1 | 0 | 0 |
+
+When a run stops for input, continue it from the project or its task worktree:
+
+```sh
+autocode --status    # what the run needs
+autocode resume      # continue it, acknowledging a pause (no --resume-paused needed)
+```
+
+AutoCode acts on the only unfinished run there. With several, it lists them and
+changes nothing; name one with `--run-dir`, which works from any directory:
+
+```sh
+autocode --run-dir /path/to/run --status
+autocode --run-dir /path/to/run --chat
+```
+
+The [workflow guide](docs/workflow.md) explains questions, plan approval and
+review. The [CLI reference](docs/cli.md) covers answers, approvals and recovery.
+
+For browser, Figma or strict test prerequisites, add
+`--task-preflight qualification/preflight.json`. The [preflight guide](docs/task-preflight.md)
+covers worker permissions, design inputs, named collection and proof setup.
+Failed prerequisites pause before model dispatch; readiness never replaces verification.
+
+## Build from a Figma design
+
+This path requires native Codex, ChatGPT login and the connected Figma plugin
+available to Codex CLI sessions.
+
+```sh
+# Design first, or implement an existing file:
+autocode ui "Design a responsive team dashboard"
+autocode "Build the supplied design" --workspace /path/to/project --engine codex \
+  --figma-file "https://www.figma.com/design/FILEKEY/Project"
+
+# Implement a completed, accepted AutoCode UI run:
+autocode --workspace /path/to/project --engine codex \
+  --ui-run /path/to/project/.autocode-ui/runs/ACCEPTED-RUN
+```
+
+See [Figma design and implementation](docs/figma.md) for design review,
+accepted handoffs and visual verification.
+Implementation reviews use [current browser capture bundles](docs/visual-captures.md):
+`autocode visual-capture --config capture.json` records the rendered implementation
+and its inputs before an independent reviewer judges the images.
+
+## Give one component its own design
+
+For an architecture with `components.json`, `dependency_trace.json` and
+`contracts/*.schema.json`, add one of these fields to the relevant component:
+
+| Component field | Input |
+| --- | --- |
+| `"ui_run": "../.autocode-ui/runs/ACCEPTED-RUN"` | A completed, accepted UI run; relative paths resolve from the architecture directory. |
+| `"figma_file": "https://www.figma.com/design/FILEKEY/Project"` | An existing Figma reference; the URL alone does not establish an accepted UI run. |
+
+Choose one field per component. Only that component receives the design;
+components without either field use their text brief.
+
+```sh
+autocode components architecture --workspace /path/to/project \
+  --options '--engine codex'
+```
+
+Design-bearing builds require native Codex. Plan approval and independent
+implementation review still apply. Repeating the command resumes saved work;
+a changed accepted handoff is rejected instead of silently changing the design
+for that build. See the [complete component example](docs/task-lanes.md#a-component-with-a-figma-design)
+for the architecture format, approvals and integration.
+
+## More guides
+
+- [Parallel task lanes and components](docs/task-lanes.md)
+- [Large projects and workstreams](docs/program.md)
+- [Execution and completion checks](docs/execution.md)
+- [Named test proof for Python, Go, Node and Vitest](docs/named-test-proof.md)
+- [Exact output, raw fallback and usage measurement](docs/exact-output.md)
+- [Dashboard](docs/dashboard.md) and [macOS app](docs/macos-app.md)
+- [Testing](docs/testing.md) and [scenario harness](scenarios/README.md)
+- [Check a coding tool/model's conformance](docs/provider-conformance.md)
+- [Task-run interface for integrations](docs/task-run.md)
+- [VS Code extension](docs/vscode.md)
+- [AutoCode inside Claude Code and other agents: skill and MCP server](docs/agent-step.md)
+- [Experimental OSS Arena and controlled improvement gates](docs/arena.md)
+
+
+### Role names
+
+The terminal and dashboard use the same job names: Requirements, Planner,
+Plan Reviewer, Builder, Tester, Completion Reviewer and Resolver.
+A configured model can perform different jobs; the current step names the job
+being done. See [roles and reviewer-routing modes](docs/models.md#roles).