[WIP] Fix Android CI/CD workflow and expand pipeline structure

[Copilot]

Thanks for asking me to work on this. I will get started on it and keep this PR's description up to date as I form a plan and make progress.

Original prompt

Architect and implement a robust Android CI/CD workflow for SentientAIBrowser, applying AIDDE v2 system principles:

1. Fix current workflow failure.

   • Replace build-android-aar command with correct Gradle build command (cd android && ./gradlew assembleRelease).
   • Add dependency installation step (yarn install or npm install).
   • Remove fragile AAR file path checks (ls on node_modules).
   • Ensure outcome is a reproducible Android release build.

2. Expand and structure the CI/CD pipeline:

   • Add a dedicated .github/workflows/do-it-check.yml implementing the 8 CI/CD gates from AIDDE (docs/aidde/05-cicd-gates.md).
   • Document every workflow and development protocol in new markdown files (e.g. docs/android-build-pipeline.md, docs/aidde/CI-CD-workflow.md).
   • Enforce traceability (commit messages, PR titles, issue body templates) as in AIDDE docs.
   • Ensure type-safety and lint/test checks.

3. Follow AIDDE commit and workflow hierarchy:

   • One feature branch per Milestone (Feature), one execution branch per Issue (Task) and atomic commits per subtask.
   • Make all changes in a feature/task branch off main.
   • All changes are documented.

Deliverables:

• FIXED .github/workflows/full-automation-retry.yml
• NEW .github/workflows/do-it-check.yml covering all AIDDE gates
• All new/changed relevant documentation files
• All commits and PRs use trace headers, resolve proper Issue IDs, and reference the feature hierarchy
• NO orphaned code, branches, or issues

PR will be opened, and you will review and approve/merge once satisfied.

This pull request was created from Copilot chat.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.