feature-tracker

NotebookLM-fed entity-resolution feature tracker over ArangoDB.

See .cursor/plans/feature-tracker_v1_d9b826ee.plan.md for the full v1 plan.

Quickstart

# 1. Install uv (https://github.com/astral-sh/uv) if you don't have it yet.
# 2. Install deps and create .venv
make install

# 3. Activate pre-commit hooks (one-time)
make hooks

# 4. Copy env template and fill in real values
cp .env.example .env

# 5. Run the quality gates
make check

Detailed setup, ingestion workflow, and deploy instructions land in later slices; this is the Slice-1 skeleton.

OAuth cutover (test data wipe)

Before enabling Google OAuth (Phase 4), run a selective wipe of dashboard test data for the active COLLECTION_PREFIX. This removes test custom signals (is_custom plus a regex on name/description), cascades their feedback, comments, and audit rows, and truncates legacy picker Users documents. It does not delete ingest entity collections or non-matching signals.

# Dry-run (default): lists matched signal _keys and sidecar counts; no writes
uv run python scripts/cutover_wipe.py

# Execute after reviewing the banner and summary (typed prefix confirmation)
uv run python scripts/cutover_wipe.py --execute

Safety

• Dry-run is the default; nothing is deleted until you pass --execute.
• Confirm the printed collection_prefix matches the Vercel dashboard COLLECTION_PREFIX for the environment you intend to wipe.
• Production requires --env prod --force in addition to --execute (see script guard message).

Matching

• Default --match targets test custom signals (case-insensitive regex on name and description; default pattern test).
• The default pattern is a substring match: any is_custom signal whose name or description contains test will be deleted (e.g. "Customer testing feedback"). Review dry-run output carefully before --execute.
• Override with --match 'your-regex' if your test data uses different naming or you need a narrower pattern.

Related tools

• uv run python scripts/clear_dev.py — full dev re-ingest reset (ingest + dashboard collections); not for OAuth cutover.
• Google OAuth env setup and production cutover checklist: Phase 5 / DATA-04 (not covered here).