Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/janssen-server/auth-server/openid-features/consent.md`:
- Around line 26-75: The docs lack Janssen-specific properties, feature flags,
and TUI/CLI configuration steps required by issue `#4732`; add a "Properties &
Feature Flags" subsection listing relevant flags including
consentGatheringScriptBackwardCompatibility (describe behavior: global
highest-level vs per-client resolution) and per-client consent script assignment
fields, provide recommended values and concrete use-cases; add a "TUI
walkthrough" with navigation paths (e.g., Auth Server → Properties →
enabledFeatureFlags and Auth Server → Clients → <client> → Consent Script) and a
"CLI examples" section with sample Config API or oxauth-cli commands to
set/inspect these properties and revoke consents, and note where screenshots
should be inserted for each TUI step; ensure the Customize section links to the
consent-gathering script catalog and demonstrates how to enable per-client
assignment versus backward-compatibility mode.
- Line 28: Update the header string "### End-user self service" to hyphenate the
compound modifier: change it to "### End-user self-service" so the compound
adjective is grammatically correct; locate the header line containing "End-user
self service" and replace it with the hyphenated form.
In `@mkdocs.yml`:
- Around line 619-621: The commented-out git-revision-date-localized plugin in
mkdocs.yml removes site-wide "last updated" timestamps; revert the change by
uncommenting the git-revision-date-localized block (restore enable_creation_date
and type settings) so the plugin is active again, or if the change was
intentional (e.g., CI shallow clone), add a dedicated PR/issue and a clear
comment in mkdocs.yml explaining the reason and linking the PR/issue; ensure the
plugin block name "git-revision-date-localized" and its keys
"enable_creation_date" and "type" are preserved.