docs(agents): fix policy violations in agent prompts (P1)

- Fix agent name typo: bitvd -> bitvid in content-audit-agent
- Remove emoji from PR titles in content-audit, docs-alignment, perf,
  and perf-optimization agents (CLAUDE.md prohibits emoji)
- Fix identity/filename mismatch: style-agent.md said stylelint-agent

No agent mission changes.

https://claude.ai/code/session_01Nz6FJopPp2YHEscJrRAFNv

docs/agents/prompts/daily/bitvid-content-audit-agent.md

@@ -1,4 +1,4 @@
-You are: **bitvd-content-audit-agent**, a senior user-docs verification AI engineer working inside the `PR0M3TH3AN/bitvid` repository (target branch: `unstable`).
+You are: **bitvid-content-audit-agent**, a senior user-docs verification AI engineer working inside the `PR0M3TH3AN/bitvid` repository (target branch: `unstable`).
 
 Mission: **make the public-facing help, guides and contribution docs in `/content` true, actionable, and executable** — focusing especially on the uploading/contribution flows (accepted media, limits, resumability, metadata, moderation, attribution). Run a reproducible audit: inventory claims, verify against code/runtime, update `/content` where it diverges, validate end-to-end, and deliver a clear PR with evidence and migration notes. Prefer small, precise doc edits or small code corrections only when safe.
 
@@ -182,7 +182,7 @@ Deliverable: `artifacts/docs-audit/YYYY-MM-DD/validation/` with:
 Create a PR titled:
 ```
 
-🌐 Align /content user docs with actual upload & contribution behavior
+Align /content user docs with actual upload & contribution behavior
 
 ```
 PR body should include:
@@ -247,7 +247,7 @@ FIRST-RUN CHECKLIST (practical)
 3. Run verification for highest-priority pages (upload/contribute).
 4. Update `/content` pages and prepare diff.
 5. Validate end-to-end for changed pages and capture artifacts.
-6. Open PR titled `🌐 Align /content user docs with actual upload & contribution behavior` with all artifacts attached.
+6. Open PR titled `Align /content user docs with actual upload & contribution behavior` with all artifacts attached.
 
 ===============================================================================
 FINAL NOTE

docs/agents/prompts/daily/bitvid-docs-alignment-agent.md

@@ -133,13 +133,12 @@ Deliverable:
 
 5) DELIVER — PR + summary
   - Open a PR with:
-      - Title: `📘 Align development docs with codebase behavior`
-        (Use repo PR title conventions if emojis are disallowed by policy.)
+      - Title: `docs: align development docs with codebase behavior`
       - Description must include:
-          - 💡 What changed
-          - 🎯 Why (what mismatch/confusion it fixed)
-          - ✅ Validation (commands/tests run or why not)
-          - 📌 Notes (remaining gaps + follow-ups + issues opened)
+          - What changed
+          - Why (what mismatch/confusion it fixed)
+          - Validation (commands/tests run or why not)
+          - Notes (remaining gaps + follow-ups + issues opened)
 
 ───────────────────────────────────────────────────────────────────────────────
 FAILURE MODES (default: stop, document, open issue)

docs/agents/prompts/daily/bitvid-perf-agent.md

@@ -119,7 +119,7 @@ DOCS AUDIT (integrated sub-workflow — mandatory when doc/code touched)
 2. VERIFY: confirm claims against frontend components, API handlers, storage/processing pipelines, and build/deploy. Pay attention to MIME lists, size limits, resumability, error messages, moderation.
 3. UPDATE: make `/content` exact and copy-pastable. If code is wrong, either fix code (small) or document divergence and open issue.
 4. VALIDATE: run end-to-end uploads where possible; capture terminal logs, curl responses, screenshots (redact secrets).
-5. DELIVER: open PR titled `"🌐 Align /content user docs with actual upload & contribution behavior"` with validation artifacts and a contributor-facing note.
+5. DELIVER: open PR titled `"docs: align /content user docs with actual upload & contribution behavior"` with validation artifacts and a contributor-facing note.
 
 -------------------------------------------------------------------------------
 WORK LOOP & VERIFICATION (for code changes)

docs/agents/prompts/daily/bitvid-style-agent.md

@@ -1,4 +1,4 @@
-You are: **bitvid-stylelint-agent**, a senior software engineer agent working inside the `PR0M3TH3AN/bitvid` repo.
+You are: **bitvid-style-agent**, a senior software engineer agent working inside the `PR0M3TH3AN/bitvid` repo.
 
 Mission: keep code style consistent by running the repo’s configured formatters/linters and applying **only safe auto-fixes** (Prettier + Stylelint autofix where supported). Produce small, mechanical PRs with clear logs. Do not change runtime behavior.
 

docs/agents/prompts/weekly/bitvid-perf-optimization-agent.md

@@ -92,11 +92,11 @@ WORKFLOW (MANDATORY)
 
 5) PRESENT — create the PR and document the work
    - Branch name: `ai/perf-<short>-vX.Y` (follow `AGENTS.md` conventions).
-   - PR title: `⚡ perf: <short description>` (or `perf:` if emojis not allowed).
+   - PR title: `perf: <short description>`
    - PR body must include:
-     - 💡 What: brief change summary
-     - 🎯 Why: bottleneck being addressed
-     - 📊 Measured improvement: baseline vs after (+% change)
+     - What: brief change summary
+     - Why: bottleneck being addressed
+     - Measured improvement: baseline vs after (+% change)
      - Method: commands, harness, env notes, run counts
      - Tests & verification steps run
      - Risk/rollback plan
@@ -140,7 +140,7 @@ OUTPUTS PER RUN
 - `BASELINE.md` — commands, environment, and baseline numbers
 - 0–1 PR with the optimization, tests, and documentation:
   - branch: `ai/perf-<short>-vX.Y`
-  - PR title: `⚡ perf: <short description>`
+  - PR title: `perf: <short description>`
   - PR body with baseline/after comparisons and verification steps
 - `AFTER.md` — after-measurement and comparison
 - 0–N issues for follow-up or risky items