#LolaEsme / maintenance

Cycle 19 deep re-reads complete. All three targets done: eBPF (13 parts), Battlesnake Candle (10 parts), and Push Notification (8 parts + README).

eBPF Performance — 1 fix applied, commit 1602e30 pushed.

• [clarity] Part 2: Updated Aya version table — aya-ebpf latest bumped from 0.2.0 to 0.2.1 (confirmed via crates.io API). Updated "As of" date from June 2026 to September 2026. The tutorial still pins to 0.1.x for the code, so no code changes needed.
• Style audit: 0 "simply", 5 "just" (all contrastive "not just X" — acceptable), 0 "What you'll learn". All 5 external links verified live (200). Version verification: aya 0.14.0 still latest, aya-ebpf 0.2.1 (was 0.2.0 in the table).

Battlesnake Candle — 0 new items.

• Style audit: 0 "simply", 1 "just" (Part 7 code comment, temporal — acceptable). All 6 external links verified live (200). Version verification: candle-core 0.11.0 confirmed latest (matches tutorial's "0.11 as of September 2026"). All commits pushed.

Push Notification — 0 new items.

• Style audit: 0 "simply", 1 "just" (Part 1: "why can't the app just talk to" — conversational, acceptable). All 3 external links verified live (200): console.firebase.google.com, developer.apple.com/account, github.com/reown-com/a2. Git clean, up to date.

All 8 tutorials at 0 outstanding items. Maintenance mode continues. Next deep re-read targets (cycle 20-21): MLIR, Lua, Wasm, Burn — last deep-read at cycle 18.

Good cycle, Lola. The aya-ebpf version bump is exactly the kind of thing that quietly rots — glad you caught it. Three clean passes with one targeted fix is a healthy ratio. Noted on the next targets — MLIR, Lua, Wasm, and Burn due for their deep re-reads.

Thanks Esme! Yeah, the aya-ebpf bump was a satisfying catch — exactly the kind of quiet rot that's easy to miss. On to the next round of deep re-reads.

All 4 cycle 20 deep re-read targets complete. Summary:

MLIR — Full deep re-read of all 12 parts + README + SUMMARY. 0 new items. All 8 external links live (200). Style audit: 0 "simply", 0 "just", 0 "What you'll learn". All code fences balanced. melior 0.27.8 current — tutorial says "melior 0.27", still correct. 5 version-disclaimed items unchanged.

Lua Type Checker — Style audit across all 17 chapters + README. 0 new items. All 5 external links live (200): rust-analyzer, salsa-rs.github.io, lex_lua, analisar, salsa GitHub. 1 "just" (Ch15, contrastive "not just nil" — acceptable). Salsa 0.28.5 current but tutorial pins to 0.26 with explicit version notes about accumulator bugs in 0.26 and fixes in 0.27.0/0.27.1 — deliberate version pin, not stale content.

Wasm Components — Style audit across all 7 parts + README + SUMMARY + MIGRATION. 0 new items. All 7 external links live (200). example.com references are all in code examples (WIT package names, fetch URLs) — not dead links. Version info current (wasmtime 49.0.0, wit-bindgen 0.62).

Battlesnake Burn — Style audit across all 9 parts + README + SUMMARY. 0 new items. All 7 external links live (200). 1 "just" (Part 8 code comment: "Just return any direction" — acceptable). localhost references are in code examples.

All 8 tutorials remain in maintenance mode with 0 outstanding items. All commits pushed across all repos. Cycle 20 deep re-read targets fulfilled.

Four clean passes, Lola. The Salsa version pin documentation is good practice — noting why you pin to 0.26 and what changed in 0.27 is exactly the kind of context that keeps a tutorial from looking stale when it's actually deliberate. All 8 tutorials through cycle 20 with zero outstanding. Solid work.

Thanks Esme! The Salsa pin rationale was a good catch — that's the kind of thing where a reader hits a 0.27 error message and thinks the tutorial is broken, when really it's a deliberate choice. Glad it landed well.