Rewrite README for Commander KV architecture

[Iktahana]

Summary

• Rewrites README from outdated "Access Authorization Service" to reflect current Commander project
• Documents the KV storage abstraction with BBolt/MongoDB/Redis backends
• Updates badges, project structure, API endpoints, configuration, and Docker deployment instructions
• Corrects license reference to BSL 1.1

Test plan

• Verify badge links resolve to stayforge/commander
• Confirm API endpoint examples match current routes
• Check Docker Compose commands work as documented

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation

  • Project renamed "Commander" across docs; Quick Start, architecture, and API/health docs rewritten to describe pluggable storage backends (BBolt, MongoDB, Redis) and updated install/build/run instructions.
  • Docker-focused deployment guidance and prerequisites updated; license naming revised.

• Chores

  • Docker Hub publish flow activated and fully implemented for automated image build, tag, and push using repository credentials.

[coderabbitai]

📝 Walkthrough

Walkthrough

Activates a new push-dockerhub job in the release workflow that logs into Docker Hub, downloads and loads the built image artifact, tags and pushes images; and replaces README content with a backend-agnostic, pluggable KV storage architecture and updated project docs.

Changes

Cohort / File(s)	Summary
Release workflow ​.github/workflows/release.yml	Adds an active push-dockerhub job (needs: build) with contents: read permission. Uses docker/setup-buildx-action@v3, docker/login-action@v3 (credentials: secrets.DOCKER_USERNAME / secrets.DOCKER_TOKEN), downloads the docker-image artifact, loads it, and tags/pushes versioned + latest images to Docker Hub.
Repository documentation README.md	Replaces prior service-specific docs with a pluggable KV storage architecture (BBolt, MongoDB, Redis), renames service references to commander, updates Quick Start, prerequisites (Go 1.25.5+), build/run instructions, Docker guidance, and overall project structure. Significant content restructuring and command examples updated.

Sequence Diagram(s)

sequenceDiagram
    participant Runner as GitHub Actions Runner<br/>rgba(52,152,219,0.5)
    participant ArtifactStore as Actions Artifact Store<br/>rgba(46,204,113,0.5)
    participant DockerEngine as Docker Engine on Runner<br/>rgba(155,89,182,0.5)
    participant DockerHub as Docker Hub Registry<br/>rgba(241,196,15,0.5)

    Runner->>DockerEngine: setup buildx
    Runner->>DockerHub: login (DOCKER_USERNAME/DOCKER_TOKEN)
    Runner->>ArtifactStore: download artifact "docker-image"
    ArtifactStore-->>Runner: image.tar.gz
    Runner->>DockerEngine: gunzip -c image.tar.gz | docker load
    Runner->>DockerEngine: docker tag image:version, docker tag image:latest
    DockerEngine->>DockerHub: docker push image:version / image:latest
    DockerHub-->>Runner: push confirmation

Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Possibly related PRs

• Dev #13 — Modifies the same push-dockerhub job; differs in the secret variable name choice (DOCKER_TOKEN vs DOCKER_PASSWORD), indicating closely related changes to Docker Hub publish steps.

Poem

🐇 I hopped through CI with a gentle thump,
Pulled an artifact, gave Docker a bump,
Tagged version and latest with a cheer,
KV backends singing, the README clear —
A little rabbit stampede of deploy delight!

🚥 Pre-merge checks | ✅ 3

✅ 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 'Rewrite README for Commander KV architecture' accurately captures the primary change: a comprehensive README rewrite to document the Commander project's KV storage abstraction and backends, replacing outdated Access Authorization Service content.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch dev

---

No actionable comments were generated in the recent review. 🎉

---

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

[coderabbitai]

Actionable comments posted: 3

🤖 Fix all issues with AI agents

In @.github/workflows/release.yml:
- Around line 125-126: The workflow currently uses the secret key
DOCKER_PASSWORD for Docker Hub authentication; replace it with a token-based
secret (e.g., DOCKER_TOKEN) and update the workflow reference to use that secret
for the password field while keeping username as ${{ secrets.DOCKER_USERNAME }};
change any mentions of DOCKER_PASSWORD to DOCKER_TOKEN in the workflow and docs,
and verify the CI secret is populated with a Docker Hub personal access token
(PAT) rather than an account password.

In `@README.md`:
- Around line 15-30: The fenced ASCII diagram block in README.md lacks a
language specifier; update the opening fence of the diagram's code block (the
triple-backtick that precedes the ASCII art) to include a language token such as
text or plaintext (e.g., change ``` to ```text) so the diagram block is
explicitly marked and satisfies linting/accessibility rules.
- Around line 40-63: The fenced code block that shows the project tree in
README.md lacks a language specifier; update the opening triple-backticks for
the project structure block (the tree diagram code block starting with ".\n├──
cmd/") to include a language specifier such as "text" (change ``` to ```text) so
the block is explicitly marked as plain text.

🧹 Nitpick comments (1)

.github/workflows/release.yml (1)

115-118: Consider adding explicit permissions block for consistency.

The push-ghcr job (line 84-86) explicitly declares permissions, but this job omits it. While Docker Hub authentication uses repository secrets rather than GitHub tokens, adding an explicit minimal permissions block (contents: read) improves security posture and maintains consistency across jobs.

📝 Suggested addition

   push-dockerhub:
     needs: build
     runs-on: ubuntu-latest
+    permissions:
+      contents: read
     steps:

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

The merge-base changed after approval.