feat: improve plugin configuration integrity

[catherineluse]

Summary

• consume the shared configuration-completeness status and hard-gate Enable
• list every required setting or secret that blocks enablement
• render declared-but-unset secrets and dedupe secrets from ordinary settings forms
• separate stored secrets unused by the installed version without deleting them
• clarify valid, untested, invalid, and required-not-set secret states
• preview upgrade reconciliation and offer Carry over or Start fresh
• show carried, new-default, reset, dropped, and required-secret status before upgrade

Why

Plugin configuration state was ambiguous and distributed across independent UI checks. Misconfigured fail-closed plugins could be enabled, secrets could render twice, obsolete secrets looked required, and upgrades discarded settings.

Validation

• 233 plugin-management tests across 20 files
• Vue TypeScript type-check
• ESLint on changed files

Companion PRs

• Backend: feat: enforce and preserve plugin configuration multiforum-backend#164
• Scanner manifest: fix: declare scanner secret only once multiforum-plugin-security-attachment-scan#3

Implements the frontend portion of #330.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
multiforum-nuxt-prod	Building	Preview	Jul 19, 2026 1:43am