Public roadmap and "good first contribution" guidance — how can community contributors plug in?

Hi maintainers,

Loving the v1.1.0 direction (K8s-native control plane, Hermes runtime, the
hiclaw CLI replacing shell scripts). I'm building a small company on top of
HiClaw + AgentScope and would like to contribute back, but I'm unclear on:
## Roadmap visibility
1. Is there a public roadmap beyond the changelog? I see the recent blog
posts (1.1.0 release, K8s-native architecture, declarative resource
management) but no consolidated "next 6 months" view.
2. What are the current focus areas for v1.2 / v1.3? Helps me avoid
duplicating work the team is already planning.
3. Are there any in-flight RFCs or design docs that aren't yet code?

## Contribution surface
4. Is there a "good first issue" or "help wanted" label triage?
5. Are there areas where community PRs are explicitly welcome vs.
6. maintainer-only (e.g., new Worker runtimes, new Manager skills,
controller internals, Helm chart improvements, docs)?
6. What's the preferred shape for a new community-contributed Worker skill
under `manager/agent/worker-skills/`?

## Specific contribution candidates I'm considering
(Happy to drop any of these if they conflict with planned work)
- [ ]
- [ ] **Hermes ↔ Hindsight memory wiring**: HiClaw's Hermes image
pins v2026.4.16 which includes Hindsight as a native memory
provider, but the bridge in `hermes/src/hermes_worker/bridge.py`
doesn't enable it by default. I'd propose a `HICLAW_HERMES_MEMORY`
env var that the bridge writes into `~/.hermes/config.yaml` as
`memory.provider: hindsight`. ~50 LOC change.

- [ ] **CoPaw (now QwenPaw) ↔ Hindsight bridge**: AgentScope's ReMe is
the current memory primitive. A `reme-hindsight-backend` plugin
would unify all three runtimes under Hindsight. Could live in
`copaw/` or upstream in QwenPaw — your call on placement.

- [ ] **`accessEntries` documentation**: Could clarify in the CRD
reference that `accessEntries` is a no-op in single-tenant
local mode without a credential-provider sidecar (caught me by
surprise reading types.go:34-35).

- [ ] **CRD reference docs**: A generated CRD schema reference (from
`api/v1beta1/types.go`) would help operators. Happy to wire up
`kubebuilder:docs` or similar.

- [ ] **Skill format spec**: A short doc formalizing the SKILL.md
frontmatter conventions used in `manager/agent/skills/` and
`manager/agent/worker-skills/`. New contributors (myself
included) currently learn by reading existing skills.

## Process questions
7. Is there a Discord / Slack where contributors hang out beyond GitHub?
(I see the Discord link in the README but want to confirm it's
active for dev discussion.)
8. Do you accept docs-only PRs to fix outdated info (e.g., the README
still mentions QwenPaw alongside CoPaw — happy to send a PR that
reflects the rebrand consistently)?
9. Is there a contributor agreement (CLA / DCO) I should sign?

Thanks for the work — happy to start small and ramp up.