recall-rag 0.5.0__tar.gz

recall_rag-0.5.0/.env.example

@@ -0,0 +1,46 @@
+# Copy to .env (gitignored) and fill in. The .env is only read by local entry points via
+# recall/_env.py — it is never committed.
+
+# Optional: enables the Voyage cloud embedder row in the evaluation (`make eval`).
+# Everything else in the project runs key-free with the local FastEmbed embedder.
+VOYAGE_API_KEY=
+
+# Optional overrides (defaults shown):
+# RECALL_DSN=postgresql://recall:recall@localhost:5432/recall
+# RECALL_EMBEDDER=fastembed          # or "hashing" for the fully-offline embedder
+# RECALL_INDEX_ROOT=.                # bounds where the MCP recall_index tool may read
+# RECALL_CALIBRATION=calibration.json # path to the per-embedder calibration written by `recall calibrate`
+
+# --- MCP transport & authentication (see docs/AUTH.md) ---
+# Default is stdio: a private pipe to one client, which needs no authentication.
+# The HTTP transports open a socket and REFUSE TO START without a token file.
+# RECALL_TRANSPORT=stdio                     # or streamable-http / sse
+# RECALL_AUTH_TOKENS_FILE=/etc/recall/tokens.json   # chmod 600; there is deliberately NO
+#                                            # env var that accepts a raw token
+# RECALL_AUTH_ISSUER_URL=https://recall.example.com
+# RECALL_AUTH_RESOURCE_URL=https://recall.example.com
+# RECALL_TENANT=default                      # stdio only; on HTTP the token carries the tenant
+
+# --- Abuse bounds (see SECURITY.md) ---
+# Per-request caps bound ONE call; the budgets below bound the aggregate, per TENANT, so a
+# client staying under the per-request cap cannot simply issue it in a loop.
+# RECALL_INDEX_MAX_FILES=2000        # per request: candidate file count
+# RECALL_INDEX_MAX_BYTES=20000000    # per request: candidate bytes (~20 MB)
+# RECALL_RATE_READ_PER_MIN=120       # per tenant: recall_search / recall_stats calls
+# RECALL_RATE_WRITE_PER_MIN=20       # per tenant: recall_index calls
+# RECALL_RATE_FORGET_PER_MIN=10      # per tenant: recall_forget calls
+# RECALL_INDEX_BYTES_PER_HOUR=209715200  # per tenant: aggregate indexed bytes (200 MiB).
+#                                    # Keep this >= RECALL_INDEX_MAX_BYTES, or requests between
+#                                    # the two sizes can never succeed.
+# Each of the four budgets takes a number or the literal `off`. A malformed value, a non-finite
+# one, or one too small to yield a non-zero rate falls back to its default rather than being read
+# as "unlimited" — only `off` disables a limit.
+# Read once at startup: changing a budget takes effect on restart.
+
+# --- Schema DDL ---
+# RECALL_SCHEMA_LOCK_TIMEOUT_MS=5000  # how long ensure_schema() may WAIT FOR A LOCK before
+#                                     # giving up. NOT a bound on the work — an HNSW build is
+#                                     # deliberately unbounded — only on queueing behind another
+#                                     # transaction. `0` waits forever. The DDL is idempotent and
+#                                     # retried on the next store open, so failing fast here
+#                                     # loses nothing and is diagnosable where a stall is not.

recall_rag-0.5.0/.gitattributes

@@ -0,0 +1,20 @@
+# Normalize all text files to LF in the repo, regardless of author OS.
+# Prevents the CRLF/LF churn that shows up when committing from Windows.
+* text=auto eol=lf
+
+# Explicit rules for common types (belt-and-suspenders).
+*.py    text eol=lf
+*.md    text eol=lf
+*.toml  text eol=lf
+*.json  text eol=lf
+*.yml   text eol=lf
+*.yaml  text eol=lf
+*.sh    text eol=lf
+Makefile text eol=lf
+
+# Binary assets — never touch line endings.
+*.png binary
+*.jpg binary
+*.jpeg binary
+*.ico binary
+*.gz binary

recall_rag-0.5.0/.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,109 @@
+name: Bug report
+description: Something in RE-call is broken or behaving incorrectly.
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for filing a bug. This project runs against a real PostgreSQL + pgvector database
+        and several swappable embedder backends, so the fields below cut straight to the questions
+        that would otherwise take a round-trip to ask.
+
+  - type: input
+    id: recall-version
+    attributes:
+      label: recall version
+      description: "`pip show recall` or the commit SHA if installed from source."
+      placeholder: "0.5.0"
+    validations:
+      required: true
+
+  - type: input
+    id: python-version
+    attributes:
+      label: Python version
+      placeholder: "3.12.4"
+    validations:
+      required: true
+
+  - type: input
+    id: pg-version
+    attributes:
+      label: PostgreSQL version
+      description: "`SELECT version();` — or the tag from your `pgvector/pgvector:pgNN` image."
+      placeholder: "PostgreSQL 16 (pgvector/pgvector:pg16), or PostgreSQL 17 if a bare-metal install"
+    validations:
+      required: true
+
+  - type: input
+    id: pgvector-version
+    attributes:
+      label: pgvector extension version
+      description: "`SELECT extversion FROM pg_extension WHERE extname = 'vector';`"
+      placeholder: "0.8.2"
+    validations:
+      required: true
+
+  - type: dropdown
+    id: embedder
+    attributes:
+      label: Embedder backend
+      description: Which `Embedder` implementation is in use.
+      options:
+        - fastembed (local, default)
+        - voyage (cloud)
+        - hashing (offline/deterministic)
+        - other / custom Embedder implementation
+    validations:
+      required: true
+
+  - type: input
+    id: corpus-size
+    attributes:
+      label: Corpus size
+      description: Roughly how many files/chunks are indexed. Retrieval behavior differs a lot
+        between a handful of docs and tens of thousands of chunks.
+      placeholder: "e.g. ~800 files / ~6,500 chunks"
+
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What happened
+      description: What you did, what you expected, and what happened instead.
+    validations:
+      required: true
+
+  - type: textarea
+    id: retrieval-detail
+    attributes:
+      label: If this is a retrieval/trust-layer issue — the query and the returned verdict
+      description: >-
+        For "the wrong chunk came back" or "it abstained when it shouldn't have" (or vice versa):
+        the exact query text, and the JSON your search call actually returned (or at minimum each
+        hit's `verdict`, `confidence`/`score`, and whether `abstained` was true). Redact anything
+        sensitive from your corpus — paraphrase the shape of the memory rather than pasting it
+        verbatim if it's private.
+      render: text
+
+  - type: textarea
+    id: repro
+    attributes:
+      label: Minimal reproduction
+      description: Smallest command/script that reproduces it. A snippet using `HashingEmbedder`
+        against a couple of throwaway markdown files reproduces most retrieval bugs without needing
+        your real corpus or an API key.
+      render: shell
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant logs / traceback
+      render: shell
+
+  - type: checkboxes
+    id: checks
+    attributes:
+      label: Checks
+      options:
+        - label: I ran this against a real pgvector database (not a mock) — this project has no mock DB path.
+        - label: I checked this isn't already covered in `README.md`'s "What this does not do" section or `results/FINDINGS.md`.

recall_rag-0.5.0/.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,68 @@
+name: Feature request
+description: Propose new behavior, a new guard, or a new evaluation for RE-call.
+labels: ["enhancement"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        This project's rule for a new claim is: measure it, and publish the negative result if it
+        doesn't hold up (see `results/FINDINGS.md`'s "Claims that were withdrawn"). The same bar
+        applies to feature requests — a proposal that includes how it would be measured gets
+        triaged faster.
+
+  - type: textarea
+    id: problem
+    attributes:
+      label: What problem does this solve
+      description: What's missing today, and what failure or friction it causes.
+    validations:
+      required: true
+
+  - type: textarea
+    id: proposal
+    attributes:
+      label: Proposed behavior
+      description: What you'd want RE-call to do instead.
+    validations:
+      required: true
+
+  - type: dropdown
+    id: area
+    attributes:
+      label: Area
+      options:
+        - Retrieval (dense/sparse/RRF fusion)
+        - Trust layer (verdicts, supersession, validity, calibration)
+        - Embedders (fastembed / voyage / hashing / new backend)
+        - MCP server (recall_search / recall_index / recall_stats)
+        - CLI (index / search / demo / lint / check / calibrate)
+        - Evaluation harness (recall/eval)
+        - Multi-tenancy / RLS
+        - Observability (logging, metrics)
+        - Other
+    validations:
+      required: true
+
+  - type: input
+    id: embedder-context
+    attributes:
+      label: Embedder(s) this affects, if relevant
+      description: Some behavior (e.g. calibration thresholds) does not transfer across embedders —
+        say which backend(s) you're thinking about.
+      placeholder: "e.g. fastembed only, or all embedders"
+
+  - type: textarea
+    id: measurement
+    attributes:
+      label: How would this be measured
+      description: >-
+        If this is a retrieval or trust-layer change: what metric would move (hit@5, superseded-
+        trust rate, false-confident rate, latency), and against which corpus (the 14-doc demo
+        corpus, the real 792-memo corpus, or a generated corpus at scale)? If it's not measurable in
+        that sense (e.g. a CLI ergonomics change), say so — that's a legitimate answer too.
+
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives considered
+      description: Anything you already tried or ruled out, and why.

recall_rag-0.5.0/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,28 @@
+## What this does and why
+
+<!-- The "why" matters more than the "what" here — see CONTRIBUTING.md and the commit-message
+     convention in `git log` (`type(scope): what changed — the reason`). -->
+
+## Area touched
+
+<!-- Retrieval / trust layer / embedders / MCP server / CLI / eval harness / multi-tenancy / other -->
+
+## Checklist
+
+- [ ] `ruff check .` passes
+- [ ] `pytest -v` passes against a real pgvector database (`docker compose up -d --wait` — no mock
+      DB in this project)
+- [ ] If a dependency changed: `uv lock` was run and the updated `uv.lock` is included (CI runs
+      `uv lock --check` as a hard gate)
+- [ ] New behavior has a test that would fail without this change — and the test asserts the actual
+      invariant, not a value a shortcut fix could also satisfy (see the README's "Engineering"
+      section for examples from this repo)
+- [ ] If this changes a published number (README claims table, `results/FINDINGS.md`,
+      `docs/WRITEUP.md`) — the doc is updated in this PR, not left to drift
+- [ ] If this changes calibration, retrieval quality, or the trust layer — `make eval` was re-run
+      and the result reviewed, not assumed unchanged
+
+## Evaluation impact (if applicable)
+
+<!-- Paste the relevant row(s) from results/RESULTS.md or results/SCALE.md before/after, or state
+     "no retrieval/trust-layer impact". -->

recall_rag-0.5.0/.github/dependabot.yml

@@ -0,0 +1,27 @@
+version: 2
+updates:
+  # `uv`, not `pip`. This project is uv-managed and CI runs `uv lock --check`, so a bump that
+  # edits pyproject.toml without regenerating uv.lock fails the audit job and can never merge —
+  # which is exactly what the first `pip` batch did (#44-#48: all red on lockfile drift, while
+  # their test jobs passed). The `uv` ecosystem updates the lockfile alongside the manifest.
+  #
+  # If a Dependabot run ever reports this ecosystem as unsupported, delete this block rather than
+  # reverting to `pip`: no dependency PRs is better than a permanent queue of unmergeable ones,
+  # and the `audit` job already runs pip-audit over the resolved dependency set, so vulnerability
+  # scanning does not depend on this file.
+  - package-ecosystem: "uv"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    labels:
+      - "dependencies"
+
+  # This half is proven: the first batch (#41-#43) bumped checkout, setup-python and setup-uv,
+  # and merged green.
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    labels:
+      - "dependencies"
+      - "ci"

recall_rag-0.5.0/.github/workflows/ci.yml

@@ -0,0 +1,165 @@
+name: CI
+
+on:
+  push:
+    branches: [master]
+  pull_request:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+
+    # Integration tests hit a real pgvector database — no mock DB. Spin one up as a service.
+    services:
+      db:
+        image: pgvector/pgvector:pg16
+        env:
+          POSTGRES_USER: recall
+          POSTGRES_PASSWORD: recall
+          POSTGRES_DB: recall
+        ports:
+          - 5432:5432
+        options: >-
+          --health-cmd "pg_isready -U recall"
+          --health-interval 2s
+          --health-timeout 3s
+          --health-retries 30
+
+    env:
+      # The suite DROPs tables, so it reads RECALL_TEST_DSN and never RECALL_DSN — see
+      # tests/conftest.py. RECALL_DSN is deliberately left unset here.
+      RECALL_TEST_DSN: postgresql://recall:recall@localhost:5432/recall
+
+    steps:
+      - uses: actions/checkout@v7
+
+      - uses: actions/setup-python@v7
+        with:
+          python-version: "3.12"
+          cache: pip
+
+      # Engine + dev tooling only. The optional heavy extras are exercised locally:
+      #   rerank/entail -> sentence-transformers (their real-model tests self-skip here)
+      #   voyage -> cloud embedder (its one test skips without VOYAGE_API_KEY)
+      - name: Install
+        run: pip install -e ".[dev]"
+
+      - name: Lint (ruff)
+        run: ruff check .
+
+      # Coverage over the SHIPPED packages only (`recall`, `recall_mcp`) — putting the tests in
+      # the denominator inflates the number with code that is 100% covered by definition.
+      #
+      # The floor is 70, measured against ~75% in exactly this environment (the `[dev]` extra,
+      # no fastembed/voyage/rerank — the model-backed tests self-skip here, so their modules read
+      # lower than a local run with the extras installed). It is a RATCHET, not a target: set
+      # below the observed number so a normal PR never trips it on noise, and raised deliberately
+      # when a real jump lands. A gate nobody fails on drifts down one PR at a time; a gate pinned
+      # to the exact current number fails on the first unlucky rounding.
+      - name: Test (pytest on real pgvector, with coverage)
+        run: pytest -q --cov=recall --cov=recall_mcp --cov-report=term-missing --cov-report=xml --cov-fail-under=70
+
+  # Static typing, in its own job: it needs no database, so a type error surfaces in ~30s instead
+  # of behind the full integration suite, and a red DB service never hides a red type check.
+  #
+  # Optional extras are deliberately NOT installed here. `recall.rerank` / `recall.entailment` /
+  # `recall.embeddings` import theirs lazily behind a guard, and pyproject's mypy overrides pin
+  # those modules to `follow_imports = skip` so this job's result does not depend on whether a
+  # 2 GB torch wheel happens to be present.
+  typecheck:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+
+      - uses: actions/setup-python@v7
+        with:
+          python-version: "3.12"
+          cache: pip
+
+      - name: Install
+        run: pip install -e ".[dev]" mypy
+
+      - name: Type check (mypy)
+        run: mypy
+
+  # The declared floors, actually installed and actually run.
+  #
+  # Every other job resolves the NEWEST of everything, so the `>=` bounds in pyproject.toml were
+  # never exercised: `mcp>=1.7`, `>=1.10` and `>=1.27.2` are indistinguishable to a green build,
+  # and two of those three were wrong — 1.10-1.27.1 installs cleanly and then fails on every
+  # authenticated call, because `AccessToken.claims` only exists from 1.27.2. `pgvector>=0.3` was
+  # wrong the same way: `from pgvector import Vector` is a 0.4.0 export, so the declared floor
+  # named versions where `import recall.store` raises ImportError. A floor nothing resolves at is
+  # documentation, not a constraint, and it is documentation that was false.
+  #
+  # Lowest supported Python as well as lowest dependencies: this is the whole floor, not half of
+  # it. Verified green at py3.11.15 + mcp 1.27.2 + pgvector 0.4.0 + psycopg 3.3.4 + pytest 8.0.0,
+  # and verified RED against the previous `mcp>=1.10` (auth wiring fails at collection).
+  floor:
+    runs-on: ubuntu-latest
+
+    services:
+      db:
+        image: pgvector/pgvector:pg16
+        env:
+          POSTGRES_USER: recall
+          POSTGRES_PASSWORD: recall
+          POSTGRES_DB: recall
+        ports:
+          - 5432:5432
+        options: >-
+          --health-cmd "pg_isready -U recall"
+          --health-interval 2s
+          --health-timeout 3s
+          --health-retries 30
+
+    env:
+      RECALL_TEST_DSN: postgresql://recall:recall@localhost:5432/recall
+
+    steps:
+      - uses: actions/checkout@v7
+
+      # The `requires-python` floor, not the version the other job happens to use.
+      - uses: actions/setup-python@v7
+        with:
+          python-version: "3.11"
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v7
+
+      # `--resolution lowest-direct`: oldest version of each DIRECT dependency, transitives
+      # resolved normally. `lowest` would also pin every transitive to its floor, which tests
+      # other projects' constraint hygiene rather than ours.
+      - name: Install the declared minimums
+        run: uv pip install --system --resolution lowest-direct -e ".[dev,mcp]"
+
+      - name: Show what actually resolved
+        run: uv pip list --system
+
+      - name: Test (pytest on real pgvector)
+        run: pytest -q
+
+  # Dependency vulnerability scan against the committed uv.lock. Runs independently of the
+  # test job (no DB needed) so a CVE advisory never blocks the functional suite and vice versa.
+  audit:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v7
+
+      # Verify the lockfile is in sync with pyproject.toml — a drifted lock would audit stale
+      # versions. Then resolve the full dependency set (all extras) to a hashed requirements file
+      # and scan it with pip-audit.
+      - name: Check lockfile is current
+        run: uv lock --check
+
+      - name: Export locked dependencies
+        run: uv export --frozen --all-extras --no-emit-project --format requirements-txt -o requirements.lock.txt
+
+      # --no-deps: the exported file already pins the full transitive set, so audit exactly
+      # those versions instead of re-resolving. This is a real gate (a known CVE fails CI); if
+      # it proves too noisy, add `continue-on-error: true` to downgrade it to advisory.
+      - name: Audit dependencies (pip-audit)
+        run: uvx pip-audit --requirement requirements.lock.txt --no-deps

recall_rag-0.5.0/.github/workflows/release.yml

@@ -0,0 +1,103 @@
+name: Release
+
+# Publishes to PyPI when a tag is pushed, and to TestPyPI on demand.
+#
+# Authentication is **Trusted Publishing** (OIDC), so there is no API token in this repository's
+# secrets — nothing to leak, nothing to rotate, and a stolen `contents: write` cannot publish. It
+# does require one-time setup on PyPI before the first run:
+#
+#   PyPI -> the `recall-rag` project (or "pending publisher" if it does not exist yet)
+#     -> Publishing -> Add a new publisher -> GitHub
+#        owner: GiulioDER   repository: RE-call   workflow: release.yml   environment: pypi
+#
+# Without that, the `publish` job fails on authentication — it never publishes to the wrong place.
+# The `environment:` is what lets a required reviewer sit between a pushed tag and a release that
+# can never be un-published: a version number on PyPI is permanent, even after a yank.
+
+on:
+  push:
+    tags: ["v*"]
+  workflow_dispatch:
+    inputs:
+      target:
+        description: "Where to publish"
+        required: true
+        default: testpypi
+        type: choice
+        options: [testpypi, pypi]
+
+permissions:
+  contents: read
+
+jobs:
+  # Build ONCE and hand the same artifacts to every downstream job. Rebuilding per job would mean
+  # the thing that was verified is not bit-for-bit the thing that was published.
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v7
+
+      - name: Build sdist and wheel
+        run: uv build
+
+      # Metadata errors (an unreadable README, a bad classifier) are rejected by PyPI at UPLOAD
+      # time, which is the worst moment to discover them: on a tag push, the tag already exists.
+      - name: Check metadata
+        run: uvx twine check dist/*
+
+      - uses: actions/upload-artifact@v5
+        with:
+          name: dist
+          path: dist/
+
+  # Install the built wheel into a clean environment and exercise it. `uv build` succeeding only
+  # proves the metadata parses — it says nothing about whether the wheel's contents import, or
+  # whether a module was left out of `[tool.hatch.build.targets.wheel].packages`.
+  smoke:
+    needs: build
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python: ["3.11", "3.13"]  # the declared floor and the newest supported
+    steps:
+      - uses: actions/download-artifact@v5
+        with:
+          name: dist
+          path: dist/
+
+      - uses: actions/setup-python@v7
+        with:
+          python-version: ${{ matrix.python }}
+
+      # From the wheel, NOT from the checkout — `pip install -e .` would import the source tree
+      # and pass even if the wheel shipped an empty package.
+      - name: Install the built wheel
+        run: pip install dist/*.whl
+
+      - name: Import and run the console script
+        run: |
+          cd "$(mktemp -d)"   # away from the source tree, so nothing resolves by accident
+          python -c "import recall, recall_mcp; from recall.trust import trusted_search; print(recall.__name__, 'ok')"
+          recall --help > /dev/null
+          echo "console script ok"
+
+  publish:
+    needs: [build, smoke]
+    runs-on: ubuntu-latest
+    environment: ${{ github.event_name == 'push' && 'pypi' || inputs.target }}
+    permissions:
+      id-token: write  # the OIDC token Trusted Publishing exchanges for an upload credential
+    steps:
+      - uses: actions/download-artifact@v5
+        with:
+          name: dist
+          path: dist/
+
+      - name: Publish
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          # A tag push always goes to PyPI. A manual run goes wherever it was asked to.
+          repository-url: ${{ (github.event_name == 'push' || inputs.target == 'pypi') && 'https://upload.pypi.org/legacy/' || 'https://test.pypi.org/legacy/' }}

recall_rag-0.5.0/.gitignore

@@ -0,0 +1,21 @@
+__pycache__/
+*.pyc
+.pytest_cache/
+.ruff_cache/
+.mypy_cache/
+.coverage
+coverage.xml
+*.egg-info/
+build/
+dist/
+.venv/
+.venv-ci/
+.env
+finetune/model*/
+calibration.json
+.claude/
+results/scale*/corpus/
+results/scale*/.recall-synthetic
+
+# LOCOMO benchmark data — fetched on demand, not vendored (see recall/eval/locomo.py)
+locomo10.json

recall_rag-0.5.0/.hypothesis/.gitignore

@@ -0,0 +1,9 @@
+# This .gitignore file was automatically created by Hypothesis. Hypothesis gitignores
+# .hypothesis by default, because we generally recommend that .hypothesis not be checked
+# into version control.
+#
+# If you *would* like to check .hypothesis into version control, you should delete this
+# file. Hypothesis will not re-create this .gitignore unless .hypothesis is deleted (and
+# if it does, that's a bug - please report it!)
+
+*

recall_rag-0.5.0/.hypothesis/constants/09ae28b390a241d0

@@ -0,0 +1,4 @@
+# file: C:\Users\gde00\AppData\Roaming\Python\Python314\site-packages\sortedcontainers\sorteddict.py
+# hypothesis_version: 6.158.0
+
+[50331648, ', ', '<not-given>', 'items', 'iteritems', 'iterkeys', 'itervalues', 'keys', 'values', 'viewitems', 'viewkeys', 'viewvalues', '{0!r}, ', '{0!r}: {1!r}', '{0}({1}{{{2}}})']

recall_rag-0.5.0/.hypothesis/constants/1b03421aacbc7cd8

@@ -0,0 +1,4 @@
+# file: C:\Users\gde00\AppData\Roaming\Python\Python314\site-packages\sortedcontainers\__init__.py
+# hypothesis_version: 6.158.0
+
+[132096, '2.4.0', 'Apache 2.0', 'Grant Jenks', 'SortedDict', 'SortedItemsView', 'SortedKeyList', 'SortedKeysView', 'SortedList', 'SortedListWithKey', 'SortedSet', 'SortedValuesView', 'sortedcontainers']

recall_rag-0.5.0/.hypothesis/constants/4f680edac8831786

@@ -0,0 +1,4 @@
+# file: C:\Users\gde00\AppData\Roaming\Python\Python314\site-packages\__editable___cca_checks_0_4_0_finder.py
+# hypothesis_version: 6.158.0
+
+['.', '.__path_hook__', '__init__.py', 'cca_checks']

recall_rag-0.5.0/.hypothesis/constants/58bfffd74f8d33bb

@@ -0,0 +1,4 @@
+# file: C:\Users\gde00\AppData\Roaming\Python\Python314\site-packages\sortedcontainers\sortedlist.py
+# hypothesis_version: 6.158.0
+
+[1000, 50331648, '!=', '...', '<', '<=', '==', '>', '>=', '__{0}__', 'equal to', 'greater than', 'index', 'keys', 'len', 'len_index', 'len_keys', 'len_lists', 'len_maxes', 'less than', 'lists', 'load', 'maxes', 'not equal to', 'offset', '{0!r} is not in list', '{0!r} not in list', '{0}({1!r})']

recall_rag-0.5.0/.hypothesis/constants/7b04dce73625ffce

@@ -0,0 +1,4 @@
+# file: C:\Users\gde00\Documents\RE-call\recall\__init__.py
+# hypothesis_version: 6.158.0
+
+['0.5.0']

recall_rag-0.5.0/.hypothesis/constants/82006d59dbfd9f8c

@@ -0,0 +1,4 @@
+# file: C:\Users\gde00\AppData\Roaming\Python\Python314\site-packages\_distutils_hack\__init__.py
+# hypothesis_version: 6.158.0
+
+['__file__', '_distutils', 'distutils', 'distutils.', 'distutils.core', 'local', 'pybuilddir.txt', 'setup.py', 'spec_for_{fullname}', 'stdlib', 'test.', 'test.test_distutils', 'test.test_importlib']

recall_rag-0.5.0/.hypothesis/constants/93fc2ddbc371af6f

@@ -0,0 +1,4 @@
+# file: C:\Users\gde00\Documents\RE-call\recall_mcp\limits.py
+# hypothesis_version: 6.158.0
+
+[0.0, 1.0, 10.0, 20.0, 60.0, 120.0, 3600.0, 200, 1024, '_rate', '_tokens', '_updated', 'forget', 'index_bytes', 'limits', 'off', 'read', 'write']

recall_rag-0.5.0/.hypothesis/constants/aacd188e88fdb02c

@@ -0,0 +1,4 @@
+# file: C:\Users\gde00\AppData\Local\Temp\claude\C--Users-gde00-Documents-progetto-sentimental--claude-worktrees-audit-fix-deep-79a8a0\7795ded5-981e-4f82-b805-70af4d8da051\scratchpad\prop_bucket.py
+# hypothesis_version: 6.158.0
+
+[0.0, 1e-06, 0.001, 0.01, 1.0, 100.0, 1000.0, 2000, '.']

recall_rag-0.5.0/.hypothesis/constants/b9060cae8ecc85e4

@@ -0,0 +1,4 @@
+# file: C:\Users\gde00\Documents\RE-call\recall\observability.py
+# hypothesis_version: 6.158.0
+
+[0.5, 0.95, 0.99, 1000.0, 1024, '%Y-%m-%dT%H:%M:%S%z', ',', 'INFO', 'RECALL_LOG_FORMAT', 'RECALL_LOG_LEVEL', '_', 'asctime', 'count', 'counters', 'exc', 'histograms', 'json', 'level', 'logger', 'message', 'nan', 'p50', 'p95', 'p99', 'recall', 'taskName', 'text', 'ts']

recall_rag-0.5.0/.hypothesis/constants/c2e77a59fc774cb4

@@ -0,0 +1,4 @@
+# file: C:\Users\gde00\AppData\Roaming\Python\Python314\site-packages\win32\lib\pywin32_bootstrap.py
+# hypothesis_version: 6.158.0
+
+[]