dp_006 q06 100 files multi_hop Codex

The v0.5.0 release notes state that v0.4.2 was yanked from crates.io. But the May 2026 retro and issue #89 give different dates for the yank. What date does each source give, and what is the most precise reconciliation of the timeline?

Gold answer

The May 2026 retro (retro-may-2026.md) states 'v0.4.2 was yanked from crates.io on 2026-05-27'. Issue #89 shows @svenh asked for a yank on 2026-05-26 and @lior-bz responded 'Yanked. crates.io banner now reads: kitabi 0.4.2 yanked: ABI break, see #89.' in a comment dated 2026-05-27. The v0.5.0 release notes state 'v0.4.2 was yanked from crates.io on 2026-06-01', which contradicts both other sources. The most precise reconciliation: the yank happened on 2026-05-27 per the retro and per the issue thread timestamp; the 2026-06-01 date in the release notes appears to be an error (possibly when the release notes were drafted rather than when the yank occurred).

Filesystem View raw JSON
Input
298k
Output
5k
Steps
1
Tools
8
Latency
1.1m
Cost
$3.73
#1 Ran find agent_memory -maxdepth 3 -type f | sort 5,104 chars
Command command_execution
find agent_memory -maxdepth 3 -type f | sort
Result 10 lines
agent_memory/code/ARCHITECTURE.md
agent_memory/code/CONTRIBUTING.md
agent_memory/code/README.md
agent_memory/code/ROADMAP.md
agent_memory/code/SECURITY.md
agent_memory/code/adrs/ADR-001-language-choice-rust.md
agent_memory/code/adrs/ADR-002-parsing-tree-sitter.md
agent_memory/code/adrs/ADR-003-plugin-api-libloading.md
agent_memory/code/rfcs/RFC-001-org-mode-bidirectional.md
agent_memory/code/rfcs/…
#1 Ran rg -n \"v0\\.5\\.0|v0\\.4\\.2|yank|yanked|issue #89|#89|May 2026|retro\" agent_memory 99,217 chars
Command command_execution
rg -n \"v0\\.5\\.0|v0\\.4\\.2|yank|yanked|issue #89|#89|May 2026|retro\" agent_memory
Result 3 lines
agent_memory/email/sponsor-outreach-bytebase.md:6:> **Related:** [sponsor-outreach-astral.md](sponsor-outreach-astral.md), [notes/retro-june-2026.md](../notes/retro-june-2026.md)
agent_memory/email/sponsor-outreach-bytebase.md:76:  - v0.5.0 shipped today: concurrent file processing, which makes batch
agent_memory/email/sponsor-outreach-bytebase.md:105:later by reading a retro document or a heated …
#1 Ran nl -ba agent_memory/releases/release-v0.5.0-2026-06-08.md | sed -n '150,185p' 3,142 chars
Command command_execution
nl -ba agent_memory/releases/release-v0.5.0-2026-06-08.md | sed -n '150,185p'
Result 7 lines
   150	</details>
   151	
   152	---
   153	
   154	## Known limitations
   155	
   156	- **Bench-suite flakiness on shared CI runners** ([#97](../../issues/issue-097-bench-suite-flaky.md), **open**). The benchmark suite occasionally produces outlier numbers (>2σ from median) when run on GitHub Actions' shared runners due to noisy neighbors. We track this but have not solved it. If you are benchma…
#1 Ran nl -ba agent_memory/notes/retro-may-2026.md | sed -n '1,140p' 11,666 chars
Command command_execution
nl -ba agent_memory/notes/retro-may-2026.md | sed -n '1,140p'
Result 7 lines
     1	# May 2026 retro — plugin system, ABI break, ban, Kavya
     2	
     3	**Date:** 2026-05-31
     4	
     5	Predecessor: [retro-april-2026.md](retro-april-2026.md)
     6	
     7	May was the most eventful month since the /r/rust post in February. Shipped the biggest release yet, had the worst self-inflicted bug yet, gained a contributor I'm genuinely excited about, watched a star counter I'd…
#1 Ran nl -ba agent_memory/issues/issue-089-plugin-api-break.md | sed -n '1,240p' 13,706 chars
Command command_execution
nl -ba agent_memory/issues/issue-089-plugin-api-break.md | sed -n '1,240p'
Result 7 lines
     1	# Plugin API breaks between v0.4.1 and v0.4.2 (silent ABI change)
     2	
     3	**Issue #89** &middot; `bug` `plugin-api` `regression` `breaking`
     4	
     5	- **Opened:** 2026-05-26 by @svenh
     6	- **Closed:** 2026-06-08 by @lior-bz (alongside the v0.5.0 release)
     7	- **Resolution:** revert the offending signature change in v0.4.3 + add an ABI-version assertion in the loader (sh…
#1 Ran nl -ba agent_memory/issues/issue-089-plugin-api-break.md | sed -n '239,340p' 1,436 chars
Command command_execution
nl -ba agent_memory/issues/issue-089-plugin-api-break.md | sed -n '239,340p'
Result 7 lines
   239	## @lior-bz commented on 2026-06-08 (closing)
   240	
   241	Closed in v0.5. `CHANGELOG-PLUGIN-API.md` is live. Thanks @svenh, @hiroshi-n, @nadiap, @kitplug-toml.
   242	
   243	ADR-003 amendment summary, for the archive:
   244	
   245	- ABI changes ALWAYS bump `abi-version`. Never silent. Reviewer must check manifest delta on any PR touching `crates/plugin-loader/` or `crates/kitabi-plugi…
#1 Ran rg -n \"0\\.4\\.2|v0\\.4\\.2|0\\.4\\.3|v0\\.4\\.3|yank|yanked|crates\\.io|PR #88|pr-088|CHANGELOG-PLUGIN-API|ABI break\" agent_memory 33,893 chars
Command command_execution
rg -n \"0\\.4\\.2|v0\\.4\\.2|0\\.4\\.3|v0\\.4\\.3|yank|yanked|crates\\.io|PR #88|pr-088|CHANGELOG-PLUGIN-API|ABI break\" agent_memory
Result 3 lines
agent_memory/email/sponsor-outreach-bytebase.md:65:binary (crates.io: `kitabi`, invoked as `kit`). It started as a personal
agent_memory/code/SECURITY.md:70:Pre-`v1.0.0` semantics: minor bumps may break the plugin ABI. ABI breaks are called out in release notes. Once we cut `v1.0.0`, this support window will widen.
agent_memory/code/SECURITY.md:99:**Fix.** Manifests are now parsed, paths are canon…
#1 Ran find agent_memory -iname '*088*' -o -iname '*plugin*api*' -o -iname '*changelog*' | sort 157 chars
Command command_execution
find agent_memory -iname '*088*' -o -iname '*plugin*api*' -o -iname '*changelog*' | sort
Result 4 lines
agent_memory/code/adrs/ADR-003-plugin-api-libloading.md
agent_memory/issues/issue-089-plugin-api-break.md
agent_memory/pr_threads/pr-088-yaml-frontmatter.md
Answer
The sources give: - v0.5.0 release notes: `2026-06-01` for the yank. See [release-v0.5.0-2026-06-08.md](/Users/prasanna/Documents/supermemoryai/supermemoryfs/.scratch/eval/eval/workspace/fs/dp_006/agent_memory/releases/release-v0.5.0-2026-06-08.md:169). - May 2026 retro: `2026-05-27`. It also says `v0.4.3` shipped `2026-05-28`. See [retro-may-2026.md](/Users/prasanna/Documents/supermemoryai/supermemoryfs/.scratch/eval/eval/workspace/fs/dp_006/agent_memory/notes/retro-may-2026.md:63). - Issue #8…
Judge: covers all asked facts
SMFS Won View raw JSON
Input
189k
Output
4k
Steps
1
Tools
8
Latency
1.8m
Cost
$2.39
#1 Ran rg --files 3,815 chars
Command command_execution
rg --files
Result 12 lines
profile.md
releases/release-v0.6.2-prep-2026-06-30.md
releases/release-v0.6.0-2026-06-22.md
releases/release-v0.5.0-2026-06-08.md
releases/release-v0.4.0-2026-05-15.md
releases/release-v0.3.5-hotfix-2026-04-28.md
releases/release-v0.3.0-2026-03-31.md
releases/release-v0.2.0-2026-02-28.md
releases/release-v0.1.0-2026-01-22.md
pr_threads/pr-095-docs-overhaul.md
pr_threads/pr-092-typst-output.md
pr_t…
#1 Ran smfs grep "v0.5.0 release notes v0.4.2 yanked crates.io May 2026 retro issue #89 yank date" 7,231 chars
Command command_execution
smfs grep "v0.5.0 release notes v0.4.2 yanked crates.io May 2026 retro issue #89 yank date"
Result 5 lines
# supermemory semantic search — 10 results for "v0.5.0 release notes v0.4.2 yanked crates.io May 2026 retro issue #89 yank date"
# searches by meaning across files in this container. usage:
#   grep "natural language query"          search all files
#   grep "query" path/to/dir/              search within directory
# output: <filepath>:<line_start>-<line_end>:<chunk> (chunk text is verbatim from t…
#1 Ran nl -ba releases/release-v0.5.0-2026-06-08.md | sed -n '145,180p' 2,872 chars
Command command_execution
nl -ba releases/release-v0.5.0-2026-06-08.md | sed -n '145,180p'
Result 3 lines
   145	- XL corpus OOM'd on v0.4.2 because the old sequential path loaded all files into memory before processing. The new scheduler streams files lazily. This is a separate improvement from the parallelism.
   146	- Times are median of 5 runs, `hyperfine --warmup 2`.
   147	- The 26× gain on the Wikipedia subset is partly from the AST flattening fix (#41) and partly from parallelism. Isolating th…
#1 Ran nl -ba notes/retro-may-2026.md | sed -n '1,120p' 10,315 chars
Command command_execution
nl -ba notes/retro-may-2026.md | sed -n '1,120p'
Result 7 lines
     1	# May 2026 retro — plugin system, ABI break, ban, Kavya
     2	
     3	**Date:** 2026-05-31
     4	
     5	Predecessor: [retro-april-2026.md](retro-april-2026.md)
     6	
     7	May was the most eventful month since the /r/rust post in February. Shipped the biggest release yet, had the worst self-inflicted bug yet, gained a contributor I'm genuinely excited about, watched a star counter I'd…
#1 Ran nl -ba issues/issue-089-plugin-api-break.md | sed -n '1,210p' 12,335 chars
Command command_execution
nl -ba issues/issue-089-plugin-api-break.md | sed -n '1,210p'
Result 7 lines
     1	# Plugin API breaks between v0.4.1 and v0.4.2 (silent ABI change)
     2	
     3	**Issue #89** &middot; `bug` `plugin-api` `regression` `breaking`
     4	
     5	- **Opened:** 2026-05-26 by @svenh
     6	- **Closed:** 2026-06-08 by @lior-bz (alongside the v0.5.0 release)
     7	- **Resolution:** revert the offending signature change in v0.4.3 + add an ABI-version assertion in the loader (sh…
#1 Ran smfs grep "v0.4.2 yanked June 1 May 27 crates.io banner issue 89 v0.4.3" /Users/prasanna/Documents/supermemoryai/supermemoryfs/.scratch/eval… 7,221 chars
Command command_execution
smfs grep "v0.4.2 yanked June 1 May 27 crates.io banner issue 89 v0.4.3" /Users/prasanna/Documents/supermemoryai/supermemoryfs/.scratch/eval/eval/workspace/smfs/dp_006/agent_memory
Result 7 lines
# supermemory semantic search — 10 results for "v0.4.2 yanked June 1 May 27 crates.io banner issue 89 v0.4.3"
# searches by meaning across files in this container. usage:
#   grep "natural language query"          search all files
#   grep "query" path/to/dir/              search within directory
# output: <filepath>:<line_start>-<line_end>:<chunk> (chunk text is verbatim from the file)

/issues/i…
#1 Ran nl -ba issues/issue-089-plugin-api-break.md | sed -n '210,320p' 2,753 chars
Command command_execution
nl -ba issues/issue-089-plugin-api-break.md | sed -n '210,320p'
Result 9 lines
   210	
   211	## @hiroshi-n commented on 2026-06-02
   212	
   213	LGTM on the assertion. Error message is specific. Path, declared, expected, symbol context, suggested action. Good.
   214	
   215	I tested with three permutations:
   216	
   217	1. Plugin built against 0.4.1 (declares abi-version=1), loader at 0.5.0 (expects 2): clean error, exit 4. Correct.
   218	2. Plugin built against 0.5.0 …
#1 Ran rg -n \"0\\.4\\.2|yank|yanked|v0\\.4\\.3|2026-06-01|2026-05-27\" 17,870 chars
Command command_execution
rg -n \"0\\.4\\.2|yank|yanked|v0\\.4\\.3|2026-06-01|2026-05-27\"
Result 2 lines
memory/profiles/sven-halgrimsson.md:154:## Issue #89 — Plugin API Silent ABI Break (v0.4.1→v0.4.2)
memory/profiles/sven-halgrimsson.md:160:The most-cited issue Sven has filed. Between v0.4.1 and v0.4.2 a change in the plugin ABI trait's internal field ordering caused a silent incompatibility: plugins compiled against v0.4.1 would load under v0.4.2 without error but produce corrupted output. No pan…
Answer
The sources give: - v0.5.0 release notes: `2026-06-01` for the crates.io yank: [release-v0.5.0-2026-06-08.md](/Users/prasanna/Documents/supermemoryai/supermemoryfs/.scratch/eval/eval/workspace/smfs/dp_006/agent_memory/releases/release-v0.5.0-2026-06-08.md:169) - May 2026 retro: `2026-05-27` for the yank, then `2026-05-28` for v0.4.3: [retro-may-2026.md](/Users/prasanna/Documents/supermemoryai/supermemoryfs/.scratch/eval/eval/workspace/smfs/dp_006/agent_memory/notes/retro-may-2026.md:63) - Issue…
Judge: covers all asked facts