#1 Ran find agent_memory -maxdepth 3 -type f | sort 5,104 chars
find agent_memory -maxdepth 3 -type f | sort
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 "ADR-003|Status and timeline|CVE-2026-31418|31418|security disclosure|MITRE|public advisory|elapsed" agent_memory . 136,638 chars
rg -n "ADR-003|Status and timeline|CVE-2026-31418|31418|security disclosure|MITRE|public advisory|elapsed" agent_memory .
agent_memory/email/sponsor-outreach-bytebase.md:174:is documented in ADR-003 in the repo, and it remains a live debate in the ./agent_memory/email/sponsor-outreach-bytebase.md:174:is documented in ADR-003 in the repo, and it remains a live debate in the agent_memory/email/security-disclosure-cve-2026-31418.md:1:# Security Disclosure Thread — CVE-2026-31418 agent_memory/email/security-disclosure-cv…
#1 Ran nl -ba agent_memory/code/adrs/ADR-003-plugin-api-libloading.md | sed -n '1,260p' 13,873 chars
nl -ba agent_memory/code/adrs/ADR-003-plugin-api-libloading.md | sed -n '1,260p'
1 # ADR-003: Plugin API — `libloading` + ABI-safe FFI (NOT WASM)
2
3 - **Number:** ADR-003
4 - **Date:** 2026-04-15
5 - **Author:** @lior-bz
6 - **Status:** Accepted (contested)
7 - **Reviewers consulted:** @svenh, @hiroshi-n, @nadiap (informal review on #103)
8 - **Supersedes:** none
9 - **Superseded by:** none
10 - **Decision deadline:** 2026-04-… #1 Ran nl -ba agent_memory/email/security-disclosure-cve-2026-31418.md | sed -n '420,445p' 1,207 chars
nl -ba agent_memory/email/security-disclosure-cve-2026-31418.md | sed -n '420,445p'
420 421 Agreed on 18:00 CET. I'll be online at that time (01:00 JST) to confirm the advisory went live. Thank you for handling this efficiently — report to patch in under 48 hours is fast work. The coordinated disclosure process worked as it should. 422 423 Regards, 424 Hiroshi 425 426 Hiroshi Nakamura | @hiroshi-n on GitHub 427 Tokyo, Japan · UTC+9 · Replies may be dela…
#1 Ran nl -ba agent_memory/email/security-disclosure-cve-2026-31418.md | sed -n '130,210p' 4,186 chars
nl -ba agent_memory/email/security-disclosure-cve-2026-31418.md | sed -n '130,210p'
130 **Subject:** Re: Security: path traversal in plugin loader 131 **Date:** 2026-04-26 16:14 CET 132 133 --- 134 135 > I am reporting a path-traversal vulnerability in kitabi's plugin loader. 136 > CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N 137 138 Hiroshi, 139 140 Confirmed receipt. I've reviewed the loader code at `src/plugin/loader.rs`. You're right — no …
#1 Ran nl -ba agent_memory/code/adrs/ADR-003-plugin-api-libloading.md | sed -n '260,430p' 4,480 chars
nl -ba agent_memory/code/adrs/ADR-003-plugin-api-libloading.md | sed -n '260,430p'
260 for v0.7 anyway — likely, given signed manifests are coming — we'll fold the 261 `dlopen2` evaluation into that work. 262 263 --- 264 265 ## 7. The #103 thread, summarised 266 267 > "This is shortsighted. WASM is the future of plugin systems and you're 268 > betting against the ecosystem to save 200ms of startup time." 269 > — community member, #103, 2026-04-18…
#1 Ran /bin/zsh -lc 'rg -n "''^## 9'"\\.|Status and timeline|"'^'"\\|\" agent_memory/code/adrs/ADR-003-plugin-api-libloading.md" 442 chars
/bin/zsh -lc 'rg -n "''^## 9'"\\.|Status and timeline|"'^'"\\|\" agent_memory/code/adrs/ADR-003-plugin-api-libloading.md"
321:## 9. Status and timeline 323:| Date | Event | 324:|---|---| 325:| 2026-04-15 | ADR-003 accepted (this document) | 326:| 2026-04-22 | PR #71 (plugin system v1) opened | 327:| 2026-04-28 | v0.3.5 hotfix for CVE-2026-31418 (manifest parser) | 328:| 2026-05-15 | v0.4.0 ships with plugin system | 329:| 2026-06-08 | v0.5.0 — ABI-version assertion added in loader (post-#89) | 330:| 2027-04 (target) …
#1 Ran rg -n \"MITRE|assigned|Submitted yesterday|CVE assigned|Date:\\*\\* 2026-04-27|Total elapsed time\" agent_memory/email/security-disclosure-c… 705 chars
rg -n \"MITRE|assigned|Submitted yesterday|CVE assigned|Date:\\*\\* 2026-04-27|Total elapsed time\" agent_memory/email/security-disclosure-cve-2026-31418.md
144:I'll request a CVE from MITRE today. Coordinated disclosure is fine; nothing goes public until we agree. My default is a 7-day window from CVE assignment, but I'm flexible. I'll come back once the CVE number is in hand, likely tomorrow morning. 180:**Date:** 2026-04-27 10:08 CET 184:> I'll request a CVE from MITRE today. 186:CVE assigned: **CVE-2026-31418**. 188:Submitted yesterday evening, re…
#1 Ran nl -ba agent_memory/email/security-disclosure-cve-2026-31418.md | sed -n '1,80p' 4,444 chars
nl -ba agent_memory/email/security-disclosure-cve-2026-31418.md | sed -n '1,80p'
1 # Security Disclosure Thread — CVE-2026-31418
2
3 **Archive note:** This thread is preserved verbatim (sanitized) for transparency in the project's security archive. This file is a redacted version of the private disclosure exchange conducted under coordinated-disclosure terms. The POC attachment has been redacted. The full unredacted thread is held offline by the maintainer.
…