feat: enhance documentation and update dependencies in mobile feature builder and development rules

.claude/agents/mobile-feature-builder.md

@@ -54,9 +54,7 @@ If any of these files are missing or unreadable, notify the user before proceedi
 - Use `BlocProvider.value()` for singleton BLoCs
 - Use `UiColors`, `UiTypography`, `UiIcons`, `UiConstants` for all design values
 - Use `core_localization` for user-facing strings
-- Write unit tests for use cases and repositories
-- Mock dependencies with `mocktail`
-- Test BLoCs with `bloc_test`
+- Add human readable doc comments for `dartdoc`  for all classes and methods.
 
 ## Standard Workflow
 
@@ -109,7 +107,6 @@ Follow these steps in order for every feature implementation:
 
 ### 8. Self-Review
 - Run `melos analyze` and fix all issues
-- Run `melos test` and ensure all pass
 - Manually verify no architectural violations exist
 - Check all barrel files are complete
 - Verify no hardcoded design values
@@ -150,9 +147,7 @@ Before declaring work complete, verify:
 - [ ] BLoCs only depend on use cases
 - [ ] Use cases only depend on repository interfaces
 - [ ] All barrel files are complete and up to date
-- [ ] Tests exist for use cases, repositories, and BLoCs
 - [ ] `melos analyze` passes
-- [ ] `melos test` passes
 
 ## Escalation Criteria
 
@@ -168,7 +163,6 @@ Stop and escalate to the human when you encounter:
 After completing implementation, prepare a handoff summary including:
 - Feature name and target app
 - List of all changed/created files
-- Test coverage percentage
 - Any concerns, trade-offs, or technical debt introduced
 - Recommendation for Architecture Review Agent review
 
@@ -179,9 +173,8 @@ As you work on features, update your agent memory with discoveries about:
 - Session store usage patterns and available stores
 - DataConnect query/mutation names and their locations
 - Design token values and component patterns actually in use
-- Common test setup patterns and shared test utilities
 - Module registration patterns and route conventions
-- Recurring issues found during `melos analyze` or `melos test`
+- Recurring issues found during `melos analyze` 
 - Codebase-specific naming conventions that differ from general Flutter conventions
 
 This builds institutional knowledge that improves your effectiveness across conversations.