Repository navigation
Description
开发主线交接(2026-10-12)
开发默认主线现为 wip/rust-core-go-extensions;旧单体 main 与 traditional 冻结于 3948a0a1ee1cefdd016a7aa45a11851545bb4b85。分支交接不是发布、部署或验收通过。原问题、源码基线、测试与未完成项保留;旧单体路径仅作历史证据,后续先在微服务源码重新确认并按职责移植,不回灌旧数据库/权限/资金实现。
主线/S11 跟踪:#895。Extore 商品同步:#894,未验收,禁止部署,尤其禁止合并/推送 Extore main。
Scope
Track reproducible frontend test parity and isolated mock acceptance for #675, not completion of model/payment migration.
Pinned snapshots:
- main:
5117b2a2272e44f51b368ac6c68877def799f256 - WIP:
bbde7468dcbd08091bc6a666c27946c2a385f2bf
Executed locally
- main: frontend typecheck/build/bundle pass; fresh PostgreSQL + Valkey main process returned 200 for status, setup and three public legal endpoints
- WIP: frontend build/bundle pass; actual Go legal host passed 26 HTTP checks (language fallback, content revisions, HEAD, POST 405, restart snapshot and unpublished content)
- Both: ForgeHome DOM tests pass 19/19 with the same explicit offline GitHub-stars fixture
- WIP typecheck fails at
apps/web/src/features/forge/home-directory-gesture.test.ts:24,29,46: requestAnimationFrame return type and Happy DOM WheelEventInit incompatibilities. main includes the applicable fixture repair from test(web): repair release acceptance fixtures [skip ci] #742 - Original main full Web test run unexpectedly attempted the public GitHub-stars GET. Source chain: HomeLanding → RepositoryLink → fetchRepositoryStars. Existing api.get mock does not cover global fetch. This is test non-hermeticity, not a data-leak finding: the source request uses credentials:'omit', no auth/body
- WIP has the same external request source; a live WIP request was not separately reproduced. The shared offline fixture lets both targeted suites finish without live stars access
Recheck
In each pinned checkout with Bun 1.3.14:
bun install --frozen-lockfile
bun run --filter @lmm/web typecheck
bun run --filter @lmm/web buildDo not assume the full test entry is offline until explicit fixtures and unexpected-request rejection exist.
Suggested fix and acceptance
- Port applicable test(web): repair release acceptance fixtures [skip ci] #742 fixture changes to WIP without deleting assertions, excluding tests, using ts-ignore or weakening type checking
- Explicit stars success/unavailable/cancellation fixtures; fail undeclared external network requests
- One local mock acceptance entry, recording exact revision and separate typecheck/component/build/HTTP-host/browser results
- Configurable main.local and wip.local loopback origins; no global DNS/hosts edits or production fallback
- First host-backed UI matrix: public legal draft/published/language fallback/unavailable states
- Preserve known WIP readiness/model 503 as an unfinished capability, not a new regression or fake successful mock integration
- Complete desktop/mobile browser acceptance where supported; keep NOT_RUN results explicit
Evidence and limits
WIP fixture
main fixture
WIP stars request
Real browser access was blocked in this environment; Rust dependency retrieval returned 403. Full Web suite was stopped when unexpected external access was detected. No full browser/core/payment acceptance claimed. main static route/asset HTTP smoke and WIP static smoke passed but do not substitute for browser behavior.
Checked existing issues/PRs for fixture, hermeticity, stars and WIP acceptance overlap. #380/#775 are broader; #758–762 retain main UX scope; #742 is the existing main fixture fix. No production changes, remote CI, real payment or model requests.
2026-10-12 七日源码审计补充:真实浏览器回归入口
审计基线:main 3948a0a1ee1cefdd016a7aa45a11851545bb4b85;默认微服务主线 9f5541b0b6ecb054fe953d539455c1e2028445f1。本节补充旧记录,不将旧快照的失败或通过状态套到新提交。
main 已合入 #722 / 1b9cc34b152c28799c85e61aa8a905a69b16d7f8,增加 隔离 Markdown 浏览器入口 与对应探针。当前 WIP 缺少该入口及等价浏览器探针;Markdown 组件仍保留,已有 URL 分类单测不等于真实浏览器中的组件/净化/DOM 验证。
- 在隔离 mock 验收中迁移真实组件探针,不连接生产、不把探针接入应用正式入口
- 区分组件级浏览器结果、真实保存/读取流程结果及未运行项,不能以旧 main 的测试文件存在证明微服务通过
- 在最终组合源码上记录桌面/移动视口、重复进入与状态恢复的实际结果,保留精确 SHA
这是测试覆盖缺口,不是已复现的线上漏洞;本次只做源码审计,未执行浏览器探针。HumanGrant 完整页面流程由 A10 #880 / S11 #895 继续跟踪。
Activity
LIghtJUNction commentedon Oct 11, 2026
当前 main 的两个 Web fixture 失败已单独归因,不与 #675 的隔离前端验收混为一谈:
mandatory-announcements.test.tsx仍期望两次操作,实际已合入的界面会按服务器顺序一次确认当前可见的全部公告;本机补丁修正断言,并检查两篇可见公告。ratio-notifications/api.test.ts的严格配置断言漏了已存在的 10 秒请求超时;本机补丁补齐这个既有合同。在基于
de2c439f26446792d4a605b2b91fa2b84777e284的独立工作区,两个修改后的定向文件实际测试通过,Web 类型检查也通过。这不是完整隔离前端、浏览器或生产验收。三个发布资格小补丁(另含 Go 生成合同同步)目前受本机提交签名未完成阻断,尚未提交、推送或形成 PR。#782 保持 OPEN,不把未交付的 main fixture 修正当作 #675 的隔离验收已完成。
LIghtJUNction commentedon Oct 12, 2026
RT16 测试入口缺口已形成独立候选 #899,commit
45f69b0834cdbc2d5d57d4dfd5e6b4616911beb9,目标是默认微服务 WIP,不回灌旧单体实现。恢复实际 Markdown/DOMPurify browser entry 与 loopback-only runner,版权保留。当前源码 URL 分类 16/16、Python 输入校验 3/3、79-module browser entry 构建、entry 类型/lint/format 和文档检查通过。
浏览器样本仍未执行:Python Playwright 缺失,明确 BLOCKED;没有安装额外依赖或放宽策略。真实保存/跨账号读取、全业务、桌面/移动浏览器和 S11 组合仍未验收。候选未合并/未部署,因此不勾销本 Issue 的完整清单,也不据此关闭 #782。