Enhance documentation following jira-cli best practices

[Copilot]

Updated README from minimal usage notes to comprehensive documentation modeled after jira-cli's structure.

Changes

• Installation: Platform-specific download commands for all supported binaries (Linux 386/amd64/arm64, macOS Intel/ARM), verification steps, and build-from-source instructions
• Usage: Expanded examples showing server startup with various flag combinations, web interface access, and command-line options reference
• Features: Documented multi-repo scanning, real-time polling, untracked file support, and 5MB size limit
• Troubleshooting: Common issues (port conflicts, missing diffs, permissions) with solutions

README grew from 22 to 158 lines with no code changes.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• https://api.github.com/repos/kitproj/diff-server/releases/tags/v0.0.1
  • Triggering command: curl -s REDACTED (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

Look at jira-cli and fully update the docs using that as a good example.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.