docs: consolidate manual test scenarios into 10 E2E tests (#701)

* docs: consolidate manual test scenarios into single E2E file

Replace 10 per-feature test files (107 scenarios, 2224 lines) with a
single docs/ai-design/manual-tests.md containing 10 end-to-end
scenarios that each exercise multiple features. Update CLAUDE.md to
reference the consolidated file.

Deleted directories (test-only):
- 2025-02-25-spv-peer-rework
- 2026-02-24-address-nonce-column
- 2026-02-24-asset-lock-fee-fix
- 2026-02-24-dashmate-auto-update
- 2026-02-24-mine-blocks-dialog
- 2026-02-24-platform-sync-simplification
- 2026-02-24-spv-sync-error-status
- 2026-02-24-sync-status-panel
- 2026-03-03-fix-nonce-reset-on-refresh
- 2026-03-05-banner-details-overlap

Preserved directories (non-test design docs):
- 2026-02-16-spv-single-runtime-refactor
- 2026-02-17-unified-messages
- 2026-02-27-banner-review-fixes

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* docs: add table of contents to manual-tests.md

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* docs: add user personas for wallet redesign

Define three user archetypes (Everyday User, Power User, Platform
Developer) to guide progressive disclosure in the wallet UI. Add
concise README as index. Reference personas in CLAUDE.md documentation
section.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* docs: add user stories catalog with 98 stories across 10 feature areas

Comprehensive user story inventory derived from source code, internal
docs, and published documentation. Each story tagged by persona
(Alex/Priya/Jordan), marked [Implemented] or [Gap], with acceptance
criteria. Covers wallet, send/receive, asset locks, identity, DPNS,
DashPay, tokens, contracts, developer tools, and network settings.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* docs: add UX design patterns reference card

Concise UI/UX conventions covering design tokens, color system, buttons,
dialogs, forms, messages, tables, loading states, navigation, keyboard
accessibility, progressive disclosure, and responsive layout. All values
verified against theme.rs and component implementations.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* docs: audit and update user stories, UX patterns, and CLAUDE.md

Full codebase audit of user-stories.md against implementation:
- Fix SND-005: [Gap] → [Implemented] (fee estimation exists)
- Fix NET-006: [Implemented] → [Gap] (no UI control)
- Add note to DPN-005 about Platform-level vote constraint
- Add 15 new stories: WAL-017..020, SND-006, IDN-012..013,
  DPY-009..011, TOK-015..017 (113 total, was 98)

Update ux-design-patterns.md with missing patterns:
- Password strength colors, interactive state colors
- Additional semantic color constants
- Shadow system tokens
- ComponentStyles button and input helpers
- Password input pattern (hold-to-reveal)

Add user stories catalog section to CLAUDE.md requiring
story updates on feature PRs.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* docs: remove hardcoded values from docs, refer to source files instead

Remove stale counts (scenario limits, story counts) and implementation
constants (pixel sizes, hex codes, padding values) that drift out of
sync with source code. Documents now explain usage/intent and point to
source files for exact values.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* chore: remove obsolete docs

* docs: note user-stories.md as exception to date-grouped docs rule

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

Author: lklimek

CLAUDE.md

@@ -36,13 +36,12 @@ Test locations:
 
 Always run `cargo clippy` and `cargo +nightly fmt` when finalizing your work.
 
+### User stories catalog
 
-### Manual test scenarios
-
-You MUST identify manual tests needed for the changes and write a manual test scenarios. Use the `claudius:qa-engineer` agent if available.
-Skip the manual test file only for non-functional changes (CI, docs, formatting, pure refactoring) — state why in the PR description.
-Put tests in docs directory, as described in "Documentation" section below. Reference the file in the PR description under "Test plan".
-Before creating a PR, re-review test scenarios and update them if needed.
+When a PR adds or significantly changes user-facing features, check `docs/user-stories.md`:
+- If a new feature matches no existing story, add one following the existing format (ID, persona, description, acceptance criteria, `[Implemented]` tag).
+- If a `[Gap]` story is now implemented, flip its tag to `[Implemented]`.
+- Skip user-story updates for non-functional changes (CI, docs, formatting, refactoring).
 
 ## CI: Safe Cargo Wrapper
 
@@ -69,7 +68,10 @@ scripts/safe-cargo.sh +nightly fmt --all
 
 ## Documentation
 
-- **docs/ai-design** should contain architecture, technical design and manual testing scenarios files, grouped in subdirectories prefixed with ISO-formatted date
+- **docs/ai-design** should contain architecture, technical design and manual testing scenarios files, grouped in subdirectories prefixed with ISO-formatted date. Exception: `docs/user-stories.md` is a living document maintained at the top level — not date-grouped.
+- **docs/personas** contains user personas (Everyday User, Power User, Platform Developer) that define the three target user archetypes and the progressive disclosure model for UI complexity. Consult these when making UX decisions about what to show/hide or how to structure wallet features.
+- **docs/user-stories.md** catalogs user stories across feature areas, tagged by persona and marked `[Implemented]` or `[Gap]`. Reference when planning new features or verifying coverage.
+- **docs/ux-design-patterns.md** is the UI/UX reference card — explains **when and how** to use design tokens, buttons, dialogs, forms, accessibility rules, and progressive disclosure. For exact values (sizes, colors, padding), refer to source files (`src/ui/theme.rs`, `src/ui/components/`). Consult when building or reviewing UI.
 - end-user documentation is in a separate repo: https://github.com/dashpay/docs/tree/HEAD/docs/user/network/dash-evo-tool , published at https://docs.dash.org/en/stable/docs/user/network/dash-evo-tool/
 
 ### Core Module Structure