docs(backend): add product intro and control-plane scope to README

[Maxima24]

1. What changed?

README.md only. Added the Clipit product intro, the status note, a "Why" section, a "Where this service fits" section and an Author section. Run instructions, test notes, layout and checks are unchanged.

2. Why?

The README said what the backend does but not what the product is or where the backend sits in it.

3. Which architecture boundary moved?

None. The new section restates ADR-001: this is the control plane and never accepts, relays or stores clipboard content.

4. How was it tested?

Docs-only change. No code, so no test suites were run.

5. Security / privacy implications

None. No secrets or config touched. Left out the draft's "no authentication between peers" limitation because the backend does pairing and signed peer rosters.

6. What is left?

The Go agent material (diagram, build steps, status checklist, relay fallback) belongs in the agent's README or a top-level README on main.

---

Checklist

• PR title is Conventional Commits.
• Security-sensitive change → tests added (n/a, docs only).
• Invalid-vector conformance still passes (n/a, docs only).
• No new dependency.
• No secrets/tokens/private keys/.env committed.
• No contract change.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
code-paste	Error		Sep 22, 2026 9:40am UTC