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>
1.2 KiB
Moonshot And Kimi Provider Shape
Last updated: dev@28d27ee | 2026-07-17
Scope
Provider IDs moonshot for official Moonshot API and kimi_code for the Kimi
Code surface; OpenAI-compatible transport with provider-specific headers and
model-specific behavior in src/llm_core.py.
Shape And Observations
Model lists use the general OpenAI-compatible identity shape unless a richer
account response is returned. Official Kimi K2.5/K2.6 fixes temperature by
thinking mode, so Odysseus omits temperature rather than sending an invalid
value (#3960). Thinking tool-call continuation requires preservation of
assistant reasoning_content (#3118). Kimi Code negotiates a small exact
User-Agent set on 403 and caches the accepted value; this is provider transport,
not model capability.
Reports distinguish K2.5/K2.6 multimodality from older K2 variants (#2522).
Promote those claims only through exact structured model IDs/families, not a
kimi name match.
Fallback And Current Gaps
Keep Moonshot and Kimi Code identities distinct even when both use OpenAI Chat. Self-hosted Kimi checkpoints inherit their serving engine shape, not official Moonshot sampling rules. The provider catalog does not yet yield a complete canonical capability card.