docs(value-objects): add documentation for MedicationFrequency value object

[gbrennon]

No description provided.

[Copilot]

Pull request overview

Adds a new domain documentation page describing the MedicationFrequency value object and its invariants.

Changes:

• Introduces docs/domain/value_objects/medication_frequency.md
• Documents the purpose of the value object and lists its enum-like variants/invariants

[Copilot]

The title has a typo: MediationFrequency doesn’t match the actual value object name/path (MedicationFrequency). This can make the doc harder to find/search and inconsistent with the code.

Suggested change

	# `MediationFrequency` -> `src/domain/value_objects/medication_frequency.rs`
	# `MedicationFrequency` -> `src/domain/value_objects/medication_frequency.rs`

[Copilot]

Doc header format is inconsistent with other value object docs (they use an em dash separator, e.g. docs/domain/value_objects/dosage.md:1). Consider using the same # Type—path`` convention here for consistency.

Suggested change

	# `MediationFrequency` -> `src/domain/value_objects/medication_frequency.rs`
	# `MedicationFrequency` — `src/domain/value_objects/medication_frequency.rs`

[Copilot]

Grammar: “This follow” should be “This follows”.

Suggested change

	- This follow an enum pattern with variants like `OnceDaily`, `TwiceDaily`, `EveryXHours(u8) or Custom(String)`.
	- This follows an enum pattern with variants like `OnceDaily`, `TwiceDaily`, `EveryXHours(u8) or Custom(String)`.

[Copilot]

This doc is much shorter than other value-object docs in this repo (which typically include sections like Constructor/Methods/Usage/Related). To keep documentation consistent and actionable, consider adding at least the constructor/methods (if any) and a Related section similar to the other files in docs/domain/value_objects/.