docs: add tracer dashboard command documentation

[swarna1101]

Summary by CodeRabbit

• Documentation
  • Added documentation for an interactive tracer dashboard, including command usage, configuration options (window, topic, count, interval) and examples.
  • Updated README Quick Start / examples with a tracer dashboard invocation.
  • Expanded Health Monitoring docs with a dedicated proxy health command, output details, and visual guides for the dashboard.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

This pull request modifies documentation only: README.md adds the tracer dashboard to the Features list and a Quick Start example; docs/guide.md adds a Tracer Dashboard section with CLI usage, options (--window, --topic, --count, --interval-ms), example invocation, exit instructions, an embedded visualization, and expanded Health Monitoring content including a health CLI example. No source code, runtime logic, or public API changes are included.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Verify CLI syntax, option names and default values match the actual tracer dashboard and health implementations.
• Check for duplicated/contradictory blocks in docs/guide.md (there appears to be repeated Tracer Dashboard content).
• Confirm image path, alt text, and rendering in the documentation site.
• Ensure formatting and style are consistent with existing docs.

Suggested reviewers

• hpsing

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Security Considerations	⚠️ Warning	Tracer dashboard command accepts unvalidated integer parameters (--count, --interval-ms, --size) without bounds checks, enabling potential denial-of-service attacks.	Implement input validation: enforce maximum limits on --count (≤10,000), --interval-ms (1-60,000 range), --size (≤10MB); return clear error messages and document safe defaults.

✅ Passed checks (7 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main changes: documentation updates for the tracer dashboard command. It is concise (48 characters), descriptive, and directly related to the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Go Build And Test Rationale	✅ Passed	PR modifies only documentation files (README.md and docs/guide.md) with no Go code logic changes, making the Go build and test rationale check non-applicable.
Concurrency Safety	✅ Passed	Concurrency safety check not applicable; PR contains only documentation changes to README.md and docs/guide.md with no code implementation or runtime logic modifications.
Public Api Changes	✅ Passed	PR contains only documentation changes to README.md and docs/guide.md with no modifications to public APIs, exported types, or functions.
Rust Best Practices	✅ Passed	The custom check for Rust best practices is not applicable to this PR. The repository is a Go project with only documentation changes, containing no Rust files or code modifications.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch docs/tracer-dashboard

---

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

[coderabbitai]

Actionable comments posted: 2

📜 Review details

Configuration used: Repository: getoptimum/coderabbit/.coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3e601a0 and ee30347.

📒 Files selected for processing (1)

• docs/guide.md (1 hunks)

🧰 Additional context used

📓 Path-based instructions (2)

**/*

⚙️ CodeRabbit configuration file

**/*: When you find the same underlying issue in multiple locations (same pattern, same fix):

• Do NOT post separate comments for each occurrence.
• Post a single primary comment on the first occurrence.
• In that comment, include a short list of “Also at: file:line” references
  for the other locations (e.g. 'Also at: foo.go:42, bar.go:17').
  Prioritize signal over volume: one strong comment that references multiple
  locations is preferred over many near-identical comments.

Files:

• docs/guide.md

**/*.md

⚙️ CodeRabbit configuration file

**/*.md: - Technical accuracy first; keep commands copy-pastable; prefer minimal prerequisites.

Files:

• docs/guide.md

🪛 markdownlint-cli2 (0.18.1)

docs/guide.md

486-486: Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)

[coderabbitai]

🧹 Nitpick | 🔵 Trivial

Clarify --interval-ms description for consistency and explicitness.

The description "Interval between published messages in ms" is clear in context, but for full consistency with the preceding options (which explicitly mention "auto-publishing demo messages" and "auto-publish"), consider rephrasing to state "Interval between auto-published demo messages in ms". This matches the past reviewer's suggestion to be explicit about what messages are referenced. [Based on past review comment]

🔎 Apply this diff:

- `--interval-ms`: Interval between published messages in ms (default: `500`)
+ `--interval-ms`: Interval between auto-published demo messages in ms (default: `500`)

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	- `--interval-ms`: Interval between published messages in ms (default: `500`)
	- `--interval-ms`: Interval between auto-published demo messages in ms (default: `500`)

🤖 Prompt for AI Agents

In docs/guide.md around line 483, the `--interval-ms` option text is ambiguous
compared to preceding options; update the description to explicitly read
"Interval between auto-published demo messages in ms (default: `500`)" so it
clearly matches the phrasing used for auto-publishing options and removes any
ambiguity about which messages are referenced.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Add blank line before code fence to comply with Markdown standards.

The fenced code block needs a blank line separating it from the preceding text per MD031.

🔎 Apply this diff:

 **Example:**
+
 ```sh
 ./mump2p tracer dashboard --topic=metrics --count=100 --interval-ms=200

</details>

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 markdownlint-cli2 (0.18.1)</summary>

486-486: Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)

</details>

</details>

<details>
<summary>🤖 Prompt for AI Agents</summary>

In docs/guide.md around lines 485-486, the fenced code block lacks a blank line
separating it from the preceding text which violates MD031; insert a single
blank line immediately before the triple-backtick opening fence so the paragraph
and the code fence are separated, then ensure the code fence contains the
intended shell block and closing backticks remain unchanged.

</details>

<!-- fingerprinting:phantom:triton:mongoose -->

<!-- This is an auto-generated comment by CodeRabbit -->