OSS Contributions
Problems I hit while using other people’s tools, taken upstream: two merged fixes and one root-caused bug report.
Bug reportsCode contributionsMaintainer collaboration- #102 AgentsMesh merged · 21 Jul 2026 The follow-up the maintainer asked for: a read-only check that finds generated files gone stale.
- #28 ai-config-sync-manager merged · 9 Jul 2026 On Windows, backups went to the wrong place. Fixed, with regression tests.
- #878 context-mode open · root cause found Oversized Markdown paragraphs slipped past the chunk cap. I traced why; other users reproduced it later.
AgentsMesh
check still passed after I edited the generated AGENTS.md. Issue #98 reproduces it: check hashed the canonical files but not the generated output.
PR #99 proposed a fix. The maintainer already had a checksum-based one in progress and kept it, because it kept check fast; they asked for the read-only stale-output part of mine as a follow-up. #99 closed without merging.
fix(check): detect generated-output drift
- Problem
- Generated-output drift passed the documented fast check.
- Change
- Proposed detecting output drift, including stale files; the maintainer chose a checksum-based base fix and requested the stale-output piece separately.
PR #102 is that follow-up: it finds stale generated outputs without running generation, and reports them through the core, API, CLI and MCP check paths. The maintainer made corrections and merged it.
fix(check): detect stale generated outputs
- Problem
- Files left in managed output locations could be absent from the lock’s output map without being reported as stale.
- Change
- Added read-only stale-output detection and exposed its result across the check surfaces, without running the generation pipeline.
Windows backup paths
On Windows, an absolute drive path could put an ai-config-sync-manager backup outside its backup root. PR #28 sanitizes the target path, keeps the POSIX layout and adds regression tests.
fix: sanitize Windows backup paths
- Problem
- An absolute Windows project path broke backup placement during sync.
- Change
- Sanitized absolute backup targets, preserved POSIX layout, and added regression coverage.
context-mode: a root cause, not a fix
Single oversized Markdown paragraphs slipped past the 4 KiB chunk bound. Issue #878 has a minimal reproduction, SQLite evidence, the root cause with its source locations, a proposed fix and a regression matrix. Other users later reproduced much larger chunks on newer versions.
The issue is still open; a linked pull request, #1091, is open and not merged.
ISSUEIssue #878open · reproduction, root cause, proposed fixSmaller traces · reports and proposals
Smaller traces
rulesync #2253 — a feature request: let fetch read Claude Code and Codex plugin manifests. The maintainer re-validated the gap against the code, then folded plugin ingestion into a broader plugin-root importer (#382) and closed this one as not planned. No code of mine merged.
ICM #313 — the SQLite store corrupted under concurrent writes on Windows. I wrote down the recovery that worked (.recover, rebuilding the full-text index, an integrity check, an atomic swap) and proposed WAL with a busy timeout, a doctor / repair command, backups and a JSONL export. The maintainer closed it as completed on 26 August 2026 through a release; I have not checked which of the proposals landed.
Who did what
- Me
- Found the problems in use, reproduced and root-caused them, set the direction, reviewed the code and tests, and steered the follow-up through maintainer review.
- AI
- Helped write code and tests for the AgentsMesh and ai-config-sync-manager pull requests, under my direction and review.
- Upstream
- The AgentsMesh maintainer chose the base checksum design, requested the follow-up, made corrections and merged it. The ai-config-sync-manager maintainer reviewed and merged PR #28. The rulesync and ICM maintainers decided what to do with the reports.
AgentsMesh PR #102 and ai-config-sync-manager PR #28 merged. AgentsMesh PR #99 closed after the maintainer chose another base design. context-mode #878 is an open, root-caused report; rulesync #2253 and ICM #313 were reports and proposals, not code.