Skip to content

docs(interactive): establish current baseline and local CI fallback - #20

Merged
rockyshi1993 merged 8 commits into
mainfrom
docs/phase0-current-baseline-ci-fallback-20261112
Nov 12, 2026
Merged

rockyshi1993 merged 8 commits into
mainfrom
docs/phase0-current-baseline-ci-fallback-20261112

Conversation

@rockyshi1993

@rockyshi1993 rockyshi1993 commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor

Purpose

Complete Phase 0 baseline and traceability against current main without changing production behavior.

  • Record the current main SHA and merged/open/closed PR state.
  • Maintain the approved 31-task P0-A crosswalk and map each task to source, tests and evidence.
  • Correct stale CI/PR references and distinguish P/M/N evidence levels.
  • Preserve the local verification fallback without relabelling local results as GitHub Actions PASS.
  • Carry forward CF-01/02/05/06/07/08 and F-02/F-04/F-07 without changing the confirmed contract.

Current baseline

Deliverables

Strict scope

Documentation only. No production source, ABI, Store schema, workflow configuration, package metadata, requirements or approved P0-A plan changed. This PR does not close P0-A, M6 native-host, C12/S13, CF-01/02/05/06/08 or Windows Secure Host gaps.

Merge only after exact-head CI 7/7 and final review of the five documentation files.


Note

Low Risk
No production runtime or schema changes; risk is limited to mis-labeling fixture-based ChatGPT replay as native-host acceptance if reviewers skip the documented P/M/N gates.

Overview
This PR expands Interactive M6/P0-A evidence and traceability without changing production Core, Store schema, or Program ABI.

It adds Phase 0 baseline documentation for current main (81c7839…): CI fallback policy, a 31-task P0-A crosswalk, refreshed roadmap/formal-source/conformance plans, and strict P / M / N evidence labeling (scripted protocol vs recorded ChatGPT vs native Grok/Codex host).

It introduces the frozen C01–C24 acceptance matrix (plus C13–C20 results write-ups) and new interactive tests: complex-c01-c12.test.mjs for scripted C01–C20 protocol cases, plus ChatGPT-authored fixture replay in c01-live-chatgpt.test.mjs and s13-chatgpt-tool-bridge.test.mjs with committed JSON fixtures, example workflows, and a reviewer skill. Normal CI requires fixtures; FLOWKIT_C01_PREPARE / FLOWKIT_S13_PREPARE only support explicit Pending-prep runs.

Docs and tests repeatedly state that the GitHub/ChatGPT bridge is M-level recorded response evidence only—not native S13/C12—so green CI must not be read as native-host or M6 closure.

Reviewed by Cursor Bugbot for commit 2aaef80. Bugbot is set up for automated code reviews on this repo. Configure here.

* 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
* test(interactive): define executable S13 ChatGPT tool-bridge acceptance workflow

* test(interactive): add auditable public Agent instruction for S13 bridge

* test(interactive): 2-stage public Pending bridge for real ChatGPT tool-using response and Host resume

* test(s13): bind actual ChatGPT model-generated response to published public Pending digest

* test(s13): generate Host-only private canary inside CI, never commit even a synthetic secret

* 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 explicit preparation mode for ChatGPT response fixture

* docs(interactive): label ChatGPT response experiment as M-level

* test(interactive): preserve original workflow identity for recorded Pending fixture

* docs(interactive): clarify ChatGPT response evidence tier and S13 limits

* test(interactive): add C01-C24 complex acceptance evidence

* 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
rockyshi1993 marked this pull request as ready for review November 12, 2026 08:51

@rockyshi1993 rockyshi1993 left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maintainer self-review completed against current main 81c7839 and exact PR HEAD 2aaef80. The current diff against main is five documentation files only: the full roadmap, 31-task P0-A crosswalk, current baseline/CI fallback, formal source register and conformance audit plan. I verified the 31 task rows, corrected the Program Retain/Genesis transaction interpretation, updated PR #11/#12 evidence tiers and merged status, corrected A-M5-03/A-M6-05 to reflect the new test-specific examples without claiming a reusable Trusted Host bridge, and refreshed CI status. No production source, ABI, Store schema, workflow, package metadata, approved requirements or P0-A plan changed. Current main run 43183321344 passed 7/7; exact PR HEAD run 43185930957 passed 7/7. Remaining CF-01/02/05/06/08 and native Host gates are explicitly still open/BLOCKED. This merges only the Phase 0 governance/documentation snapshot, not P0-A completion.

@rockyshi1993
rockyshi1993 merged commit 7e5960f into main Nov 12, 2026
9 checks passed
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