Finalize repo-scoping runtime rename

This commit is contained in:
2026-05-15 21:16:34 +02:00
parent 084159e51c
commit 28fad1b248
62 changed files with 445 additions and 305 deletions

View File

@@ -27,10 +27,12 @@ pytest
Run the API:
```bash
uvicorn repo_registry.web_api.app:app --reload
uvicorn repo_scoping.web_api.app:app --reload
```
The API creates a local SQLite database at `var/repo-registry.sqlite3` by default. The database path, `REPO_REGISTRY_` environment prefix, and `repo_registry` Python package name remain compatibility details after the product rename to Repository Scoping.
The API creates a local SQLite database at `var/repo-scoping.sqlite3` by
default. Runtime configuration uses the `REPO_SCOPING_` environment prefix, and
the Python package is `repo_scoping`.
## First API Loop
@@ -40,7 +42,10 @@ curl -X POST http://127.0.0.1:8000/repos \
-d '{"url":"https://example.com/mail-router.git"}'
```
The registry imports name and description from `pyproject.toml`, `package.json`, or README where possible. Then add abilities, capabilities, features, and evidence under that repository and inspect:
The registry uses the submitted repository path or URL as the default name, then
imports description and fallback metadata from `pyproject.toml`, `package.json`,
or README where possible. Then add abilities, capabilities, features, and
evidence under that repository and inspect:
```bash
curl http://127.0.0.1:8000/repos/1/ability-map
@@ -135,17 +140,17 @@ draft.
The FastAPI settings object also accepts `llm_provider` and `llm_model`. By
default `llm_provider` is unset, so analysis is fully offline and deterministic.
Environment variables use the `REPO_REGISTRY_` prefix:
Environment variables use the `REPO_SCOPING_` prefix:
```bash
REPO_REGISTRY_LLM_PROVIDER=gemini
REPO_REGISTRY_LLM_MODEL=gemini-2.5-flash
REPO_SCOPING_LLM_PROVIDER=gemini
REPO_SCOPING_LLM_MODEL=gemini-2.5-flash
```
LLM assistance can also be disabled even when a provider is configured:
```bash
REPO_REGISTRY_LLM_ENABLED=false
REPO_SCOPING_LLM_ENABLED=false
```
Individual analysis requests may opt out with `{"use_llm_assistance": false}`.