[Existing app][Contacts Import] Document safety boundaries and contributor handoff

[kryputh]

Summary

Improve the existing Contacts Import surface. This issue is intentionally scoped to existing app code and should not introduce a new standalone tool or unrelated feature.

Current area

import wizard steps, contact parser, malformed row handling, preview data, and contact import types

Relevant paths

• src/features/contacts/ImportWizard.tsx
• src/features/contacts/parseContacts.ts
• src/features/contacts/types.ts

Goal

improve the current contacts import wizard so contact data parsing is transparent and recoverable.

Work focus

Document the current safety, privacy, and contributor boundaries for this area. The goal is to make future changes easier to review without adding new product scope.

Acceptance criteria

• Documentation names the files, data contracts, and user-facing states a contributor must understand.
• Safety notes call out fake demo data, privacy assumptions, and any trust/security-sensitive behavior.
• The handoff includes a lightweight QA checklist for this area.
• Docs link to existing local files or tests instead of inventing a new architecture.

Scope guardrails

• Keep the work inside the relevant existing app/module paths above unless a small shared helper is clearly justified.
• Do not add a new V1/V2 tool folder for this issue.
• Do not use real user data, secrets, private keys, or live customer mail.
• Keep copy and UI aligned with the Stealth Mail safety, speed, and sender-control positioning.

Suggested validation

• Run the most relevant unit or e2e tests for the touched area.
• Run �un x tsc --noEmit and �un run lint when the local environment supports the project dependency install.

[gloskull]

Hello, I have 4 years of experience delivering solutions for projects like this, covering backend, frontend, and smart contract development. After carefully reviewing your requirements, I have a clear understanding of the task and am confident in my ability to deliver a clean, efficient, and thoroughly tested solution on time. I prioritize code quality, maintainability, and industry best practices throughout the development process.

[Kureszn]

I've reviewed the issue and believe I can contribute effectively. My experience spans software development, blockchain technologies, cybersecurity and open source collaboration. I take a structured approach to contributions carefully understanding the existing codebase, identifying the root cause and delivering a thoroughly tested implementation.