Development

[fikrilal]

Summary

Describe what changed and why.

Risk Class

• low
• medium
• high

Risk notes:

• Production impact areas touched (if any):
• Why this risk class was selected:

Acceptance Criteria

Checks Run

List exact commands and outcomes.

dart run tool/verify.dart --env dev

Additional checks:

# examples:
# fvm flutter analyze
# dart run custom_lint
# fvm flutter test
# dart run tool/verify_codegen.dart
# dart run tool/verify_project_map_drift.dart

Evidence

• Tests added/updated where behavior changed
• Screenshots/video attached (UI changes)
• Logs/error traces attached (runtime or failure-path changes)
• Mobile runtime evidence attached for medium/high UI/runtime PRs (see docs/engineering/mobile_runtime_harness.md)
• No speculative refactor mixed into this PR

Links/artifacts:

Runtime evidence details (if applicable):

• Device ID:
• Flavor:
• Integration targets:
• Evidence artifact paths:

Safety And Rollback

• Potential failure mode:
• Rollback strategy:
• Follow-up required after merge (if any):

Reviewer Focus

Point reviewers to the highest-risk files/decisions:

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
33827767	Triggered	Generic Password	9bd6559	tool/agent/auth_fixture_evidence_check.sh	View secret
33827767	Triggered	Generic Password	fd05860	tool/agent/login_logout_evidence_check.sh	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}