handover

Handover: Handover (0.4.0 shipped, public, launch in progress)

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.

0. Orientation (one paragraph)

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.

1. Identity (verify each; do not trust blindly)

| 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 |

2. Current state as verifiable claims

| 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 |

3. Canonical sources (ranked; when they disagree, higher wins; code is truth)

  1. This file, for status and the next action.
  2. README.md (the docs router), for topic → authoritative doc → code path.
  3. RELEASE.md for the gated publish checklist (all gates done except full launch); ARXIV_SUBMISSION.md for the paper submission package + endorsement plan; PUBLICATION_VENUES.md for status across every venue (Zenodo/arXiv/OSF/JOSS/TechRxiv), not just arXiv; IDENTITY_AND_LINKS.md for this project’s locked identity decisions (canonical cross-project copy: ideas-folder/IDENTITY_AND_LINKS.md); PORTING.md for non-Claude-Code use.
  4. PROTOCOL.md for the format and rubric; SECURITY.md for the threat model; STALENESS.md for the enforcement roadmap.
  5. The tests, for the contract the code actually meets.

4. What changed since the last handoff (do not rebuild these)

5. Negative knowledge (the irreducible core, if you must cut length, cut this last)

6. Next action

  1. Run ./test/run.sh and confirm 37 passed, 0 failed (mirror of the header first_action).
  2. Owner-gated, in progress: finish the arXiv submission. Endorsement request sent 2026-08-02 (code 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.
  3. Owner-gated, in progress: finish the OSF Preprints submission, package ready in PUBLICATION_VENUES.md, currently blocked on the step-1 Next-button bug documented in §5. Retry with the paste-then-nudge-a-character workaround.
  4. Once arXiv clears: update README.md citation section + CITATION.cff with the real arXiv:26XX.XXXXX ID and whichever category (cs.AI primary, per §5) actually got announced.
  5. Remaining launch channels, not yet started, roughly in this order: 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.

7. Open questions / blocked on user

8. Verify the whole thing still holds

./test/run.sh