Read this first. It is self-contained. You should not need anything outside this file plus repo access to continue. It supersedes the handover-oss-readiness handoff (pre-publish) that used to be canonical here.
Handover is an enforced agent-to-agent handover document (a strict validated header plus a prose body) with deterministic zero-dependency Node tooling: handover-lint scores a doc 0–100 and verifies it against the live repo, handover-scaffold fills the header from git, and bench/run.js measures whether a handoff actually transfers via planted traps. Since the last handoff, the project actually shipped and launch is underway. geekidharsh/handover is public (tag v0.4.0, CI green), the arXiv paper (paper/handover.html/.pdf, 8pp) is finished with two independent reviews’ fixes applied, and the Claude Code community-marketplace plugin submission is in for review. What’s NOT done: the arXiv submission itself is blocked on endorsement (see §6). Zenodo is now done, DOI 10.5281/zenodo.21797944 minted off release v0.4.1, badged in README, in CITATION.cff. OSF Preprints submission is in progress (owner-gated, hit a UI paste/validation bug, see §5). TechRxiv was investigated and excluded (their policy explicitly rejects AI-assisted content, see §5). JOSS is gated until ~2027-02-03 (6-month public-history requirement). Remaining channels not yet executed: awesome-claude-code, Show HN, Reddit, ClawHub. Full venue-by-venue status: PUBLICATION_VENUES.md. This repo (handover-lab, private, renamed from handover on 2026-08-02) is the working copy; edit here first, always. The public repo is kept in sync by copying specific files across (paper, plugin manifest), never edited independently; it has its own local clone at ~/Github-repos/handover.
| Fact | Value | Verify |
|—|—|—|
| Branch | dev | git rev-parse --abbrev-ref HEAD |
| True at commit | ead2df33667e | git log ead2df33667e..HEAD --oneline (drift if non-empty) |
| Plugin version | 0.4.0 (package/CITATION bumped to 0.4.1 for Zenodo archival only, protocol/plugin unchanged) | grep version .claude-plugin/plugin.json |
| Protocol version | 1 (unchanged since 0.4.0) | grep CURRENT_PROTOCOL_VERSION bin/lib/handover-doc.js |
| Tests | 37 checks, 0 failures | ./test/run.sh |
| Public repo | github.com/geekidharsh/handover, PUBLIC, tag v0.4.1 | gh repo view geekidharsh/handover --json visibility |
| Zenodo DOI | 10.5281/zenodo.21797944 (archived off v0.4.1) | zenodo.org/account/settings/github/repository/geekidharsh/handover |
| Local clones | handover-lab (this one, private working copy) + handover (public, separate clone, sibling directory) | ls ~/Github-repos \| grep -i handover |
| Claim | Verify |
|—|—|
| Full suite passes | ./test/run.sh |
| Repo-verification suite passes (21 checks) | bash test/verify.test.sh |
| The git pre-commit hook suite passes, including fail-open | bash test/hook.test.sh |
| Three bench scenarios exist, not one | ls bench/scenarios |
| --claims cannot execute a table inside a code fence | grep -n maskBody bin/handover-lint.js |
| No private-repo references remain in shipping files | ! grep -riq ideas-folder README.md PROTOCOL.md CHANGELOG.md docs/ARCHIVE.md |
| Public repo is a byte-identical mirror of this repo’s paper | diff paper/handover.html ~/Github-repos/handover/paper/handover.html |
| .claude-plugin/marketplace.json passes strict validation | claude plugin validate . --strict |
| Claude Code community-marketplace submission was filed | [belief, unverified], submitted via platform.claude.com/plugins/submit 2026-08-02, confirmation screen said “Plugin submitted for review”; no programmatic status check found |
| arXiv account geekidharsh exists and is verified | [belief, unverified]; no CLI-checkable state; verify at arxiv.org login |
ideas-folder/IDENTITY_AND_LINKS.md); PORTING.md for non-Claude-Code use.geekidharsh/handover, made public, tag v0.4.0, GitHub Release cut, CI green. Do not re-run the history scrub.~/Github-repos/handover → renamed to ~/Github-repos/handover-lab (matches the GitHub rename); the public repo got its own fresh clone at the now-free ~/Github-repos/handover path. Both are real, independent local git repos. Do not assume they’re the same checkout.harshvardhanpandey@hotmail.com, paper only, deliberately not in NOTICE/README/CITATION.cff). Do not re-litigate these fixes without new findings.harshvardhanpandey@hotmail.com (a rewrite to harsh@household.dev was considered and explicitly rejected, Handover isn’t a household.dev room). Canonical copy of this identity file lives in ideas-folder, not duplicated per-project.marketplace.json had a real bug fixed first (missing top-level description, caught by claude plugin validate).v0.4.1 cut specifically for archival (version bump only, no functional changes), DOI 10.5281/zenodo.21797944 minted automatically, badge added to README, identifier added to CITATION.cff. Do not cut another release for this, it’s closed.shalini-kshama/{Carbro,Nanimaa,Poppy}), not third-party OSS, do not cite that count as external contribution credit. Stack Overflow account is real (3,609 rep) but topically unrelated. Full detail in PUBLICATION_VENUES.md.--claims extracted commands from raw document lines and armed any table whose last column merely contained “verif”. Adversarial review proved two working command-execution escapes (a table inside a code fence; a “Verified By” roster column). The working approach is fence-masked lines plus an exact header match. Full write-up: SECURITY.md finding 4.--repo git calls by string-interpolating true_at_sha into a shell command, a command-injection hole. All git probes stay shell-free via execFileSync.cs.SE as primary category / cs.AI as cross-list (matches the closest-sibling paper, SWE Context Bench’s own classification, and the paper’s actual contribution, protocol/tooling/benchmark, not an AI technique). Mid-submission the category got changed live to cs.AI primary / cs.SE cross-list instead. Both are defensible; this is what was actually filed, don’t silently revert to the original plan when picking this back up, and update README.md/CITATION.cff with whichever primary category the announced paper actually carries once it’s live.uis.edu institutional-email shortcut for endorsement was tried first, dead, no longer accessible. Don’t route through it. Real endorsement code for cs.AI (B8G7VE, cs.SE may need its own separate one) was requested and sent to help@arxiv.org since no personal contact with an existing arXiv account was available. Full plan + draft emails in ARXIV_SUBMISSION.md.~/Github-repos/handover → handover-lab broke Freeway’s zone recognition for the new path (a write was denied). Fixed correctly by proposing the zone (freeway zone propose) and waiting for human approval + a separate freeway zone ratify step, ratify is a real, separate step after approve, not automatic; also discovered zone ratify has no per-request scoping, it promotes the entire staged batch. Do not route around a Freeway denial by finding another tool path, propose and wait. Logged as real CLI gaps in agent-freeway-lab/ISSUES.md (Z-78 through Z-81).agent-freeway-lab while accidentally on a stale, already-merged branch (audit/governance-2026-07-23) instead of main, always run git branch --show-current before committing in an unfamiliar/reused checkout, don’t assume the last-known branch is still current.osf.io/preprints/osf/submit, not the picker UI. On that path, step 1’s Next button did nothing after pasting title+abstract; no error, not greyed out. Root-caused as a likely paste-vs-framework-validation gap (common in JS form wizards: paste doesn’t always fire the same event a keystroke does). Fix: after pasting, click into the field and add/delete one character to force a real change event.bench/README.md); drift-to-claim mapping; negative-knowledge expiry; PR/ticket liveness; provenance/signing. On the STALENESS roadmap, not forgotten. Also: an MCP-server wrapper for lint/scaffold/bench, considered for discoverability (MCP registries), explicitly out of scope for this launch, real scope not a listing action.handover-doc.js) stays pure and deterministic. --claims implies --verify. The git pre-commit hook deliberately does not pass --verify/--claims. Patent: decided not to file (recorded in docs/RELEASE.md Gate 0, do not re-litigate without new information)../test/run.sh and confirm 37 passed, 0 failed (mirror of the header first_action).B8G7VE, cs.AI) has passed arXiv Support’s typical same-day turnaround with no reply as of 2026-08-04, a follow-up in the same thread is warranted, not a new email. If cs.SE cross-list also prompts for its own endorsement, capture that code too. A cold-contact backup email to a cited author (SWE Context Bench recommended) is drafted and ready in ARXIV_SUBMISSION.md if Support stays slow.README.md citation section + CITATION.cff with the real arXiv:26XX.XXXXX ID and whichever category (cs.AI primary, per §5) actually got announced.awesome-claude-code (owner must submit, their policy says humans only, not agents), Show HN (best once arXiv is live, one shot), Reddit (r/ClaudeAI, r/AI_Agents), X thread (@brownlittlefish). Medium/Substack companion writeup is done (brownlittlefish.substack.com/p/handover-a-machine-checkable-protocol). Full detail in PUBLICATION_VENUES.md.cs.SE need its own separate endorsement code, or did cs.AI’s endorsement cover both? Unknown until the form is revisited post-endorsement../test/run.sh