Skip to content

Add GPT-6 Sol/Luna, verified Cookie routing and account-scoped prompt rules - #192

Merged
HTExplicit merged 7 commits into
mainfrom
feat/gpt6-routing-prompts
Sep 23, 2026
Merged

HTExplicit merged 7 commits into
mainfrom
feat/gpt6-routing-prompts

Conversation

@HTExplicit

Copy link
Copy Markdown
Owner

新增 GPT-6 Sol/Luna 后,账号模型同步和客户端目录需要保留接入方式各自的容量与能力;旧 292 长度门控也不能证明当前业务出口实际返回了请求的模型。本次把模型目录、Cookie 路由验证和 Codex 出站身份接到现有插件边界,并修复提示词的纯 WebSocket 漏注入和插件页面刷新引起的布局变化。

  • 添加准确的 Sol/Luna ID、API 与官方 Codex 参考容量、独立价格、长请求阶梯及配置导出。实时账号元数据优先,手动映射保留,未知 GPT-6 不归并到 Astra;Ultra 只作为客户端委派能力。
  • 使用独立 Cookie 候选和逐模型资格替代长度判定。只有完整成功响应和原始上游模型匹配才能发布资格;绑定账号、身份、路由与实际连接,120 秒上限、同值不延龄、删除标记及有界续获保留 fail-closed。
  • 统一 HTTP、WS、账号测试及采集的出站身份,提供账号指纹只读详情及明确的 profile 选择。官方 CLI 的隔离本地采样与生产观测分开展示,未捕获的生产 TLS 特征保持未知,私密 Cookie 和凭据不进入展示。
  • 基于现有不可变模板版本增加四位置规则、严格 system/developer 或原生控制字段、账号 inherit/off/custom、revision CAS 和最终发包预览。覆盖 HTTP、协议转换、HTTP→WS、连接池及纯 WS passthrough,并在重试或账号切换时精确撤回本站注入。
  • 修复同值 context 刷新重建 iframe;主题和字体就绪后切换,失败保留最后外观;按帧合并自然高度测量,保持菜单正常伸缩。

宿主目标为 0.2.7-codexrip.2,七个内置插件统一为 0.2.8 并声明新的最低宿主版本。迁移保留现有提示词内容、开关、默认范围和停止状态。使用说明及验证边界见 .downstream/gpt6-routing-and-prompts.md。

已完成与改动直接对应的模型、Cookie 状态/连接、HTTP/WS 提示词、账号 CAS、指纹投影和 UI 定向离线检查;新增提示词迁移与绑定在隔离 PostgreSQL 18.1 上通过。真实 Chromium 验证两个 15 秒刷新、主题失败与恢复、字体加载、菜单伸缩及桌面断点,保持相同布局下的滚动位置,未发送真实模型请求。前端与公共 SDK 类型、受影响 UI 构建和定向 lint 已通过,正常必需 CI 继续执行。

生产验收由本次独立持久账本限制为一个目录确认的 OAuth 非 shadow 账号、最多七个出站阶段,每次 25 秒及 128 KiB,不重试失败、不自动登记续获。该验收在新版本部署后执行;本 PR 的离线结果不等同于线上模型恢复或质量证明。

@HTExplicit
HTExplicit enabled auto-merge (squash) September 23, 2026 04:25
Codex and others added 6 commits September 23, 2026 12:33
Keep the first turn-state value fixed within one logical turn, reuse it for
same-turn retries and continuations, and clear it on a new turn or owner
change across Cindy HTTP->WSv2, ingress, forwarder reconnect and the HTTP
bridge, restoring the Cindy/API session contracts required CI flagged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… transport

- Attach the plaintext identity observation only to the zstd wire copy;
  unrewritten OAuth requests are returned untouched and inspected directly
  by the final-outbound observer instead of being copied and re-read.
- Report a qualified account-test wire once (the qualified route already
  observes its leased wire).
- Identity tests derive existing accounts with the legacy seed profile; the
  seed-less derivation keeps meaning a new account's v2 Windows reference.
- Account-test stubs serve the unified Do and connection-lease entry points;
  the mapped-model account test now proves Cookie qualification gating.
- Build the PR candidate image as <base>-codexrip.candidate so bundled
  plugins requiring the newest downstream host still verify.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
List the final carrier and role each delivery mode emits for Codex OAuth,
API-key/Cindy Responses and Chat Completions, including the explicit
rejection of strict system on Codex OAuth.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
API-key accounts keep the per-session provenance key while Codex OAuth
state is scoped to the logical turn, so the commit-boundary fixtures now
derive the seed for the destination account, and the WSv2 execution-scope
test sends turn ids on fresh sockets and reads the turn-scoped key. Also
use a tagged switch in the bridge isolation fixture (staticcheck QF1003).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Lower the validation socket's per-message read limit to the probe cap and
reject the stage once the frames read exceed it, instead of only checking
the running total between frames (a single frame could reach 16 MiB).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@HTExplicit
HTExplicit merged commit c95d472 into main Sep 23, 2026
16 checks passed
@HTExplicit
HTExplicit deleted the feat/gpt6-routing-prompts branch September 23, 2026 07:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant