Skip to content

[G01] Account workflow provenance GET lifecycle - #161

Merged
jjangg96 merged 6 commits into
mainfrom
issue-160-provenance-accounting
Nov 3, 2026
Merged

jjangg96 merged 6 commits into
mainfrom
issue-160-provenance-accounting

Conversation

@jjangg96

@jjangg96 jjangg96 commented Nov 3, 2026 •

Copy link
Copy Markdown
Contributor

Fixes #160

Summary

  • Durably account for the authenticated workflow-run GET in the per-attempt journal and fixed account admission ledger before dispatch. Hold the account lock through the observed GET and durable confirmation; ambiguous outcomes remain pending and block replay before installation-token minting.
  • On ledger replay, bind each historical reusable-callee claim to its confirmed GET event by slot, attempt and journal identities, controller-approval digest, source, run ID, workflow ref, SHA and path.
  • Add causal recovery fixtures and field-isolated replay regression coverage; align the broker/G02 evidence docs and exact-head review history.

TDD and verification

  • RED at exact base a4d6f03b81cbc77f51bf9eb0d37fdf47d67c02f3: workflow-GET lost-response replay completed inspect and minted twice; repeated on a fresh archive of that base.
  • RED at exact prior PR head b9ca7c96c7881391a1cc9ed6f06b6a7848e9f1b4 with a test-only overlay: independent mutations of attempt, journal, controller-approval digest, source, workflow run ID, ref, SHA and path each let inspect complete and mint twice. A slot mismatch failed closed, and the matching-history control passed.
  • Corrected selector TestBrokerExperimentV3HistoricalWorkflowProvenanceClaimReplayBinding passes under go test -race -count=1 -timeout=180s -run '^TestBrokerExperimentV3HistoricalWorkflowProvenanceClaimReplayBinding$' -v . (all nine mismatch cases plus the named matching-history control, 7.673s).
  • On unchanged implementation commit eefe8dfde5134b014b54ca45277640c6401c0395, focused verification, full G02 go test -race -p=1 -count=1 -timeout=300s ./... (all packages; root 143.977s), and go vet -p=1 ./... passed. The test-only follow-up was rerun with the focused race selector above.
  • git diff --check passed. Go 1.27.3 was used with downloads disabled and caches/temp on external storage.

Candidate and review state

  • Current exact head: a1181bff77027cb436ba9fc8bb1c3dfe5bb60051 (documentation-only update after the test candidate).
  • Prior code/test head f0b4e97d323a0dc637dfe6cff9c74fa62ca1d922 passed hosted Go checks and exact-head GitHub Codex review with no major findings. Independent Luna Max confirmed the replay-binding P2 was resolved and found no remaining source P0/P1/P2 issue; it held overall because evidence wording still described that pushed candidate as local/pending. Commit a1181bf labels earlier pending states as historical and records the then-current review status.
  • Hosted Go check passed for exact head a1181bff77027cb436ba9fc8bb1c3dfe5bb60051; GitHub Codex completed review of that exact head with no findings, and independent Luna Max reviewed the same SHA and returned APPROVE with no P0-P3 findings.

No provider credentials, tokens, workflow dispatch, runner, Scale Set, Docker, host-service or canary operation was performed. Issue #160 and parent issue #1 remain OPEN; Project #2 remains In progress while G01 live and production qualification gates remain unresolved.

@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-03T17:03:01.882657Z 85baf46 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

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Delightful!

Reviewed commit: b9ca7c96c7

ℹ️ 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 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. Keep it up!

Reviewed commit: 73c1299319

ℹ️ 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 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. Breezy!

Reviewed commit: f0b4e97d32

ℹ️ 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 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. Keep it up!

Reviewed commit: a1181bff77

ℹ️ 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 force-pushed the issue-160-provenance-accounting branch from a1181bf to 85baf46 Compare November 3, 2026 17:01
@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. You're on a roll.

Reviewed commit: 85baf46dc4

ℹ️ 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 fae718d into main Nov 3, 2026
1 check passed
@jjangg96
jjangg96 deleted the issue-160-provenance-accounting branch November 3, 2026 17:24
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.

G01: account for pre-admission workflow provenance GET in recovery evidence

1 participant