27 lines
1.3 KiB
Markdown
27 lines
1.3 KiB
Markdown
## Purpose
|
|
|
|
Canonical specification for manual-fetch-recovery requirements synced from OpenSpec change deltas.
|
|
|
|
## Requirements
|
|
|
|
### Requirement: Manual command supports bootstrap and recovery workflows
|
|
The system SHALL allow operators to run the forced fetch command during first-time setup and after failed scheduled cycles.
|
|
|
|
#### Scenario: Bootstrap content population
|
|
- **WHEN** the system is newly deployed and contains no current news items
|
|
- **THEN** an operator can run the force-fetch command immediately
|
|
- **AND** the command attempts to populate the dataset without waiting for the next hourly schedule
|
|
|
|
#### Scenario: Recovery after failed scheduled fetch
|
|
- **WHEN** a prior scheduled fetch cycle failed or produced incomplete results
|
|
- **THEN** an operator can run the force-fetch command on demand
|
|
- **AND** the system performs a fresh one-off fetch attempt
|
|
|
|
### Requirement: Repeated manual runs remain operationally safe
|
|
The system SHALL support repeated operator-triggered runs without corrupting data integrity.
|
|
|
|
#### Scenario: Repeated invocation in same day
|
|
- **WHEN** an operator runs the force-fetch command multiple times within the same day
|
|
- **THEN** existing deduplication behavior prevents duplicate persistence for matching items
|
|
- **AND** each command run completes with explicit run status output
|