Add Local Docker deployment guide

[sergeyklay]

🎯 Scope & Context

Type: Chore

Intent: Provide comprehensive documentation for local Docker deployment of the Oar project, enabling developers to quickly set up and run the application in Docker containers with persistent data volumes for development and testing purposes.

🧭 Reviewer Guide

Entry Point: docs/development/002-local-docker.md

Complexity: Low

Estimated Review Time: ~20 minutes

Sensitive Areas: None - documentation review focuses on clarity, accuracy of Docker commands, completeness of prerequisites, and correctness of configuration examples.

⚠️ Risk Assessment

• Breaking Changes: No - all modifications are documentation additions with no functional impact to codebase or build process.
• Migrations/State: No - documentation only, no migration or state management required.

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds a new documentation file at docs/development/002-local-docker.md describing local Docker deployment: goal, prerequisites, step‑by‑step build and run commands, environment/configuration (env vars, volumes), verification steps, and troubleshooting. Also updates .cursor/commands/document.md to standardize list formatting (dash → asterisk), adjust indentation/reflow, add bullets under Output Format (writing/context rules and explicit fenced-code-language), and replace the “Using Rules (CRITICAL)” header with bulleted guidance. No code changes or public API/exported-entity modifications.

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Add Local Docker deployment guide' directly and accurately summarizes the main change: a new documentation file for local Docker deployment.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

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

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 54e5639 and a5e2cd9.

📒 Files selected for processing (2)

• .cursor/commands/document.md (1 hunks)
• docs/development/002-local-docker.md (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• .cursor/commands/document.md

🚧 Files skipped from review as they are similar to previous changes (1)

• docs/development/002-local-docker.md

---

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 85.77%. Comparing base (ede6ef3) to head (a5e2cd9).
⚠️ Report is 2 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #31   +/-   ##
=======================================
  Coverage   85.77%   85.77%           
=======================================
  Files          12       12           
  Lines        1631     1631           
  Branches       76      106   +30     
=======================================
  Hits         1399     1399           
  Misses        232      232           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ede6ef3 and 54e5639.

📒 Files selected for processing (1)

• docs/development/002-local-docker.md (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

**/*.md

📄 CodeRabbit inference engine (.cursor/rules/writing.mdc)

**/*.md: Write like humans speak. Avoid corporate jargon and marketing fluff.
Be confident and direct. Avoid softening phrases like "I think," "maybe," or "could."
Use active voice instead of passive voice.
Use positive phrasing—say what something is rather than what it isn't.
Say "you" more than "we" when addressing external audiences.
Use contractions like "I'll," "won't," and "can't" for a warmer tone.
Be specific with facts and data instead of vague superlatives.
Back up claims with concrete examples or metrics.
Highlight customers and community members over company achievements.
Use realistic, product-based examples instead of foo/bar/baz in code.
Make content concrete, visual, and falsifiable.
Make a promise in the title so readers know exactly what they'll get if they click.
Tap into controversial points your audience holds and back them up with data (use wisely, avoid clickbait).
Share something uniquely helpful that makes readers better at meaningful aspects of their lives.
Avoid vague titles like "My Thoughts On XYZ." Titles should be opinions or shareable facts.
Write placeholder titles first, complete the content, then spend time iterating on titles at the end.
Replace "a bit" with more specific language.
Replace "a little" with more specific language.
Remove "actually/actual" from markdown documentation.
Remove "agile" from markdown documentation.
Remove "arguably" from markdown documentation.
Replace "assistance" with "help" in markdown documentation.
Replace "attempt" with "try" in markdown documentation.
Remove "battle tested" from markdown documentation.
Replace "best practices" with "proven approaches" in markdown documentation.
Replace "blazing fast/lightning fast" with specific metrics like "build XX% faster" in markdown documentation.
Remove "business logic" from markdown documentation.
Remove "cognitive load" from markdown documentation.
Replace "commence" with "start" in markdown documentation.
Replace "delve" with "go into" in markdow...

Files:

• docs/development/002-local-docker.md

---

⚙️ CodeRabbit configuration file

**/*.md: 1. Consider the file './AGENTS.md' the overview/introduction of the project. 2. When reviewing the file markdown files, they should be linted with help
from the tools markdownlint and languagetool, pointing out any issues.
3. You may assume the markdown files will contain GitHub flavor Markdown.

Files:

• docs/development/002-local-docker.md

🪛 markdownlint-cli2 (0.18.1)

docs/development/002-local-docker.md

95-95: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

🔇 Additional comments (1)

docs/development/002-local-docker.md (1)

1-152: Document is clear and practical—nicely done.

The guide is direct, specific, and avoids the usual documentation fluff. You've got realistic examples (actual Docker commands, port numbers, file paths), practical troubleshooting that covers real pain points, and you consistently address readers as "you" instead of corporate plural. The sections flow logically from build → run → verify → configure → troubleshoot. Tables are well-organized and the flag breakdown is helpful for someone new to Docker.

Only fix: the MD040 linting issue on line 95.