docs(collection): document all roles and fix metadata drift

Replace ansible-galaxy init placeholders across the collection and
correct documentation that drifted from the code, after a multi-agent
review of every role README against its defaults, tasks and templates.

Collection level:
- README: role table for all 16 roles, requirements and role-ordering
- galaxy.yml: declare community.docker and community.general deps,
  real description/tags/urls; normalize license to MIT-0
- meta/runtime.yml: requires_ansible '>=2.15.0'
- plugins/README: document the homarr_layout filter and
  garage_credentials lookup instead of scaffold boilerplate

Per-role meta/main.yml and README for the placeholder roles
(389ds, authentik, authentik_outpost_ldap, base, collabora, drawio,
garage, homarr, httpbin, keycloak, nextcloud, opencloud, traefik).

Correctness fixes found during review:
- keycloak: wrong domain default, drop invented keycloak_cert_resolver,
  document the provisioning feature
- garage: root_domain is .s3.<first-entry>, not the bare domain
- opnform: jwt/front_api secrets use `openssl rand -hex 32`; align the
  validation fail_msg in tasks/main.yml accordingly
- send: S3 example references garage_s3_domains[0] (was singular)
- opencloud: document required opencloud_wopi_domain

License normalized to MIT-0 across galaxy.yml, role meta and READMEs to
match the SPDX headers.

roles/389ds/README.md

@@ -1,38 +1,43 @@
-Role Name
-=========
+# 389ds
 
-A brief description of the role goes here.
+Deploys [389 Directory Server](https://www.port389.org/) (`389ds/dirsrv`)
+as an LDAP directory via Docker Compose. After the container starts, the
+role creates the configured suffix and a set of base organizational
+units (e.g. `users`, `groups`).
 
-Requirements
-------------
+## Requirements
 
-Any pre-requisites that may not be covered by Ansible itself or the role should be mentioned here. For instance, if the role uses the EC2 module, it may be a good idea to mention in this section that the boto package is required.
+- Docker and Docker Compose on the target host (e.g. via
+  `digitalboard.core.base`)
+- Ansible collection: `community.docker`
 
-Role Variables
---------------
+## Role variables
 
-A description of the settable variables for this role should go here, including any variables that are in defaults/main.yml, vars/main.yml, and any variables that can/should be set via parameters to the role. Any variables that are read from other roles and/or the global scope (ie. hostvars, group vars, etc.) should be mentioned here as well.
+| Variable | Default | Description |
+| --- | --- | --- |
+| `ds389_image` | `docker.io/389ds/dirsrv:3.1` | Container image. |
+| `ds389_suffix` | `dc=example,dc=com` | Root suffix of the directory. |
+| `ds389_root_dn` | `cn=Directory Manager` | Directory Manager bind DN. |
+| `ds389_root_password` | `changeme` | Directory Manager password — **override this**. |
+| `ds389_instance_name` | `localhost` | Directory server instance name (slapd config dir). |
+| `ds389_hostname` | `389ds` | Container hostname (defaults to `ds389_service_name`). |
+| `ds389_backend_network` | `backend` | Docker network LDAP clients connect over (created by Compose). |
+| `ds389_ldap_port` | `3389` | Published LDAP port (container port 3389). |
+| `ds389_ldaps_port` | `3636` | Published LDAPS port (container port 3636). |
+| `ds389_base_ous` | `[users, groups]` | Base OUs created after startup. |
 
-Dependencies
-------------
+## Example
 
-A list of other roles hosted on Galaxy should go here, plus any details in regards to parameters that may need to be set for other roles, or variables that are used from other roles.
+```yaml
+- hosts: directory
+  become: true
+  roles:
+    - role: digitalboard.core.389ds
+      vars:
+        ds389_suffix: "dc=example,dc=org"
+        ds389_root_password: "{{ vault_ds389_root_password }}"
+```
 
-Example Playbook
-----------------
+## License
 
-Including an example of how to use your role (for instance, with variables passed in as parameters) is always nice for users too:
-
-    - hosts: servers
-      roles:
-         - { role: username.rolename, x: 42 }
-
-License
--------
-
-BSD
-
-Author Information
-------------------
-
-An optional section for the role authors to include contact information, or a website (HTML is not allowed).
+MIT-0

roles/389ds/meta/main.yml

@@ -1,35 +1,26 @@
 #SPDX-License-Identifier: MIT-0
 galaxy_info:
-  author: your name
-  description: your role description
-  company: your company (optional)
+  author: digitalboard
+  description: Deploy 389 Directory Server (LDAP) via Docker Compose
+  company: Digitalboard
+  license: MIT-0
 
-  # If the issue tracker for your role is not on github, uncomment the
-  # next line and provide a value
-  # issue_tracker_url: http://example.com/issue/tracker
+  min_ansible_version: "2.14"
 
-  # Choose a valid license ID from https://spdx.org - some suggested licenses:
-  # - BSD-3-Clause (default)
-  # - MIT
-  # - GPL-2.0-or-later
-  # - GPL-3.0-only
-  # - Apache-2.0
-  # - CC-BY-4.0
-  license: license (GPL-2.0-or-later, MIT, etc)
+  platforms:
+    - name: Debian
+      versions:
+        - bookworm
+    - name: Ubuntu
+      versions:
+        - jammy
+        - noble
 
-  min_ansible_version: 2.2
-
-  # If this a Container Enabled role, provide the minimum Ansible Container version.
-  # min_ansible_container_version:
-
-  galaxy_tags: []
-    # List tags for your role here, one per line. A tag is a keyword that describes
-    # and categorizes the role. Users find roles by searching for tags. Be sure to
-    # remove the '[]' above, if you add tags to this list.
-    #
-    # NOTE: A tag is limited to a single word comprised of alphanumeric characters.
-    #       Maximum 20 tags per role.
+  galaxy_tags:
+    - 389ds
+    - ldap
+    - directory
+    - docker
+    - digitalboard
 
 dependencies: []
-  # List your role dependencies here, one per line. Be sure to remove the '[]' above,
-  # if you add dependencies to this list.