You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 50a79ce
Browse filesBrowse the repository at this point in the historyBrowse files
chore(vendor): re-sync the Interchange set and @intX deps to 0.5.0
Every published @intx/* dependency moves 0.3.0 -> 0.5.0 (root dependencies
and devDependencies, plus the published-package entries inside the vendored
manifests) and all eleven vendored Interchange paths re-sync to upstream
aa7b78ee, the peel of tag v0.5.0, recorded as a SHA because the released npm
metadata ships an empty gitHead. All forty-one entries across the five
PATCHES.md ledgers re-adjudicate to KEEP (32 inference, 4 types, 3 agent,
1 storage-isogit, 1 tools-posix); store.ts is the one patched file upstream
drift touched and goes through a three-way merge.
The adopted storage-isogit durability rewrite adds reads-before-write to
every session-record checkpoint: +1,000 .git readFile, +400 worktree readFile
and +200 worktree stat per 200 turns, against -200 .git/index writes. Those
are counted operations, not timings, so the CI session-store perf baseline
moves with the branch and is re-recorded here from the head arm; the four
failing counters, the cause and the accepted trade are disclosed in
docs/VENDORING.md rather than rounded away.
bin/vendor-patch-diff now prints the shape of each divergence (files, +, -)
so the per-ledger numbers quoted in PATCHES.md come from repo tooling; the
five re-sync sections quote its current output.
0 commit comments