pryscraper/STATUS.md
cryptorugmunch 07288a01d7
All checks were successful
CI / typecheck (push) Successful in 51s
CI / Secret scan (gitleaks) (push) Successful in 32s
CI / lint (push) Successful in 47s
CI / Security audit (bandit) (push) Successful in 35s
CI / test (push) Successful in 1m20s
feat(db): add Alembic migrations (#6)
2026-07-03 02:22:33 +02:00

2.4 KiB

//: # (Copyright (c) 2026 Rug Munch Media LLC)

STATUS.md — PryScraper

Where we are RIGHT NOW. Update before every commit.

Last Updated

2026-07-03 - Phase 0 router split + tests + Apify schema lib + PRY_API_KEY deployed

Current Status

🟡 pre-production - core scraping/template routers split, e2e tests added, Talos PRY_API_KEY set, deploy pending.

Deployment Status

  • Last deploy: TBD
  • Current version: 3.0.0-phase0
  • Health: TBD
  • Uptime (30d): TBD
  • Active branch: main

Open Issues

  • None — track in forgejo issues

Recent Activity

  • 2026-07-02: Repository created from fleet-template
  • 2026-07-03: Split scraping endpoints from api.py into routers/scraping.py + deps.py
  • 2026-07-03: Split template endpoints into routers/templates.py + added POST /v1/templates/batch
  • 2026-07-03: Added e2e tests for scraping and template routers (23 new/passing)
  • 2026-07-03: Added reusable Apify actor schema builder (apify_schema.py)
  • 2026-07-03: Set PRY_API_KEY in Talos /srv/pry/.env; auth now active on restart
  • 2026-07-03: Added /v1/templates/batch to x402 paid endpoints + pricing

Known Issues / Tech Debt

  • Deploy at /srv/pry/ is out of sync with repo (needs pull + restart to activate PRY_API_KEY and router changes)
  • All 80+ site templates unverified - only ~30-40% known to work end-to-end. Run templates/validate_templates.py before claiming template coverage.
  • State storage in ~/.pry/*.json - no concurrency safety, no transactions. See plan to migrate to SQLite.
  • PRY_X402_WALLET, PRY_X402_FACILITATOR env vars unset in deploy - x402 payments not active.
  • License collision resolved 2026-07-03: dual MIT (core) + BSL 1.1 (stealth/anti-detection). See ADR-0002.
  • mcp_production.py and x402.py exist in repo but are NOT deployed. Top priority for next deploy.

Status Indicators

Use these in commit messages + status updates:

  • 🟢 healthy — deployed, monitored, no issues
  • 🟡 degraded — running but with known issues
  • 🔴 down — service unavailable
  • 🚧 in-development — pre-production, expect breakage
  • ⏸️ paused — work intentionally stopped