Contributors wanted: tools, tests and native integration trials

[okgrit]

Build the tools with us

Code, tests, installation fixes and architecture proposals are welcome. Here are concrete places to start, in the order we are prioritizing these projects:

Project	Contribution	First useful result
Done is a claim	Try public JSON summaries in CI · implementation #20	Run a synthetic receipt through --format json, retain the reporter exit separately from parsing, and share actual results or blockers.
Done is a claim	Evidence after a recorder interruption	A bounded reproduction and backward-compatible design; incomplete evidence must never imply success.
Remember, Dammit.	Native Claude Code save/correction/recall trial	A sanitized report from an isolated vault, including fresh-session recall, scope checks and actual blockers.
dotline	Native Claude Code channel round trip	A real native receive/reply/readback trial; the manual mailbox demo is only a starting point.

The JSON summary is now available on main at ed83afab7018e039d3e1a57584a3790a885ef851 through PR #20. Schema/test-plan input is credited to sacravenger / NaN Mesh. Real CI-consumer reports and reproducible follow-up defects are welcome; maintainer synthetic checks do not establish an outside integration.

Each issue links the source boundary and acceptance criteria. Start by commenting on the issue with your intended platform or small design so we can coordinate overlapping work. Alternative designs and simpler fixes are welcome. A useful blocked reproduction or careful review can also be a contribution.

For a small bug, a focused PR with a reproduction and regression test is welcome. For a larger CLI, storage or architecture change, discuss the proposed contract first. Changes receive review for compatibility, scope and evidence; authors keep credit for their work.

Tried the flagship in a real project? Share what happened, including what failed or remained uncertain. Keep private logs, source data, credentials and machine details out of public reports. Use synthetic fixtures for integration trials.

Contributor guide · Inspectable examples · Agent-free dotline demo

A smaller documentation contribution

dotline #4: add a Bash local-demo walkthrough is open for a docs-only PR: one new guide and one link, preserving the PowerShell rehearsal. Start with a synthetic loopback run on the platform you can test and report its actual result. No AI account or public tunnel is needed for that manual exchange. Please coordinate in issue #4 before starting.

Flagship documentation contribution: GitHub Actions

Add a minimal JSON receipt recipe in #23 is open for contributors familiar with Bash and GitHub Actions. The scope is two existing guides: one explained job and one link. Use generated fixtures to check matching evidence, changed inputs and a recorded command failure, retaining the reporter result through summary generation. Hosted-run verification is part of final acceptance; a draft can identify that check as pending. Coordinate in issue #23 before starting.