[V1][team] Customer Support Macro Tool - Architecture and folder contract

[kryputh]

Goal

Create the isolated architecture contract for this tool as a self-contained mini-product.

Tool: Customer Support Macro Tool

Release tier: V1

Audience: team

Required labels

This issue must carry these campaign labels:

• GrantFox OSS
• Maybe Rewarded
• Official Campaign
• Tooling Ecosystem
• V1 Launch Tool
• Team Tool

Implementation folder

All work for this issue must stay inside:

text tools\v1\team\customer-support-macro-tool/

V1 launch-with-mail tool. Build the tool so it can be ready for launch, but keep the work isolated until an explicit integration issue links it.

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

• Define internal module boundaries for components, services, hooks, tests, and docs.
• Document data ownership, dependencies, and integration constraints.
• Add folder-local architecture notes without touching core app files.

Acceptance criteria

• The tool has a clear folder-local architecture plan.
• The issue work does not modify the main app shell, routing, inbox architecture, wallet core, Stellar core, or design system.
• The specs explain what future contributors may and may not change.
• 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.

[123xiaode456-boop]

/attempt #1195

[clintjeff2]

Hello, I have 6 years of experience working on tasks like this and handling similar challenges across backend, frontend, and smart-contract development. I have carefully read and fully understood the task requirements, and I am confident I can deliver a clean, efficient, and well-tested solution promptly. I always ensure high-quality implementation, maintainability, and adherence to best practices.

Pull request in 5 hours.

[mxrtins04]

please can i be assigned this issue?

[nonggde]

/claim #429

Submitted PR: #1315

Scope: adds a folder-local architecture contract for Customer Support Macro Tool, including service/storage/hook/fixture/test boundaries, data ownership, future integration adapter constraints, and a Node architecture contract test. The PR stays entirely inside tools/v1/team/customer-support-macro-tool/.

Validation:

• node --test tools/v1/team/customer-support-macro-tool/tests/architecture-contract.test.mjs
• npx --yes prettier --check on changed Customer Support Macro Tool files
• git diff --check
• ASCII scan over changed Customer Support Macro Tool files

Note: existing Vitest suites were attempted, but the checkout lacks local Vitest/Vite plugin dependencies needed to load the tool/root Vitest config. This PR does not change runtime services, hooks, fixtures, or existing Vitest tests.