Files
computer-playbook/roles/web-app-joomla/meta/rbac.yml
kevinveenbirkenbachandClaude Opus 4.7 c55ad69c41 refactor: drop requirement-file references from code, add doc rule + lint
Strip every `req <NNN>`, `req-<NNN>`, `Requirement <NNN>`,
`requirement-<NNN>`, and `docs/requirements/<NNN>-...md` mention from
non-Markdown source files. Comments anchored to requirement numbers
rot when requirements are renumbered or rewritten and conflate
present-state behaviour (which the comment should describe) with the
audit trail of how the code got there (which belongs in commit
messages, PR descriptions, and the requirement file itself).

* Document the rule in `docs/contributing/documentation.md` under
  "Comments". Code MUST describe the *why* in present-state language;
  contract enforcement lives in tests, not folklore.
* Clean 254 source files across `roles/`, `tests/`, `plugins/`,
  `cli/`, `scripts/`, `utils/`, `group_vars/`, and the repo-root
  `eslint.config.js`. Pure comment / docstring / log-message edits;
  no behavioural change.
* Add `tests/lint/repository/test_no_req_references_in_code.py` to
  enforce the rule going forward across `.js`, `.py`, `.yml`,
  `.yaml`, `.j2`, and `.sh` files. The legacy
  `test_no_stale_requirement_refs.py` is exempt as the only file
  whose purpose is to detect these very tokens.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-10 16:25:22 +02:00

16 lines
598 B
YAML

---
# RBAC declaration for the in-role plg_system_keycloak OIDC plugin
# The plugin maps the Keycloak `groups` claim
# onto Joomla's built-in usergroup IDs:
#
# /roles/web-app-joomla/administrator → Super Users (id 8)
# /roles/web-app-joomla/editor → Editor (id 4)
# /roles/web-app-joomla → Registered (id 2)
#
# `administrator` is the implicit role auto-added by and is
# always present, so only the additional roles below need explicit
# declaration.
roles:
editor:
description: Editor in Joomla — maps onto the built-in `Editor` user-group (id 4).