f97d588042
Move the info popover (intro'd in the previous commit) into a dedicated `frontend/src/components/KBInfoPopover.vue` component so both the document KB header and the FAQ KB header can share the exact same metadata surface. - KnowledgeBase.vue: replace the inline popover and the now-dead helper computeds (kbLastUpdated, kbHasDistinctUpdate, infoCardCapabilities, infoCardChunking, infoCardStats, chunkingStrategyLabel, supportedFileTypesList, accessRoleLabel, accessPermissionSummary) and their CSS with a single <KBInfoPopover> tag. The page still fetches parser engines and forwards the supported file types so the "Accepted formats" row renders for document KBs. - FAQEntryManager.vue: drop the legacy inline meta strip (role tag · share source · last updated) along with the accessRoleLabel / accessPermissionSummary / kbLastUpdated / effectiveKBPermission computeds it only served, and wire the same <KBInfoPopover> into the actions cluster next to the settings button. FAQ KBs don't pass supportedFileTypes so the format row simply hides itself. - KBInfoPopover.vue: self-contained — re-derives access role, shared-binding and chunking config from kbInfo + the org/auth stores. supported-file-types remains an opt-in prop so callers decide whether the parser-engine pipeline is relevant. No user-visible regressions: both pages now render the same Basic / Access / Capabilities / Chunking / Stats / Storage Binding sections, with rows hiding when they don't apply.