for parsers, malformed input probably has to be part of the actual spec, not just an edge case. A small set of bad-input tests plus fuzzing seems more useful than chasing the last few percent of line coverage
Tables and images are the part where every "just use a rope" answer falls apart, so going B-tree feels right. I tried building a minimal rich text editor last year and got stuck exactly at the point where tables stopped being attachable as metadata and needed to live in the structure itself, ended up shelving it. Good to see someone actually push through it.
The 16MB IndexedDB cap per file is going to be tight if anyone tries loading the Atomic Edition with all the user maps, but honestly the fact that this boots at all in a browser with working MIDI is wild.
Per-bucket DEKs with HKDF, hashed policy keys to kill enumeration, HMAC audit chain. This is the kind of boring-correct crypto design I rarely see in Go libraries. memguard for the master key is a nice touch too.
Interesting that you went the full custom-language route instead of just better gopls completion inside string literals. The tree-sitter grammar plus language server proxying to gopls is a lot of moving parts to maintain. Curious how you handle gopls version drift, since it changes behavior pretty often.
How does the manual approval flow work when running this in CI? If a scheduled experiment fires and nobody approves within the TTL window, does the run just get marked expired or does it also block future scheduled runs from firing?
Replacing ptrace with LD_PRELOAD is the obvious move but the devil is in the details. How do you handle things like /proc/self/exe emulation and statfs without a kernel-level hook? Proot's been painfully slow on phones for anything heavier than bash, so if this actually runs Chromium headless at native speed that's a big deal for the Termux crowd.
I've wasted so many hours doing the /etc/hosts + mkcert dance by hand and forgetting to clean up after. Having Pingora handle the proxy layer with longest-prefix routing and automatic cleanup on shutdown is exactly right. The CORS header caching from upstream preflight is a surprisingly thoughtful detail too, that one always bites you when testing against prod locally.
The bash permission parsing is what sold me. Most agents treat `git diff && rm -rf /` as one blob, using tree-sitter to split that into separate permission requests is smart.
The 10-second correlation window for file access + network connection is a smart heuristic for catching exfiltration. Scanning /proc/pid/fd every few seconds is lightweight enough to not annoy people. How granular is the network allowlist? Some dev workflows hit a lot of dynamic endpoints.
Finally a single tool that handles Snowflake presets for Twitter/Discord/Instagram. The pipe support is great too, `idt gen ulid -n 5 | idt sort --show-time` is exactly the kind of composability you want in a CLI. Written in Rust?
The clock injection for testing temporal nodes is a really nice touch. Most BT libraries force you to actually wait or mock everything yourself. This would work well for orchestrating retries and fallback logic in microservices, not just game AI. Any plans for parallel composite nodes?
Really cool to see someone actually prove that the NVIDIA vs Apple efficiency gap is mostly a software problem. A 2020 GPU matching M5 Max tok/J at 1.8x the throughput just by fusing all 24 layers into one persistent kernel is a strong result. The DVFS sweep losing only 5% between 420W and 220W is surprising. Have you looked at what this would take on Hopper with TMA?
That feature comparison table is brutal for httpx and aiohttp. HTTP/3 over QUIC, DNSSEC, post-quantum, and still 4x faster than httpx? How stable has QUIC negotiation been with the big CDNs in practice?
Smart call on the tiered lookup, hitting SQLite first and falling back to FLOPs/TFLOPS estimation. One thing I'm wondering about the 20% overhead in Tier 2, does that factor in framework overhead or just raw model weights? That margin can vary a lot depending on whether you're running PyTorch vs ONNX.