architecture: add cross-repo dependency map (UI → API, local dev ports)

[abhi0324]

📋 Description

JIRA ID: N/A

Summary:
Add architecture/cross-repo-dependency-map.md and link it from SUMMARY.md. The new doc lists UI repositories and their primary backend APIs with canonical local-development ports, and notes shared services (Common-API/Common-UI) and backend-only services (FHIR, Identity, BeneficiaryID). Motivation: reduce onboarding friction and make local environment wiring explicit.

---

✅ Type of Change

• 📚 Documentation (updates to docs or readme)

Summary by CodeRabbit

• Documentation
  • Added new architecture documentation page detailing cross-repository dependency mapping, including frontend-to-backend repository relationships and local development port references.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: f91848d1-f3d4-45f5-ae7d-4b86863ac22e

📥 Commits

Reviewing files that changed from the base of the PR and between 93e5398 and 01beb32.

📒 Files selected for processing (2)

• SUMMARY.md
• architecture/cross-repo-dependency-map.md

---

📝 Walkthrough

Walkthrough

This PR adds documentation describing the cross-repository dependency map for the AMRIT system. It introduces a new architecture reference page mapping frontend repositories to backend API repositories, shared dependencies, and local development ports, with a corresponding table-of-contents entry.

Changes

Cross-Repo Dependency Documentation

Layer / File(s)	Summary
Documentation Index SUMMARY.md	Architecture section table-of-contents entry added for "Cross-repo dependency map" linking to architecture/cross-repo-dependency-map.md.
Dependency Mapping Tables architecture/cross-repo-dependency-map.md	Three mapping tables introduced: Direct UI to API mappings listing frontend repositories with ports and their corresponding backend APIs; Shared components table for Common-UI and Common-API shared services; Backend services table for APIs without dedicated UI rows.
Usage Guidance and Related Documentation architecture/cross-repo-dependency-map.md	Reading instructions explain how to use the tables to verify frontend-to-API wiring and shared dependencies. Related documentation links point to system architecture overview, API guide, and codebase structure pages.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A map of the warren draws near,
Frontend and backend in harmony clear,
Shared common threads, ports all aligned,
Dependencies charted, so all will know thy mind!
Hop through the docs, the structure's defined. 🗺️

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: adding a cross-repo dependency map documentation with details about UI-API mappings and local development ports.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

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.}