Skip to content

fix(hooks): refresh the shipped Yupana bundle to 0.15.4 - #190

Merged
scbrown merged 4 commits into
mainfrom
grant/epps0w-yupana-bundle-20261024
Oct 24, 2026
Merged

scbrown merged 4 commits into
mainfrom
grant/epps0w-yupana-bundle-20261024

Conversation

@scbrown

@scbrown scbrown commented Oct 24, 2026

Copy link
Copy Markdown
Collaborator

The shipped Yupana hook bundle is still 0.10.5, so a normal bundle refresh can replace a newer registered bundle with stale hooks. Carry the exact canonical v0.15.4 bundle, pin its source commit and bytes, and keep controls for the failure hook, native edit guard and opt-in read hook. Other tool bundles and notify ownership are unchanged.

Validation: three Python controls pass; the old carrier fails the origin/read-hook controls while the existing-route preservation control passes. Native hook-bundle tests: 15 passed, 2 intentionally ignored host-registry tests; HOME guard clean across 157 watched paths and 5 UID resources. Formatting passes.

Demo unavailable: live hook registration is outside this source-only PR. Offline declaration transcript: version 0.10.5 -> 0.15.4; hooks 4 -> 7; read hook 0 -> 1; no legend flags enabled. Reproduce with python3 tests/test_yupana_bundle_origin.py; provenance is in hook-bundles/yupana.origin.json. The read hook remains Claude-only and default-off; this does not enroll Codex or activate a legend trial.

Delivery: normal reviewed Tambo release/install and whole-bundle registration, retaining unrelated hooks. Rollback restores the prior reviewed whole bundle via the same path. No registry write, service restart or environment change was performed.

@scbrown

scbrown commented Oct 24, 2026

Copy link
Copy Markdown
Collaborator Author

Fixed the shared CLI fixture at f8dd87303cc25507e5ebcb568de13891ffc911d1 (current main merged). The fixture previously parsed every file under hook-bundles/ as a bundle; the new provenance sidecar triggered the name unwrap and failed unrelated CLI tests. It now seeds from the actual hook_bundles::BUNDLES inventory. Bundle and provenance bytes are unchanged.

Before: the installer self-update CLI control fails at fixture setup. After: full all-features tests pass 288 passed, 12 ignored, including that control; all three bundle-origin controls pass and a private altered-bundle negative still fails. Normal-concurrency verification was repeated on the integrated head. An earlier local Text file busy unit-test failure is retained; it was not counted as passing.

Fresh hosted CI is pending. No hook registration, daemon change or trial enrollment performed.

@scbrown

scbrown commented Oct 24, 2026

Copy link
Copy Markdown
Collaborator Author

Independent source review (Ian): APPROVE exact 86f6cb698340769a183641d548f90503ead910e9 against 7ae5e2c07210b9b02bd5fc8224ddb83fcba1dc79.

Reviewed all six changed paths. The carrier matches the pinned Yupana v0.15.4 tag/commit after version substitution and canonical JSON formatting; its packaged SHA256 is 650098cc77a3520f23632b9716a5ca19f237dd2184ea1f024311b719cb776b23. It is semantically identical to the source template, rather than a literal raw-file copy. Existing failure/edit routes remain, read-hook enrollment stays Claude-only, and notify ownership is untouched. The documented exit-0 denial envelope survives the wrapper. The fixture now seeds the actual runtime bundle inventory instead of treating provenance sidecars as bundles; the adapter source witness matches its file.

Independent validation: 15 bundle tests passed (two host-registry tests intentionally ignored), two CLI bundle controls, one installer self-update regression, and three Python controls passed. HOME/resource guard clean. Native content review accepted 9cf3ee6837d51b1c1a50f578b717577d93ecd307eb6b48216f3b7bb5c0e0044c.

This approves the source carrier. Registration, release/install, feature flags, and live hook/legend acceptance retain their separate holds.

@scbrown
scbrown merged commit bcf91fc into main Oct 24, 2026
22 checks passed
@scbrown
scbrown deleted the grant/epps0w-yupana-bundle-20261024 branch October 24, 2026 14: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