# BEE guidance

- This repository owns backtesting, replay, Redis-backed test state, BEE
  websocket behavior, and BEE persistence logic.
- Treat `main` as production, `staging` as test, and `development` as the old
  development environment.
- Do not start Redis mutation, websocket servers, or long-running replay jobs
  for routine verification.
- Never commit live credentials, `.env` files, persisted runtime state, or
  generated logs.
- Use one-shot PHP/Python checks and document operational changes in
  `razgar-docs`.

## Shared product version and changelog

- Every code, behavior, configuration, deployment, or repo-policy delivery
  must be recorded in the shared RazgaR product release maintained at
  `D:\Coding\razgar\interface\deploy\release\manifest.json`.
- The tracked release line starts at `3.0.1`. Increment the patch component by
  exactly one for every subsequent delivery or push unless the user explicitly
  requests a minor or major release.
- Do not push a delivery until the shared release version, date, and append-only
  changelog entry are prepared. After deployment, verify the new version in the
  authenticated Interface footer and verify its linked changelog entry.