Fix Mermaid startup sequence rendering for PR #45 follow-up

[gamblecodezcom]

User description

Motivation

• Fix a GitHub Mermaid parse error so the README's startup flow for prod-run.sh renders correctly and documents the intended runtime behavior.

Description

• Replace the broken diagram with a valid sequenceDiagram under Startup flow (prod-run.sh) and add a short note to keep the deploy directory casing as Runewager to match systemd expectations.

Testing

• Ran npm run check and npm test, and both completed successfully (syntax check passed and all 4 tests passed).

---

Codex Task

---

CodeAnt-AI Description

Document prod-run.sh startup flow with sequence diagram

What Changed

• Added a startup sequence diagram for prod-run.sh that shows operator actions and script responsibilities
• Clarifies runtime validations (directories, dependencies, .env, logrotate/cron/systemd) performed before launch
• Shows divergent behavior: when run under systemd the app is executed in the foreground; when run from a shell it checks for existing bot processes and launches the app in the background with nohup, then re-checks process status after 15s

Impact

✅ Clearer startup steps for operators
✅ Fewer deployment errors from misconfigured runs
✅ Shorter troubleshooting when service fails to start

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[codeant-ai]

CodeAnt AI is reviewing your PR.

[coderabbitai]

Caution

Review failed

The head commit changed during the review from 68a8bb3 to c9549e5.

---

Note

🎁 Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codeant-ai]

CodeAnt AI finished reviewing your PR.