sanad-agent: Skill for Claude Code

Sanad Client Tester

Use this skill to select and execute the smallest reliable verification boundary for the Sanad Flutter Client. The main file owns invariants and routing only; load the focused reference that matches the task instead of reading every procedure.

Non-negotiable invariants

• Use fvm for every Flutter or Dart operation.
• Analyze before testing, then run focused unit/widget coverage; broaden only when the change surface requires it.
• Use --concurrency=1 only for tests that bind ports or exclusive resources.
• Keep successful analyzer and test output to the final five lines while preserving exit status through pipefail; rerun only a failure unfiltered.
• Use sanad-dev for managed runtime discovery and control. Never infer ownership from process age, directory naming, or a hardcoded port.
• Before a UI action, inspect current state and resolve a unique stable key. Do not fall back to coordinates while a keyed target can be added or discovered.
• Treat create, send, delete, submit, and similar effects as one-shot phases. Never retry an ambiguous irreversible action automatically.
• Wait on lifecycle or UI events rather than snapshot/model polling, then verify the resulting state deterministically.
• Do not stop, restart, or mutate a runtime not proven to be owned by the current worktree. Runtime source switching requires explicit user authorization under the repository contract.
• Keep logs bounded and free of secrets or entered values.

Canonical conversation fast path

When a request fits scripts/sanad_conversation_workflow.py and supplies its required device, conversation, provider/model, message, and return inputs, load only references/jev-conversation-automation.md and execute the runner immediately. Do not run separate sanad-dev status, snapshot, find, log reads, --help, or full jev-dual-brain-automation skill loading first. The runner's internal ownership resolution, snapshot, exact-key admission, one-shot phase ledger, event waits, Jev call, and return verification are the preflight and execution boundary.