Skip to content

test(offline): repair protocol gate regressions - #164

Merged
jjangg96 merged 3 commits into
mainfrom
g01-postmerge-ci-recovery
Nov 3, 2026
Merged

jjangg96 merged 3 commits into
mainfrom
g01-postmerge-ci-recovery

Conversation

@jjangg96

@jjangg96 jjangg96 commented Nov 3, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • Refresh G01 command fixtures for active workflow runs and GroupPolicy v2 selected workflow evidence.
  • Assert the separate read-only and management installation-token lifecycle, durable revocation intent, and exact request counts.
  • Split G02 race tests into bounded protocol groups while preserving package discovery, the complementary test/example/fuzz run, and routing sentinels.

Part of #1. This PR does not close issue #1; its live canary acceptance remains open.

Verification

  • OFFLINE_EXPERIMENT_MODULE=experiments/g01-scaleset OFFLINE_EXPERIMENT_PROFILE=core bash scripts/check-offline-experiments.sh — passed with Go 1.27.3, race checks, and vet.
  • OFFLINE_EXPERIMENT_MODULE=experiments/g02-auth bash scripts/check-offline-experiments.sh — passed with Go 1.27.3, race checks, and vet; offline only.
  • go test -count=1 -timeout=600s -run '^TestToolingDefaultG02PartitionsRun$' ./scripts — passed (282.924s).
  • git diff --check, bash -n scripts/check-offline-experiments.sh, and gofmt -d on changed Go files — passed.

Go module/build caches and temporary files were directed to an external work volume. No live canary, Scale Set, runner, credential, or host operation was performed.

Exact-head follow-up — 2026-11-04

Candidate: 3c56bc6e6a536c4daefd397f621176c6f93938e6, based on 325effa8408f87ca51769d683b0a0862623d1ea5.

The two follow-up commits route the G02 workflow-provenance timeout and selection sentinel into bounded partitions, and make the G01 subprocess fixtures assert the workflow authorization and token revocation lifecycle.

Local evidence on this candidate:

  • G01 core offline check passed with race partitions and vet.
  • G02 full offline check passed with race partitions and vet.
  • Default G02 partition sentinel passed; formatting, shell syntax, and diff checks passed.
  • No live provider, credential, runner, Scale Set, Docker, or host operation was performed.

Independent gpt-5.6-luna / max exact-head delta review: APPROVE; no P0/P1 defect found. The reviewer raised four P2/P3 fixture-coverage notes. They are triaged as nonblocking and closed without follow-up: RS256 signature verification is exercised by the focused adapter/ACK fixture; full query/header/body assertions remain owned by adapter-level tests while this process fixture checks authority and sequence; broker and admission journals each assert their own record order alongside the exact request order; and the V3 transport's referenced-workflow injection is fixture-only provider shaping. None identifies a production behavior defect in this delta.

Fresh @codex review was requested for this exact head. Hosted PR quick check is running. The prior Public CI run on base 325effa8408f87ca51769d683b0a0862623d1ea5 failed in G01 process fixtures and the G02 offline partition; this candidate contains the corresponding fixture and partition corrections, with integration status to be recorded separately.

Issue #1 remains OPEN / Project #2 In progress. Production provenance and trust-root custody, broker-only execution, server-side conditional cleanup, runtime/isolation/resource qualification, protected-canary configuration, and the separately authorized Linux ARM64/JIT canary remain open.

Review and exact-head gate — 2026-11-04

  • Hosted PR Go check passed on exact head 3c56bc6e6a536c4daefd397f621176c6f93938e6: run 41719670811.
  • Fresh GitHub Codex manual review completed on that exact head with no findings: review result.
  • The prior Codex P2 from 4cf4111 is resolved: TestBrokerExperimentV3SelectionRejectsMissingStateBeforePipeOwnership is now in the G02 read-only/pre-effect selector, and the tooling regression verifies both that the selected test runs and that a failing selected test fails its partition.
  • The independent Luna Max exact-head delta review approved the candidate. Its four P2/P3 fixture-coverage notes were triaged and closed without follow-up as documented above.

Issue #1 remains OPEN / Project #2 In progress while its live gates remain.

@jjangg96

jjangg96 commented Nov 3, 2026

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 3, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-03T21:14:24.870981Z 3c56bc6 Manual request
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4cf4111ec8

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

v3_read_only_regex='^TestBrokerExperimentV3(ReadOnlyPreflightRejectsBeforeWriteMint|StopsWhenReadOnlyTokenRevocationIsUncertain|RevokedRecordSyncFailureStopsBeforeWriteMint|DoubleRevocationJournalSyncFailureBlocksLaterInspect|LostReadTokenMintResponseBlocksLaterInspect|RevokesTokenFromRejectedReadIssuance|DoesNotRevokeVerificationTokenCollision)$'
v3_provenance_regex='^TestBrokerExperimentV3(LostWorkflowProvenanceResponseBlocksLaterInspect|WorkflowProvenancePreRequestFailureRecordsNoDispatchForLaterInspect|HistoricalWorkflowProvenanceClaimReplayBinding|LegacyIncompleteClaimWithoutManagementLifecycleBlocksLaterInspect|PreRequestFailureRecordsNoDispatchForLaterInspect|RepeatsCalleeFenceAfterWritePreflight)$'
paired_process_regex='^TestBrokerPaired'
g02_non_paired_skip_regex='^TestPaired|^TestBrokerPaired|^TestBrokerExperimentV3|^Test(LegacyControllerEntryRejectsMalformedInputBeforeAdmission|LegacyPairedEntryRejectsMalformedInputBeforeAdmission|BrokerControllerClaimsAttemptBeforeProvenanceSideEffects)$'

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Keep the v3 policy-selection test in an executed partition

The G02 offline gate now skips TestBrokerExperimentV3SelectionRejectsMissingStateBeforePipeOwnership entirely: it matches this blanket exclusion, but none of the explicit partition selectors include it. Previously it ran in the complement. This silently removes coverage for rejecting missing state before consuming credential pipes and for rejecting mismatched callee, group, and run policies. Local go help testflag confirms that -skip runs only tests “that do not match the regular expression.” Add this test to a partition or restrict the complement exclusion to the names actually routed elsewhere.

Useful? React with 👍 / 👎.

@jjangg96

jjangg96 commented Nov 3, 2026

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Another round soon, please!

Reviewed commit: 3c56bc6e6a

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@jjangg96
jjangg96 merged commit 853d176 into main Nov 3, 2026
1 check passed
@jjangg96
jjangg96 deleted the g01-postmerge-ci-recovery branch November 3, 2026 21:17
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