Add AI administrative transparency and capability status #9058

Goal

Give LibreSign administrators a clear, Nextcloud-native view of AI availability and LibreSign policy state without duplicating provider configuration or inventing trust metadata.

This issue is part of the AI foundation epic.

Administrative experience

The settings UI should explain:

• LibreSign uses AI capabilities configured by the Nextcloud administrator;
• technical availability comes from Nextcloud Task Processing;
• LibreSign policy decides whether each supported LibreSign capability may be used;
• depending on the configured provider, document content may be processed outside the Nextcloud instance;
• provider/model configuration remains in Nextcloud.

Show only capabilities that the current LibreSign version actually knows how to consume.

Do not create dead toggles for roadmap features.

Provider metadata

Display only provider/trust/privacy metadata exposed through supported public Nextcloud contracts.

Do not:

• infer local/remote processing from provider app names;
• maintain a provider trust table;
• implement an Ethical AI Rating locally;
• equate local processing with ethical/trusted processing.

If no authoritative metadata is available, use neutral explanatory language.

UX and prototype requirement

Before final implementation:

• inspect current LibreSign administration/Policy Workbench layout;
• inspect Nextcloud AI administration patterns and official Vue components;
• produce a concrete UI proposal or prototype for capability status, policy entry points and the data-processing notice;
• define empty/unavailable/error states;
• verify that the screen does not imply LibreSign configures the provider.

The interaction should be understandable to an administrator who knows LibreSign but not Task Processing internals.

Contextual documentation

Provide contextual access to the LibreSign documentation where it materially helps administrators understand:

• Nextcloud-side prerequisites;
• LibreSign AI policies;
• data-processing implications;
• unavailable capability troubleshooting.

Use the project's established help affordance where possible rather than adding ad-hoc external links.

Accessibility

Use standard Nextcloud components and preserve:

• keyboard navigation;
• accessible labels/descriptions;
• responsive layout;
• understandable status text independent of color.

Tests

Cover at least:

• no supported AI capability available;
• one supported capability available;
• multiple capabilities with different policy state;
• provider/capability disappears;
• missing optional provider metadata;
• frontend does not display a capability that LibreSign cannot consume;
• policy denial is represented without implying the provider is unavailable.

Use Playwright for important administrator flows when consistent with current settings coverage.

Done when

• Administrators can distinguish technical availability from LibreSign authorization.
• No provider/model credentials or selection are duplicated in LibreSign.
• The data-processing notice is accurate without unsupported trust claims.
• The UX has been prototyped/reviewed before implementation.
• Accessibility and empty/error states are covered.
• Contextual documentation access is available where appropriate.
• Automated tests cover representative capability/policy states.