Preserve civil daypart clocks across DST
This commit is contained in:
@@ -13,7 +13,12 @@ Each `Definition` declares a stable ID and display name, prompt ID and version,
|
||||
| `tomorrow` | `2.0.0` | `weather-balanced` | Next local civil day | Evening | `tomorrow.md` |
|
||||
| `hourly` | `2.0.0` | `weather-light` | Rolling six-hour interval | — | `hourly.md` |
|
||||
|
||||
Daily derives its filename from the resolved valid-period start in the effective timezone, so multiple Daily items have distinct destinations. Exact template fields and schema assets belong to [report templates](../templates.md) and [generated-text internals](generatedtext.md). Prompt assets own default profile selection; the registry stores no provider setting.
|
||||
Daily derives its filename and run identity from the resolved valid-period start
|
||||
in the effective timezone, so multiple Daily items have distinct destinations
|
||||
and identifiers. Exact template fields and schema assets belong to [report
|
||||
templates](../templates.md) and [generated-text internals](generatedtext.md).
|
||||
Prompt assets own default profile selection; the registry stores no provider
|
||||
setting.
|
||||
|
||||
## Collaborators And Boundaries
|
||||
|
||||
|
||||
Reference in New Issue
Block a user