Initial server source import

This commit is contained in:
sashatrask
2026-09-30 20:30:56 +03:00
commit 170dd941b9
498 changed files with 261563 additions and 0 deletions
@@ -0,0 +1,37 @@
## MODIFIED Requirements
### Requirement: Query-scoped safety bounds
The system SHALL support exact-query overrides for configured queries only, limited to `pages`, `per_page`, and `max_targets`, without changing source-wide defaults for other queries.
#### Scenario: Configured query receives bounded arguments
- **WHEN** a source builds arguments for a configured query with an exact override
- **THEN** it SHALL apply that query's configured page, page-size, and target bounds
#### Scenario: Retired query has no override
- **WHEN** a query is removed from a source rotation
- **THEN** the source SHALL NOT retain an override for that query
#### Scenario: Ordinary query retains source defaults
- **WHEN** the same source builds arguments for any query without an override
- **THEN** it SHALL retain the source-wide page, page-size, and target values
#### Scenario: Invalid override fails closed
- **WHEN** a query override is not a mapping or contains a key outside the allowlist
- **THEN** argument construction SHALL fail before discovery or queue mutation
## REMOVED Requirements
### Requirement: Exact OpenAI core discovery
**Reason**: The completed bounded rollout produced 43 linked origin credentials and no strict-usable credential for any provider, meeting the approved global retirement rule.
**Migration**: Remove `openai` from GitHub, GitLab, and DockerHub rotations and allow normal modulo-based query rotation to continue without editing persisted source state.
### Requirement: Source-specific rollout limits
**Reason**: The exact-query rollout is complete and its query is being retired, so source-specific `openai` execution bounds are no longer active policy.
**Migration**: Remove the three matching `openai` overrides while retaining the generic exact-query override mechanism and all overrides for configured ecosystem queries.
### Requirement: End-to-end canary evidence
**Reason**: The exact-query canary reached terminal evidence and its measured all-provider strict yield is captured by the pruning decision.
**Migration**: Evaluate future keyword retirement under `discovery-keyword-pruning` using canonical all-provider lineage and measured exposure.