Add glossary tooltips for protocol terms across the create wizard and detail pages

[1nonlypiece]

📌 Description

Terms like "penalty bps", "compliance score", "drawdown", "attestation", and
"early exit" appear throughout the create wizard and commitment detail components
with no inline explanation. New users must leave the flow to understand them.

This issue adds a reusable glossary tooltip keyed by term.

Goal: make protocol terminology self-explanatory in context.

🎯 Requirements and Context

• A GlossaryTerm component renders an info affordance with an accessible
  tooltip/popover (built on the Dialog/popover primitives or a focusable
  tooltip).
• Definitions live in a single src/lib/glossary.ts map so copy stays
  consistent.
• Apply to key labels in CreateCommitmentStepConfigure.tsx,
  CommitmentDetailParameters, and CommitmentDetailAllocationConstraints.
• Keyboard and screen-reader accessible (aria-describedby).

🛠️ Suggested Execution

1. Fork the repo and create a branch

git checkout -b feature/glossary-tooltips

2. Implement changes

• New src/lib/glossary.ts and src/components/GlossaryTerm.tsx.
• Apply to the configure step and detail parameter/constraint components.
• Add src/components/__tests__/GlossaryTerm.test.tsx (RTL).
• Add docs/GLOSSARY.md.

3. Test and commit

• Run the repo test suite: pnpm test
• Cover edge cases: unknown term fallback, open/close via keyboard, multiple
  tooltips on a page.

Example commit message

feat: glossary tooltips for protocol terms in create and detail views

✅ Guidelines

• Minimum 95% test coverage on new/changed lines.
• Clear, reviewer-friendly documentation.
• Timeframe: 96 hours.

🏷️ Labels

type-feature · area-frontend · MAYBE REWARDED · GRANTFOX OSS ·
OFFICIAL CAMPAIGN

💬 Community & Support

• Join the CommitLabs contributor Discord: https://discord.gg/WV7tdYkJk
• Please introduce yourself before you start so we can avoid duplicate work.

[AugistineCreates]

@AugistineCreates has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Please assign. You will get a pr today

ℹ️ Repo Maintainers: To accept this application, review their application or assign @AugistineCreates to this issue.

[drips-wave]

Congratulations, @AugistineCreates! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @AugistineCreates: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign campaign!

@AugistineCreates's PR #912 was approved and merged by @1nonlypiece.

🏆 @AugistineCreates: You earned 40 FoxPoints for this contribution! Your current tier: Builder (1,991 total points). Track your full progress on GrantFox.

👏 Great work, @AugistineCreates! Keep contributing to Commitlabs-Org.

[drips-wave]

This issue has been completed by @AugistineCreates as part of the Stellar Wave Program's 6th Wave 🥳

😎 @AugistineCreates: You earned 100 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.