Bot-authored commit adds Replit config, Azure provider, and IP Analytics tables
A single commit from `Antigravity AI <bot@antigravity.ai>` drops three loosely related scaffolds onto the fork. None of it is wired into existing routes and most of it needs significant rework before it could ship.
The Replit config (stable-23_11 Nix, start.sh entrypoint) is environment-specific and not portable. The Azure OpenAI provider follows the right structural pattern - three-touch extension across types.ts, models.ts, and index.ts - but uses the archived @azure/openai v2 package rather than the current openai SDK. It also borrows apiKeys.claude as the Azure key (marked "temporarily"), logs every raw stream event to an unbounded file in cwd, and implements content-safety guardrails as a two-item hardcoded array: ["unsafe_word", "malicious_term"].
The IP Analytics subsystem is the most revealing piece. Three Postgres tables cover saved_portfolios (with objstore:// URIs), brand_scenarios (FTO risk, tech coverage, competitor overlap as jsonb metrics), and trademark_evaluations (Standard/Verbose modes, TMView reality-check status). Demo seed data includes org names "Danone", "Next", "Steve Madden", and "HLK IP" - that last one is a UK IP firm, which flags the product direction. A Python FastAPI service runs as a second backend. The analytics engine inside it returns random.uniform(...) floats.
The seed script runs on backend boot. If production Supabase credentials are present, it writes to prod.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?