Repository navigation
test(interactive): record ChatGPT-authored response bound to FlowKit Pending (M-level) - #11
Merged
Merged
Conversation
…l-using response and Host resume
…public Pending digest
…even a synthetic secret
Contributor
Author
S13 自主接入实测 — 证据、独立复审与裁决（2026-11-11）结论：当前 ChatGPT 模型确实参与了真实 FlowKit JavaScript 工具执行链，闭环功能验证 PASS；但该测试不构成 Codex 原生 S13 验收，PR 保持 Draft。 两段真实操作证据阶段 A：由真实源码发布 Pending
阶段 B：真实 ChatGPT 在阅读阶段 A 的输出后回复
必须写清的验收边界
源码复审裁决只修改 4 个测试/示例文件（工作流定义、公开 Skill、模型回复 fixture、Host 测试）；0 生产运行时/ABI/API/DB 变更，未引入 Context、模型代理服务、用户产物存储、自动部署。 判定：ChatGPT 自主工具链可行性验证 PASS；M6 S13 原生宿主/独立来源认证仍 BLOCKED。 |
Contributor
Author
验证覆盖范围重新审计（2026-11-11）：不可把一次模型回合扩大为复杂 S13 验收复审裁决：此 PR 只证明一条 ChatGPT 参与的简单模型工具桥接 Happy Path，不能作为复杂工作流验收，也不能使 M6 S13 PASS。 A. PR #11 究竟验证了什么
B. 与其他测试不可混同
C. 建议冻结的 P0-A 复杂验收集合（12 条，先用脚本覆盖逆境、再选 3–5 条由真实 Grok Build 验证）
每条用例必须记录： 本次只作覆盖复审与验收建议，不擅自扩大已有 PR 的代码范围、不合并、不修改 main。 |
Add current-main M6 scripted Host integration coverage, root-discovery fixtures, Linux cross-UID CI, and the full Interactive delivery roadmap. This is test/CI/documentation only and does not complete native-host C12/S13 or M6 final acceptance.
Add the reviewed Trusted Host V2 threat model, deployment profiles, security acceptance matrix, and explicit Phase 2 limitations. This is documentation-only: it does not implement Host isolation, Grok native provenance, Windows ACL enforcement, or Phase 3/4 runtime changes. F-02 and F-04 remain pending real validation; F-07 formal V0.3/V0.6-R5 conformance remains blocked. Merge does not authorize Phase 3 or claim C12/S13/M6 acceptance.
…dit plan Record independently validated Requirements V0.3 and Technical Design V0.6-R5 originals, limited Core PoC results and Phase 2 traceability roadmap. Reconcile the previously confirmed M1–M6 P0-A plan and existing M1–M5 implementation. Documentation only: no Core/API/Program ABI/Store schema changes, no Phase 3 authorization, no C12/S13 or full conformance PASS claim.
* docs(interactive): add source-backed T/R/S crosswalk and initial P0-A gap findings * docs(interactive): document Host/Public terminal State projection contract difference * docs(interactive): record async Store contract divergence from confirmed V0.6-R5 * docs(interactive): add Phase 2 R2 code-evidence review and R04 mutation findings * docs(interactive): link R04 independent regression PR and retrigger Phase 2 CI
…idence * docs(interactive): record local verification of PR 16 and 17 The report keeps the PR heads, commands, R04 failure output, the snapshot fix result, and the merge recommendation. Raw decisive logs are stored beside it. No product code changes. * docs(interactive): record that Actions for PR 16-19 are still queued The 13:15 +08 reconfirm keeps all four draft PRs unmerged. Run status is queued with an empty conclusion. That is not a matrix pass and not a proven Actions outage.
start() copied caller-owned State and startIntent only after loadInteractiveProgram resolved. That await yields even when the loader is already settled, so a caller could change both objects before the Checkpoint and startIntentHash were created. Copy both with the existing bounded canonical snapshot first, and preserve the initial-State capacity error. Later Store writes use those copies. Includes the R04 regression tests from PR #17.
rockyshi1993
changed the title
* test(interactive): freeze C01-C12 scenario matrix and scripted/live/native evidence separation * test(interactive): C01-C04,C10,C11 scripted complex runs with real Program signed Host and SQLite * test(interactive): C01/C03 live multi-Agent two-Condition workflow definition * test(interactive): real ChatGPT multi-Agent 5-turn replay bridge with schema rejection and SQLite reopen * test(c01-live): actual ChatGPT requirements analysis bound to published Pending #1 * test(c01-live): ChatGPT architecture response to real dependent Pending #2 * test(c01-live): actual ChatGPT implementation plan from real Pending #3 * test(c03-live): ChatGPT deliberately submits invalid reviewApproved type to test real retry Pending * test(c01-live): genuine ChatGPT corrected review after real attempt-2 Pending #5 * docs(interactive): record C01-C12 detailed scripted and five-turn real ChatGPT evidence with open native gates * test(interactive): extend complex P0-A acceptance with C13-C20 interleavings * docs(interactive): extend risk-mapped C13-C24 acceptance and native-host gates * test(interactive): inspect durable Store state while Pending frame intentionally redacts State * test(interactive): verify C16 durable Checkpoint while Pending frame hides private State * docs(interactive): record independently checked 7/7 CI and C13-C24 layered verdict * test(interactive): rebase M6 Host integration on current main Add current-main M6 scripted Host integration coverage, root-discovery fixtures, Linux cross-UID CI, and the full Interactive delivery roadmap. This is test/CI/documentation only and does not complete native-host C12/S13 or M6 final acceptance. * docs(interactive): add Trusted Host V2 conditional security design Add the reviewed Trusted Host V2 threat model, deployment profiles, security acceptance matrix, and explicit Phase 2 limitations. This is documentation-only: it does not implement Host isolation, Grok native provenance, Windows ACL enforcement, or Phase 3/4 runtime changes. F-02 and F-04 remain pending real validation; F-07 formal V0.3/V0.6-R5 conformance remains blocked. Merge does not authorize Phase 3 or claim C12/S13/M6 acceptance. * docs(interactive): recover frozen baselines and establish evidence audit plan Record independently validated Requirements V0.3 and Technical Design V0.6-R5 originals, limited Core PoC results and Phase 2 traceability roadmap. Reconcile the previously confirmed M1–M6 P0-A plan and existing M1–M5 implementation. Documentation only: no Core/API/Program ABI/Store schema changes, no Phase 3 authorization, no C12/S13 or full conformance PASS claim. * docs(interactive): archive Phase 2 formal conformance R1/R2 audit * docs(interactive): add source-backed T/R/S crosswalk and initial P0-A gap findings * docs(interactive): document Host/Public terminal State projection contract difference * docs(interactive): record async Store contract divergence from confirmed V0.6-R5 * docs(interactive): add Phase 2 R2 code-evidence review and R04 mutation findings * docs(interactive): link R04 independent regression PR and retrigger Phase 2 CI * docs(interactive): archive local R04 reproduction and verification evidence * docs(interactive): record local verification of PR 16 and 17 The report keeps the PR heads, commands, R04 failure output, the snapshot fix result, and the merge recommendation. Raw decisive logs are stored beside it. No product code changes. * docs(interactive): record that Actions for PR 16-19 are still queued The 13:15 +08 reconfirm keeps all four draft PRs unmerged. Run status is queued with an empty conclusion. That is not a matrix pass and not a proven Actions outage. * fix(interactive): snapshot start inputs before first await (R04) start() copied caller-owned State and startIntent only after loadInteractiveProgram resolved. That await yields even when the loader is already settled, so a caller could change both objects before the Checkpoint and startIntentHash were created. Copy both with the existing bounded canonical snapshot first, and preserve the initial-State capacity error. Later Store writes use those copies. Includes the R04 regression tests from PR #17. * test(interactive): require complete recorded ChatGPT responses in normal CI * docs(interactive): clarify recorded model-response evidence tier
rockyshi1993
marked this pull request as ready for review
November 12, 2026 08:29
rockyshi1993
commented
Nov 12, 2026
rockyshi1993
left a comment
rockyshi1993
left a comment
Contributor
Author
There was a problem hiding this comment.
Maintainer self-review completed against the current-main merge tree and exact PR HEAD. The unique files are a workflow example, public Skill, response fixture, test and evidence documentation; no production Core/ABI/Store schema changes. The test explicitly distinguishes a GitHub-tool-delivered ChatGPT-authored response from a FlowKit native JS-tool invocation and native S13. Normal CI now requires the full response fixture; only FLOWKIT_S13_PREPARE=1 permits a preparation-only run. Exact HEAD Actions run 43182753787 passed all 7/7 jobs; all four OS/Node verify cells passed, with 387/387 tests in the Node 22 cells. This is M-level recorded response evidence only; C12/S13 native Host remains BLOCKED.
This was referenced Nov 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Scope
Preserve a reproducible M-level ChatGPT-authored response → exact FlowKit Pending → trusted Host acceptance experiment.
requestId/taskDigestin CI output.runId/requestId/taskDigest, and exercises Host signature/CAS, duplicate Ack and SQLite close/reopen.docs/interactive-chatgpt-response-evidence.mdrecords the evidence boundary and preparation procedure.Important evidence boundary
This is NOT a FlowKit native JavaScript-tool invocation and NOT native S13. The model returns its response through a GitHub tool action; the test replays that response through FlowKit. There is no independent provider/session attestation, and no Grok Build/Codex native-tool proof. Native Host S13 remains BLOCKED.
Phase 1 and Phase 2 are separate Actions invocations with separate temporary SQLite databases. Phase 2 reconstructs the deterministic Pending and tests restart within its own DB; it does not continue the physical DB from Phase 1.
Test gate
Normal CI requires the complete response fixture. The no-fixture preparation path is available only when explicitly invoked with
FLOWKIT_S13_PREPARE=1; it cannot silently produce a green normal CI run.Verification
c9b6033c8302cbb205f251f68aba2f45222d7191.Note
Medium Risk
The coordinator
start()snapshot change affects durable State and start-intent hashing at run creation; incorrect copying could break idempotency or capacity handling, though scope is limited to that path.Overview
Adds M-level ChatGPT acceptance: workflows, recorded turn fixtures, and
docs/interactive-chatgpt-response-evidence.mdthat bind a real model response to an exact Pending (runId/requestId/taskDigest) and replay it through the trusted Host—not native S13.The only production change fixes R04 in
coordinator.start(): deep-copy callerstateandstartIntentbefore the firstawaitso mutations after the call cannot alter the initial checkpoint orstartKeyidempotency.CI and test wiring expand coverage:
npm testincludestests/integration/*, the Host isolation job runsnpm ciplusm6-e2ewithFLOWKIT_M6_ISOLATION, and new integration pieces includem6-ledger-boundaryand the scriptedm6-workerfixture. A large set of acceptance, Phase 2 audit, and verification docs/evidence is added alongside.Reviewed by Cursor Bugbot for commit c9b6033. Bugbot is set up for automated code reviews on this repo. Configure here.