mirror of
https://github.com/pewdiepie-archdaemon/odysseus.git
synced 2026-09-17 13:42:21 +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>
48 lines
2.0 KiB
Markdown
48 lines
2.0 KiB
Markdown
# ChatGPT Subscription Provider Shape
|
|
|
|
Last updated: dev@e57f60b | 2026-07-20
|
|
|
|
## Scope
|
|
|
|
Canonical provider ID `chatgpt_subscription`; Codex Responses transport;
|
|
auth and runtime code in `src/chatgpt_subscription.py`,
|
|
`routes/chatgpt_subscription_routes.py`, and `src/llm_core.py`.
|
|
There is no dedicated ChatGPT Subscription canonical reader on current `dev`.
|
|
|
|
## Catalog Shape
|
|
|
|
The account-scoped Codex models endpoint returns root `models[]`; `slug` is the
|
|
request identity and `visibility`/`priority` control availability/order. These
|
|
fields do not prove tools, reasoning, vision, or context. Null/malformed model
|
|
lists fail soft rather than crashing discovery (#5280/#5281).
|
|
|
|
The canonical generic reader does not accept `slug`-only items, so this runtime
|
|
catalog is not currently normalized into `ModelCapabilityRecord` values.
|
|
|
|
## Request And Response Shape
|
|
|
|
Transport uses a ChatGPT backend Responses endpoint, `input` items, flattened
|
|
function tools, streamed function-call argument events, exact `call_id`, and
|
|
`function_call_output` continuation. Parallel calls and encrypted reasoning
|
|
continuity require preserving typed output/history rather than coercing all
|
|
roles to text. This shape is supported by the existing adapter and the focused
|
|
tool-calling follow-up evidence in #5490; unmerged observations remain claimed
|
|
until integrated/reproduced.
|
|
|
|
OAuth/device credentials and refresh are provider-session behavior. Expired
|
|
credentials should return an actionable reconnect error, not generic model
|
|
failure.
|
|
|
|
## Fallback And Safety
|
|
|
|
Only the explicit internal base/ChatGPT host selects this provider. Never send
|
|
subscription credentials to a custom OpenAI-compatible URL. Catalog slugs stay
|
|
identity-only unless account-scoped fields or probes supply capability.
|
|
|
|
## Current Gaps
|
|
|
|
- Comprehensive Responses tool/reasoning parity is still evolving.
|
|
- Account model slugs are not consumed by the canonical reader package.
|
|
- The account catalog does not currently provide a complete canonical
|
|
capability card for every slug.
|