You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
31 lines
1.2 KiB
Markdown
31 lines
1.2 KiB
Markdown
# Clarifications Resolved (2026-03-28)
|
|
|
|
This memo records product/contract decisions provided after the initial audit.
|
|
|
|
## Final Decisions
|
|
1. Theme creation:
|
|
- Creating a theme is allowed without sending categories.
|
|
- Default categories are `Divers` and `Sans date`.
|
|
- Category creation requires an existing theme.
|
|
2. Schedule API contract:
|
|
- `GET /themes/{id}/schedule` returns `200` with `null` when absent.
|
|
3. Canonical theme defaults:
|
|
- `max_items_per_category = 4`
|
|
- `summary_length = 3`
|
|
4. Preferred source scope:
|
|
- Preferred sources are managed per theme.
|
|
5. Import/export scope:
|
|
- Bulk import, CSV import, and CSV export are always bound to the selected theme.
|
|
6. Fallback category label:
|
|
- Canonical label is `Divers`.
|
|
7. Source-link extraction mode:
|
|
- Fully deprecated.
|
|
8. Frontend UI guideline:
|
|
- Using `Button` component instead of raw `<button>` is strict everywhere.
|
|
9. QA release gate:
|
|
- Deterministic coverage is required in CI before release (scheduler/SSE and critical paths).
|
|
|
|
## Implementation Impact
|
|
- Contract drift items flagged by the audit are now actionable with no remaining ambiguity.
|
|
- Follow-up refactoring/implementation teams should treat this memo as the tie-breaker over older conflicting docs.
|