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
Keep a second credential error from failing the session (#926)
* Keep a second credential error from failing the session
A rebuilt agent reused seq 0 for the next same-category inference
error, so commitErrors threw Duplicate error record and
afterCheckpoint failed the run. Resume the durable error sequence
on assembly and drop a colliding flush instead of failing the
session.
* Ledger vendor error sequence patches
* Drop only the colliding error record on a duplicate flush
A stale-seq assembly flushing [seq0/dup, seq1/fresh] discarded the whole batch, losing fresh diagnostics. The flush now maps the colliding key back to its record, drops only that record, and retries the rest in the same flush.
|`vendor/intx-inference/`|`faremeter/interchange`|`0205b07b64d03f0fec2e4be3593c764070a9ba8a`| Yes — `PATCHES.md`| Local fixes not yet upstream | runtime | 2027-03-07 or when patches land upstream and publish |
51
-
|`vendor/intx-types/`|`faremeter/interchange`|`0205b07b64d03f0fec2e4be3593c764070a9ba8a`|No | Cross-package coupling with `@intx/inference`| runtime | 2027-03-07 or when the coupled trio publishes past `0.3.0`|
52
-
|`vendor/intx-storage-isogit/`|`faremeter/interchange`|`0205b07b64d03f0fec2e4be3593c764070a9ba8a`|No | Cross-package coupling with `@intx/inference`| runtime | 2027-03-07 or when the coupled trio publishes past `0.3.0`|
53
-
|`vendor/intx-agent/`|`faremeter/interchange`|`0205b07b64d03f0fec2e4be3593c764070a9ba8a`|No | Vendored at Interchange head ahead of npm | runtime | 2027-03-07 or when `@intx/agent@>=0.4.0` publishes |
51
+
|`vendor/intx-types/`|`faremeter/interchange`|`0205b07b64d03f0fec2e4be3593c764070a9ba8a`|Yes — `PATCHES.md`| Cross-package coupling with `@intx/inference`| runtime | 2027-03-07 or when the coupled trio publishes past `0.3.0`|
52
+
|`vendor/intx-storage-isogit/`|`faremeter/interchange`|`0205b07b64d03f0fec2e4be3593c764070a9ba8a`|Yes — `PATCHES.md`| Cross-package coupling with `@intx/inference`| runtime | 2027-03-07 or when the coupled trio publishes past `0.3.0`|
53
+
|`vendor/intx-agent/`|`faremeter/interchange`|`0205b07b64d03f0fec2e4be3593c764070a9ba8a`|Yes — `PATCHES.md`| Vendored at Interchange head ahead of npm | runtime | 2027-03-07 or when `@intx/agent@>=0.4.0` publishes |
54
54
|`vendor/intx-authz/`|`faremeter/interchange`|`0205b07b64d03f0fec2e4be3593c764070a9ba8a`| No | Vendored at Interchange head ahead of npm | runtime | 2027-03-07 or when `@intx/authz@>=0.4.0` publishes |
55
55
|`vendor/intx-log/`|`faremeter/interchange`|`0205b07b64d03f0fec2e4be3593c764070a9ba8a`| No | Vendored at Interchange head ahead of npm | runtime | 2027-03-07 or when `@intx/log@>=0.4.0` publishes |
56
56
|`vendor/intx-tools-posix/`|`faremeter/interchange`|`0205b07b64d03f0fec2e4be3593c764070a9ba8a`| No | Vendored at Interchange head ahead of npm | runtime | 2027-03-07 or when `@intx/tools-posix@>=0.4.0` publishes |
@@ -118,9 +118,11 @@ The 2026-09-07 sync also vendored the remaining four consumed packages
118
118
(`@intx/agent`, `@intx/authz`, `@intx/log`, `@intx/tools-posix`) at the
119
119
same upstream commit, completing the set: every `@intx/*` package this
120
120
repo imports now resolves to vendored source. None of the four carried
121
-
local patches at vendoring time; their trees are verbatim upstream
122
-
copies. `@intx/tools-lsp` remains on published npm (`0.3.0`) — it is a
123
-
thin adapter whose transitive `@intx/*` dependencies resolve to the
121
+
local patches at vendoring time. `@intx/agent` later gained the error-seq
122
+
patches ledgered in `vendor/intx-agent/PATCHES.md`; the other three remain
123
+
verbatim upstream copies. `@intx/tools-lsp` remains on published npm
124
+
(`0.3.0`) — it is a thin adapter whose transitive `@intx/*` dependencies
125
+
resolve to the
124
126
vendored workspaces via root `overrides`, so it tracks the vendored set
125
127
without being vendored itself. Published transitive dependencies that
126
128
stay on npm (`@intx/crypto`, `@intx/inference-discovery`,
@@ -187,13 +189,14 @@ those packages now resolves to the single root instance. As of this sync,
187
189
188
190
## Patched vs. verbatim
189
191
190
-
Of the eleven vendored paths, exactly one carries local patches:
191
-
`@intx/inference` — every divergence is a real fix not yet upstream, listed
192
-
one-per-patch in `vendor/intx-inference/PATCHES.md`. The other ten paths
193
-
(nine whole packages plus the partial `vendor/intx-workflow-host/adapters/`
192
+
Of the eleven vendored paths, four carry local patches:
193
+
`@intx/inference`, `@intx/types`, `@intx/storage-isogit`, and
194
+
`@intx/agent` — every divergence is a real fix not yet upstream, listed
195
+
one-per-patch in that package's `PATCHES.md`. The other seven paths
196
+
(six whole packages plus the partial `vendor/intx-workflow-host/adapters/`
194
197
tree) are verbatim copies of upstream — no modifications. A diff against a
195
198
pristine upstream checkout at the same commit and paths will show 100%
196
-
upstream-authored lines.
199
+
upstream-authored lines for those seven.
197
200
198
201
## Notable upstream shape changes carried by the 2026-08-22 sync
199
202
@@ -229,12 +232,12 @@ different reason — the vendored mime sources import `@intx/crypto`, which
229
232
stays on published npm, and `Bun.build` cannot resolve that bare specifier
230
233
from inside the vendor workspace.
231
234
232
-
`@intx/inference` carries local patches — real fixes not yet present
233
-
upstream, not workarounds for something upstream has since fixed. Every
234
-
patched location carries a one-line comment naming its site-specific entry
235
-
in `vendor/intx-inference/PATCHES.md` (e.g. `#reactor-ts-correlating-ids-leak`),
236
-
so `grep -rn "Locally patched" vendor/intx-inference/src` finds every
237
-
divergence. **Markers are navigation; the SHA-diff is proof.** Run
235
+
Patched packages carry local fixes not yet present upstream, not
236
+
workarounds for something upstream has since fixed. Every patched
237
+
location carries a one-line comment naming its site-specific entry in
238
+
that package's `PATCHES.md` (e.g. `#reactor-ts-correlating-ids-leak`),
239
+
so `grep -rn "Locally patched" vendor/*/src` finds every divergence.
240
+
**Markers are navigation; the SHA-diff is proof.** Run
238
241
`bin/vendor-patch-diff` against a pristine upstream checkout at the
239
242
recorded SHA to print exactly the lines that are ours. A correspondence
240
243
test (`tests/unit/vendor-patch-ledger.test.ts`) fails if a marker anchor
@@ -253,7 +256,8 @@ does not resolve to a ledger heading, or if a ledger heading has no marker.
253
256
`adapters/substrate-mailbox-store.ts` and
254
257
`adapters/substrate-mailbox-store.test.ts`). Run
255
258
`bun install`, `bun run typecheck`, `bun run build`, `bun run test`.
256
-
3. For a **patched** package (`@intx/inference`): before overwriting
259
+
3. For a **patched** package (`@intx/inference`, `@intx/types`,
260
+
`@intx/storage-isogit`, `@intx/agent`): before overwriting
257
261
anything, run `bin/vendor-patch-diff` (optionally
258
262
`--upstream /path/to/interchange`) to re-derive the exact local
259
263
divergences against the recorded SHA — do not trust `PATCHES.md`'s
0 commit comments