Add AgTech Ops Hub (Sprint 1): contextualized farm data to action items

[leanmachine1209-ui]

What this is

A new standalone app under agtech-ops/ — an agriculture operations hub / bridge that ingests a range of sources (partner files, Dropbox exports, WhatsApp, and video/clip tag metadata), compiles and aggregates everything across sources, and uses an AI agent to build a logged, prioritized action-item list for ops teams. Runs end-to-end with zero external services or API keys.

Screenshot (live demo)

Compiled overview + media-tag workflow signals + the agent-built action-item log:

Dashboard: compiled overview, media tags, and agent action-item log

Pipeline

INGEST (files · WhatsApp · clip tags) → NORMALIZE + STORE → COMPILE + AGGREGATE → AGENT → ACTION-ITEM LOG

What works

• Multi-format intake — .csv, .tsv, .xlsx/.xls, .json (tabular) and .txt, .md, .log, .pdf, .docx (free text → data); WhatsApp auto-detected.
• Video/clip metadata & tags — clip metadata with tags/duration/camera (from an upstream vision model, e.g. YOLO on a Jetson) is auto-detected as media events; tags become workflow signals that drive actions (a clip tagged lame → a vet task).
• Compile & aggregate — totals, per-source/per-asset counts, top tags, clip counts, and numeric metric time series.
• AI action-item-log agent — a "Haiku agent" (Claude Haiku via LiteLLM when a key is set; deterministic offline fallback) turns incoming bridge data into an append-only, prioritized log; each entry records a rationale and the agent that produced it.
• Deliver — FastAPI API (/ingest/files, /report, /agent/run, /agent/log, /action-items, /health, …) + a Streamlit dashboard (native charts, renders robustly behind tunnels/proxies).
• Deploy — render.yaml + Dockerfile (health check verified).

Testing

• 33 pytest tests, fully offline. All passing.
• CLI + live (Cloudflare tunnel) end-to-end with bundled multi-format sample_data/ incl. clips.json: 5 files → 23 events → tags aggregated → agent log with rationale citing clip tags.

Not included (needs decisions/credentials)

Stripe paywall + agrefine.us landing routing (needs keys + domain/auth decisions). Note: the AG-Refine digital-twin and farm-bridge work referenced in discussion live in separate repos and are out of scope for this PR.

This PR adds an application, not a catalog entry, so the default catalog-entry PR template does not apply.

_{To show artifacts inline, enable in settings.}