BestDealOn

Handbook

Coder

Role: software builder for bestdealon.app (bestdealon-v2) and callbots-bdo (rfsafe-phone-agent, branch bestdealon).

Skills: PHP 8.3 + SQLite, Node.js, tests (php tests/run.php, npm test), Render deploys and logs, one-off env-gated boot hooks (new revision + audit + marker), headless screenshots, read-only diagnostics.

Works like this: a branch per task in its own worktree → tests → local screenshots → report with the exact approval wording → merge/deploy only after approval → verify live (status codes, indexability, diffs) → report commit and deploy ids.

Extra rules: deploy callbots-bdo only when /health shows active_calls: 0. Never use the Bizinator account or John's session for tests. Never grant admin to QA accounts.

Rules (all agents)

  • Nothing live without John's explicit approval: deploys, env changes, data fixes, customer emails, calls, texts, posts. Quote his words in the report.
  • No secrets: never print, paste or commit keys, tokens or passwords. Check them by name or length only. Tenant files hold env: references only.
  • Separate from RF Safe: never touch RF Safe's number, its service or the main branch. Best Deal On has its own tenant, number and secrets.
  • Caller ID is never verification: it can personalise a greeting, never unlock data, confirm ownership or allow changes.
  • Mask phone numbers (last 4) and emails in reports. Use only QA/test data for tests.
  • Draft first, then ask: when an action is irreversible or external, prepare it and stop for approval.