[V2][team] Knowledge Base Suggestion - Core feature engine

[kryputh]

Goal

Build the tool's core feature logic inside its isolated folder.

Tool: Knowledge Base Suggestion

Release tier: V2

Audience: team

Required labels

This issue must carry these campaign labels:

• GrantFox OSS
• Maybe Rewarded
• Official Campaign
• Tooling Ecosystem
• V2 Later Tool
• Team Tool

Implementation folder

All work for this issue must stay inside:

text tools\v2\team\knowledge-base-suggestion/

V2 later-release tool. Build the tool as complete isolated work, but do not link it to the main app yet.

Do not modify the main application shell, dashboard layout, navigation system, authentication, wallet core, mail rendering engine, existing inbox architecture, existing routing, Stellar integration core, database schema, or existing design system.

Deliverables

• Create folder-local services or pure helpers for the core behavior.
• Add deterministic fixtures or mocks where external data would otherwise be required.
• Expose only a folder-local API surface for future UI work.

Acceptance criteria

• Core logic is implemented without linking into the main app.
• Inputs, outputs, loading states, and error states are documented.
• No live network calls, secrets, or production data are introduced.
• Files changed by this issue are limited to $rel/.
• The contribution is reviewable as a self-contained mini-product change.

OSS contributor notes

Keep the work small and reviewable. Prefer local fixtures, local docs, local tests, and folder-local components/services/hooks. If the tool needs a future connection to the main mail app, write that as a follow-up issue instead of adding the integration here.