Taking over the Manual namespace

Hi @g-raph,

I'd like to ask whether you'd be willing to hand over the `manual` namespace.

From the outside the project looks finished with: created in 2017, no releases, no issues. If you're planning to come back to it, please just say so in a comment here, I'll withdraw the request and find another name.

If not, here's what I'd like to use it for:

We've built a site operations manual system for admin users: the manual pages are markdown files living in the site's codebase, rendered inside the admin theme as a navigable hierarchy. It's aimed at the agency/freelancer → client handover situation, where someone has to document a site for the people who will actually run it. Authoring is done in the editor with AI agent assistance, so the manual is written and updated alongside the code it documents. We're running it on client sites and want to release it as contrib.

The `manual` short name is the natural fit for it.

On preserving what's there: per policy nothing would be deleted. The existing branch and commit history stay, our work would go on a new branch, and I'd add a note to the project page explaining that the namespace was repurposed.

I've also sent you a message via the contact tab pointing at this issue. Per the Drupal.org procedure for taking over an obsolete project's namespace, if there's no reply here within 14 days I'll move this issue to the Drupal.org project ownership queue.

Thanks,
Nodar.