chore(deps): align @wasmagent/* to latest, adopt AEP v0.3 evidence fields - #10
Merged
Merged
Conversation
…elds Bumps all 17 @wasmagent/* dependencies from the pinned 1.x line to current latest (core 1.0->3.3, model-* 1.0->2.0, aep 1.2->2.3, etc.), which had drifted two majors behind upstream. Beyond making it compile, this makes bscode — the Golden Path reference workload — actually exercise the AEP v0.3 evidence schema it now depends on, so the workload demonstrates the fields rather than emitting a v0.2-shaped record through a v0.3 library. AEP v0.3 fields now populated in buildAEPEvidence(): - side_effect_class: derived per tool (network-egress for git_push/ npm_publish, mutate-external for bash, mutate-local for file edits, read otherwise). Drives the emitter's run_side_effect_class_max. - recording_mode: risk-proportional per the AEP README — full for external/egress/tainted actions, delta for local mutation, validation for read-only. - approval_mode + deny_reason_class on capability decisions: executed tools -> policy-allow-with-receipt; firewall denials -> policy-deny-with-evidence + policy-rule. - input_taint_labels added alongside output_taint_labels for tainted input. Schema version emitted is now aep/v0.3; updated the assertion, the roundtrip script, and regenerated the shared JSONL fixture with a real Ed25519 signature. Added tests pinning the new-field derivation. Verification (providers down, operator manual build): - apps/worker: tsc clean, 511 pass / 0 fail (--isolate), wrangler build OK - apps/web: tsc clean, next build OK - biome check apps/: clean
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.
What
Bumps all 17
@wasmagent/*dependencies from the pinned1.xline to current npm latest (core1.0→3.3,model-*1.0→2.0,aep1.2→2.3, etc.). They had drifted two majors behind upstream.Why more than a bump
bscode is the Golden Path reference workload — the sample other integrators copy. If it emits a v0.2-shaped AEP record through a v0.3 library, the new evidence fields go undemonstrated. So this also makes
buildAEPEvidence()actually populate the AEP v0.3 schema:side_effect_class— derived per tool:network-egress(git_push/npm_publish),mutate-external(bash),mutate-local(file edits),readotherwise. Feeds the emitter'srun_side_effect_class_max.recording_mode— risk-proportional per the AEP README:fullfor external/egress/tainted actions,deltafor local mutation,validationfor read-only.approval_mode+deny_reason_class— executed tools →policy-allow-with-receipt; firewall denials →policy-deny-with-evidence+policy-rule.input_taint_labelsadded alongsideoutput_taint_labelsfor tainted input.Schema version emitted is now
aep/v0.3: updated the assertion + roundtrip script and regenerated the shared JSONL fixture with a real Ed25519 signature. Added tests pinning the new-field derivation.Verification (providers down — operator manual build)
apps/worker: tsc clean · 511 pass / 0 fail (--isolate) · wrangler build OKapps/web: tsc clean · next build OKbiome check apps/: cleanLocal gates green; queue merge uses local CI as source of truth per ops policy.