Make EcoBot a credible AI usage companion

[hari3mo]

EcoBot now offers a public sample workspace, access-code-protected live chat, and local live mode, with conversation history kept in the visitor's browser. Each live answer carries provider-reported token usage and dated GPT-4o-mini cost estimates; environmental calculations are a separate, explicitly hypothetical scenario.

The daily monetary cap is disabled by default. DAILY_SPEND_LIMIT_USD can enable a shared UTC-day allowance later; zero pauses paid requests. Atomic reservations, durable request IDs, session/IP throttling, and no automatic provider retries protect live requests independently of that default.

Changes

• Rebuild the responsive Chat, My Usage, Prompt Templates, and Methodology pages; preserve all 12 prompt templates and add comparison, export, and deletion.
• Remove the chat-triggered admin bypass, unsafe HTML rendering, central prompt logging, Sheets exports, and automatic Git commits.
• Preserve paid usage through empty answers and concurrent browser tabs; count shared historical receipts once in global totals and CSV exports.
• Add reproducible setup, screenshots, privacy/methodology/operations documentation, pinned dependencies, and Vercel configuration.

Validation

• All 42 Python checks pass in GitHub Actions, including SQLite and MySQL concurrent reservations, authentication, malformed inputs, provider failures, and pricing.
• Both Chromium acceptance scripts pass, covering mobile layout, exports, storage recovery, draft preservation, simultaneous replies, and deletion during an in-flight request.
• Both push and pull-request CI workflows pass against a disposable MySQL 8.4 service. Tests make no paid API calls.

Deployment

Use a separate Vercel project with its Root Directory at the repository root rather than app/. Leave the original project's settings, environment variables, domains, and production branch unchanged. Sample mode needs no credentials. Protected live mode requires server-side API/session/access-code settings and initialized MySQL ecobot_ control tables. Existing remote datasets are not read or modified. This PR does not merge or enable production live requests.

The existing Vercel integration still builds from app/, where its custom install command cannot find the new root-level requirements file. The original project's settings and production deployment remain untouched. All 42 backend checks and both browser acceptance suites pass on final commit f1aa473. A separate root-based, sample-only Vercel preview project is awaiting explicit approval; the old integration's preview check remains failed until that deployment configuration is addressed separately.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
eco-bot	Error		Sep 25, 2026 7:55pm UTC