chore: init agent config and repo learnings

[Lionvsx]

Summary

• Adds .agents/LEARNINGS.md template for tracking repo-level engineering learnings
• Sets up dev as integration branch for future PRs

Arboriia Mockups — Delivered

Live deployment: https://arboriia-mockups.vercel.app

Screens implemented

Screen	URL	Status
Admin Dashboard	/admin	✅ Done
Freelance Dashboard	/freelance	✅ Done
Client Portal	/client	✅ Done
CRA Preview	/cra/:id	✅ Done

Tech stack

• Next.js 16.2.2 (App Router) + TypeScript
• Tailwind CSS + shadcn/ui
• All data hardcoded from PRD mock data
• Global demo nav bar to switch between Freelance / Client / Admin

Test plan

• Visit https://arboriia-mockups.vercel.app — redirects to /admin
• Admin: navigate all sidebar sections (Accueil, Missions, CRA, Factures, Freelances)
• Freelance: toggle calendar days, change mission selector, check updated summary
• Client: test validate flow + contest flow with textarea
• CRA Preview: accessible from Freelance > Mes CRA > "Voir le CRA →"

🤖 Generated with Claude Code

---

Summary by CodeRabbit

• Documentation
  • Added a learnings documentation file for recording and organizing project insights and feedback.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
arboriia-mockups	Ready	Preview, Comment	Apr 3, 2026 1:26pm

[coderabbitai]

Walkthrough

A new markdown document was added to .agents/LEARNINGS.md to serve as a centralized location for recording project-specific learnings sourced from PR reviews, bugs, and engineering feedback. The file includes descriptive header text and formatting conventions specified via HTML comment.

Changes

Cohort / File(s)	Summary
Documentation .agents/LEARNINGS.md	New file created with instructions for centralized project learning documentation, including formatting conventions for entries with dates and context.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'chore: init agent config and repo learnings' directly relates to the main change—adding .agents/LEARNINGS.md for tracking engineering learnings, though it mentions 'agent config' which is not evidenced in the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 04-03-chore_init_repo_learnings_and_agent_config

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

[coderabbitai]

🧹 Nitpick comments (1)

.agents/LEARNINGS.md (1)

7-7: Add a concrete entry template to reduce formatting drift.

Consider including an example entry format (date, source, learning, action) directly below this comment so contributors append consistently.

✍️ Suggested addition

 <!-- Format: one learning per entry, with date and context -->
+ 
+ ## YYYY-MM-DD — <context: PR/bug/incident>
+ - Learning: <what was learned>
+ - Action: <what changed / guardrail added>

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In @.agents/LEARNINGS.md at line 7, Add a concrete example entry template
immediately below the existing HTML comment "<!-- Format: one learning per
entry, with date and context -->" so contributors follow a consistent structure;
include fields like "Date:", "Source:", "Learning:", and "Action:" with a short
example entry to demonstrate formatting and encourage compliance with the
four-part pattern.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In @.agents/LEARNINGS.md:
- Line 7: Add a concrete example entry template immediately below the existing
HTML comment "<!-- Format: one learning per entry, with date and context -->" so
contributors follow a consistent structure; include fields like "Date:",
"Source:", "Learning:", and "Action:" with a short example entry to demonstrate
formatting and encourage compliance with the four-part pattern.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 22fe68e9-0a75-4fe5-83bc-09e3be932011

📥 Commits

Reviewing files that changed from the base of the PR and between a075b4c and aadb596.

📒 Files selected for processing (1)

• .agents/LEARNINGS.md