[project-start] clever driver mobile app repo bootstrap

[OziinG]

request summary

Create a new EVNSolution/clever-driver-app target repository and bootstrap it for the Clever driver mobile app MVP.

request context

The operator is preparing a dedicated driver app repo after server-side Admin Drivers/Routes/Orders work. The user wants the repo created so they can open parallel sessions across the app, server, and reference repos.

business intent

Enable the first mobile driver MVP: phone-number access, location-information and personal-information consent, and viewing the route assigned for the current delivery day.

constraints

• Follow CLEVER target-repo bootstrap rules from clever-agent-project.
• First main push must include root AGENTS.md.
• New target repo should be public under EVNSolution.
• Use main as deploy branch and dev as integration/work branch.
• Scope here is repository bootstrap only; product implementation remains follow-up issue work.
• Reference systems: clever-delivery-server and local Tomatono app context.

expected outcome

• EVNSolution/clever-driver-app exists remotely and locally.
• Seeded AGENTS.md, docs/project-brief.md, PR template, and ruleset script are committed and pushed.
• dev branch exists for future linked-issue work.
• Repository rulesets are applied when admin preflight passes.
• Worktree is clean and ready for new sessions.

candidate template lineage

CLEVER target repo seed templates from clever-agent-project/docs/templates, lifecycle_action=repo-bootstrap.

candidate target repo

EVNSolution/clever-driver-app

candidate target service

clever-driver-app

intake mode

agent-assisted

approval status

approved

notes

Follow-up implementation issue should cover driver auth/phone login, consent capture, and assigned route retrieval after server API contracts are finalized.

[OziinG]

Target repo created: EVNSolution/clever-driver-app\n\nTarget bootstrap issue: EVNSolution/clever-driver-app#1

[OziinG]

Bootstrap completed.

Evidence:

• Repo: https://github.com/EVNSolution/clever-driver-app
• Initial commit: 89b4a6b
• Branches pushed: main, dev
• Default branch: dev
• Rulesets applied: CLEVER protect main, CLEVER protect dev
• Seed files: AGENTS.md, docs/project-brief.md, .github/PULL_REQUEST_TEMPLATE.md, scripts/apply-github-rulesets.sh, README.md
• Validation: bash -n scripts/apply-github-rulesets.sh; admin preflight ready=true; worktree clean after push

[OziinG]

PR #2 merged to dev and completed the repo role/platform/scenario/basic setup pass.

Evidence:

• PR: Document driver app repo role and plan clever-driver-app#2
• merge commit: 4180d5d3df29092e8243cab08b82e5338eacbc90
• branch: cc-145-repo-role-plan local/remote cleaned up
• validation: git diff --check HEAD^1..HEAD passed
• validation gap: package.json not present yet, so npm workspace/lint/typecheck/build commands are not applicable until app runtime bootstrap

Context/wiki result:

• clever-context-monorepo update not needed for this PR because it only clarified target repo planning docs, README, and baseline ignore rules.
• No public API, implemented runtime, deploy profile, env/secret category, or data flow contract changed.

[OziinG]

Completed by EVNSolution/clever-driver-app#2 merged to dev at 4180d5d3df29092e8243cab08b82e5338eacbc90. Follow-up implementation should start from a new target issue and GitHub Development linked branch.