docs(readme): preserve opencode contributor guidance

- add an OpenCode sync guide link to the README docs matrix

- keep the community project attribution intact

- document that contributor community integrations should move

  into docs pages instead of being dropped

CLAUDE.md

@@ -27,6 +27,10 @@ the docs site, but **do not remove the `## Community Projects` section** or the
 `## Star History` section unless the user explicitly asks for those sections to
 be deleted. Treat both as protected README content.
 
+When a contributor adds a useful community integration section to `README.md`,
+prefer preserving the attribution in `## Community Projects` and moving the
+setup substance into a docs page, rather than deleting the contribution.
+
 Outside provider-specific Gemini and Antigravity docs, avoid using `ccs gemini`
 or `ccs agy` as the primary hero example, default starter route, or generic
 workflow example. Prefer `ccs`, `ccs codex`, `ccs kiro`, `ccs glm`, Droid

README.md

@@ -108,6 +108,7 @@ reference material.
 | Compare OAuth providers, Claude accounts, and API profiles | [Provider Overview](https://docs.ccs.kaitran.ca/providers/concepts/overview) |
 | Learn the dashboard structure and feature pages | [Dashboard Overview](https://docs.ccs.kaitran.ca/features/dashboard/overview) |
 | Configure profiles, paths, and environment variables | [Configuration](https://docs.ccs.kaitran.ca/getting-started/configuration) |
+| Keep OpenCode aligned with your live CCS setup | [OpenCode Sync Plugin](https://docs.ccs.kaitran.ca/features/workflow/opencode-sync) |
 | Browse every command and flag | [CLI Commands](https://docs.ccs.kaitran.ca/reference/cli-commands) |
 | Recover from install, auth, or provider failures | [Troubleshooting](https://docs.ccs.kaitran.ca/reference/troubleshooting) |
 | Understand storage, config, and architecture details | [Reference](https://docs.ccs.kaitran.ca/reference/architecture) |