Absolute date picker

## Summary
Tell us, in a few words, what the component or pattern would do.

## 💬 Description
A full description of what the component or pattern should be and how it should work.

## 💰 User value
Describe why this is important and how it will help users (either developers, designers or the end-users). Think about how it makes people's lives easier, more accessible or quicker to build stuff.

## 📚 User Stories
If relevant, describe the high-level functionality as user stories.

*As an* ICDS user:
*I need*
*So that*

## 📝 Acceptance Criteria
If relevant, describe in full detail the different interactions and edge cases that the component or patterns needs to fulfil.

*Given*
*When*
*Then*

## ✏ Designs
If there's a Figma design file (or other mock-up), include it here.

## 🧾 Guidance
If there's written guidance or documentation, include a link to it here.

## Additional info
Tell us anything else useful to help us understand your suggestion.

The issue contains only a blank proposal template and does not name a file, test, entry point, design, or acceptance criteria. Start by clarifying the date picker's intended behavior, user value, designs, guidance, and edge cases; the work is done only when those requirements and implementation locations are defined.

Written by the indexing model from the issue text.