[ENGG-5120]: Add optional rank field to API data structure

[dinex-dev]

Summary by CodeRabbit

• New Features
  • Introduced an optional "rank" field across request/record schemas and API types.
  • API responses from local sync now include rank when present, and parsed results propagate rank into returned data.

[linear]

ENGG-5120 Local sync changes

[coderabbitai]

Walkthrough

This pull request adds an optional rank field to the API surface. rank?: string was introduced in types.ts and schemas.ts, and the fs-utils.ts utility now assigns data.rank = record.rank when constructing API objects, causing the returned API payload to include the parsed record's rank when present.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 3 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ 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 clearly and accurately summarizes the main change: adding an optional rank field to the API data structure across multiple files.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into master

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

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch ENGG-5120

---

No actionable comments were generated in the recent review. 🎉

---

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