docs: add configuration verification step

[Mohit-001-hash]

Summary

Added a verification note to the Quick Start section explaining how contributors can confirm that the adiuvare.yaml configuration file has been generated successfully before integrating Adiuvare into their application.

Why

The README describes how to generate the configuration file but does not explain how to verify that it was created successfully. This addition helps contributors validate their setup before proceeding.

Scope

• bug fix
• documentation
• tests
• TUI / CLI improvement
• framework integration
• signal change
• configuration or route-policy change

Verification

How did you verify the change?

Commands run:

# Documentation-only change

Notes:

• I ran the relevant tests locally
• I updated docs if behavior changed
• I updated screenshots if the TUI changed materially

Signal-specific notes

Signal type:

• hard signal (trackA)
• soft signal (trackB)
• not applicable

Source, reproducer, or proof:

Not applicable.

Benign case checked:

Not applicable.

Performance note:

Not applicable.

TUI notes

• not applicable

Local-only file check

• I did not accidentally stage local-only files such as adiuvare.yaml or local conftest.py changes

Related issue

Closes #None (documentation improvement)