Repository navigation
chore(vendor): re-sync interchange vendor trees to 0.4.0, re-carry patches - #1424
Merged
TheGreatAxios merged 3 commits intoOct 15, 2026
Conversation
Re-sync per the docs/VENDORING.md procedure; adjudication lands with the patch commit.
Adjudicated the local patch ledger against upstream 0.4.0 (5453d0b0): all 38 ledger entries verified KEEP; the four carried-forward DROP notes are contradicted by evidence at this pin and are kept, with reasons recorded in docs/VENDORING.md; three unclear labels adjudicated no-match with the closest candidates noted; one previously never-ledgered tools-posix divergence (paged read_file description + registry-contract test) recovered and ledgered now. PATCHES.md ledgers, docs/VENDORING.md, and the vendored package.json src-mode export convention arrive here, not in the pristine commit.
Contributor
|
Triage: Fail @TheGreatAxios, please address the following:
|
The first sync commit still contains local lines, so it is not an unmodified upstream tree, and the second commit is not a patch-only replay onto a later pin. The auditable tree is the branch tip. @intx/tools-posix stays in the patched set, and packages published at npm 0.4.0 are no longer described as unpublished or ahead of npm.
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
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.
Summary
vendor/intx-*trees to upstream interchange 0.4.0 (5453d0b0). Commit865f63c6is not a pristine byte-identical snapshot of that pin (local lines remain, includingephemeralTurns/Locally patchedinvendor/intx-inference/src/reactor.ts). The auditable artifact is the branch tip: upstream5453d0b0plus the carried local patches. Replaying the second commit onto a later pristine pin is not patch-only.ephemeralTurns/ExtendedInferenceOptions(reactor.ts; used by director/nudge-director/cache-breakpoint), doom-loop poll exemption, stream-terminal detector pair, andClassifiedAbortRaw— with a companion settle test in the vendorederrors.test.ts.PATCHES.mdledgers updated + the commissioned adjudication recorded: 38 ledger entries verified KEEP; the four carried-forward DELETE notes are contradicted at this pin and kept (context-transforms pair, agent flush chain, commitment boundary, frozen-turns pair); three unclear ledger labels adjudicated no-match with closest candidates named;expectedFromremoval is post-0.4.0 and reconciles with zero first-party references (the correlator-as-capability model change this enables is tracked in CL-10678's security work).bin/vendor-patch-diffsurfaced a never-ledgered pre-existing divergence invendor/intx-tools-posix(pagedread_filedescription + registry-contract test) — now ledgered with markers,tools-posixmoved verbatim to patched in the VENDORING tables, and step 3 of the resync procedure lists it as patched so a later sync does not dropregistry-ts-read-file-paging-description../testingsubpath (waitUntiland friends) live in vendored@intx/types/@intx/agent;ApprovalItemandwaitForReactorDonearrive verbatim;PerCallInferenceOptionsis post-0.4.0 (HEAD, CL-10656 scope) soephemeralTurnsstays for the nudge use-case with reasons recorded.@intx/mailbox,@intx/agent,@intx/authz,@intx/log,@intx/harness, and@intx/tools-posixare published at npm0.4.0. Patched packages stay vendored for their local patches. Verbatim packages are not described as unpublished.src/changes; all tests green.Verification
bun run checkexit 0: full one-process suite 8938 pass / 0 fail across 580 files;bun test scripts/vendor-patch-ledger.test.ts2 pass (marker-ledger correspondence, incl. the recovered tools-posix entry);e2e/vendored-carry.test.tsgreen (both carried-patch integration tests).git diff 4dd0ee01..HEAD --stat -- src/is empty. There is no exhaustivecmpclaiming865f63c6matches upstream.intx-types/package.jsonkeeps the documented src-mode/0.2.2local convention (not a re-sync miss; the +4 delta is the./testingsubpath adoption) — VENDORING.md documents this convention.substrate-mailbox-store.test.tsfailure (cannot resolve@intx/hub-sessionsfrom the vendored subtree) is documented in VENDORING and unchanged by this branch.Fixes CL-10651