chore(cpex-ocsf-audit): track PR #84 at 499ee91, hold base64 at 0.22 to match the PPE tree - #525
Merged
Merged
Conversation
…to match the PPE tree Teryl answered the two dependency findings on praxis-proxy/policy PR #84 on 2026-09-09: sha2 is a workspace dependency at 0.11 (ef20d8f), and base64 stays at 0.22 across the tree because jsonwebtoken 11 requires it. The same head merges the #82 docs reorganisation (docs/content/auditing.md). Nothing on the seam this crate consumes changed between 3e7734e and 499ee91. - Move the praxis-policy-core pin to 499ee91; regenerate the lock. - Pin base64 down from 0.23 to 0.22 so the in-tree copy under reference/plugins/ocsf-audit is a copy and PPE stays on one base64; a Renovate rule holds it there. - PRAXIS-INTREE-PLAN.md: only p256 is a workspace-table add now; the base64 question is settled; auditing guide path updated. - PRAXIS-PORT-RESULTS.md, README, Cargo.toml and the CI comment record the re-verification. Verified on 1.96.1 with cpex at 64c8eba: warning-free --locked builds and 34 tests green on both hosts; emit_sample and decision_sink_demo byte-identical to the committed vectors; panic_drive lands on gw-1:decision on PPE. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019XNHGsnzrXrncvFnSSCZTF
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
1 participant
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.
Why
Teryl answered the two dependency findings on praxis-proxy/policy PR #84 on 2026-09-09:
sha2is now a workspace dependency at0.11(ef20d8f), which is what praxis-bot asked for.base64stays at0.22across the tree becausejsonwebtoken11 (used byidentity-jwt) requires it;0.23would put two majors in the build. Verified against the PPE lock:jsonwebtoken 11.0.0listsbase64 0.22.1.The same head merges the #82 docs reorganisation, which moves the auditing guide to
docs/content/auditing.md. Nothing on the seam this crate consumes changed between3e7734eand499ee91(theppe-corediff is thesha2manifest line and two doc-comment renames).What
integrations/cpex-ocsf-audit: pinpraxis-policy-coreat499ee91; regenerateCargo.lock.base64down from0.23(a Renovate bump, fix(deps): update rust non-major #497) to0.22, so the copy that lands underreference/plugins/ocsf-auditperPRAXIS-INTREE-PLAN.mdis a copy and the PPE build stays on one base64. OnlyEngine::{encode,decode}ongeneral_purpose::STANDARDis used, identical across both majors. Arenovate.jsonrule holds it below0.23.PRAXIS-INTREE-PLAN.md:sha2andbase64drop out of the workspace-table adds (onlyp256remains), thebase64open question is recorded as settled, the auditing guide path follows the move.PRAXIS-PORT-RESULTS.md,README.md, theCargo.tomlpin comment and the CI workflow comment record the re-verification; the CI comment no longer hard-codes a PR head that goes stale on every bump.Verification
Run the way CI runs it: toolchain 1.96.1, cpex sibling at
64c8eba.499ee91)cargo check --locked --all-targets,RUSTFLAGS=-D warningscargo test --lockedcargo run --example emit_samplevsSAMPLE-OUTPUT.mdcargo run --example decision_sink_demovsSAMPLE-OUTPUT-DECISIONS.mdcargo run --example panic_driveplugin_panic,gw-1:decision, host epoch,stream_seq0All results above are with
base64 = "0.22"in place; the same bar was also green at the new pin before the base64 change.Docs and dependency pins only; no source change.
🤖 Generated with Claude Code
https://claude.ai/code/session_019XNHGsnzrXrncvFnSSCZTF
Generated by Claude Code