mediaite-ghostink/Makefile at main · Abstract-Data/mediaite-ghostink · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
# Peer reviewers use `make peer-setup` (sync dev+tui, validate, then `forensics peer-setup` hints).
.PHONY: help install install-reviewer install-baseline install-probability install-all-extras \
	peer-verify peer-verify-network peer-setup peer-hints lint format test coverage clean \
	pipeline scrape extract analyze report quarto-build deploy clean-generated all \
	docs-versions docs-cli docs-python docs-quarto docs-dev docs-build docs-clean

help: ## Show this help
	@grep -E '^[a-zA-Z_-]+:.*?## .*$$' $(MAKEFILE_LIST) | sort | awk 'BEGIN {FS = ":.*?## "}; {printf "\033[36m%-20s\033[0m %s\n", $$1, $$2}'

install: ## Install dependencies (minimal; use install-reviewer for dev+tui)
	uv sync

install-reviewer: ## Python deps for review: dev + tui (no torch / baseline extras)
	uv sync --extra dev --extra tui

install-baseline: ## Reviewer + Phase 10 baseline (pydantic-ai); still no torch
	uv sync --extra dev --extra tui --extra baseline

install-probability: ## Reviewer + Phase 9 probability (large torch/transformers download)
	uv sync --extra dev --extra tui --extra probability

install-all-extras: ## All optional extras (large download; full optional tracks)
	uv sync --extra dev --extra tui --extra baseline --extra probability

peer-verify: ## Run forensics validate (includes preflight)
	uv run forensics validate

peer-verify-network: ## Validate plus WordPress/Ollama endpoint probes (warnings only)
	uv run forensics validate --check-endpoints

peer-hints: ## Print copy-paste setup commands (uv, Ollama pulls from config, etc.)
	uv run forensics peer-setup

peer-setup: install-reviewer peer-verify ## One-shot peer bootstrap: sync, validate, setup hints
	uv run forensics peer-setup

lint: ## Run linter (Python sources only; notebooks are executed via Quarto)
	uv run ruff check src tests scripts

format: ## Format code
	uv run ruff format src tests scripts

format-check: ## Check formatting without changes
	uv run ruff format --check src tests scripts

test: ## Run all tests
	uv run pytest tests/ -v

coverage: ## Run tests with coverage (see pyproject.toml addopts / fail_under)
	uv run pytest tests/ -v

clean: ## Clean generated data and caches
	rm -rf data/raw data/features data/analysis data/reports data/pipeline
	find . -type d -name __pycache__ -exec rm -rf {} + 2>/dev/null || true
	find . -type d -name .pytest_cache -exec rm -rf {} + 2>/dev/null || true

# Pipeline commands
scrape: ## Run scrape stage
	uv run forensics scrape

extract: ## Run feature extraction
	uv run forensics extract

analyze: ## Run analysis stage
	uv run forensics analyze

report: ## Generate report
	uv run forensics report

pipeline: ## Run full pipeline (scrape → extract → analyze → report)
	uv run forensics all

all: pipeline ## Alias for full pipeline including Quarto report

quarto-build: ## Render Quarto book to data/reports
	quarto render --output-dir data/reports

deploy: quarto-build ## Publish HTML book to Cloudflare Pages
	npx wrangler pages deploy data/reports --project-name=ai-writing-forensics

clean-generated: ## Remove extracted features, embeddings, analysis JSON, reports
	rm -rf data/features/*.parquet
	rm -rf data/embeddings/*.npy
	rm -rf data/analysis/*.json
	rm -rf data/reports/*

# Documentation site (Astro Starlight under website/)

docs-versions: ## Resolve release tags into the autodoc configs (CI does this automatically)
	cd website && bun run sync-versions

docs-cli: docs-versions ## Regenerate Typer CLI reference (per-version via worktrees when tags exist)
	@command -v uv >/dev/null 2>&1 || { echo "uv not on PATH"; exit 1; }
	cd website && bun run docs:cli

docs-python: docs-versions ## Regenerate Python API reference via pydoc-markdown (per-version via worktrees when tags exist)
	@command -v pydoc-markdown >/dev/null 2>&1 || { \
	  echo "pydoc-markdown not on PATH. Install with: pipx install pydoc-markdown"; \
	  exit 1; \
	}
	cd website && bun run docs:python

docs-quarto: ## Render the Quarto book into website/public/report (evergreen — always main)
	quarto render --output-dir website/public/report

docs-dev: docs-cli ## Run the docs site locally (http://localhost:4321/mediaite-ghostink/)
	cd website && bun install && bun run dev

docs-build: docs-cli docs-quarto ## Build the docs site for deploy (versioned CLI + Python API + evergreen report)
	cd website && bun install --frozen-lockfile && bun run docs:python && bun run build

docs-clean: ## Remove generated docs content (synced, ADRs, CLI, API, embedded report)
	rm -rf website/src/content/docs/synced website/src/content/docs/adr
	rm -rf website/src/content/docs/cli website/src/content/docs/api
	rm -rf website/public/report website/dist website/.astro

# Quality gates
check: lint format-check test ## Run all quality checks