@anureo/code-review 0.0.0-stage → 0.3.0

package/LICENSE

@@ -0,0 +1,201 @@
+                                 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 2026 Yoichi
+
+   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.

package/bin/anureo-review.d.ts

@@ -0,0 +1,2 @@
+#!/usr/bin/env bun
+export {};

package/bin/anureo-review.js

@@ -0,0 +1,3 @@
+#!/usr/bin/env bun
+import { runCli } from "../src/cli.js";
+process.exitCode = await runCli(process.argv.slice(2));

package/package.json

@@ -1,6 +1,45 @@
 {
   "name": "@anureo/code-review",
-  "version": "0.0.0-stage",
-  "stub": true,
-  "description": "Temporary package placeholder for staged publishing"
-}
+  "version": "0.3.0",
+  "description": "Module-based parallel code review powered by Anureo workflows",
+  "license": "Apache-2.0",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/hi-youichi/anureo-sdk.git",
+    "directory": "apps/code-review"
+  },
+  "publishConfig": {
+    "access": "public"
+  },
+  "type": "module",
+  "exports": {
+    ".": {
+      "types": "./src/index.d.ts",
+      "import": "./src/index.js",
+      "default": "./src/index.js"
+    }
+  },
+  "bin": {
+    "anureo-review": "./bin/anureo-review.js"
+  },
+  "dependencies": {
+    "@anureo/adapter-claude": "0.3.0",
+    "@anureo/adapter-codex": "0.3.0",
+    "@anureo/adapter-hermes": "0.3.0",
+    "@anureo/adapter-pi": "0.3.0",
+    "@anureo/sdk": "0.3.0",
+    "@anureo/workflow": "0.3.0",
+    "zod": "4.6.7"
+  },
+  "engines": {
+    "node": ">=22",
+    "bun": ">=1.4.2"
+  },
+  "files": [
+    "src",
+    "bin",
+    "schema",
+    "protocol",
+    "examples"
+  ]
+}

package/src/angles.d.ts

@@ -0,0 +1,19 @@
+/** Supply a review perspective through ReviewOptions.angles; reviewCode copies and validates
+ * the selection before analysis and retains its order in each module's angle results. */
+export interface ReviewAngle {
+    /** Stable identity, unique within the selection, nonblank and at most 256 UTF-8 bytes. */
+    id: string;
+    /** Nonblank display label included in prompts and reports. */
+    title: string;
+    /** Nonblank guidance included verbatim in both review and verification tasks. */
+    instructions: string;
+}
+/** Review concrete behavior, contract violations and lifecycle failures. */
+export declare const correctnessAngle: ReviewAngle;
+/** Review obstacles to understanding and safely changing the implementation. */
+export declare const codeQualityAngle: ReviewAngle;
+/** Review responsibility, contract, state and dependency ownership. */
+export declare const designAngle: ReviewAngle;
+/** Default perspectives when ReviewOptions.angles is omitted, in report order. Preflight
+ * copies the angle records before dispatch. The CLI also uses these IDs for --angle selection. */
+export declare const defaultAngles: readonly ReviewAngle[];

package/src/angles.js

@@ -0,0 +1,217 @@
+/** Review concrete behavior, contract violations and lifecycle failures. */
+export const correctnessAngle = {
+    id: 'correctness',
+    title: 'Correctness',
+    instructions: `Goal: find concrete incorrect behavior, broken contracts, reachable
+edge cases, races, and resource lifecycle failures.
+
+Investigation:
+Trace an actual entry point through its callers, dependencies, state mutations,
+outputs, and tests. Inspect the dependency implementation or declared contract
+when behavior depends on return values, cancellation, error propagation, or replay.
+Compare equivalent paths across commands, backends, and library versus CLI entry
+points. Follow failure paths as carefully as successful execution.
+
+Checks:
+- State and concurrency: inspect mutations before and after each await, admission
+  and dispatch ordering, shared stop flags, partial effects, deterministic output
+  where required, and cleanup after failure or cancellation. A sibling's failure
+  must not be mistaken for this task's execution outcome.
+- Error propagation: trace null results, rejected tasks, empty catches, and broad
+  fallback handlers. Check that causes survive aggregation, systemic failures stop
+  unsafe or futile dispatch, and programming errors are not treated as correctable
+  user or model input. Trace error codes, retryability, fatality, and outcome
+  certainty through wrappers, persisted records, reports, and consumers; retaining
+  a message alone may discard information needed for a correct decision.
+  Check existing retry and partial-success contracts.
+- Trust boundaries: follow external data through parsing, authorization, and
+  rendering. Type assertions and prompt instructions do not enforce a contract.
+  Check actual read/write scope controls, context-sensitive output encoding, and
+  whether validators establish their advertised guarantees. An incomplete index
+  cannot prove a real symbol absent; a substring match alone may not establish an
+  exact source location. Check consistent path and LF/CRLF handling end to end.
+  Compare granted tools and readable/writable resources with the task's needs and
+  stated restrictions. Check whether claimed restrictions are enforceable and
+  violations observable; audit records do not replace access control.
+- Completion and reporting: follow required fields, coverage gaps, skipped work,
+  and errors into summaries, status, exit codes, and user-visible reports. Check
+  for information discarded while success is still claimed. Separate host facts,
+  model assertions, confirmed effects, and unknown execution outcomes.
+- Capacity and time: inspect the entire encoded input, auxiliary metadata, final
+  aggregation, subprocess buffers, and fallback payloads against actual limits.
+  Check known constraints before expensive dispatch. Distinguish an operation or
+  observation timeout from a deadline that actually bounds external execution.
+- Recovery and side effects: trace both writers and restart readers. Check cache
+  misses versus corruption, stale dependencies, repeatability, and attribution of
+  observed changes. Inspect whether generated artifacts can enter normal source
+  discovery or version control under the tool's default behavior.
+
+Findings:
+Explain the reachable preconditions, causal code path, actual versus expected
+behavior, violated invariant, and impact. A complete static trace is sufficient;
+do not claim a reproduction, incident, or measured cost that was not observed.
+Do not report style preferences, unsupported risks, or feature requests. Return
+no findings when the inspected paths support no correctness defect.`,
+};
+/** Review obstacles to understanding and safely changing the implementation. */
+export const codeQualityAngle = {
+    id: 'code-quality',
+    title: 'Code Quality',
+    instructions: `Goal: find concrete obstacles to understanding and safely changing
+the implementation. Demonstrated reading or editing costs are valid findings even
+without a runtime bug; use the maintenance task as the triggering scenario.
+
+Investigation:
+Read complete functions, relevant callers, sibling implementations, tests, and
+public usage documentation. Choose a task such as changing a default, understanding
+a failure, adding a result state, or locating a reported artifact. Follow the
+actual reading path and identify what must be remembered or edited together.
+
+Checks:
+- Expression: dense multi-statement lines, unnamed compound conditions, positional
+  booleans, deep nesting, and large closures that obscure distinct steps or failure
+  decisions. Explain the hidden meaning, not just a line count.
+- Intent and terminology: inconsistent names for the same concept, one name for
+  different concepts, outdated public wording, misleading optional access, and
+  missing explanations of invariants, status transitions, compatibility choices,
+  timeout relationships, preconditions, return semantics, or thrown errors.
+- Rules and constants: compare path checks, defaults, budget formulas, version
+  markers, error classification, and serialization helpers across all relevant
+  entry points. Identify shared semantics, actual divergence, and the places a
+  change must update. Check unexplained magic values and repeated normalization.
+- Local data flow: hidden mutation inside map/filter callbacks, successive field
+  overwrites, non-null assertions whose justification is distant, and public
+  inferred types that force consumers to inspect an implementation. Explain the
+  specific reasoning burden rather than banning a language construct.
+- Redundancy: repeated validation of already established facts, unused fields or
+  exports, write-only data, constant placeholders, no-op catches/rethrows, and
+  repeated conversion of immutable schemas. Search production, generated, public,
+  and compatibility uses before declaring code dead; test-only use is a clue.
+- Test feedback: inspect whether pure rules can only be exercised through a full
+  process, fixtures omit relevant failure/state combinations, message assertions
+  couple tests to wording, or real sleeps make ordering assumptions. Identify the
+  behavior a missing or weak assertion would fail to distinguish; do not infer a
+  production bug merely from missing coverage.
+- Automated safeguards: when concrete recurring formatting, complexity, import,
+  or unused-code problems are demonstrated, inspect whether maintained local and
+  CI checks detect them. Explain the recurrence and prevention gap before proposing
+  a guardrail; an absent tool or a preferred tool choice alone is not a defect.
+- Validation feedback: inspect whether independent input or response issues can
+  be reported together instead of consuming one correction round per issue. Check
+  field locations, actual versus expected values, and useful repair guidance.
+  Respect checks that depend on earlier parsing or must stop for safety.
+- User-facing clarity and engineering claims: compare help, defaults, dry-run
+  estimates, scripts, package exports, runtime declarations, and emitted artifacts
+  with their implementations. Check actionable errors, failure-time artifact
+  locations, consistent naming/language, and reports organized for decisions rather
+  than raw internal records. Passing on one runtime does not prove full support.
+- Published usability: follow the declared package entry points, executable paths,
+  included files, and documentation from a consumer's installed-package context.
+  Check that necessary usage guidance and referenced resources are shipped or
+  discoverable, rather than available only in the repository. Judge build scripts
+  against the declared source or compiled distribution strategy; do not require
+  transpilation or a particular documentation filename without a consumer need.
+
+Findings:
+Explain the maintenance task, exact obstacle and affected locations, resulting
+cost, and smallest behavior-preserving improvement. Describe how the proposed
+change reduces tracing, edit locations, or ambiguity. Share code only when its
+semantics and reasons to change match; similar syntax alone is insufficient.
+Missing comments, formatting tools, JSDoc, or a preferred style are not standalone
+defects. Do not prescribe abstractions just to shorten code or tests that mirror
+implementation. Focus on local clarity and consistency; structural ownership
+changes belong to design, and concrete behavior failures belong to correctness.
+Return no findings when the actual maintenance tasks are already clear.`,
+};
+/** Review responsibility, contract, state and dependency ownership. */
+export const designAngle = {
+    id: 'design',
+    title: 'Design',
+    instructions: `Goal: find structural problems in responsibility, contract, state,
+and dependency ownership. Concrete maintenance or change-propagation costs are
+valid findings without a runtime bug. Use a supported change scenario rather than
+an invented future requirement.
+
+Investigation:
+Map a real operation from entry point through application coordination, domain
+decisions, state/effects, external adapters, persistence, and result consumers.
+Identify participants, authoritative rules, and state owners before recommending
+boundaries. Inspect callers and sibling flows across modules as context; do not
+infer missing collaboration from a directory listing or an incomplete index.
+
+Checks:
+- Responsibilities and dependencies: look for orchestration, model interaction,
+  validation, domain decisions, I/O, prompts, and rendering changing for unrelated
+  reasons inside one owner. Check misplaced shared helpers, infrastructure that
+  knows presentation policy, configuration/dependencies/control callbacks mixed
+  together, and CLI-specific restrictions embedded in general library primitives.
+  Distinguish source dependency direction from the runtime call direction.
+- Contracts and domain rules: trace each producer to its consumers. Check parallel
+  schema/type definitions, copied upstream policies, and domain invariants spread
+  across validators, aggregators, and repair code. Identify who should own the
+  rule, its versioning, and the consumer-specific subset or projection.
+- State and lifecycle: check representable contradictory states, redundant fields
+  encoding the same fact, bag objects accumulating unrelated lifecycle data, and
+  shared closures acting as an implicit stateful object. Distinguish immutable
+  configuration/plans from mutable progress, task outcomes, and global control.
+- Failure policy: distinguish expected branches, correctable responses, programming
+  errors, local failures, systemic failures, and unknown outcomes. Check whether
+  failure scope matches its cause, partial work survives, and concurrent results
+  carry their own causes instead of relying on side-channel variables. Follow
+  structured error metadata across layer boundaries and persisted projections;
+  identify the consumer that needs codes, retryability, fatality, or outcome
+  certainty. Check whether correction protocols collect independent validation
+  issues and preserve actionable diagnostics within their correction budget.
+- Trust and normalization: establish the owner of boundary parsing, permissions,
+  evidence validation, output encoding, and text/path normalization. Check redundant
+  defensive validation without a trusted representation or a clear guarantee.
+  Preserve necessary integrity and freshness checks when data crosses a new
+  boundary or can change; do not simply remove all repeated checks.
+  Compare necessary capabilities with granted tools and resource access. Identify
+  who enforces restrictions and who records violations or verifies claimed checks;
+  least privilege, enforcement, and auditability are separate responsibilities.
+- Persistence and identity: follow both writes and actual restart loads. Separate
+  authoritative records from reports and diagnostic projections. Check duplicate
+  full payloads, ambiguous copies, competing locks/fingerprints, and whether cache
+  keys identify immutable content or incidental reads. Account for repeated reads
+  and resumes, not only one successful execution.
+- Recovery: distinguish cache miss, missing material, integrity mismatch, stale
+  dependencies, and uncertain side effects. Check whether defaults match the
+  operation's repeatability and whether one stale item unnecessarily invalidates
+  unrelated work. Explain when re-execution is safe rather than prescribing it.
+  Trace which source, configuration, prompt, schema, model, and backend changes
+  invalidate saved results under the declared reuse contract. Distinguish storage
+  format versions from behavior revisions, and identify the coverage of each
+  fingerprint. Check both accidental stale reuse and unnecessary invalidation;
+  do not reject intentionally compatible reuse solely because a version changed.
+- Capacity and resources: account separately for primary input, auxiliary indexes,
+  encoding overhead, retries, stored copies, and final aggregation. Check that
+  scope limits expensive preparation, fixed-size calls have a feasible batching
+  strategy, and degradation paths themselves fit the limits. Identify the actual
+  growth variable and bottleneck; do not invent thresholds or measured costs.
+  Check ownership of execution deadlines, cancellation, and resource release.
+- Protocols and observability: trace every required field to a consumer, including
+  gaps and partial results. Check completion semantics and whether progress shows
+  work remaining rather than an incidental queue. For model protocols, inspect
+  remaining budgets, predictable dependency context, actionable correction
+  feedback, short references, and unnecessary nested encoding. Keep deterministic
+  identity resolution and verification with the host where appropriate.
+- Testability: inspect whether pure decisions can be tested without infrastructure
+  and whether external services, environment, clocks, and identifiers are explicit
+  and controllable where needed. Connect a boundary change to a concrete test or
+  maintenance scenario; dependency injection is not an end in itself.
+
+Findings:
+Name the current owners and collaboration, the affected consumer or supported
+change scenario, the invariant or propagation cost, and a focused alternative.
+Compare local simplification with introducing a new boundary, including added
+indirection, compatibility, and the guarantee that must be preserved.
+Do not infer defects from missing classes, interfaces, patterns, layers, or folder
+names. Preserve sound existing designs; do not fill a quota or demand broad rewrites.
+Keep expression issues in code quality and runtime defects in correctness. Report
+a related structural cause here only when it warrants a distinct design change.
+Return no findings when there is no supported structural improvement.`,
+};
+/** Default perspectives when ReviewOptions.angles is omitted, in report order. Preflight
+ * copies the angle records before dispatch. The CLI also uses these IDs for --angle selection. */
+export const defaultAngles = [correctnessAngle, codeQualityAngle, designAngle];

package/src/cli.d.ts

@@ -0,0 +1,27 @@
+import type { Client } from '@anureo/sdk';
+import { type ReviewHarness } from "./client.js";
+/** Run the CLI with arguments following the executable name. The bin entry point awaits the result
+ * and assigns it to process.exitCode. Returns 0 for help or a complete review without findings,
+ * 1 for a complete review with findings, and 2 for incomplete coverage or reported errors.
+ * Help and CLI parsing failures acquire no backend. When a report is available, it is written
+ * before client disposal. The command awaits disposal before settling once a client is acquired.
+ * A failure to emit the final diagnostic can reject.
+ */
+export declare function runCli(args: string[], dependencies?: CliDependencies): Promise<number>;
+/** Internal execution seams for runCli; omitted hooks use the production client and process streams. */
+interface CliDependencies {
+    /** Receives the canonical directory and selected backend after preflight. runCli owns the returned
+     * initialized client and awaits its disposal, including after review or report-output failure. */
+    createClient?: (cwd: string, harness: ReviewHarness) => Promise<Client>;
+    /** Synchronously consume help or the final report. Throws become CLI errors. */
+    stdout?: (text: string) => void;
+    /** Synchronously consume progress and diagnostics. Progress throws are retained in the report;
+     * diagnostic throws can reject runCli. */
+    stderr?: (text: string) => void;
+    /** Fallback when no positional directory is supplied; defaults to process.cwd(). Does not chdir. */
+    cwd?: string;
+    /** Supplies only the CODEX_MODEL fallback when --model is omitted; defaults to process.env.
+     * Built-in adapter factories still read process.env. */
+    env?: Record<string, string | undefined>;
+}
+export {};