Skip to content

fix(workflows): adopt QPK drift workflow with updated AAB parser - #221

Merged
Pigbibi merged 1 commit into
mainfrom
codex/crypto-aab-drift-adoption-20260906
Sep 6, 2026
Merged

Pigbibi merged 1 commit into
mainfrom
codex/crypto-aab-drift-adoption-20260906

Conversation

@Pigbibi

@Pigbibi Pigbibi commented Sep 6, 2026

Copy link
Copy Markdown
Contributor

Scope

  • Update only drift job reusable-workflow uses@ to merged QPK #552 commit 33e506f1c89977f55f284d777fb5b748cfd30798, which checks out AIAuditBridge 2351c987d6df12d48355aaa5803db8b089476310.
  • Update the existing workflow test and make the independent preflight/runtime QPK refs explicit: preflight stays aae333fe8b3fe5aeb32e1ff135ab14ea7db32420; runtime quant_platform_kit_ref stays cd6edbb32bb85ec6d280c2dafea4dd8ecd3ccdab.
  • Exactly two files. No package pins, QPK_PIN, dependencies, lockfiles, profiles, strategy logic, permissions, schedules or dispatch conditions changed.

Validation

  • Existing focused workflow test baseline: 1 passed.
  • Tests first: new expected workflow ref against old workflow produced 1 failed at the exact uses-ref assertion.
  • After changing only the workflow uses-ref: 1 passed in 0.02s.
  • Tests ran with an existing read-only interpreter, clean environment, worktree-local PYTHONPATH, network denied and bytecode/cache disabled; no environment changes or dependency installation.
  • actionlint on drift-check.yml: passed.
  • git diff --check and cached diff check: passed.
  • Exact two-file scope and workflow uses-only comparison: passed; independent runtime refs and triggers unchanged.
  • Natural required CI will run configured actionlint and engineering tests/lint/build. No manual drift run was dispatched.

Adoption boundary

This completes the targeted caller reference change for the already merged QPK/AAB fixes; it does not upgrade QPK runtime libraries or perform an organization-wide pin rollout. Existing authorized scheduling can naturally adopt it after merge. AAB checkout crosses 59 commits; the main conversation separately verified existing parser/orchestrator/pipeline/drift entrypoint compatibility offline.

No real research, AI/provider/broker invocation, artifact acquisition or manual workflow dispatch was performed. Passing CI is not evidence of an actual drift/review cycle. Merge remains coordinated by the main conversation; auto-merge is not enabled.

@Pigbibi
Pigbibi merged commit e606b93 into main Sep 6, 2026
3 of 4 checks passed
@Pigbibi
Pigbibi deleted the codex/crypto-aab-drift-adoption-20260906 branch September 6, 2026 06:13
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