docs(maintainers): list website/ in the docs map and align CONTRIBUTING

Setup, configuration and deployment docs live in website/, which is
published as the docs site, but the map sent them to /docs and did not
list website/ at all. Add it, and drop the "when those paths are used"
hedge on /specs, which exists.

CODEOWNERS has no rules until #593 settles the per-area map; say so
instead of describing reviewers it does not list.

CONTRIBUTING.md still had a single maintainer curating main, which the
Release Maintainer section replaces. Name the Product Owner's GitHub
account and say where a community proposal starts, matching the
existing issue forms.

docs/maintainers/product-and-features.md

@@ -1,6 +1,6 @@
 # Product and feature proposals
 
-Pewds is the Product Owner for Odysseus and has final authority over product direction. Maintainers own technical feasibility, implementation, and safety.
+Pewds ([@pewdiepie-archdaemon](https://github.com/pewdiepie-archdaemon)) is the Product Owner for Odysseus and has final authority over product direction. Maintainers own technical feasibility, implementation, and safety.
 
 ## Which changes require product approval?
 
@@ -27,6 +27,8 @@ A Product Owner proposal is already product-approved; it is not automatically te
 
 ## Community or maintainer initiated
 
+Community proposals start as a Feature Request issue. Check [ROADMAP.md](../../ROADMAP.md) and existing issues first; take early ideas to [Discussions](https://github.com/odysseus-dev/odysseus/discussions/categories/ideas).
+
 ```text
 Feature proposal
     -> Product Owner accepts / rejects, where approval is required