3 Commits

Include renames

Author	SHA1	Message	Date
kevinveenbirkenbachandClaude Fable 5	da598a2d67	feat(readme): roles overview table with homepage/video backfill ... Add cli.build.readme.overview (make readme-index / make docs) rendering a roles overview in the root README: Name, Lifecycle, Homepage, Video, Description, Integrated with, Install. New info-media lint requires homepage + video in every invokable role's meta/info.yml (opt out via '# nocheck: info-media' in meta/main.yml); backfilled 147 roles with researched, adversarially-verified homepages and official videos. Retire the 'unsupported' lifecycle value: fold it into 'eol' as a valid live end-of-life status (shipped but untested/unmaintained) across the stage lists, symbol glossary, allow-list lint and docs. Retag confluence, jira, minio, phpldapadmin to eol and magento to pre-alpha. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-07-17 19:10:01 +02:00
kevinveenbirkenbachandClaude Opus 4.7	2a023ca6a1	chore(lint): autoformat strict-failure semantics + claude.sh rename ... * scripts/lint/autoformat.sh: - rename run_sort_claude_settings worker to run_claude (matches the renamed scripts/lint/claude.sh). - drop the EXIT trap that wiped status_dir; cleanup happens explicitly after `wait` returns, so a parallel worker that interrupts the parent never races a vanished status dir. - each worker now captures its tool's exit code and writes one of OK / SKIP / FAIL. Tolerated `expected violations remain`-style exits (markdownlint-cli2 rc≤1, ansible-lint rc≤2) still count as OK; only real failures count as FAIL. - all workers run to completion regardless of individual tool failures (so the user always sees the full picture); after the summary, the script exits 1 if any worker reported FAIL. * scripts/lint/sort_claude_settings.sh -> scripts/lint/claude.sh (history preserved via git mv); update test_claude_settings_sorted.py fix-hint accordingly. Plus working-tree drift across roles/, group_vars/, inventories/, requirements/, and .pre-commit-config.yaml accumulated from the make-test setup phase regenerating generated artefacts during recent test runs. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-09 01:30:49 +02:00
kevinveenbirkenbachandClaude Opus 4.7	91c57e0471	feat(req-013): alpha-to-beta promotion for 13 in-scope roles ... Promote akaunting, baserow, bluesky, bookwyrm, bridgy-fed, flowise, fusiondirectory, jenkins, joomla, minio, postmarks, libretranslate, xmpp from `lifecycle: alpha` to `lifecycle: beta` per requirement 013. socialhome stays alpha (operator-excluded). SSO/LDAP integration per role: - minio + jenkins + joomla + fusiondirectory: native first-party paths (MINIO_IDENTITY_OPENID/_LDAP, oic-auth + ldap + role-strategy JCasC, plg_system_keycloak, LDAP-as-storage). All V0+V1 verified. - akaunting, baserow, bookwyrm, flowise, postmarks, libretranslate: oauth2-proxy perimeter gate as universal glue path. Native in-app OIDC integrations deferred to follow-up issues #219 (Baserow), #220 (BookWyrm), #221 (Akaunting). - bluesky: variant A+ login-broker (oauth2-proxy → broker → social-app) with AES-256-GCM-encrypted PDS app-passwords cached in-process (Keycloak user-attribute storage caused LDAP federation conflicts that broke other realm-clients' OIDC logins). - xmpp: native ejabberd LDAP backend for both variants (mod_oauth2_client is contrib-only and deferred). - bridgy-fed: documented SSO/LDAP/RBAC exception (federated source- platform auth, no local user table). Project-wide bugfixes: - web-app-oauth2-proxy: propagate X-Forwarded-User / -Preferred-Username / -Email / -Groups via auth_request_set bridge (set_xauthrequest + pass_user_headers in cfg + nginx headers in following_directives.conf). Benefits all 8 oauth2-proxy consumers. - scripts/tests/deploy/local/deploy/fresh-kept-app.sh: bake `RUNTIME=dev` into the matrix-init host vars so the Playwright E2E gate fires (was silently skipped on kept-deploys). From-scratch role implementations: jenkins (JCasC + plugin pre-bake + JVM cacerts CA-trust entrypoint), fusiondirectory (LDAP-as-storage compose), xmpp (ejabberd LDAP backend ejabberd.yml). Verification: - Per-role baseline: each in-scope role passed standalone V0/V1 Playwright suites green. - Multi-app fresh-purged-apps over all 13 in-scope roles (FULL_CYCLE=true): Pass 1 sync + Pass 2 async both `failed=0`, every role's Playwright suite green. Doc 013 acceptance section reflects the divergences (oauth2-proxy glue path, in-memory bluesky cache, deferred contrib modules) with explicit follow-up issue references. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-02 12:47:01 +02:00