feat: complete deployment codebase for BackOne DPI dashboard with dynamic telemetry, rebranding, database size tracking, and modular design

docs/vibe-coding/aider-cli.md

@@ -0,0 +1,13 @@
+# Aider CLI
+
+Aider does not auto-load `AGENTS.md`; tell it to read the file explicitly.
+
+- One-off: `aider --read AGENTS.md --read SKILLS.md`
+- Persistent: add to `.aider.conf.yml` in the project root:
+  ```yaml
+  read:
+    - AGENTS.md
+    - SKILLS.md
+  ```
+- `--read` files are loaded read-only into context (Aider won't try to edit them),
+  which is the correct mode for rules files.

docs/vibe-coding/antigravity-cli.md

@@ -0,0 +1,17 @@
+# Antigravity CLI
+
+Antigravity (Google) reads a root-level `AGENTS.md` natively as its primary
+standing-instructions file — no changes needed, this kit's `AGENTS.md` is picked up
+as-is.
+
+- **Verify it's loaded**: run `agy inspect` in the project root; it lists loaded
+  config sources and should show `AGENTS.md`.
+- **Global rules** (apply to every project, not just this one) live in
+  `~/.gemini/GEMINI.md` — keep that file for personal cross-project preferences only;
+  project-specific rules belong in `AGENTS.md`.
+- **Workspace-only rules** (not meant to travel with the repo) can go in
+  `.agents/rules/` instead.
+- **Skills**: Antigravity supports directory-based Skills loaded only when relevant.
+  If you want the `SKILLS.md` roles enforced more strictly, mirror each role as a
+  `.agents/skills/<role>/SKILL.md` package; otherwise the plain `SKILLS.md` reference
+  from `AGENTS.md` §4 is sufficient.

docs/vibe-coding/antigravity-ide.md

@@ -0,0 +1,13 @@
+# Antigravity IDE
+
+Same config model as the [Antigravity CLI](antigravity-cli.md) — the IDE and CLI
+share the same agent harness.
+
+- Root-level `AGENTS.md` is read automatically before any agent starts work in the
+  workspace; this kit's `AGENTS.md` needs no changes.
+- Global, cross-project preferences: `~/.gemini/GEMINI.md`.
+- Project-only, non-shared rules: `.agents/rules/` in the workspace.
+- Skills (directory-based, loaded on demand) live under `.agents/skills/` if you want
+  to promote a `SKILLS.md` role into a dedicated loadable package.
+- To confirm the IDE picked up `AGENTS.md`, open the agent's context/inspector panel
+  and check the loaded-files list.

docs/vibe-coding/copilot-workspace.md

@@ -0,0 +1,17 @@
+# GitHub Copilot Workspace
+
+Copilot reads `.github/copilot-instructions.md`, not `AGENTS.md`, so add a short
+pointer file rather than duplicating content:
+
+```markdown
+<!-- .github/copilot-instructions.md -->
+Follow the rules in /AGENTS.md and the roles in /SKILLS.md for every task in this
+repository.
+```
+
+- Keep the pointer file minimal — Copilot loads it into every request's context, so
+  don't paste the full `AGENTS.md` content in twice.
+- For instructions scoped to a specific path (e.g. only `*.test.ts`), Copilot also
+  supports `.github/instructions/<name>.instructions.md` files with an
+  `applyTo:` glob in frontmatter — use these for anything that shouldn't apply
+  repo-wide, keeping the cross-tool `AGENTS.md` general.

docs/vibe-coding/cursor-composer.md

@@ -0,0 +1,20 @@
+# Cursor Composer
+
+Cursor does not read `AGENTS.md` natively — it uses its own rules format. Point
+Composer at this kit's rules with a small pointer rule rather than duplicating
+content:
+
+1. Create `.cursor/rules/agents.mdc` (the current, non-deprecated format — the old
+   single `.cursorrules` file still works but is legacy) with:
+   ```
+   ---
+   alwaysApply: true
+   ---
+   Read and follow AGENTS.md and SKILLS.md at the project root before doing any work.
+   ```
+2. Keep the actual rules in `AGENTS.md`/`SKILLS.md` as the source of truth — the
+   `.mdc` file is just a pointer, so Cursor and Claude Code/other tools never drift
+   out of sync.
+3. For rules that should only apply to certain paths (e.g. only `src/api/**`), add
+   additional scoped `.mdc` files under `.cursor/rules/` with a `globs:` frontmatter
+   key — that's Cursor-specific and doesn't belong in the cross-tool `AGENTS.md`.

docs/vibe-coding/cursor-ide.md

@@ -0,0 +1,12 @@
+# Cursor IDE
+
+Same rules mechanism as [Cursor Composer](cursor-composer.md) — Composer is Cursor's
+agent mode within the same IDE, sharing `.cursor/rules/`.
+
+- Add the `.cursor/rules/agents.mdc` pointer rule described in cursor-composer.md
+  once; it applies to both chat/Tab completions and Composer/Agent mode.
+- Check **Settings → Rules** in the IDE to confirm the rule is active and
+  `alwaysApply: true` (so it's loaded on every request, not just glob-matched files).
+- If migrating an existing project off legacy `.cursorrules`, move its content into
+  `AGENTS.md`/`SKILLS.md` first, then replace `.cursorrules` with the pointer `.mdc`
+  file — don't maintain both.

docs/vibe-coding/opencode-ide.md

@@ -0,0 +1,10 @@
+# OpenCode
+
+OpenCode reads a root-level `AGENTS.md` natively, the same convention Claude Code
+uses for `CLAUDE.md` — this kit's `AGENTS.md` is picked up as-is with no pointer file
+needed.
+
+- Confirm it's loaded via OpenCode's session/context inspector before relying on it.
+- If OpenCode is used alongside Claude Code on the same repo, keep `CLAUDE.md` as the
+  thin `@AGENTS.md` import (already set up in this kit) so both tools read one source
+  of truth.

docs/vibe-coding/openhands-agent.md

@@ -0,0 +1,12 @@
+# OpenHands Agent
+
+OpenHands prefers a root-level `AGENTS.md` as always-on context injected at
+conversation start — this kit's `AGENTS.md` needs no changes or pointer file.
+
+- **V0**: repo-specific instructions can additionally live in
+  `.openhands/microagents/repo.md`.
+- **V1**: prefer `.openhands/skills/` for repo-specific skills; `.openhands/microagents/`
+  is still read for backward compatibility.
+- If you want the `SKILLS.md` roles loaded as on-demand context (rather than always
+  injected), convert each role into a microagent/skill file under
+  `.openhands/skills/<role>/` with the appropriate frontmatter trigger.

docs/vibe-coding/vs-code.md

@@ -0,0 +1,13 @@
+# VS Code (Copilot Chat / Agent Mode)
+
+VS Code's built-in Copilot Chat and Agent Mode use the same
+`.github/copilot-instructions.md` mechanism described in
+[copilot-workspace.md](copilot-workspace.md) — set that up once and both the
+Workspace and the editor's inline chat/agent mode pick it up.
+
+- Enable `github.copilot.chat.codeGeneration.useInstructionFiles` in VS Code settings
+  if instructions aren't being applied automatically.
+- Path-scoped instructions: `.github/instructions/<name>.instructions.md` with an
+  `applyTo:` glob, same as Copilot Workspace.
+- These files should stay thin pointers to `AGENTS.md`/`SKILLS.md` — see
+  copilot-workspace.md for the exact pointer snippet.