@reviewsensei/cli-win32-x64 0.1.0

package/bin/_internal/review_sensei-0.1.0.dist-info/METADATA

@@ -0,0 +1,542 @@
+Metadata-Version: 2.4
+Name: review-sensei
+Version: 0.1.0
+Summary: Provider-neutral AI code review engine with an Ollama adapter.
+Author: Mohamad Alsabbagh
+License-Expression: MIT
+Project-URL: Homepage, https://github.com/malsabbagh/review-sensei
+Project-URL: Source, https://github.com/malsabbagh/review-sensei
+Project-URL: Issues, https://github.com/malsabbagh/review-sensei/issues
+Project-URL: Documentation, https://github.com/malsabbagh/review-sensei/tree/main/docs
+Project-URL: Changelog, https://github.com/malsabbagh/review-sensei/blob/main/CHANGELOG.md
+Project-URL: Security, https://github.com/malsabbagh/review-sensei/blob/main/SECURITY.md
+Keywords: code-review,github,ollama,ai,developer-tools
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Software Development :: Quality Assurance
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: cryptography<51,>=44
+Requires-Dist: jsonschema<5,>=4.18
+Dynamic: license-file
+
+# ReviewSensei
+
+ReviewSensei is an open-source, provider-neutral AI code review engine. It turns
+unified pull-request diffs into validated summaries and inline findings. Ollama
+is the first supported model provider, with a small adapter seam for additional
+providers later.
+
+> Alpha: this repository provides an open-source review engine and CLI. The
+> primary usage path is running ReviewSensei in your own GitHub Actions
+> workflow. Setup-v4 callers follow the operator-managed public `v4` tag; the
+> Worker validates that tag before creating the setup PR and the broker resolves
+> it again when issuing a capability. The example workflow installs the
+> requested exact package from PyPI first and falls back to its executing commit
+> only when the distribution is unavailable. It
+> defaults to a local Ollama endpoint and does not require a hosted backend.
+
+## What it does
+
+- Keeps review business logic independent of GitHub and model vendors.
+- Sends a structured prompt to a replaceable provider adapter.
+- Requires provider output to be valid JSON.
+- Rejects inline comments that target files or lines outside the supplied diff.
+- Supports local Ollama servers and Ollama Cloud through the same adapter.
+- Loads approved repository-local learnings and returns validated learning proposals.
+- Supports ordered review stages with structured categories and explicit focus
+  items.
+- Selects lenses by changed path and can attach bounded, lens-specific
+  learnings and architecture documents from a trusted target checkout.
+- Exposes a host-independent concurrency plan with latest-wins pull-request
+  runs and one provider slot per pull request.
+- Publishes versioned JSON Schemas for review results, learnings, categories,
+  stages, and concurrency plans.
+- Provides a narrow GitHub App JWT and installation-token auth adapter for
+  optional App-identity comments or reviews.
+- Avoids retaining raw prompts and provider responses in the engine.
+
+## Quick start
+
+ReviewSensei supports Python 3.11, 3.12, 3.13, and 3.14:
+
+```bash
+python3 -m venv .venv
+source .venv/bin/activate
+python -m pip install .
+review-sensei --version
+```
+
+The default is a local Ollama server using Qwen3.5 4B. Leave the API key empty
+and select the local mode:
+
+```bash
+export REVIEWSENSEI_PROVIDER_MODE="local"
+export REVIEWSENSEI_LOCAL_MODEL="qwen3.5:4b"
+unset OLLAMA_API_KEY
+```
+
+Ollama Cloud is explicit opt-in:
+
+```bash
+export OLLAMA_API_KEY="your-key"
+export REVIEWSENSEI_PROVIDER_MODE="cloud"
+export REVIEWSENSEI_CLOUD_MODEL="deepseek-v4-flash:cloud"
+unset OLLAMA_BASE_URL OLLAMA_MODEL
+```
+
+### Run through npx
+
+Node.js 22 or newer can invoke the same Python review engine through the
+provider-neutral `@reviewsensei/cli` launcher:
+
+```bash
+npx --yes @reviewsensei/cli@0.1.0 --version
+npx --yes @reviewsensei/cli@0.1.0 --help
+```
+
+The launcher selects one of the five native packages (macOS arm64/x64,
+glibc Linux arm64/x64, or Windows x64), forwards arguments unchanged, and
+does not contain a JavaScript review engine. It has no install/download hook;
+`prepare-diff` still requires an external `git` executable. Provider and
+configuration flags are identical to the Python CLI above. Linux musl and
+other architectures receive a bounded unsupported-target error.
+
+The package version is intentionally identical to the Python project and
+release tag. See [`docs/installation.md`](docs/installation.md),
+[`docs/releasing.md`](docs/releasing.md), and [ADR 0031](docs/adr/0031-npm-launcher-and-standalone-platform-packages.md)
+for prerequisites, release ordering, provenance, and version-forward rollback
+guidance (internal tracking issue #103).
+
+Generate a bounded diff and run a review:
+
+```bash
+review-sensei prepare-diff \
+  --repository . \
+  --base-ref main \
+  --head-ref feature \
+  --output pr.patch
+review-sensei \
+  --diff pr.patch \
+  --repository owner/repository \
+  --pull-request 42 \
+  --title "Reviewable change" \
+  --learning-root /path/to/target-branch-checkout \
+  --context-root /path/to/target-branch-checkout \
+  --output review.json
+```
+
+The output is a validated JSON document containing `summary`, `comments`,
+`provider`, `model`, and `learning_proposals`. Learning proposals are not
+stored or used automatically.
+
+The published schema files live under `src/review_sensei/schemas/` and are
+included in the installed package. Public compatibility rules, CLI flags, error
+categories, and provider protocol expectations are documented in
+[`docs/public-contracts.md`](docs/public-contracts.md).
+
+The package also includes the repository contract schemas
+[`review-category.schema.json`](src/review_sensei/schemas/review-category.schema.json),
+[`review-stage.schema.json`](src/review_sensei/schemas/review-stage.schema.json),
+and [`learning-entry.schema.json`](src/review_sensei/schemas/learning-entry.schema.json)
+used by the repository contract validator. Runtime loaders remain the semantic
+authority after structural validation.
+
+## GitHub App identity
+
+Optional App-identity publication is documented in
+[`docs/github-app-auth.md`](docs/github-app-auth.md). It is a narrow
+authentication adapter for GitHub App JWTs and installation access tokens; it
+is not a hosted review service, webhook receiver, or durable delivery store.
+
+### GitHub App setup-v4 integration
+
+The optional setup-v4 integration adds a reviewable, generated caller by using
+the operator-managed `v4` git tag as the only update channel:
+`malsabbagh/review-sensei/.github/workflows/review-sensei-run.yml@v4`.
+The Worker validates the tag before writing the caller, and the Cloudflare
+broker resolves the same tag at capability exchange time and checks the
+executing workflow SHA. Moving `v4` is therefore the public cutoff action.
+The selected provider mode applies consistently to automatic pull-request
+reviews, manual reviews, learning proposals, artifacts, and authorized
+`@sensei` conversations. Cloud runs use GitHub-hosted compute; local runs use
+the operator-controlled labeled self-hosted runner. Every generated write
+switch defaults to `false`.
+
+Cloud mode may pass the existing customer-owned `OLLAMA_API_KEY` secret by
+name (`secrets.OLLAMA_API_KEY`) to the public reusable workflow. The App
+does not create, read, persist, log, or reveal that secret value. The Worker
+broker only issues one capability-scoped installation token after verifying
+the signed Actions OIDC identity, exact v4 workflow ref and runtime SHA,
+repository identity, fork status, installation, replay state, and rate limit.
+
+Installation, reinstall, permission-acceptance, and repository-added events
+reconcile absent or older generated clients through at most one setup-v4 PR.
+Current v4 is a no-op; managed v3 and older generated clients are migrated
+through a setup PR, while custom, malformed, and future setup files are no-write
+cases. See [`docs/installation.md`](docs/installation.md),
+[`docs/github-app-registration.md`](docs/github-app-registration.md), and the
+proposed [`docs/adr/0025-cloud-local-feature-parity-and-conversation-reactions.md`](docs/adr/0025-cloud-local-feature-parity-and-conversation-reactions.md).
+The optional OIDC broker documented there is a hosted issuance-only backend
+that never distributes the App private key.
+
+## Offline evaluation
+
+Issue #9 includes a synthetic, CC0-1.0 corpus that runs without network access
+or provider credentials:
+
+```bash
+python scripts/validate_evaluation_corpus.py
+review-sensei evaluate --mode fixture --corpus evaluation/v1/corpus.json \
+  --output evaluation-report.json
+```
+
+Fixture evaluation is a deterministic regression signal, not a broad model
+benchmark. See [`docs/evaluation.md`](docs/evaluation.md) for live-provider
+acknowledgements, privacy limits, metrics, and approval policy.
+
+The corpus also documents an exact standalone fixture-provider check. Use the
+pinned `fixture-v1` model when comparing the output to the off-by-one oracle;
+the normal CLI default is `qwen3.5:4b` in local mode.
+
+## Bounded review contract
+
+All diff text, paths, source comments, repository context, model output, and
+configured metadata are untrusted. The provider-neutral core validates them
+before a provider call and validates the complete result before a publisher can
+consume it. The public defaults are a hard ceiling; an embedding application
+may only tighten them:
+
+```python
+from review_sensei import ReviewLimits, ReviewRequest
+
+limits = ReviewLimits(max_diff_bytes=256_000, max_comments=40)
+request = ReviewRequest(diff=diff_text, limits=limits)
+```
+
+The default profile is: diff 1,048,576 bytes, 50,000 lines, 500 files, and
+5,000 hunks; repository metadata 512 bytes; title 4,096 bytes; instructions
+65,536 bytes; 64 metadata pairs with 128-byte keys and 4,096-byte values;
+model identifiers 256 bytes; 100 learning entries; 64 active categories; 64
+lens contexts; rendered prompts 4,194,304 bytes; provider response envelopes
+1,048,576 bytes; summary 32,768 bytes; 250 comments with 16,384-byte bodies;
+100 learning proposals with 16,384 bytes per serialized proposal and 262,144
+bytes for the compact UTF-8 serialization of the complete proposal array
+(including brackets and separators); 2,097,152 bytes per publisher-facing
+result; and line numbers up to 2,147,483,647. These are byte limits unless a
+unit is stated otherwise.
+
+Repository paths are strict canonical NFC UTF-8, `/`-separated, relative paths:
+no empty, dot, parent, absolute, drive/UNC, backslash, surrounding whitespace,
+control/format/surrogate, or silently normalized forms are accepted. Glob
+tokens are allowed only in pattern fields; real Git paths may contain literal
+glob characters and are preserved without being interpreted. Git C-quoted
+paths are decoded as strict bytes before the same path checks. Exact duplicate
+comments identified by `(path, line, body)` use stable first-wins ordering;
+comments that differ in body remain distinct. Expected failures are sanitized
+and never include a prompt, diff, provider body, credential, or supplied secret
+marker. Invalid structured provider output receives one fresh, sanitized
+correction attempt per stage; the rejected attempt is discarded completely and
+a second invalid response fails closed. Transport and resource-limit failures
+are not retried by this policy.
+
+Migration is code-free: canonicalize paths before constructing requests, replace
+context-source `path: "."` with explicit root-level files/directories, and split
+inputs that exceed a hard ceiling. Rollback is also code-only: revert the
+limits/validation integration and restore the prior parser, constructors, and
+provider read boundary; no stored data migration is required.
+
+## Structured review stages
+
+Pass `--stages-dir` to replace the packaged default stage with an ordered set of
+JSON stage files. Reusable review categories—also called lenses—can live in a
+separate directory with one JSON file per category:
+
+```json
+{
+  "id": "correctness",
+  "title": "Correctness",
+  "focus": [
+    "Incorrect behavior and invalid assumptions",
+    "Boundary conditions and error handling"
+  ],
+  "applies_to": ["src/**", "tests/**"]
+}
+```
+
+Stages reference the stable category ids:
+
+```json
+{
+  "name": "Correctness and security",
+  "outputs": ["comments"],
+  "category_ids": ["correctness", "security"],
+  "prompt_template": "Examine every focus item below. Use only its id as a comment category.\n<review-categories>\n{review_categories}\n</review-categories>\n<pull-request-diff>\n{diff}\n</pull-request-diff>"
+}
+```
+
+Run it with:
+
+```bash
+review-sensei --diff pr.patch --stages-dir examples/stages \
+  --categories-dir examples/categories \
+  --context-root /path/to/target-branch-checkout
+```
+
+`--categories-dir` requires `--stages-dir`. Category files are loaded into a
+validated catalog, and each stage's `category_ids` are resolved in the declared
+order. An unknown or duplicate id fails before any provider call. For a small,
+self-contained stage, the original inline `categories` array remains supported;
+a stage cannot use inline categories and `category_ids` together.
+
+Supported outputs are `summary`, `comments`, and `learning_proposals`.
+Available placeholders are `{diff}`, `{repository}`, `{pull_request}`, `{title}`,
+`{instructions}`, `{learnings}`, `{context_text}`, `{proposal_instruction}`,
+`{review_categories}`, and `{review_context}`. A stage that declares categories
+must include `{review_categories}`. If any of its categories declares context,
+the stage must also include `{review_context}`. If the provider assigns a
+category to a comment, it must use one of the active stage ids; classification
+is optional for compatibility. If multiple stages reuse an id, the entire lens
+definition must be identical.
+
+Inline findings may also carry independent `severity` (`critical`, `high`,
+`medium`, or `low`) and `fix_effort` (`trivial`, `small`, `moderate`, `large`,
+or `unknown`) labels. Severity describes likely impact, while fix effort
+describes remediation scope rather than a time estimate. The existing
+`category` id is the lens source and is shown as a human-readable lens label;
+no composite priority score or second `lens` field is emitted. These fields are
+optional so legacy provider results remain valid. When present, the same labels
+appear on inline GitHub comments and deterministic severity/lens/quick-win
+counts appear in the review summary. Labels are validated as printable,
+bounded provider text and Markdown-escaped before publication so untrusted
+output cannot inject structure or exceed the configured comment-body limit.
+The formatted summary is checked against `max_summary_bytes`, and the complete
+framed GitHub review body is bounded to 65,536 bytes before publication.
+
+Stage files are trusted operator configuration because they control the model's
+instructions. Category files have the same trust boundary. Load both from a
+reviewed target-branch checkout or deployment bundle, never from an untrusted
+pull-request head. Empty directories, duplicate ids or stage names, symlinked
+files, oversized configurations, malformed categories, unknown fields or
+references, and unknown placeholders fail before a provider is called. See
+[`examples/categories`](examples/categories) and
+[`examples/stages`](examples/stages) for a reusable catalog and three-stage
+pipeline.
+
+### Lens applicability and context
+
+Each lens applies to the whole diff by default. Set `applies_to` to activate it
+only when at least one changed repository path matches. `*` matches within one
+path segment and `**` matches zero or more complete segments, so `src/**`
+includes arbitrarily nested source files. Deleted paths and both sides of a
+rename participate in lens selection. A lens can also select approved learning
+categories and explicit document sources:
+
+```json
+{
+  "id": "architecture",
+  "title": "Architecture",
+  "focus": [
+    "Layer boundaries and dependency direction",
+    "Consistency with architecture documents and decision records"
+  ],
+  "applies_to": ["**"],
+  "context": {
+    "learnings": {
+      "categories": ["architecture"],
+      "include_uncategorized": true
+    },
+    "documents": [
+      {"path": "AGENTS.md"},
+      {"path": "docs/architecture.md"},
+      {"path": "docs/architecture", "include": ["**/*.md"]},
+      {"path": "docs/adr", "include": ["**/*.md"], "exclude": ["drafts/**"]}
+    ]
+  }
+}
+```
+
+`--context-root` identifies the trusted target-branch checkout. When omitted it
+falls back to `--learning-root`; when neither is supplied, optional document
+sources are skipped and required ones fail. ReviewSensei never scans the current
+working directory implicitly. To intentionally select root-level Markdown files,
+declare each root-level file or an explicit canonical directory (for example
+`"path": "docs"`) with an `include` pattern. The root shorthand `"path": "."`
+is intentionally rejected.
+
+Document selection is deterministic and rejects traversal, symlinks, secret-like
+filenames, unsupported formats, unreadable text, and oversized context. Each
+document is sent with its repository-relative path and SHA-256 digest. The
+packaged default pipeline includes an architecture lens whose optional sources
+are `AGENTS.md`, `docs/architecture.md`, `docs/architecture/**/*.md`, and
+`docs/adr/**/*.md`.
+
+## Repository-local learnings
+
+Durable repository knowledge lives in the reviewed repository under
+`.github/review-sensei/learnings/`, with one JSON object per file. These files are
+normal repository content, so their history, review, merge, and rollback are
+visible to maintainers.
+
+```json
+{
+  "id": "provider-boundary",
+  "title": "Keep provider calls behind adapters",
+  "rule": "Review business logic must not import provider SDKs.",
+  "scope": ["src/**"],
+  "rationale": "Provider changes should not alter review behavior.",
+  "category": "architecture",
+  "source": "https://github.com/owner/repository/pull/123"
+}
+```
+
+Only `active` entries are loaded. Scope patterns are matched against changed
+repository paths; use `["*"]` for a repository-wide rule. The learning root
+must be a checkout of the target branch or target commit, not the untrusted
+head checkout. This prevents a pull request from changing its own review
+context before it is merged.
+
+## Local Ollama
+
+```bash
+export REVIEWSENSEI_PROVIDER_MODE="local"
+export REVIEWSENSEI_LOCAL_MODEL="qwen3.5:4b"
+unset OLLAMA_API_KEY
+review-sensei --diff pr.patch
+```
+
+## Providers
+
+The core depends on this small interface:
+
+```python
+class ReviewProvider(Protocol):
+    name: str
+    model: str | None
+
+    def complete(self, request: ProviderRequest) -> ProviderResponse: ...
+```
+
+Registering another provider means translating `ProviderRequest` into that
+provider's API and returning `ProviderResponse`. The review service, diff
+validation, output schema, and GitHub-independent behavior remain unchanged.
+See [the architecture guide](docs/architecture.md).
+
+## GitHub integration
+
+The GitHub App opens a setup-v4 PR containing a thin caller pinned to the full
+SHA resolved from the operator-managed `v4` public git tag at installation
+time. The reusable workflow prefers the requested exact package from PyPI and,
+only when that package/version is unavailable, installs the executing workflow
+commit directly from the public GitHub source. Unrelated PyPI installation
+failures remain fatal. All nine
+`REVIEWSENSEI_*` repository variables are created with safe defaults: automatic
+review, GitHub writes, learning PRs, mention replies, and artifact upload are
+off. The App never creates the customer-owned
+`OLLAMA_API_KEY` secret.
+The five feature switches are all disabled by default.
+
+When explicitly enabled, same-repository pull requests can run automatic review
+with either provider mode: cloud on a GitHub-hosted runner or local Ollama on
+the labelled self-hosted runner. ReviewSensei checks out only trusted base
+content, constructs a bounded diff without executing head code, validates the
+model result, and publishes one exact-head App-authored review containing its
+summary and valid inline changed-line comments. Learning proposals are separate
+draft PRs. Their historical candidate discovery retains the 1,000-PR bound but
+starts with 20-item pages and retries the same item offset with 10, 5, then 1
+item only when the transport reports an oversized response. The 512 KiB
+transport ceiling remains unchanged. Fork pull requests fail closed before
+provider or broker access.
+
+When automatic review and GitHub writes are enabled, ReviewSensei selects
+`APPROVE` for a validated exact-head result only when it has no inline findings
+and a final bounded GitHub thread sweep confirms that every existing review
+thread is resolved. Any open finding or thread, draft/closed/fork/stale PR,
+App-authored PR, or incomplete thread lookup keeps the event as `COMMENT` or
+fails closed; `@sensei` replies are always ordinary comments. Existing review
+markers still deduplicate one publication per head, so resolving a thread does
+not retroactively approve an already-published review.
+
+The approval policy is deliberately conservative: severity, fix effort, lens,
+and model confidence help triage findings but never override an unresolved
+thread. A later head must receive a fresh clean review after the final
+resolution sweep. See [ADR 0030](docs/adr/0030-gate-app-approvals-on-resolved-review-threads-and-exact-head-review-safety.md)
+for the criteria and rollback path.
+
+Manual review and authorized `@sensei` replies use the same selected provider
+mode. Each authorized mention receives a temporary 👀 reaction while the reply
+is generated; ReviewSensei removes it after the reply or another terminal
+outcome. Follow-up mentions in the same inline or PR conversation include the
+bounded prior thread, diff context, findings, and trusted-base learnings. Cloud
+mode sends that bounded conversation context to Ollama Cloud; local mode keeps
+it on the configured local service. Published review summaries and inline
+findings also tell readers to reply with @sensei followed by their question.
+`review.json` is uploaded only when
+`REVIEWSENSEI_UPLOAD_ARTIFACTS=true`; setup-v4 does not create a separate
+version artifact. See [installation and migration](docs/installation.md) and
+the reviewable
+[`setup-v4 example`](examples/github-actions/review-sensei-review.yml).
+
+## Concurrency policy
+
+Hosts that run more than one review worker can reuse the same deterministic
+policy:
+
+```python
+from review_sensei import ReviewConcurrencyPlan, ReviewService
+
+plan = ReviewService(provider).concurrency_plan(request)
+# Enforce plan.workflow in the run scheduler.
+# Enforce plan.provider in the provider-stage scheduler.
+```
+
+The workflow group is keyed by repository and pull request and is latest-wins.
+The provider group uses the same pull-request identity, admits one active
+provider stage, and does not cancel the active stage. Different pull requests
+therefore remain independent. `ReviewConcurrencyPlan.for_non_review_trigger()`
+creates an isolated workflow group with no provider slot for triggers that do
+not request a review. ReviewSensei returns this policy but does not own durable
+queue state or cross-process cancellation.
+
+## Data handling
+
+ReviewSensei sends the prompt and full diff to the selected provider. With the
+workflow's default local base URL, those values stay on the configured local
+Ollama service; with a cloud base URL, the diff and selected context are sent to
+that provider explicitly. The engine does not promise provider retention,
+training, or deletion behavior. Read the provider's current terms before
+sending private or regulated source code.
+
+See [data handling](docs/data-handling.md) for the complete contract.
+
+## Development
+
+```bash
+python -m pip install -r requirements/ci.txt
+python -m pip install -e .
+python scripts/check_action_pins.py
+python scripts/validate_json_contracts.py
+python -m ruff format --check setup.py src tests scripts
+python -m ruff check setup.py src tests scripts
+python -m mypy src
+python -m compileall -q src
+python -m coverage run --source=review_sensei --branch -m unittest discover -s tests -v
+python -m coverage report --precision=2 --show-missing --fail-under=80
+python -m unittest discover -s tests -v
+python -m build
+git diff --check
+review-sensei --help
+```
+
+See [CONTRIBUTING.md](CONTRIBUTING.md), [SECURITY.md](SECURITY.md), and
+[SUPPORT.md](SUPPORT.md) before opening an issue or pull request.
+
+## License
+
+ReviewSensei is released under the [MIT License](LICENSE).

package/bin/_internal/review_sensei-0.1.0.dist-info/RECORD

@@ -0,0 +1,103 @@
+../../Scripts/review-sensei.exe,sha256=L423J5_oI2PFjXn3UuPE-J0hq8CcyxKPUBOjBYabSbA,108355
+review_sensei-0.1.0.dist-info/INSTALLER,sha256=zuuue4knoyJ-UwPPXg8fezS7VCrXJQrAP7zeNuwvFQg,4
+review_sensei-0.1.0.dist-info/METADATA,sha256=VrbrN2WY_qx9njR7EBXgrl6TYr-CpgfFkA2mHuE4JKc,25227
+review_sensei-0.1.0.dist-info/RECORD,,
+review_sensei-0.1.0.dist-info/REQUESTED,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
+review_sensei-0.1.0.dist-info/WHEEL,sha256=YVMoNqKzERt-wjUZwJ33xBGAwnFl-4cqbYkTtWa4itE,91
+review_sensei-0.1.0.dist-info/direct_url.json,sha256=EDhpXdSFq1qZfl2FCT07Hg2gleInjGFaAwkFy0selqU,67
+review_sensei-0.1.0.dist-info/entry_points.txt,sha256=Eki1ToC6hiOv8PMEAd2Cnbh5WWstVzzzf0XmHBHzpMQ,57
+review_sensei-0.1.0.dist-info/licenses/LICENSE,sha256=-eVBqOV92YK1K76UIcK5MrgUh0EiQMe8xNhSysQE68s,1095
+review_sensei-0.1.0.dist-info/top_level.txt,sha256=VCF4gJIJPP3MPJntoITDjMhJ8MUZfVLj-z3-VUQ9XDY,14
+review_sensei/__init__.py,sha256=IscQDESrMeyAT6R9Eh_qXyynJjdEFT143JiMEt51tqc,1784
+review_sensei/__main__.py,sha256=0iDYjdmiXNBinFF23WUyotsdpA6wFKjoB5aw3esTSRg,83
+review_sensei/__pycache__/__init__.cpython-311.pyc,,
+review_sensei/__pycache__/__main__.cpython-311.pyc,,
+review_sensei/__pycache__/cli.cpython-311.pyc,,
+review_sensei/__pycache__/concurrency.cpython-311.pyc,,
+review_sensei/__pycache__/context.cpython-311.pyc,,
+review_sensei/__pycache__/conversation.cpython-311.pyc,,
+review_sensei/__pycache__/diff.cpython-311.pyc,,
+review_sensei/__pycache__/errors.cpython-311.pyc,,
+review_sensei/__pycache__/evaluation.cpython-311.pyc,,
+review_sensei/__pycache__/learnings.cpython-311.pyc,,
+review_sensei/__pycache__/models.cpython-311.pyc,,
+review_sensei/__pycache__/presentation.cpython-311.pyc,,
+review_sensei/__pycache__/schemas.cpython-311.pyc,,
+review_sensei/__pycache__/service.cpython-311.pyc,,
+review_sensei/__pycache__/stages.cpython-311.pyc,,
+review_sensei/__pycache__/validation.cpython-311.pyc,,
+review_sensei/__pycache__/workflow.cpython-311.pyc,,
+review_sensei/cli.py,sha256=FLubo1VkboFMEN0AS7cXtYFRMJOGcTxQQCyDNCGF7xQ,23513
+review_sensei/concurrency.py,sha256=iy6_gtBgm6z_cjug42Ppm14KSrQsCt0JGr9WJu46ZX8,8110
+review_sensei/context.py,sha256=TRY4s5aYkSJSbCBpoZSPR10XOcUELMLpYSdpC6Thg8Q,11776
+review_sensei/conversation.py,sha256=Qdl5qSFMsRRbu7dtsl1RPy1h_syqqTxXKry-jesUFe4,5202
+review_sensei/default_categories/01-correctness.json,sha256=ZeTTvEavHU6_ih7JKhv8a6gH-4wRJGv0abckRWNWTfs,211
+review_sensei/default_categories/02-security.json,sha256=6mz8Hlteb9q1PouLDmDoR-1wxrN31XR2X5I9yoYiG-E,231
+review_sensei/default_categories/03-architecture.json,sha256=Fg3VsUCzl9trCpSnoOgwTqfNHbB7a4znEfrw2apqjXA,806
+review_sensei/default_categories/03-maintainability.json,sha256=eyF9_slQ50LwEqSSet63jthfNp9ZOTnwiDVtVYjVv1A,229
+review_sensei/default_categories/04-tests.json,sha256=UHhvH79bae9FmLJT_MYNvki4Y9xhJDLpDuLdgp2npe0,208
+review_sensei/default_stages/01-default-review.json,sha256=UKqLyIv85O41ruX1rsWIbaXUsyfs-8JDwp2zBvc7KmE,3175
+review_sensei/diff.py,sha256=ED5kqwdAf8oVt10sIpJ1vgFGmpE5ZSk05JhTIG6pnVk,21027
+review_sensei/errors.py,sha256=dr_hhXId1dDjD3xpskys8FPAANbn9Zw4Lz1KJEYP_vk,1088
+review_sensei/evaluation.py,sha256=mGkJghN3LqXFUwbSEAb9i1_8clgkaXXBUAO0kORrwSQ,25338
+review_sensei/hosting/__init__.py,sha256=zqIukHwfUzai3x7dJS2nFNlVhP7EQWQ47-4pGCi2Sz0,84
+review_sensei/hosting/__pycache__/__init__.cpython-311.pyc,,
+review_sensei/hosting/github/__init__.py,sha256=jxmANmeJzOc8iYhZBN7iloD3FjrWUkoNr9xMoCePV0o,5275
+review_sensei/hosting/github/__pycache__/__init__.cpython-311.pyc,,
+review_sensei/hosting/github/__pycache__/application.cpython-311.pyc,,
+review_sensei/hosting/github/__pycache__/approval.cpython-311.pyc,,
+review_sensei/hosting/github/__pycache__/auth.cpython-311.pyc,,
+review_sensei/hosting/github/__pycache__/broker.cpython-311.pyc,,
+review_sensei/hosting/github/__pycache__/broker_client.cpython-311.pyc,,
+review_sensei/hosting/github/__pycache__/conversation.cpython-311.pyc,,
+review_sensei/hosting/github/__pycache__/errors.cpython-311.pyc,,
+review_sensei/hosting/github/__pycache__/http.cpython-311.pyc,,
+review_sensei/hosting/github/__pycache__/jwt.cpython-311.pyc,,
+review_sensei/hosting/github/__pycache__/learning_pr.cpython-311.pyc,,
+review_sensei/hosting/github/__pycache__/oidc.cpython-311.pyc,,
+review_sensei/hosting/github/__pycache__/publication.cpython-311.pyc,,
+review_sensei/hosting/github/__pycache__/setup.cpython-311.pyc,,
+review_sensei/hosting/github/__pycache__/webhooks.cpython-311.pyc,,
+review_sensei/hosting/github/application.py,sha256=GGVHQNe5GS4cOfWtk8b_CYKZuxrdU7794rkz_OKCjJw,8707
+review_sensei/hosting/github/approval.py,sha256=VGZ5XvMB0MmnW9sgK4P_nkByTEhdZeHRfNOFkL-oN7Q,1369
+review_sensei/hosting/github/auth.py,sha256=koITagUX9piVboGJ_smEhPsCf4rOQkOqqSKeLKvFRbc,19055
+review_sensei/hosting/github/broker.py,sha256=FFC7DsFhzy1tENXTCmLNuYzX2cHaYsgMkDGwXEcJaTU,18014
+review_sensei/hosting/github/broker_client.py,sha256=FNBHGWH-I3mPM_XlYz8gJVokQonMXDnB2KaD2lV0x7k,5306
+review_sensei/hosting/github/conversation.py,sha256=r1K8t5qq9bXM3eFzUOsS7mE0aABRIVxB8NgLpZ2RB7o,38400
+review_sensei/hosting/github/errors.py,sha256=QxndyYxP2hAr-imZyeUu76tPkPSBehsX361F4aaeVKc,5157
+review_sensei/hosting/github/http.py,sha256=Xa8WAmLNp8lvrzBxFGGwp6QJQUPZ1ZJciB7SislKNzI,6957
+review_sensei/hosting/github/jwt.py,sha256=mTakXBxU-GR-hBnIZE-FryfFXwpS9hJ7qb3X7P0FBMo,4582
+review_sensei/hosting/github/learning_pr.py,sha256=hT7FmmpWCnUO5WCQEmP9XioQiceNALxuJCtcZXAQxSU,112424
+review_sensei/hosting/github/oidc.py,sha256=h3UVcBYQIKy-xQS7Ixv3_fy670mmuBoNKSYurPZWZ60,13310
+review_sensei/hosting/github/publication.py,sha256=PJClEB2ajxFscwh6jXTYY0I0r36MmDA80J8vl_Ayu6o,22007
+review_sensei/hosting/github/setup.py,sha256=8Atgg27bmytPt8t1VxaacjY54DcXUFy1FLr8E1MEe1E,71186
+review_sensei/hosting/github/webhooks.py,sha256=7hh_YlF7riV6wov7A_27aOb5g6-Ivob1PBWR4m5bF3I,13662
+review_sensei/learnings.py,sha256=3c_HYmSaq3pznRPbePSHbCHp_8_O90wZSJgsKo7PATE,4450
+review_sensei/models.py,sha256=CdyxKoG1wzj54W4lzvHaCTEQkR9IAZm-zhceNz_3nis,43337
+review_sensei/presentation.py,sha256=3MNpUKfo6sbsx8a5aU-f3oFnDFBWkVdRevvR4ZngvAs,4208
+review_sensei/providers/__init__.py,sha256=r9RCFnNXwrHY1HxhyLVhXPT2mS6gxfpoAMo22e-ndvg,347
+review_sensei/providers/__pycache__/__init__.cpython-311.pyc,,
+review_sensei/providers/__pycache__/base.cpython-311.pyc,,
+review_sensei/providers/__pycache__/fixture.cpython-311.pyc,,
+review_sensei/providers/__pycache__/ollama.cpython-311.pyc,,
+review_sensei/providers/__pycache__/registry.cpython-311.pyc,,
+review_sensei/providers/base.py,sha256=NPGpFoo0qRJFJp2j3mFn4vM0Eb3MSWtAxKz1kb2Xj0s,401
+review_sensei/providers/fixture.py,sha256=-HXetG6cXpWd5NlF1-RMA3aqyr88YHwYpiyz0Bc6BO8,1554
+review_sensei/providers/ollama.py,sha256=V6megK0aECd1N-WwNSrUQi-tWjsPDvc2txsJ370LhG4,5181
+review_sensei/providers/registry.py,sha256=NSB1fkozVCPCsvJn6wW67d5-Z5A7jG4IijkhxhXdbr4,2389
+review_sensei/schemas.py,sha256=Txz6PbKWFUpqsuIHp6CcyhjUTLYkywNx5W5xnh5M_uk,1981
+review_sensei/schemas/concurrency-plan.schema.json,sha256=YtHPlfShzFPLE4sQMEn7TogW3souwiKC6d4yd-kgFRY,830
+review_sensei/schemas/conversation-reply.schema.json,sha256=3NihWNn5K1DvtQP0dr0RTf0QlJCFVq-TuYz30Ohjji8,465
+review_sensei/schemas/evaluation-corpus.schema.json,sha256=0W3-zgmVFa5AjDSs385szKNt4DX_D_ZdrE9ur3Nrnz0,7905
+review_sensei/schemas/evaluation-report.schema.json,sha256=BmTJW7RYQTx3taFJoYfmKujJLWnLLTynv5D3e-CVyKE,9269
+review_sensei/schemas/learning-entry.schema.json,sha256=5Xj9ovfB-OjzZShHiv9mHxMIZWVQfEyz-N2Odv8zfHM,1273
+review_sensei/schemas/learning-proposal.schema.json,sha256=FVYG4sFWGil_66-6NlliFCk2LpiCfJn-yTrY4dN-b0E,644
+review_sensei/schemas/review-category.schema.json,sha256=Rni93qGN2LyJSrHRF-GcgVdAjqXGnDU5yjIjG2wn7pI,2189
+review_sensei/schemas/review-comment.schema.json,sha256=j_5mZC66e_5HZJ2jDjjNAIVhQ7eOO2S6QabuZQ2RFnc,616
+review_sensei/schemas/review-result.schema.json,sha256=dQRL4-0lXYqJdm7yJ5FQhQAkPIQZyAAHzuhS2CTiQ18,1735
+review_sensei/schemas/review-stage.schema.json,sha256=6HrPqijpMFgYy7F1dnUwL2kt_Du1HpIIaZbOWxROJe0,4180
+review_sensei/schemas/stage.schema.json,sha256=Fsho33NPMXDSfX9Nv9RqmcF3H_9bOoSHHjxoWvm9ifk,2728
+review_sensei/service.py,sha256=XlRjmNUZdc14PjpeGY7hh1YrMffOaS6Y5Yn5CDhjhTQ,19252
+review_sensei/stages.py,sha256=kA2LOLx0C89lUmlauBKx5JJcdx4mDZKoXviMG2Z33sI,22376
+review_sensei/validation.py,sha256=6ak6ElAFIJiGj53nz4wiUW8X234ESMRtMWut0TMMFAw,10403
+review_sensei/workflow.py,sha256=V8WoiVg5CHMPHPqef85tBRCHd6oJBIxh4c5EJ5BlUoU,16082

package/bin/_internal/review_sensei-0.1.0.dist-info/WHEEL

@@ -0,0 +1,5 @@
+Wheel-Version: 1.0
+Generator: setuptools (84.0.0)
+Root-Is-Purelib: true
+Tag: py3-none-any
+

package/bin/_internal/review_sensei-0.1.0.dist-info/direct_url.json

@@ -0,0 +1 @@
+{"dir_info": {}, "url": "file:///D:/a/review-sensei/review-sensei"}

package/bin/_internal/review_sensei-0.1.0.dist-info/entry_points.txt

@@ -0,0 +1,2 @@
+[console_scripts]
+review-sensei = review_sensei.cli:main