mirror of
https://github.com/pewdiepie-archdaemon/odysseus.git
synced 2026-09-15 04:32:23 +02:00
RaresKeYandStressTestor
7026cf40b5
* docs(specs): restore bootstrap after dev rewrite
* docs(specs): remove runtime inventory snapshot
* docs(specs): reconcile current dev truth
* docs(specs): document scheduled task actions as an owner-attribution source
Owner Attribution covered cookie, bearer-token and internal-loopback
requests. Scheduled task actions are a fourth source and behave
differently: _execute_action passes owner=task.owner off the stored
ScheduledTask row, so no request and no resolved principal are in
flight, and route-level require_user() never runs.
Webhook triggers are the sharp case. They are unauthenticated by
design with the token as the only credential and execute under the
stored task.owner.
Paths cite routes/task/task_routes.py, the canonical location after
the task subpackage move (#6081); routes/task_routes.py on current dev
is the backward-compat shim.
* docs(specs): add chained tasks to the trigger list, refresh dev stamp
Review feedback from RaresKeY on the previous commit.
"Every trigger path" was too broad: success-chained tasks are another
path into _execute_action. Added them with their own citation, and
noted that chaining additionally requires the target task to share
task.owner and rejects cycles, which is stricter than the trigger-side
checks. Softened the lead-in to "these trigger paths".
Line 56 still pointed at routes/task_routes.py for webhook credential
validation. That path is the backward-compat shim on current dev after
the task subpackage move (#6081); repointed to the canonical
routes/task/task_routes.py.
Stamp moved to dev@2a6b09b. Inspection backing that bump was scoped:
every file path cited in this spec was mechanically checked to resolve
on 2a6b09b, and every file:line in the Owner Attribution additions was
read against it. Behavioral claims elsewhere in the file were not
re-audited.
* docs(specs): correct SECURE_COOKIES description to match current behavior
Third of the stale details RaresKeY enumerated. The cookie section
described SECURE_COOKIES as purely opt-in, which stopped being true.
_secure_cookie() (routes/auth_routes.py:89) treats an explicit true or
false as authoritative and derives the Secure attribute from the
request otherwise, including when the variable is unset and when
docker-compose injects it present-but-empty. Either the connection
scheme or the first X-Forwarded-Proto hop being https is enough.
* docs(specs): refresh current dev truth
---------
Co-authored-by: StressTestor <212606152+StressTestor@users.noreply.github.com>
42 lines
1.8 KiB
Markdown
42 lines
1.8 KiB
Markdown
# OpenRouter Provider Shape
|
|
|
|
Last updated: dev@e71f8ce | 2026-08-25
|
|
|
|
## Scope
|
|
|
|
Canonical provider ID `openrouter`; OpenAI-compatible chat dialect; rich reader
|
|
`src/model_capability_readers/openrouter.py`.
|
|
|
|
## Catalog Shape
|
|
|
|
`GET /api/v1/models` returns `data[]`. Canonical fields are:
|
|
|
|
- `id` (falling back to `name`) and display `name`;
|
|
- `architecture.input_modalities`, `architecture.output_modalities`, and
|
|
compatibility `architecture.modality`;
|
|
- `context_length` and `top_provider.max_completion_tokens`;
|
|
- `supported_parameters`, `default_parameters`, `supported_voices`, and
|
|
`per_request_limits`.
|
|
|
|
Modalities determine family and vision/file/audio/image/video behavior.
|
|
Recognized supported parameters claim tools, JSON/structured output,
|
|
reasoning, and web search. Sampling/default parameters become controls, not
|
|
capabilities. Descriptions, pricing, author slugs, and tokenizer names do not.
|
|
|
|
## Provider Versus Routed Endpoint
|
|
|
|
OpenRouter normalizes requests while routing a model to one of several
|
|
underlying providers. The catalog model record is OpenRouter-scoped. Do not
|
|
copy a direct-provider quirk to OpenRouter unless its normalized API and exact
|
|
model/endpoint evidence require it. `top_provider` limits describe the current
|
|
route class, not a permanent global model limit.
|
|
|
|
## Fallback And Safety
|
|
|
|
The reader receives OpenRouter through explicit selection or an exact/label-bounded `openrouter.ai` hostname hint. Future fields remain raw. If modalities are absent, it falls back to an identity-only OpenRouter record and does not parse the model slug; supported-parameter controls are not retained on that fallback path.
|
|
|
|
## Current Gaps
|
|
|
|
- Per-upstream endpoint differences can still invalidate an aggregate claim.
|
|
- Catalog values change frequently and need freshness/expiry when persisted.
|