GitHubivarvong

ply

main
ply5 git calls344 ms48 KiB3 cachedprotocol v2
2528 lines123 KiBRaw

Git behaviour coverage

ply is a Git protocol conformance and behaviour-testing instrument for Cloudflare Artifacts as well as a client. This matrix counts server behaviours, not git commands: each row is a behaviour or failure mode of a Git server, the ply operations and tests that exercise it, and who has independently checked the server's answer.

  • unsupported: ply has no operation that exercises it. Stock git or hand-built wire probes may still have observed Artifacts.
  • implemented: ply exercises it, but only against fakes or its own expectations; nothing independent has judged the server.
  • verified: at least one independent check. The types make a verified row without evidence impossible.

Evidence kinds:

  • ply_vs_reference_git (ply↔git): ply against git http-backend in this suite, with git's own output as the expected value; the cited file runs real git.
  • ply_vs_artifacts (ply↔Artifacts): ply against Artifacts in a recorded run.
  • native_git_vs_artifacts (git↔Artifacts): stock git against Artifacts in a recorded run, with git http-backend beside it as the baseline.
  • wire_probe_vs_artifacts (wire↔Artifacts): hand-built requests (pkt-lines, packs, HTTP framing) against Artifacts beside the same baseline. Neither ply nor stock git sends these bytes.

Only Artifacts evidence says anything about Artifacts; reference evidence says ply's probe is right. Recorded runs are private (their harnesses hold credentials): test/behaviours/runs.ts keeps each run's id, date and check names, never its verdicts.

Summary

118 behaviours: 106 verified, 2 implemented, 10 unsupported. Of the verified, 84 carry some Artifacts evidence and 65 carry evidence of ply itself against Artifacts.

areabehavioursverifiedimplementedunsupported
refs9801
caps9603
fetch201901
pack181800
push191801
concurrency7700
tags6600
ancestry7610
errors7511
interrupted6600
http10703
all118106210

Verified behaviours by evidence kind (a behaviour counts once under each kind it has):

evidence kindverified behaviours
ply_vs_reference_git103
ply_vs_artifacts65
native_git_vs_artifacts58
wire_probe_vs_artifacts21

Gaps

Each behaviour that is not verified by both ply↔git and ply↔Artifacts, filed under the first of these classes that holds:

Exercised by ply, judged by nothing independent (2)

  • ancestry.cut-graph: A server that withholds ancestors without saying shallow: ply fails closed, nothing pushed.
  • errors.not-git-response: A 200 that is not git (HTML, wrong content type) is not_git, never parsed as protocol.

Verified against git http-backend only: no evidence of any kind from Artifacts (22)

  • refs.advertisement-shapes: Unusual but legal listings (duplicate names, ordering, raw bytes in names) are read as git reads them.
  • caps.required-capabilities: A server missing a capability ply needs (ls-refs, fetch) is refused as unsupported before any operation.
  • caps.object-format: object-format=sha1 is accepted; any other object format is refused as unsupported.
  • caps.filter-not-advertised: A server whose fetch= line lists no filter (stock http-backend) gets no filter argument after one probe.
  • fetch.acknowledgments-ready-packfile: v2 response sections in order (acknowledgments, ready, shallow-info, packfile); a server that breaks the order is a protocol error, as it is for git.
  • fetch.filter-combine: filter combine:blob:none+tree:<k> (a commit and the first levels of its path in one request).
  • fetch.sideband-bands: Side-band in the packfile section: band 1 data, band 2 progress, band 3 fatal error.
  • pack.ofs-delta-resolve: A served pack with OFS_DELTA chains resolves to the objects git verify-pack lists.
  • pack.thin-ref-base: A thin REF base supplied from outside the pack is checked against its claimed id before a delta applies.
  • pack.truncated-served-pack: A served pack cut at any byte is refused, typed, on every read path, where git index-pack refuses it.
  • pack.corrupt-served-pack: A served pack with a corrupt header field, zlib member, delta or checksum is refused exactly where git index-pack --strict refuses it.
  • pack.served-pack-limits: Hostile sizes in a served pack (object size, delta result, chain depth, inflated total) are refused before allocation.
  • pack.push-duplicate-object: A pushed pack never names one object twice (a strict receiver refuses it).
  • push.report-status-v2: report-status-v2: option lines after ok.
  • push.sideband-hook-output: side-band-64k on receive-pack: the report on band 1, hook output on band 2.
  • push.hook-rejection: A pre-receive or update hook that declines: ng with the hook's reason, ref unchanged.
  • concurrency.two-transfer-runners: Two resumable transfers of one plan at once both finish with the planned head; each refused step is settled by reading refs.
  • errors.err-pkt-line: An ERR pkt-line anywhere in a response is a typed remote error carrying the scrubbed message.
  • interrupted.abort-during-push: An external AbortSignal during a push: aborted if the body was never pulled, ambiguous once sent; git decides what landed.
  • interrupted.resumable-transfer: A multi-step transfer paused or interrupted is resumed from refs, not from local state, and ends at the planned head.
  • http.redirects: A 3xx on the advertisement is followed as git follows it (within policy); a 3xx on a POST is never followed.
  • http.sideband-keepalive: Empty band-1 keepalives while a hook runs do not end the push read.

Artifacts observed by stock git or wire probes, never by ply (19)

  • caps.fetch-argument-gating: ply sends a fetch argument (filter, shallow, include-tag, thin-pack, ofs-delta) only when the advertisement allows it, as git fetch does.
  • caps.receive-pack-capabilities: receive-pack capabilities (report-status, report-status-v2, side-band-64k, atomic, push-options, delete-refs, ofs-delta, object-format) are read and checked before the POST.
  • fetch.want-tip-full-pack: want of a tip with done and no filter: the pack holds exactly what pack-objects sends.
  • fetch.want-have-line-syntax: want/have/shallow lines: upload-pack's verdict on each class of id, and ply refusing non-ids before the wire.
  • fetch.have-negotiation: Multi-round have/ACK negotiation, then done: the server stops at common commits and sends only what is missing.
  • fetch.filter-tree-depth: filter tree:<depth> (tree:0 commit only, tree:1, tree:2).
  • fetch.filter-blob-limit: filter blob:limit=<n>.
  • fetch.deepen-depth: deepen <n>: a shallow pack cut n commits below each want, with shallow-info naming the boundary.
  • fetch.deepen-since: deepen-since <time>.
  • fetch.deepen-not: deepen-not <ref>.
  • fetch.deepen-relative-unshallow: Fetch after a shallow clone: deepen-relative, a deeper depth, and unshallow, from the client's shallow list.
  • fetch.include-tag: include-tag: annotated tags that point into the pack are sent with it.
  • fetch.thin-pack: thin-pack with haves: deltas against objects the client has, resolved against external bases.
  • fetch.ofs-delta-requested: ofs-delta: OFS_DELTA entries only when asked for.
  • pack.push-ofs-delta-accepted: receive-pack accepts a pushed pack with OFS_DELTA entries when it advertises ofs-delta.
  • push.push-options: push-options: sent only when advertised; they reach the hook.
  • http.credential-forms: Bearer, Basic and URL-userinfo credentials produce the Authorization header git sends for the same input.
  • http.chunked-request-body: A large push body streamed with chunked transfer-encoding (duplex half).
  • http.large-request-body: A large push request body (tens of MiB) reaches the server whole.

Verified on Artifacts, but ply's probe is not checked against git http-backend (3)

  • concurrency.read-after-write: A landed push is visible at once to ls-refs and to fetch (no stale advertisement after a push).
  • errors.repository-not-found: A repository that does not exist: the advertisement answers 404, typed not_found.
  • errors.http-status-classes: Statuses 4xx/5xx/429 at each stage map to ply's typed classes, and a refused optional feature is not retried for them.

Not exercisable by ply (10)

  • refs.v0-upload-pack-advertisement: The v0/v1 upload-pack advertisement (refs and capabilities on the info/refs GET, no Git-Protocol header).
  • caps.server-option: v2 server-option arguments on ls-refs and fetch.
  • caps.wait-for-done-packfile-uris-sideband-all: v2 fetch features wait-for-done, packfile-uris and sideband-all.
  • caps.object-info: The v2 object-info command (object sizes without a pack).
  • fetch.filter-sparse-oid: filter sparse:oid=<blob>.
  • push.signed-push: push-cert (signed pushes).
  • errors.malformed-requests-to-server: How the server answers malformed requests (bad pkt-line lengths, misplaced delimiters, unknown commands and capabilities).
  • http.request-content-encoding: A gzip-encoded request body.
  • http.content-length-framing: A request whose Content-Length disagrees with its body.
  • http.expect-continue-and-dumb-http: Expect: 100-continue, and the dumb HTTP protocol.

Behaviours

Ref advertisement and ls-refs (refs, 9)

idstatusevidenceply opstests
refs.ls-refs-listingverifiedply↔git, ply↔Artifacts, git↔Artifacts, wire↔ArtifactslsRefs, listRefs3
refs.ref-prefixverifiedply↔git, ply↔Artifacts, git↔ArtifactslsRefs, listRefs1
refs.symref-headverifiedply↔git, ply↔Artifacts, git↔ArtifactslsRefs, push2
refs.directory-file-conflictverifiedply↔git, ply↔Artifacts, git↔Artifactspush1
refs.peeled-tagsverifiedply↔git, ply↔Artifacts, git↔ArtifactslsRefs, listRefs1
refs.unborn-empty-repoverifiedply↔git, ply↔ArtifactslsRefs2
refs.advertisement-shapesverifiedply↔gitlsRefs2
refs.v0-upload-pack-advertisementunsupported (observed)git↔Artifacts, wire↔Artifacts—0
refs.receive-pack-advertisementverifiedply↔git, ply↔Artifacts, wire↔ArtifactsreceiveCaps, push2
refs.ls-refs-listing

v2 ls-refs lists every ref with its object id.

Ops: src/lsrefs.ts lsRefs, src/refops.ts listRefs.

Tests:

  • test/parity.test.js: ls-refs == git ls-remote (prefixes, symrefs, peeled tags, many refs)
  • test/e2e-customer.test.js: listRefs is for-each-ref, before the deletes
  • test/probes/wire.test.js: reference: ${plan.id} meets its answer with every sender

Evidence:

  • ply↔git: test/parity.test.js
  • ply↔Artifacts: validate-7b0c310f: refs list (peeled tags)
  • ply↔Artifacts: loadgen-phase6-plyw-20261025: refs/small
  • git↔Artifacts: loadgen-compat-20261024: ls_remote/small/v2
  • git↔Artifacts: validate-7b0c310f: git judge: fsck --strict, refs, history
  • ply↔git: test/probes/wire.test.js
  • ply↔Artifacts: wire-20261115t2116-1nam: refs.ls-refs-listing#two-thousand-refs/art-ply
  • git↔Artifacts: wire-20261115t2116-1nam: refs.ls-refs-listing#two-thousand-refs/art-git
  • wire↔Artifacts: wire-20261115t2116-1nam: refs.ls-refs-listing#two-thousand-refs/art-raw
  • wire↔Artifacts: wire-20261115t2116-1nam: refs.ls-refs-listing#two-thousand-refs/art-curl
  • wire↔Artifacts: wire-20261115t2116-1nam: refs.ls-refs-listing#unknown-argument/art-raw
  • wire↔Artifacts: wire-20261115t2116-1nam: refs.ls-refs-listing#unknown-argument/art-curl

The two-thousand-refs plan lists 1500 branches, 500 annotated tags and HEAD and compares a digest of the whole listing.

refs.ref-prefix

ls-refs ref-prefix arguments restrict the listing to refs under the given prefixes.

Ops: src/lsrefs.ts lsRefs, src/refops.ts listRefs.

Tests:

  • test/parity.test.js: ['refs/heads/main', 'refs/tags/v1'], ['HEAD']

Evidence:

  • ply↔git: test/parity.test.js
  • ply↔Artifacts: loadgen-phase6-plyw-20261025: refs/prefix
  • ply↔Artifacts: loadgen-phase6-plyw-20261025: refs/prefix_tags
  • git↔Artifacts: loadgen-compat-20261024: ls_remote_ref_prefix/small/v2
refs.symref-head

ls-refs symrefs reports the target of HEAD, and the target is the default branch.

Ops: src/lsrefs.ts lsRefs, src/push.ts push.

Tests:

  • test/parity.test.js: ls-refs == git ls-remote (prefixes, symrefs, peeled tags, many refs)
  • test/probes/probes.test.js: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository

Evidence:

  • ply↔git: test/parity.test.js
  • ply↔Artifacts: loadgen-phase6-plyw-20261025: refs/n4_head
  • ply↔Artifacts: loadgen-phase6-plyw-20261025: refs/n4
  • ply↔git: test/probes/probes.test.js
  • ply↔Artifacts: probes-20261115t2113-phhp: refs.symref-head#delete-default-branch/art-ply
  • git↔Artifacts: probes-20261115t2113-phhp: refs.symref-head#delete-default-branch/art-git
  • ply↔Artifacts: probes-20261115t2133-txqj: refs.symref-head#delete-default-branch/art-ply
  • git↔Artifacts: probes-20261115t2133-txqj: refs.symref-head#delete-default-branch/art-git

The delete-default-branch probe asks for a delete of the branch HEAD names and reads HEAD back with ls-remote --symref.

refs.directory-file-conflict

A ref cannot be both a name and a directory: creating refs/heads/a/b while refs/heads/a exists (or the reverse, or both in one push) is refused and leaves the existing ref as it was.

Ops: src/push.ts push.

Tests:

  • test/probes/probes.test.js: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository

Evidence:

  • ply↔git: test/probes/probes.test.js
  • ply↔Artifacts: probes-20261115t2126-d4jn: refs.directory-file-conflict#file-then-dir/art-ply
  • git↔Artifacts: probes-20261115t2126-d4jn: refs.directory-file-conflict#file-then-dir/art-git
  • ply↔Artifacts: probes-20261115t2126-d4jn: refs.directory-file-conflict#dir-then-file/art-ply
  • git↔Artifacts: probes-20261115t2126-d4jn: refs.directory-file-conflict#dir-then-file/art-git
  • ply↔Artifacts: probes-20261115t2126-d4jn: refs.directory-file-conflict#both-in-one-push/art-ply
  • git↔Artifacts: probes-20261115t2126-d4jn: refs.directory-file-conflict#both-in-one-push/art-git
  • ply↔Artifacts: probes-20261115t2133-txqj: refs.directory-file-conflict#file-then-dir/art-ply
  • git↔Artifacts: probes-20261115t2133-txqj: refs.directory-file-conflict#file-then-dir/art-git
  • ply↔Artifacts: probes-20261115t2133-txqj: refs.directory-file-conflict#dir-then-file/art-ply
  • git↔Artifacts: probes-20261115t2133-txqj: refs.directory-file-conflict#dir-then-file/art-git
  • ply↔Artifacts: probes-20261115t2133-txqj: refs.directory-file-conflict#both-in-one-push/art-ply
  • git↔Artifacts: probes-20261115t2133-txqj: refs.directory-file-conflict#both-in-one-push/art-git
refs.peeled-tags

ls-refs peel attaches the peeled id to annotated tags, and only to them.

Ops: src/lsrefs.ts lsRefs, src/refops.ts listRefs.

Tests:

  • test/parity.test.js: ls-refs == git ls-remote (prefixes, symrefs, peeled tags, many refs)

Evidence:

  • ply↔git: test/parity.test.js
  • ply↔Artifacts: validate-7b0c310f: refs list (peeled tags)
  • git↔Artifacts: loadgen-compat-20261024: ls_remote_tags/small/v2
refs.unborn-empty-repo

An empty repository lists no refs, and ls-refs unborn names the branch HEAD will be born on.

Ops: src/lsrefs.ts lsRefs.

Tests:

  • test/lsrefs-unborn.test.js: lsRefs unborn: the argument, the answer and the ref listing agree with git, across every cell
  • test/lsrefs-unborn.test.js: lsRefs unborn: an empty repository clones to the branch ply reports (git clone is the oracle)

Evidence:

  • ply↔git: test/lsrefs-unborn.test.js
  • ply↔Artifacts: validate-7b0c310f: refs (empty)
  • ply↔Artifacts: loadgen-phase6-plyw-20261025: refs/empty
refs.advertisement-shapes

Unusual but legal listings (duplicate names, ordering, raw bytes in names) are read as git reads them.

Ops: src/lsrefs.ts lsRefs.

Tests:

  • test/space/advertisement.test.js: refs: every cell, judged by git ls-remote; a duplicate ref resolves to its first listing in git fetch
  • test/git-bytes.test.js: byte content × object field × operation

Evidence:

  • ply↔git: test/space/advertisement.test.js

No Artifacts evidence: ply has never asked Artifacts to list a ref with non-UTF-8 or unusual bytes.

refs.v0-upload-pack-advertisement

The v0/v1 upload-pack advertisement (refs and capabilities on the info/refs GET, no Git-Protocol header).

Unsupported: ply asks for protocol v2 on upload-pack and refuses a server that answers otherwise (src/caps.ts).

Observed:

  • git↔Artifacts: loadgen-compat-20261024: ls_remote/small/v0
  • git↔Artifacts: loadgen-compat-20261024: clone_full/small/v0
  • git↔Artifacts: loadgen-compat-20261024: depth_1/small/v0
  • wire↔Artifacts: wire-20261115t2038-ee4x: refs.v0-upload-pack-advertisement#no-protocol-header/art-raw
  • wire↔Artifacts: wire-20261115t2038-ee4x: refs.v0-upload-pack-advertisement#no-protocol-header/art-curl
  • git↔Artifacts: wire-20261115t2038-ee4x: refs.v0-upload-pack-advertisement#no-protocol-header/art-git
  • wire↔Artifacts: wire-20261115t2116-1nam: refs.v0-upload-pack-advertisement#two-thousand-refs/art-raw
  • wire↔Artifacts: wire-20261115t2116-1nam: refs.v0-upload-pack-advertisement#two-thousand-refs/art-curl
  • git↔Artifacts: wire-20261115t2116-1nam: refs.v0-upload-pack-advertisement#two-thousand-refs/art-git

Stock git, raw requests and curl have probed v0 on Artifacts; ply has not.

refs.receive-pack-advertisement

The receive-pack advertisement (v0 form: capabilities on the first ref, capabilities^{} for an empty repository).

Ops: src/receivecaps.ts receiveCaps, src/push.ts push.

Tests:

  • test/space/advertisement.test.js: push: request × advertised atomic × advertised push-options × object-format, judged by git push
  • test/push.test.js: push matrix: configs × hooks × commands × caps, parity with git push

Evidence:

  • ply↔git: test/space/advertisement.test.js
  • ply↔Artifacts: validate-7b0c310f: write: root commit (edit changes)
  • wire↔Artifacts: loadgen-phase2-20261025: receive_caps/artifacts

Capabilities and protocol v2 (caps, 9)

idstatusevidenceply opstests
caps.v2-capability-advertisementverifiedply↔git, ply↔Artifacts, wire↔Artifactsdiscover, parseCapabilitiesV22
caps.required-capabilitiesverifiedply↔gitcheckRequiredV2, discover1
caps.object-formatverifiedply↔gitdecideObjectFormat, discover1
caps.fetch-argument-gatingverifiedply↔git, wire↔ArtifactsfetchPack, fetchRequest1
caps.filter-not-advertisedverifiedply↔gitfetchPack, readFile, listTree1
caps.receive-pack-capabilitiesverifiedply↔git, wire↔ArtifactsreceiveCaps, checkPushCaps2
caps.server-optionunsupported (observed)wire↔Artifacts—0
caps.wait-for-done-packfile-uris-sideband-allunsupported (observed)wire↔Artifacts—0
caps.object-infounsupported (observed)wire↔Artifacts—0
caps.v2-capability-advertisement

The v2 capability advertisement: version 2, agent, ls-refs and fetch features, object-format, server-option, session-id.

Ops: src/discover.ts discover, src/caps.ts parseCapabilitiesV2.

Tests:

  • test/space/advertisement.test.js: caps: every cell through discover() (derived from the table)
  • test/space/advertisement.test.js: real git http-backend configurations advertise exactly what the renderer writes for their cell

Evidence:

  • ply↔git: test/space/advertisement.test.js
  • ply↔Artifacts: validate-7b0c310f: discover
  • ply↔Artifacts: loadgen-phase6-plyw-20261025: discover/v2_caps
  • wire↔Artifacts: loadgen-phase2-20261025: capability_table/v2
  • wire↔Artifacts: loadgen-phase5-delta-20261025: caps/v2_fetch_features
  • wire↔Artifacts: wire-20261115t2116-1nam: caps.v2-capability-advertisement#unknown-capability-line/art-raw
  • wire↔Artifacts: wire-20261115t2116-1nam: caps.v2-capability-advertisement#unknown-capability-line/art-curl
caps.required-capabilities

A server missing a capability ply needs (ls-refs, fetch) is refused as unsupported before any operation.

Ops: src/closed.ts checkRequiredV2, src/discover.ts discover.

Tests:

  • test/space/advertisement.test.js: caps: every cell through discover() (derived from the table)

Evidence:

  • ply↔git: test/space/advertisement.test.js

Artifacts advertises every required capability, so the refusal has never been reached against it.

caps.object-format

object-format=sha1 is accepted; any other object format is refused as unsupported.

Ops: src/closed.ts decideObjectFormat, src/discover.ts discover.

Tests:

  • test/space/advertisement.test.js: push: request × advertised atomic × advertised push-options × object-format, judged by git push

Evidence:

  • ply↔git: test/space/advertisement.test.js

ply has not probed a sha256 repository on any server.

caps.fetch-argument-gating

ply sends a fetch argument (filter, shallow, include-tag, thin-pack, ofs-delta) only when the advertisement allows it, as git fetch does.

Ops: src/fetchpack.ts fetchPack, src/fetch.ts fetchRequest.

Tests:

  • test/space/advertisement.test.js: request: fetch arguments ply sends, judged by git fetch

Evidence:

  • ply↔git: test/space/advertisement.test.js
  • wire↔Artifacts: wire-20261115t2116-1nam: caps.fetch-argument-gating#unknown-fetch-argument/art-raw
  • wire↔Artifacts: wire-20261115t2116-1nam: caps.fetch-argument-gating#unknown-fetch-argument/art-curl
caps.filter-not-advertised

A server whose fetch= line lists no filter (stock http-backend) gets no filter argument after one probe.

Ops: src/fetchpack.ts fetchPack, src/read.ts readFile, src/read.ts listTree.

Tests:

  • test/no-filter.test.js: reads: readFile, listTree, readCommit, readLog, checkoutTree answer the same on both; one probe, then no filter

Evidence:

  • ply↔git: test/no-filter.test.js
caps.receive-pack-capabilities

receive-pack capabilities (report-status, report-status-v2, side-band-64k, atomic, push-options, delete-refs, ofs-delta, object-format) are read and checked before the POST.

Ops: src/receivecaps.ts receiveCaps, src/receivecaps.ts checkPushCaps.

Tests:

  • test/space/advertisement.test.js: push: request × advertised atomic × advertised push-options × object-format, judged by git push
  • test/push-pack.test.js: atomic the server does not advertise: unsupported, no POST, the pack unread

Evidence:

  • ply↔git: test/space/advertisement.test.js
  • wire↔Artifacts: loadgen-phase2-20261025: receive_caps/artifacts
  • wire↔Artifacts: loadgen-phase5-delta-20261025: caps/receive_pack_ofs_delta
  • wire↔Artifacts: wire-20261115t2116-1nam: caps.receive-pack-capabilities#unknown-capability-on-push/art-raw
  • wire↔Artifacts: wire-20261115t2116-1nam: caps.receive-pack-capabilities#unknown-capability-on-push/art-curl
caps.server-option

v2 server-option arguments on ls-refs and fetch.

Unsupported: discover() reads the capability; no ply operation sends a server-option.

Observed:

  • wire↔Artifacts: loadgen-phase2-20261025: capability_table/v2
caps.wait-for-done-packfile-uris-sideband-all

v2 fetch features wait-for-done, packfile-uris and sideband-all.

Unsupported: src/closed.ts names them only to classify an advertisement; ply never requests them.

Observed:

  • wire↔Artifacts: loadgen-phase5-delta-20261025: caps/v2_fetch_features
caps.object-info

The v2 object-info command (object sizes without a pack).

Unsupported: No ply operation sends command=object-info.

Observed:

  • wire↔Artifacts: loadgen-phase2-20261025: object_info/artifacts
  • wire↔Artifacts: wire-20261115t2038-ee4x: caps.object-info#size/art-raw
  • wire↔Artifacts: wire-20261115t2038-ee4x: caps.object-info#size/art-curl

Fetch: negotiation, filters, shallow, include-tag, thin packs (fetch, 20)

idstatusevidenceply opstests
fetch.want-tip-full-packverifiedply↔git, git↔ArtifactsfetchPack1
fetch.want-non-tip-objectverifiedply↔git, ply↔Artifacts, git↔ArtifactsfetchPack, fetchObject, readFile2
fetch.want-unreachable-or-unknownverifiedply↔git, ply↔Artifacts, git↔Artifacts, wire↔ArtifactsfetchPack2
fetch.want-have-line-syntaxverifiedply↔git, wire↔ArtifactsfetchRequest, negotiate1
fetch.have-negotiationverifiedply↔git, git↔Artifactsnegotiate, fetchPack2
fetch.acknowledgments-ready-packfileverifiedply↔gitfetchPack2
fetch.filter-blob-noneverifiedply↔git, ply↔Artifacts, git↔ArtifactsfetchPack, fetchPackFiltered, readFile2
fetch.filter-tree-depthverifiedply↔git, git↔ArtifactsfetchPack, readCommit2
fetch.filter-blob-limitverifiedply↔git, git↔ArtifactsfetchPack1
fetch.filter-combineverifiedply↔gitfetchPack, readFile2
fetch.filter-sparse-oidunsupported (observed)git↔Artifacts, wire↔Artifacts—0
fetch.filter-refusal-fallbackverifiedply↔git, ply↔ArtifactslearnFilter, fetchPack, readFile2
fetch.deepen-depthverifiedply↔git, git↔ArtifactsfetchPack, fetchObject3
fetch.deepen-sinceverifiedply↔git, git↔ArtifactsfetchPack1
fetch.deepen-notverifiedply↔git, git↔ArtifactsfetchPack1
fetch.deepen-relative-unshallowverifiedply↔git, git↔ArtifactsfetchPack1
fetch.include-tagverifiedply↔git, git↔ArtifactsfetchPack1
fetch.thin-packverifiedply↔git, git↔ArtifactsfetchPack, resolvePack2
fetch.ofs-delta-requestedverifiedply↔git, wire↔ArtifactsfetchPack, parsePack1
fetch.sideband-bandsverifiedply↔gitparseSideband, fetchPack2
fetch.want-tip-full-pack

want of a tip with done and no filter: the pack holds exactly what pack-objects sends.

Ops: src/fetchpack.ts fetchPack.

Tests:

  • test/protocol.test.js: exhaustive fetch matrix: wants × haves × deepen × filter × server

Evidence:

  • ply↔git: test/protocol.test.js
  • git↔Artifacts: loadgen-compat-20261024: clone_full/small/v2
  • git↔Artifacts: loadgen-compat-20261024: clone_full/big/v2
  • git↔Artifacts: validate-7b0c310f: git judge: fsck --strict, refs, history

On Artifacts only stock git has fetched full packs; ply always fetches there with a filter or a depth.

fetch.want-non-tip-object

want of an object that is not an advertised tip (an older commit, a tree, a blob, a tag) by id.

Ops: src/fetchpack.ts fetchPack, src/fetch.ts fetchObject, src/read.ts readFile.

Tests:

  • test/protocol.test.js: exhaustive fetch matrix: wants × haves × deepen × filter × server
  • test/read.test.js: readFile bytes == git show <ref>:<path> for every blob path and every ref form

Evidence:

  • ply↔git: test/protocol.test.js
  • ply↔git: test/read.test.js
  • ply↔Artifacts: validate-7b0c310f: read/blob README.md
  • ply↔Artifacts: validate-7b0c310f: tree (root, src)
  • git↔Artifacts: loadgen-phase3-20261025: reachable_nontip/v2/artifacts
  • git↔Artifacts: loadgen-phase2-20261025: fetch_reachable_sha

The reference fixtures set uploadpack.allowAnySHA1InWant; a differential run must give the reference server the want policy Artifacts has.

fetch.want-unreachable-or-unknown

want of an unreachable or nonexistent id: the server refuses (ERR not our ref), and ply reports a typed remote_error.

Ops: src/fetchpack.ts fetchPack.

Tests:

  • test/mutant-kill-tree.test.js: ERR upload-pack: not our ref x
  • test/probes/probes.test.js: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository

Evidence:

  • git↔Artifacts: loadgen-phase3-20261025: unreachable_local/v2/artifacts
  • git↔Artifacts: loadgen-phase3-20261025: fake_sha/v2/artifacts
  • wire↔Artifacts: loadgen-phase4-hostile-20261025: proto/want_short_oid
  • wire↔Artifacts: loadgen-phase4-hostile-20261025: proto/want_nonhex_oid
  • ply↔git: test/probes/probes.test.js
  • ply↔Artifacts: probes-20261115t1926-gfhc: fetch.want-unreachable-or-unknown#phantom/art-ply

ply sends an unknown want against git http-backend in the probes (#phantom, an id no one holds); an unreachable but present id is not probed.

fetch.want-have-line-syntax

want/have/shallow lines: upload-pack's verdict on each class of id, and ply refusing non-ids before the wire.

Ops: src/fetch.ts fetchRequest, src/negotiate.ts negotiate.

Tests:

  • test/want-oracle.test.js: want: git upload-pack and fetchRequest agree on every class

Evidence:

  • ply↔git: test/want-oracle.test.js
  • wire↔Artifacts: loadgen-phase4-hostile-20261025: proto/have_bad_oid
  • wire↔Artifacts: loadgen-phase4-hostile-20261025: proto/shallow_bad_oid
fetch.have-negotiation

Multi-round have/ACK negotiation, then done: the server stops at common commits and sends only what is missing.

Ops: src/negotiate.ts negotiate, src/fetchpack.ts fetchPack.

Tests:

  • test/protocol.test.js: exhaustive fetch matrix: wants × haves × deepen × filter × server
  • test/want-oracle.test.js: negotiate: an acknowledgment that is not an object id

Evidence:

  • ply↔git: test/protocol.test.js
  • git↔Artifacts: loadgen-compat-20261024: incremental_fetch/scratch/v2

On Artifacts only stock git has negotiated; no ply probe has sent haves there.

fetch.acknowledgments-ready-packfile

v2 response sections in order (acknowledgments, ready, shallow-info, packfile); a server that breaks the order is a protocol error, as it is for git.

Ops: src/fetchpack.ts fetchPack.

Tests:

  • test/fetch-lying-server.test.js: a fetch sent with done and answered with acknowledgments only is a protocol error, as it is for git
  • test/fetch-lying-server.test.js: a fetch sent with done and answered with acknowledgments before its packfile is a protocol error, as it is for git

Evidence:

  • ply↔git: test/fetch-lying-server.test.js
fetch.filter-blob-none

filter blob:none: commits and trees, and blobs only when wanted by id.

Ops: src/fetchpack.ts fetchPack, src/fetchpack.ts fetchPackFiltered, src/read.ts readFile.

Tests:

  • test/protocol.test.js: exhaustive fetch matrix: wants × haves × deepen × filter × server
  • test/log.test.js: readLog on blob:none: the trees are harvested

Evidence:

  • ply↔git: test/protocol.test.js
  • ply↔Artifacts: validate-7b0c310f: read/blob README.md
  • ply↔Artifacts: validate-7b0c310f: tree (root, src)
  • ply↔Artifacts: loadgen-phase6-plyw-20261025: read/small
  • git↔Artifacts: loadgen-compat-20261024: filter_blob_none+lazy_checkout/deep/v2
fetch.filter-tree-depth

filter tree:<depth> (tree:0 commit only, tree:1, tree:2).

Ops: src/fetchpack.ts fetchPack, src/read.ts readCommit.

Tests:

  • test/protocol.test.js: exhaustive fetch matrix: wants × haves × deepen × filter × server
  • test/read.test.js: readCommit fetches the commit object only: one tree:0 deepen-1 fetch, no tree fetches

Evidence:

  • ply↔git: test/protocol.test.js
  • git↔Artifacts: loadgen-compat-20261024: filter_tree_0/deep/v2
fetch.filter-blob-limit

filter blob:limit=<n>.

Ops: src/fetchpack.ts fetchPack.

Tests:

  • test/protocol.test.js: exhaustive fetch matrix: wants × haves × deepen × filter × server

Evidence:

  • ply↔git: test/protocol.test.js
  • git↔Artifacts: loadgen-compat-20261024: filter_blob_limit_2m/big/v2
fetch.filter-combine

filter combine:blob:none+tree:<k> (a commit and the first levels of its path in one request).

Ops: src/fetchpack.ts fetchPack, src/read.ts readFile.

Tests:

  • test/protocol.test.js: exhaustive fetch matrix: wants × haves × deepen × filter × server
  • test/path-trees.test.js: a server that takes it: first contact is tree:0

Evidence:

  • ply↔git: test/protocol.test.js
  • ply↔git: test/path-trees.test.js

No Artifacts evidence of any kind for combine filters.

fetch.filter-sparse-oid

filter sparse:oid=<blob>.

Unsupported: No ply operation builds a sparse:oid filter; the wire probe hands one to fetchPackFiltered only to watch it refused, which is not support.

Observed:

  • git↔Artifacts: loadgen-compat-20261024: filter_sparse_oid/wide/v2
  • wire↔Artifacts: wire-20261115t2038-ee4x: fetch.filter-sparse-oid#refused/art-raw
  • wire↔Artifacts: wire-20261115t2038-ee4x: fetch.filter-sparse-oid#refused/art-curl
  • git↔Artifacts: wire-20261115t2038-ee4x: fetch.filter-sparse-oid#refused/art-git
fetch.filter-refusal-fallback

A server that advertises filter but refuses a filter spec with HTTP 400: ply records the refusal for that remote and falls back to blob:none.

Ops: src/transport.ts learnFilter, src/fetchpack.ts fetchPack, src/read.ts readFile.

Tests:

  • test/artifacts-compat.test.js: Unsupported Git fetch filter; only blob:none is supported.
  • test/path-trees.test.js: an Artifacts-like server (only blob:none): never asked for the deep fetch

Evidence:

  • ply↔git: test/artifacts-compat.test.js
  • ply↔Artifacts: validate-7b0c310f: read/blob README.md
  • ply↔Artifacts: loadgen-phase6-plyw-20261025: read/small

The reference tests emulate the 400 with a proxy in front of git; git judges the results, not the refusal.

fetch.deepen-depth

deepen <n>: a shallow pack cut n commits below each want, with shallow-info naming the boundary.

Ops: src/fetchpack.ts fetchPack, src/fetch.ts fetchObject.

Tests:

  • test/protocol.test.js: exhaustive fetch matrix: wants × haves × deepen × filter × server
  • test/parity.test.js: clone --depth N / --filter / --shallow-since / --shallow-exclude: same invocation, same shallow set, same objects
  • test/fetchobject-deepen.test.js: fetchObject costs one object

Evidence:

  • ply↔git: test/parity.test.js
  • git↔Artifacts: loadgen-compat-20261024: depth_1/small/v2
  • git↔Artifacts: loadgen-compat-20261024: depth_n/small/v2
fetch.deepen-since

deepen-since <time>.

Ops: src/fetchpack.ts fetchPack.

Tests:

  • test/parity.test.js: clone --depth N / --filter / --shallow-since / --shallow-exclude: same invocation, same shallow set, same objects

Evidence:

  • ply↔git: test/parity.test.js
  • git↔Artifacts: loadgen-compat-20261024: shallow_since/deep/v2
fetch.deepen-not

deepen-not <ref>.

Ops: src/fetchpack.ts fetchPack.

Tests:

  • test/parity.test.js: clone --depth N / --filter / --shallow-since / --shallow-exclude: same invocation, same shallow set, same objects

Evidence:

  • ply↔git: test/parity.test.js
  • git↔Artifacts: loadgen-compat-20261024: shallow_exclude/deep/v2
fetch.deepen-relative-unshallow

Fetch after a shallow clone: deepen-relative, a deeper depth, and unshallow, from the client's shallow list.

Ops: src/fetchpack.ts fetchPack.

Tests:

  • test/parity.test.js: fetch after a shallow clone: --deepen (relative), --depth=N, --unshallow, --shallow-since, --shallow-exclude

Evidence:

  • ply↔git: test/parity.test.js
  • git↔Artifacts: loadgen-phase2-20261025: deepen_relative_v2
  • git↔Artifacts: loadgen-compat-20261024: unshallow/deep/v2
  • git↔Artifacts: loadgen-phase2-20261025: depth_beyond_history
fetch.include-tag

include-tag: annotated tags that point into the pack are sent with it.

Ops: src/fetchpack.ts fetchPack.

Tests:

  • test/parity.test.js: includeTag: true

Evidence:

  • ply↔git: test/parity.test.js
  • git↔Artifacts: loadgen-compat-20261024: depth_1/wide/v2
  • git↔Artifacts: loadgen-compat-20261024: clone_full/small/v2

ply's own operations never ask for include-tag; only a fetchPack caller that sets it does.

fetch.thin-pack

thin-pack with haves: deltas against objects the client has, resolved against external bases.

Ops: src/fetchpack.ts fetchPack, src/packresolve.ts resolvePack.

Tests:

  • test/protocol.test.js: exhaustive fetch matrix: wants × haves × deepen × filter × server
  • test/edges.test.js: thin-pack fetch with have resolves against external base

Evidence:

  • ply↔git: test/edges.test.js
  • git↔Artifacts: loadgen-phase5-delta-20261025: storage/thin_fetch
fetch.ofs-delta-requested

ofs-delta: OFS_DELTA entries only when asked for.

Ops: src/fetchpack.ts fetchPack, src/packresolve.ts parsePack.

Tests:

  • test/protocol.test.js: exhaustive fetch matrix: wants × haves × deepen × filter × server

Evidence:

  • ply↔git: test/protocol.test.js
  • wire↔Artifacts: loadgen-phase5-delta-20261025: caps/upload_v0_ofs_thin
fetch.sideband-bands

Side-band in the packfile section: band 1 data, band 2 progress, band 3 fatal error.

Ops: src/fetch.ts parseSideband, src/fetchpack.ts fetchPack.

Tests:

  • test/adversarial.test.js: { name: 'fetch band 3 (commit)'
  • test/remote-text.test.js: listRefs (ERR) and readFile (fetch ERR, fetch band 3) carry none of it

Evidence:

  • ply↔git: test/adversarial.test.js

Band 3 is only ever injected by a proxy; no server has been made to send ply a fatal band-3 line.

Packfiles: OFS/REF deltas, thin bases, malformed packs (served and pushed) (pack, 18)

idstatusevidenceply opstests
pack.ofs-delta-resolveverifiedply↔gitparsePack, resolvePackRange, scanPack1
pack.ref-delta-resolveverifiedply↔git, ply↔ArtifactsparsePack, resolvePackRange, scanPack2
pack.thin-ref-baseverifiedply↔gitresolvePack1
pack.truncated-served-packverifiedply↔gitparsePack, scanPack, resolvePackRange1
pack.corrupt-served-packverifiedply↔gitparsePack, scanPack, fetchPack2
pack.served-pack-limitsverifiedply↔gitparsePack, resolvePackRange3
pack.push-ofs-delta-acceptedverifiedply↔git, wire↔Artifactspush, pushPack2
pack.push-thin-against-server-baseverifiedply↔git, ply↔Artifacts, git↔Artifacts, wire↔ArtifactseditFile, push2
pack.push-thin-missing-baseverifiedply↔git, ply↔Artifacts, wire↔ArtifactspushPack1
pack.push-corrupt-pack-refusedverifiedply↔git, ply↔Artifacts, wire↔ArtifactspushPack, classifyReport4
pack.push-duplicate-objectverifiedply↔gitpush1
pack.push-malformed-object-refusedverifiedply↔git, ply↔Artifacts, wire↔ArtifactspushPack1
pack.push-bad-header-refusedverifiedply↔git, ply↔ArtifactspushPack1
pack.push-bad-entry-refusedverifiedply↔git, ply↔ArtifactspushPack1
pack.push-duplicate-entriesverifiedply↔git, ply↔ArtifactspushPack1
pack.push-fsck-tree-refusedverifiedply↔git, ply↔Artifacts, git↔Artifactspush1
pack.push-fsck-commit-refusedverifiedply↔git, ply↔Artifacts, git↔Artifactspush1
pack.push-decompression-ratioverifiedply↔git, ply↔Artifacts, git↔Artifactspush1
pack.ofs-delta-resolve

A served pack with OFS_DELTA chains resolves to the objects git verify-pack lists.

Ops: src/packresolve.ts parsePack, src/packrangeresolve.ts resolvePackRange, src/pullstream.ts scanPack.

Tests:

  • test/pack-range-resolve.test.js: this repository's pack with OFS deltas matches git verify-pack

Evidence:

  • ply↔git: test/pack-range-resolve.test.js

Artifacts sends REF_DELTA only, so no fetch from it reaches OFS resolution.

pack.ref-delta-resolve

A served pack of REF_DELTA entries only (what Artifacts sends) resolves in any order.

Ops: src/packresolve.ts parsePack, src/packrangeresolve.ts resolvePackRange, src/pullstream.ts scanPack.

Tests:

  • test/pack-range-resolve.test.js: this repository's pack, REF_DELTA only (what Artifacts sends)
  • test/edges.test.js: REF_DELTA packs (server without ofs-delta) resolve identically

Evidence:

  • ply↔git: test/pack-range-resolve.test.js
  • ply↔Artifacts: validate-7b0c310f: read/blob README.md
  • ply↔Artifacts: validate-7b0c310f: viewer: /r/ply blob (README.md)
pack.thin-ref-base

A thin REF base supplied from outside the pack is checked against its claimed id before a delta applies.

Ops: src/packresolve.ts resolvePack.

Tests:

  • test/space/thin-base.test.js: thin REF base: every claim × byte form against git hash-object and index-pack --fix-thin

Evidence:

  • ply↔git: test/space/thin-base.test.js
pack.truncated-served-pack

A served pack cut at any byte is refused, typed, on every read path, where git index-pack refuses it.

Ops: src/packresolve.ts parsePack, src/pullstream.ts scanPack, src/packrangeresolve.ts resolvePackRange.

Tests:

  • test/space/pack-cut.test.js: cut: every byte offset of every pack is refused, typed, on every path

Evidence:

  • ply↔git: test/space/pack-cut.test.js
pack.corrupt-served-pack

A served pack with a corrupt header field, zlib member, delta or checksum is refused exactly where git index-pack --strict refuses it.

Ops: src/packresolve.ts parsePack, src/pullstream.ts scanPack, src/fetchpack.ts fetchPack.

Tests:

  • test/space/pack-cut.test.js: corrupt: every header-field class is refused exactly where git index-pack --strict refuses it, typed
  • test/adversarial.test.js: every protocol-aware mutator × every stage: typed error or git-verified success, never silent corruption

Evidence:

  • ply↔git: test/space/pack-cut.test.js
pack.served-pack-limits

Hostile sizes in a served pack (object size, delta result, chain depth, inflated total) are refused before allocation.

Ops: src/packresolve.ts parsePack, src/packrangeresolve.ts resolvePackRange.

Tests:

  • test/adversarial.test.js: I4 limits: hostile sizes are rejected before allocation; memory does not grow
  • test/delta-bound.test.js: A delta that asks for a huge result must die before the output buffer exists
  • test/space/pack-cut.test.js: caps: maxObjectSize, maxInflatedTotal, maxDeltaChain at, and one under, what each real pack needs

Evidence:

  • ply↔git: test/space/pack-cut.test.js
pack.push-ofs-delta-accepted

receive-pack accepts a pushed pack with OFS_DELTA entries when it advertises ofs-delta.

Ops: src/push.ts push, src/receivecaps.ts pushPack.

Tests:

  • test/push-once.test.js: push: an ofs delta whose base is a repeated object still names its base
  • test/push-pack.test.js: a stock git pack of known length: chunked stream, ref moves, fsck --strict clean, span counts the body

Evidence:

  • ply↔git: test/push-pack.test.js
  • wire↔Artifacts: loadgen-phase5-delta-20261025: push/ofs
pack.push-thin-against-server-base

receive-pack completes a thin pushed pack whose REF bases it holds (every ply edit pushes blob and tree deltas this way).

Ops: src/edit.ts editFile, src/push.ts push.

Tests:

  • test/edges.test.js: push = commit + 100 tree deltas + blob delta
  • test/probes/probes.test.js: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository

Evidence:

  • ply↔git: test/edges.test.js
  • ply↔Artifacts: validate-7b0c310f: write: edit README find/replace (c1)
  • wire↔Artifacts: loadgen-phase5-delta-20261025: push/thin_ok
  • ply↔git: test/probes/probes.test.js
  • ply↔Artifacts: probes-20261114t2226-yyjq: pack.push-thin-against-server-base#literal-delta/art-ply
  • git↔Artifacts: probes-20261114t2226-yyjq: pack.push-thin-against-server-base#literal-delta/art-git
pack.push-thin-missing-base

receive-pack refuses a thin pushed pack whose base it does not hold, and moves no ref.

Ops: src/receivecaps.ts pushPack.

Tests:

  • test/probes/probes.test.js: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository

Evidence:

  • wire↔Artifacts: loadgen-phase5-delta-20261025: push/thin_missing
  • ply↔git: test/probes/probes.test.js
  • ply↔Artifacts: probes-20261114t2226-yyjq: pack.push-thin-missing-base#ghost-base/art-ply

pushPack carries a thin pack whose delta base the server lacks in the probes, against the reference and Artifacts.

pack.push-corrupt-pack-refused

receive-pack refuses a corrupt pushed pack (unpack error, ng for every ref) and moves no ref.

Ops: src/receivecaps.ts pushPack, src/push.ts classifyReport.

Tests:

  • test/push-pack.test.js: a corrupt pack against stock git
  • test/custom-exchange.test.js: a corrupt pack: the report is unpackFailed
  • test/push-unpack-host.test.js: the echoed shape is unpackFailed and decides push_rejected; delete-only stays ambiguous
  • test/probes/probes.test.js: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository

Evidence:

  • ply↔git: test/push-pack.test.js
  • wire↔Artifacts: loadgen-phase4-hostile-write-20261025: pack/corrupt_zlib
  • wire↔Artifacts: loadgen-phase4-hostile-write-20261025: pack/bad_checksum
  • wire↔Artifacts: loadgen-phase4-hostile-write-20261025: pack/truncated
  • wire↔Artifacts: loadgen-phase4-hostile-write-20261025: pack/bad_magic
  • wire↔Artifacts: loadgen-phase4-hostile-write-20261025: pack/wrong_object_count
  • ply↔git: test/probes/probes.test.js
  • ply↔Artifacts: probes-20261114t2226-yyjq: pack.push-corrupt-pack-refused#bad-trailer/art-ply
  • ply↔Artifacts: probes-20261114t2226-yyjq: pack.push-corrupt-pack-refused#bad-zlib/art-ply
  • ply↔Artifacts: probes-20261114t2226-yyjq: pack.push-corrupt-pack-refused#truncated/art-ply

ply's reading of Artifacts' own unpack-failure report is tested on bytes copied from prod into a fake (push-unpack-host.test.js) and live by the corrupt-pack probes (bad trailer, bad zlib, truncated).

pack.push-duplicate-object

A pushed pack never names one object twice (a strict receiver refuses it).

Ops: src/push.ts push.

Tests:

  • test/push-once.test.js: push: a list that names objects twice is one object each on the wire

Evidence:

  • ply↔git: test/push-once.test.js
pack.push-malformed-object-refused

receive-pack refuses a well-framed pack that holds a malformed object or a delta with no base.

Ops: src/receivecaps.ts pushPack.

Tests:

  • test/probes/probes.test.js: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository

Evidence:

  • wire↔Artifacts: loadgen-phase4-hostile-write-20261025: pack/invalid_commit_payload
  • wire↔Artifacts: loadgen-phase4-hostile-write-20261025: pack/delta_missing_base
  • ply↔git: test/probes/probes.test.js
  • ply↔Artifacts: probes-20261114t2226-yyjq: pack.push-malformed-object-refused#missing-blob/art-ply
  • ply↔Artifacts: probes-20261114t2226-yyjq: pack.push-malformed-object-refused#delta-copy-past-end/art-ply
  • ply↔Artifacts: probes-20261115t2113-phhp: pack.push-malformed-object-refused#tag-type-mismatch/art-ply

ply's encoders never write a malformed object (the encode-*-fsck tests); the probes carry one through pushPack: a commit naming a missing blob, a delta copying past its base.

pack.push-bad-header-refused

receive-pack refuses a pushed pack whose header is wrong (signature, version, object count more or fewer than sent), moves no ref, and still serves the repository fsck-clean.

Ops: src/receivecaps.ts pushPack.

Tests:

  • test/probes/probes.test.js: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository

Evidence:

  • ply↔git: test/probes/probes.test.js
  • ply↔Artifacts: probes-20261115t1926-gfhc: pack.push-bad-header-refused#bad-signature/art-ply
  • ply↔Artifacts: probes-20261115t1926-gfhc: pack.push-bad-header-refused#bad-version/art-ply
  • ply↔Artifacts: probes-20261115t1926-gfhc: pack.push-bad-header-refused#count-more/art-ply
  • ply↔Artifacts: probes-20261115t1926-gfhc: pack.push-bad-header-refused#count-fewer/art-ply

Probe packs are written by the harness with the trailer recomputed, so only the header is wrong; ply sends them through pushPack.

pack.push-bad-entry-refused

receive-pack refuses a pushed pack with a bad entry (stated size not what the zlib stream inflates to, a reserved object type, an OFS_DELTA reaching before the pack, a delta whose stated result size it does not write), moves no ref, and still serves the repository fsck-clean.

Ops: src/receivecaps.ts pushPack.

Tests:

  • test/probes/probes.test.js: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository

Evidence:

  • ply↔git: test/probes/probes.test.js
  • ply↔Artifacts: probes-20261115t1926-gfhc: pack.push-bad-entry-refused#size-header-mismatch/art-ply
  • ply↔Artifacts: probes-20261115t1926-gfhc: pack.push-bad-entry-refused#bad-type/art-ply
  • ply↔Artifacts: probes-20261115t1926-gfhc: pack.push-bad-entry-refused#ofs-delta-before-start/art-ply
  • ply↔Artifacts: probes-20261115t1926-gfhc: pack.push-bad-entry-refused#delta-size-mismatch/art-ply
pack.push-duplicate-entries

receive-pack with fsckObjects refuses a pushed pack that names every object twice (git index-pack --strict), moves no ref, and still serves the repository fsck-clean.

Ops: src/receivecaps.ts pushPack.

Tests:

  • test/probes/probes.test.js: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository

Evidence:

  • ply↔git: test/probes/probes.test.js
  • ply↔Artifacts: probes-20261115t1926-gfhc: pack.push-duplicate-entries#every-object-twice/art-ply

pack.push-duplicate-object is ply's side (it never sends one object twice); this is the server's answer to a pack that does.

pack.push-fsck-tree-refused

receive-pack with fsckObjects refuses a pushed tree git fsck calls an error (unsorted, a name twice, a / in a name, .git, a zero-padded mode), moves no ref, and still serves the repository fsck-clean.

Ops: src/push.ts push.

Tests:

  • test/probes/probes.test.js: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository

Evidence:

  • ply↔git: test/probes/probes.test.js
  • ply↔Artifacts: probes-20261115t1926-gfhc: pack.push-fsck-tree-refused#unsorted/art-ply
  • git↔Artifacts: probes-20261115t1926-gfhc: pack.push-fsck-tree-refused#unsorted/art-git
  • ply↔Artifacts: probes-20261115t1926-gfhc: pack.push-fsck-tree-refused#duplicate-name/art-ply
  • git↔Artifacts: probes-20261115t1926-gfhc: pack.push-fsck-tree-refused#duplicate-name/art-git
  • ply↔Artifacts: probes-20261115t1926-gfhc: pack.push-fsck-tree-refused#slash-in-name/art-ply
  • git↔Artifacts: probes-20261115t1926-gfhc: pack.push-fsck-tree-refused#slash-in-name/art-git
  • ply↔Artifacts: probes-20261115t1926-gfhc: pack.push-fsck-tree-refused#dot-git/art-ply
  • git↔Artifacts: probes-20261115t1926-gfhc: pack.push-fsck-tree-refused#dot-git/art-git
  • ply↔Artifacts: probes-20261115t1926-gfhc: pack.push-fsck-tree-refused#zero-padded-mode/art-ply
  • git↔Artifacts: probes-20261115t1926-gfhc: pack.push-fsck-tree-refused#zero-padded-mode/art-git

Seeded byte for byte with git hash-object --literally and pushed by both ply and stock git, whose pack writers carry the object unchecked. A tree with mode 100664 (badFilemode) is only a warning to receive.fsckObjects and is not probed.

pack.push-fsck-commit-refused

receive-pack with fsckObjects refuses a pushed commit with a malformed author line (bad date, missing email, bad time zone, a date that overflows), moves no ref, and still serves the repository fsck-clean.

Ops: src/push.ts push.

Tests:

  • test/probes/probes.test.js: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository

Evidence:

  • ply↔git: test/probes/probes.test.js
  • ply↔Artifacts: probes-20261115t1926-gfhc: pack.push-fsck-commit-refused#bad-date/art-ply
  • git↔Artifacts: probes-20261115t1926-gfhc: pack.push-fsck-commit-refused#bad-date/art-git
  • ply↔Artifacts: probes-20261115t1926-gfhc: pack.push-fsck-commit-refused#missing-email/art-ply
  • git↔Artifacts: probes-20261115t1926-gfhc: pack.push-fsck-commit-refused#missing-email/art-git
  • ply↔Artifacts: probes-20261115t1926-gfhc: pack.push-fsck-commit-refused#bad-timezone/art-ply
  • git↔Artifacts: probes-20261115t1926-gfhc: pack.push-fsck-commit-refused#bad-timezone/art-git
  • ply↔Artifacts: probes-20261115t1926-gfhc: pack.push-fsck-commit-refused#date-overflow/art-ply
  • git↔Artifacts: probes-20261115t1926-gfhc: pack.push-fsck-commit-refused#date-overflow/art-git
pack.push-decompression-ratio

receive-pack takes a pushed blob that inflates about a thousandfold (16 MiB of one byte in about 16 KiB), under its object and pack caps, and serves it back.

Ops: src/push.ts push.

Tests:

  • test/probes/probes.test.js: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository

Evidence:

  • ply↔git: test/probes/probes.test.js
  • ply↔Artifacts: probes-20261115t1926-gfhc: pack.push-decompression-ratio#zeros-16mib/art-ply
  • git↔Artifacts: probes-20261115t1926-gfhc: pack.push-decompression-ratio#zeros-16mib/art-git

Push and receive-pack (push, 19)

idstatusevidenceply opstests
push.create-refverifiedply↔git, ply↔Artifacts, git↔Artifactspush, createBranch3
push.first-commit-empty-repoverifiedply↔git, ply↔Artifacts, git↔ArtifactscommitChanges, push2
push.fast-forward-updateverifiedply↔git, ply↔Artifacts, git↔Artifactspush, editFile2
push.non-fast-forwardverifiedply↔git, ply↔Artifacts, git↔Artifactspush3
push.delete-refverifiedply↔git, ply↔Artifacts, git↔Artifactspush, deleteBranch3
push.atomicverifiedply↔git, ply↔Artifacts, git↔Artifactspush, pushPack, runTransfer3
push.non-atomic-partialverifiedply↔git, ply↔Artifacts, git↔Artifactspush2
push.report-statusverifiedply↔git, ply↔Artifactspush, classifyReport3
push.report-status-v2verifiedply↔gitpush1
push.sideband-hook-outputverifiedply↔gitpush1
push.push-optionsverifiedply↔git, git↔Artifactspush, pushPack2
push.hook-rejectionverifiedply↔gitpush1
push.ref-name-rulesverifiedply↔git, ply↔Artifacts, git↔Artifacts, wire↔Artifactspush2
push.ref-to-missing-object-refusedverifiedply↔git, ply↔ArtifactspushPack1
push.size-limitsverifiedply↔git, ply↔Artifacts, git↔Artifacts, wire↔Artifactspush, pushPack2
push.many-ref-updatesverifiedply↔git, ply↔Artifacts, git↔Artifacts, wire↔Artifactspush1
push.signed-pushunsupported (observed)git↔Artifacts—0
push.from-shallow-cloneverifiedply↔git, ply↔Artifacts, git↔Artifactspush1
push.from-partial-cloneverifiedply↔git, ply↔Artifacts, git↔ArtifactsfetchPack, push1
push.create-ref

A command with the zero old id creates a ref.

Ops: src/push.ts push, src/refops.ts createBranch.

Tests:

  • test/push.test.js: 'create': t =>
  • test/e2e-customer.test.js: createBranch from a branch name, a short name, a peeled annotated tag
  • test/probes/probes.test.js: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository

Evidence:

  • ply↔git: test/push.test.js
  • ply↔Artifacts: validate-7b0c310f: branch create (feat from c0)
  • ply↔Artifacts: loadgen-phase6-plyw-20261025: branch/create
  • git↔Artifacts: loadgen-phase2-20261025: new_branch
  • ply↔git: test/probes/probes.test.js
  • ply↔Artifacts: probes-20261114t2226-yyjq: push.create-ref#plain/art-ply
  • git↔Artifacts: probes-20261114t2226-yyjq: push.create-ref#plain/art-git
  • ply↔Artifacts: probes-20261114t2226-yyjq: push.create-ref#already-exists/art-ply
  • git↔Artifacts: probes-20261114t2226-yyjq: push.create-ref#already-exists/art-git
push.first-commit-empty-repo

The first push to an empty repository creates the default branch from a root commit.

Ops: src/changes.ts commitChanges, src/push.ts push.

Tests:

  • test/changes.test.js: commitChanges: start × place × op against git cat-file and fsck --strict
  • test/probes/probes.test.js: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository

Evidence:

  • ply↔git: test/changes.test.js
  • ply↔Artifacts: validate-7b0c310f: write: root commit (edit changes)
  • ply↔git: test/probes/probes.test.js
  • ply↔Artifacts: probes-20261114t2226-yyjq: push.first-commit-empty-repo#root/art-ply
  • git↔Artifacts: probes-20261114t2226-yyjq: push.first-commit-empty-repo#root/art-git
push.fast-forward-update

A fast-forward update with the current old id lands.

Ops: src/push.ts push, src/edit.ts editFile.

Tests:

  • test/push.test.js: push matrix: configs × hooks × commands × caps, parity with git push
  • test/probes/probes.test.js: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository

Evidence:

  • ply↔git: test/push.test.js
  • ply↔Artifacts: validate-7b0c310f: write: edit README find/replace (c1)
  • ply↔Artifacts: loadgen-phase6-plyw-20261025: edit/ok
  • ply↔git: test/probes/probes.test.js
  • ply↔Artifacts: probes-20261114t2226-yyjq: push.fast-forward-update#plain/art-ply
  • git↔Artifacts: probes-20261114t2226-yyjq: push.fast-forward-update#plain/art-git
push.non-fast-forward

A non-fast-forward update: refused under receive.denyNonFastForwards, accepted as a forced update otherwise.

Ops: src/push.ts push.

Tests:

  • test/push.test.js: 'nonff-update': t =>
  • test/push.test.js: 'deny-nonff': { 'receive.denyNonFastForwards': 'true' }
  • test/probes/probes.test.js: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository

Evidence:

  • ply↔git: test/push.test.js
  • git↔Artifacts: loadgen-phase2-20261025: non_ff_reject
  • git↔Artifacts: loadgen-compat-20261024: force_push/scratch/v2
  • ply↔git: test/probes/probes.test.js
  • ply↔Artifacts: probes-20261114t2226-yyjq: push.non-fast-forward#with-old-id/art-ply
  • git↔Artifacts: probes-20261114t2226-yyjq: push.non-fast-forward#with-old-id/art-git
push.delete-ref

A command with the zero new id deletes a ref (delete-refs); refused under receive.denyDeletes.

Ops: src/push.ts push, src/refops.ts deleteBranch.

Tests:

  • test/push.test.js: 'delete': t =>
  • test/push.test.js: 'deny-deletes': { 'receive.denyDeletes': 'true' }
  • test/probes/probes.test.js: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository

Evidence:

  • ply↔git: test/push.test.js
  • ply↔Artifacts: validate-7b0c310f: branch delete (CAS ok)
  • ply↔Artifacts: loadgen-phase6-plyw-20261025: branch/delete
  • git↔Artifacts: loadgen-compat-20261024: tag_push_delete/scratch/v2
  • ply↔git: test/probes/probes.test.js
  • ply↔Artifacts: probes-20261114t2226-yyjq: push.delete-ref#plain/art-ply
  • git↔Artifacts: probes-20261114t2226-yyjq: push.delete-ref#plain/art-git
push.atomic

atomic: several ref updates land together or not at all.

Ops: src/push.ts push, src/receivecaps.ts pushPack, src/transfer.ts runTransfer.

Tests:

  • test/push.test.js: 'multi-atomic': t =>
  • test/push-pack.test.js: atomic: checked against the advertisement, then sent; two refs land together
  • test/probes/probes.test.js: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository

Evidence:

  • ply↔git: test/push-pack.test.js
  • git↔Artifacts: loadgen-compat-20261024: atomic_push_multi_ref/scratch/v2
  • ply↔git: test/probes/probes.test.js
  • ply↔Artifacts: probes-20261114t2226-yyjq: push.atomic#all-land/art-ply
  • ply↔Artifacts: probes-20261114t2226-yyjq: push.atomic#one-stale/art-ply
  • git↔Artifacts: probes-20261114t2226-yyjq: push.atomic#all-land/art-git
  • git↔Artifacts: probes-20261114t2226-yyjq: push.atomic#one-stale/art-git

The one-stale variant makes one command fail at the server: another writer moves its ref while the request is held.

push.non-atomic-partial

A non-atomic multi-ref push the server applies in part is push_partial, naming what landed.

Ops: src/push.ts push.

Tests:

  • test/push.test.js: assert.equal(err.code, 'push_partial'
  • test/probes/probes.test.js: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository

Evidence:

  • ply↔git: test/push.test.js
  • ply↔git: test/probes/probes.test.js
  • ply↔Artifacts: probes-20261114t2226-yyjq: push.non-atomic-partial#one-stale/art-ply
  • git↔Artifacts: probes-20261114t2226-yyjq: push.non-atomic-partial#one-stale/art-git

Probed by a two-ref push while another writer moves one ref (src/probe-scenarios.ts). Per-check outcomes are in the private run record.

push.report-status

report-status: an unpack line (ok or a reason) and an ok or ng line per command, classified as landed, rejected, conflict or ambiguous.

Ops: src/push.ts push, src/push.ts classifyReport.

Tests:

  • test/space/push-ng.test.js: push ng: cells observed from git
  • test/space/push-outcome.test.js: The push-outcome enumerator
  • test/push.test.js: push matrix: configs × hooks × commands × caps, parity with git push

Evidence:

  • ply↔git: test/push.test.js
  • ply↔Artifacts: validate-7b0c310f: write: root commit (edit changes)

push-ng and push-outcome judge the class table over a fake transport; their git-observed cells are recorded bytes.

push.report-status-v2

report-status-v2: option lines after ok.

Ops: src/push.ts push.

Tests:

  • test/push.test.js: reportV2: true

Evidence:

  • ply↔git: test/push.test.js

No Artifacts evidence: no recorded run says whether Artifacts advertises report-status-v2.

push.sideband-hook-output

side-band-64k on receive-pack: the report on band 1, hook output on band 2.

Ops: src/push.ts push.

Tests:

  • test/push.test.js: hook stderr visible on band 2 when side-band is requested

Evidence:

  • ply↔git: test/push.test.js
push.push-options

push-options: sent only when advertised; they reach the hook.

Ops: src/push.ts push, src/receivecaps.ts pushPack.

Tests:

  • test/push.test.js: options reached the hook
  • test/push-pack.test.js: push options: refused when not advertised, sent when they are

Evidence:

  • ply↔git: test/push.test.js
  • git↔Artifacts: loadgen-phase2-20261025: push_options
push.hook-rejection

A pre-receive or update hook that declines: ng with the hook's reason, ref unchanged.

Ops: src/push.ts push.

Tests:

  • test/push.test.js: 'pre-receive-reject': ['pre-receive'

Evidence:

  • ply↔git: test/push.test.js

Artifacts runs no user hooks; this is reference-only by nature.

push.ref-name-rules

receive-pack's ref-name rules ("funny refname"): ply refuses before the wire exactly what receive-pack refuses, and also any name over 1024 bytes, which receive-pack accepts.

Ops: src/push.ts push.

Tests:

  • test/space/refname.test.js: ref names: ply agrees with git check-ref-format and receive-pack on every cell
  • test/probes/wire.test.js: reference: ${plan.id} meets its answer with every sender

Evidence:

  • ply↔git: test/space/refname.test.js
  • git↔Artifacts: loadgen-phase2-20261025: invalid_ref_names
  • wire↔Artifacts: loadgen-phase4-hostile-write-20261025: ref/dotdot
  • wire↔Artifacts: loadgen-phase4-hostile-write-20261025: ref/control_char
  • wire↔Artifacts: loadgen-phase4-hostile-write-20261025: ref/long_name
  • ply↔git: test/probes/wire.test.js
  • ply↔Artifacts: wire-20261115t2116-1nam: push.ref-name-rules#leading-dash/art-ply
  • ply↔Artifacts: wire-20261115t2116-1nam: push.ref-name-rules#component-200/art-ply
  • ply↔Artifacts: wire-20261115t2116-1nam: push.ref-name-rules#path-1000/art-ply
  • ply↔Artifacts: wire-20261115t2116-1nam: push.ref-name-rules#component-300/art-ply
  • git↔Artifacts: wire-20261115t2116-1nam: push.ref-name-rules#leading-dash/art-git
  • git↔Artifacts: wire-20261115t2116-1nam: push.ref-name-rules#component-200/art-git
  • git↔Artifacts: wire-20261115t2116-1nam: push.ref-name-rules#path-1000/art-git
  • git↔Artifacts: wire-20261115t2116-1nam: push.ref-name-rules#component-300/art-git
  • git↔Artifacts: wire-20261115t2116-1nam: push.ref-name-rules#path-4000/art-git
  • wire↔Artifacts: wire-20261115t2116-1nam: push.ref-name-rules#dot-dot/art-raw
  • wire↔Artifacts: wire-20261115t2116-1nam: push.ref-name-rules#at-brace/art-raw
  • wire↔Artifacts: wire-20261115t2116-1nam: push.ref-name-rules#lock-suffix/art-raw
  • wire↔Artifacts: wire-20261115t2116-1nam: push.ref-name-rules#control-char/art-raw
  • wire↔Artifacts: wire-20261115t2116-1nam: push.ref-name-rules#del-char/art-raw
  • wire↔Artifacts: wire-20261115t2116-1nam: push.ref-name-rules#space/art-raw
  • wire↔Artifacts: wire-20261115t2116-1nam: push.ref-name-rules#colon/art-raw
  • wire↔Artifacts: wire-20261115t2116-1nam: push.ref-name-rules#backslash/art-raw
  • wire↔Artifacts: wire-20261115t2116-1nam: push.ref-name-rules#double-slash/art-raw
  • wire↔Artifacts: wire-20261115t2116-1nam: push.ref-name-rules#trailing-slash/art-raw
  • wire↔Artifacts: wire-20261115t2116-1nam: push.ref-name-rules#trailing-dot/art-raw
  • wire↔Artifacts: wire-20261115t2116-1nam: push.ref-name-rules#dot-component/art-raw
  • wire↔Artifacts: wire-20261115t2116-1nam: push.ref-name-rules#bare-head/art-raw
  • wire↔Artifacts: wire-20261115t2116-1nam: push.ref-name-rules#refs-heads-at/art-raw
  • wire↔Artifacts: wire-20261115t2116-1nam: push.ref-name-rules#refs-heads-head/art-raw
  • wire↔Artifacts: wire-20261115t2116-1nam: push.ref-name-rules#path-4000/art-raw
  • wire↔Artifacts: wire-20261115t2116-1nam: push.ref-name-rules#leading-dash/art-raw
  • wire↔Artifacts: wire-20261115t2116-1nam: push.ref-name-rules#component-200/art-raw
  • wire↔Artifacts: wire-20261115t2116-1nam: push.ref-name-rules#path-1000/art-raw
  • wire↔Artifacts: wire-20261115t2116-1nam: push.ref-name-rules#component-300/art-raw

The wire plans send each refused name from a raw socket; stock git and ply refuse them before any request, so their Artifacts checks for those names say nothing about the server and are not cited. ply's 1024-byte cap (src/validate.ts) refuses the 4000-byte name receive-pack and stock git push.

push.ref-to-missing-object-refused

receive-pack refuses a command whose new id is in neither the pack nor the repository (missing necessary objects), moves no ref, and still serves the repository fsck-clean.

Ops: src/receivecaps.ts pushPack.

Tests:

  • test/probes/probes.test.js: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository

Evidence:

  • ply↔git: test/probes/probes.test.js
  • ply↔Artifacts: probes-20261115t1926-gfhc: push.ref-to-missing-object-refused#not-in-pack-or-repo/art-ply
  • ply↔Artifacts: probes-20261115t2113-phhp: push.ref-to-missing-object-refused#tag-of-missing-object/art-ply

Stock git refuses such a push client side, so only ply (pushPack with a pack of no objects) sends it.

push.size-limits

A push over the server's object or pack size cap is refused with a report ply classifies as limit_exceeded.

Ops: src/push.ts push, src/receivecaps.ts pushPack.

Tests:

  • test/push-unpack-host.test.js: Artifacts 64 MiB cap is limit_exceeded with got/max in bytes, not push_rejected or ambiguous
  • test/probes/probes.test.js: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository

Evidence:

  • git↔Artifacts: loadgen-phase2-20261025: blob_push_ceiling
  • git↔Artifacts: loadgen-compat-20261024: large_blob_push_24m/scratch/v2
  • wire↔Artifacts: loadgen-phase4-hostile-write-20261025: pack/zlib_bomb_40m
  • ply↔git: test/probes/probes.test.js
  • ply↔Artifacts: probes-20261114t2226-yyjq: push.size-limits#pack-over-cap/art-ply
  • git↔Artifacts: probes-20261114t2226-yyjq: push.size-limits#pack-over-cap/art-git

A 66 MiB pack against a 64 MiB cap. ply classifies the server's stated cap as limit_exceeded; git http-backend (receive.maxInputSize) refuses with unpacker error, its reason on band 2 only, which ply reports as push_rejected: an expected difference, src/probe-allow.ts.

push.many-ref-updates

One push carrying many ref updates.

Ops: src/push.ts push.

Tests:

  • test/probes/probes.test.js: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository

Evidence:

  • git↔Artifacts: loadgen-phase2-20261025: many_refs_5000
  • wire↔Artifacts: loadgen-phase4-hostile-write-20261025: ref/fifty_updates
  • ply↔git: test/probes/probes.test.js
  • ply↔Artifacts: probes-20261114t2226-yyjq: push.many-ref-updates#fifty-creates/art-ply
  • git↔Artifacts: probes-20261114t2226-yyjq: push.many-ref-updates#fifty-creates/art-git

The probe sends 50 creates in one push; no other test sends more than a few.

push.signed-push

push-cert (signed pushes).

Unsupported: ply signs commits (src/sign.ts) but never sends a push certificate.

Observed:

  • git↔Artifacts: loadgen-phase2-20261025: signed_push
push.from-shallow-clone

A push from a shallow clone: when the server holds the boundary commit the push lands; when it lacks the history below the boundary the push is refused and no ref moves.

Ops: src/push.ts push.

Tests:

  • test/probes/probes.test.js: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository

Evidence:

  • ply↔git: test/probes/probes.test.js
  • ply↔Artifacts: probes-20261114t2226-yyjq: push.from-shallow-clone#boundary-held/art-ply
  • git↔Artifacts: probes-20261114t2226-yyjq: push.from-shallow-clone#boundary-held/art-git
  • ply↔Artifacts: probes-20261114t2226-yyjq: push.from-shallow-clone#history-missing/art-ply
  • git↔Artifacts: probes-20261114t2226-yyjq: push.from-shallow-clone#shallow-update/art-git

ply keeps no shallow state; its form of the push is the same objects without the history below the boundary.

The stock git push into a repository without the boundary history is compared against git http-backend with receive.shallowUpdate=true.

push.from-partial-clone

A push from a blob:none partial clone sends only the new objects, including a tree that names a blob the client never fetched, and lands.

Ops: src/fetchpack.ts fetchPack, src/push.ts push.

Tests:

  • test/probes/probes.test.js: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository

Evidence:

  • ply↔git: test/probes/probes.test.js
  • ply↔Artifacts: probes-20261114t2226-yyjq: push.from-partial-clone#blob-none/art-ply
  • git↔Artifacts: probes-20261114t2226-yyjq: push.from-partial-clone#blob-none/art-git
  • ply↔Artifacts: probes-20261114t2226-yyjq: push.from-partial-clone#reuse-absent-blob/art-ply
  • git↔Artifacts: probes-20261114t2226-yyjq: push.from-partial-clone#reuse-absent-blob/art-git

Concurrent updates and stale refs (concurrency, 7)

idstatusevidenceply opstests
concurrency.stale-old-oidverifiedply↔git, ply↔Artifacts, git↔Artifactspush, pushPack, editFile4
concurrency.concurrent-writersverifiedply↔git, ply↔Artifacts, git↔ArtifactseditFile, push3
concurrency.ref-created-between-read-and-pushverifiedply↔git, ply↔Artifacts, git↔Artifactspush, createBranch, createTag, commitChanges3
concurrency.ref-deleted-between-read-and-pushverifiedply↔git, ply↔Artifacts, git↔Artifactspush, commitChanges2
concurrency.read-after-writeverifiedply↔Artifacts, git↔ArtifactslsRefs, readFile, readCommit1
concurrency.empty-report-under-contentionverifiedply↔git, ply↔Artifacts, git↔Artifactspush, classifyReport3
concurrency.two-transfer-runnersverifiedply↔gitrunTransfer1
concurrency.stale-old-oid

A push whose old id is no longer the ref's value is refused (compare-and-swap) and the ref is unchanged.

Ops: src/push.ts push, src/receivecaps.ts pushPack, src/edit.ts editFile.

Tests:

  • test/push.test.js: 'stale-old': t =>
  • test/push-pack.test.js: a stale old oid is cas_conflict, as push reports it
  • test/custom-exchange.test.js: receive-pack refuses a command (stale old id)
  • test/probes/probes.test.js: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository

Evidence:

  • ply↔git: test/push.test.js
  • ply↔git: test/push-pack.test.js
  • git↔Artifacts: loadgen-phase2-20261025: force_with_lease_stale
  • ply↔git: test/probes/probes.test.js
  • ply↔Artifacts: probes-20261114t2226-yyjq: concurrency.stale-old-oid#race/art-ply
  • ply↔Artifacts: probes-20261114t2226-yyjq: concurrency.stale-old-oid#direct/art-ply
  • git↔Artifacts: probes-20261114t2226-yyjq: concurrency.stale-old-oid#race/art-git
  • ply↔Artifacts: probes-20261114t2226-yyjq: concurrency.stale-old-oid#delete-vs-update/art-ply
  • git↔Artifacts: probes-20261114t2226-yyjq: concurrency.stale-old-oid#delete-vs-update/art-git

The validate CAS checks (stale head, stale delete) are refused by ply-web from ls-refs, before any push. The probe run sends the stale old id to Artifacts itself: directly from ply, and from a race (another writer moves the ref while the receive-pack request is held) from ply and stock git.

concurrency.concurrent-writers

Concurrent writers on one ref: one wins each round, the rest are refused as stale and retry; nothing is lost.

Ops: src/edit.ts editFile, src/push.ts push.

Tests:

  • test/probes/probes.test.js: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository
  • test/concurrency.test.js: concurrent CAS writers converge; conflicts are observed and retried, never lost
  • test/edit-race-f34.test.js: same-file edit race ×1000 attempts: only ok and cas_conflict

Evidence:

  • ply↔git: test/probes/probes.test.js
  • ply↔git: test/concurrency.test.js
  • ply↔git: test/edit-race-f34.test.js
  • ply↔Artifacts: loadgen-phase6-plyw-20261025: edit/race_same_file
  • ply↔Artifacts: loadgen-phase6-plyw-20261025: edit/race_diff_files
  • git↔Artifacts: loadgen-phase2-20261025: fetch_push_race
  • ply↔Artifacts: probes-20261114t2226-yyjq: concurrency.concurrent-writers#create-vs-create/art-ply
  • git↔Artifacts: probes-20261114t2226-yyjq: concurrency.concurrent-writers#create-vs-create/art-git
  • ply↔Artifacts: probes-20261114t2226-yyjq: concurrency.concurrent-writers#delete-vs-update/art-ply
  • git↔Artifacts: probes-20261114t2226-yyjq: concurrency.concurrent-writers#delete-vs-update/art-git
concurrency.ref-created-between-read-and-push

Another writer creates the target ref between ply's ls-refs and its receive-pack: the create is refused, naming the winner.

Ops: src/push.ts push, src/refops.ts createBranch, src/refops.ts createTag, src/changes.ts commitChanges.

Tests:

  • test/e2e-customer.test.js: createBranch and createTag lose a race to a ref made between ls-refs and receive-pack: cas_conflict naming the winner
  • test/changes-create-race.test.js: commitChanges creating a ref from a base
  • test/probes/probes.test.js: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository

Evidence:

  • ply↔git: test/e2e-customer.test.js
  • ply↔git: test/probes/probes.test.js
  • ply↔Artifacts: probes-20261114t2226-yyjq: concurrency.ref-created-between-read-and-push#race/art-ply
  • git↔Artifacts: probes-20261114t2226-yyjq: concurrency.ref-created-between-read-and-push#race/art-git

validate's duplicate-branch check is refused by ply-web from ls-refs, before receive-pack; the probe run's race reaches receive-pack.

concurrency.ref-deleted-between-read-and-push

Another writer deletes the target ref between ply's read and its push.

Ops: src/push.ts push, src/changes.ts commitChanges.

Tests:

  • test/changes-delete-race.test.js: head pinned to the base: a target deleted mid-call is cas_conflict and stays deleted
  • test/probes/probes.test.js: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository

Evidence:

  • ply↔git: test/changes-delete-race.test.js
  • ply↔git: test/probes/probes.test.js
  • ply↔Artifacts: probes-20261114t2226-yyjq: concurrency.ref-deleted-between-read-and-push#race/art-ply
  • git↔Artifacts: probes-20261114t2226-yyjq: concurrency.ref-deleted-between-read-and-push#race/art-git
concurrency.read-after-write

A landed push is visible at once to ls-refs and to fetch (no stale advertisement after a push).

Ops: src/lsrefs.ts lsRefs, src/read.ts readFile, src/read.ts readCommit.

Tests:

  • test/transfer.test.js: ls-refs that lags a push: settled by reading again, not by sending again

Evidence:

  • ply↔Artifacts: validate-7b0c310f: freshness: refs-after-write
  • ply↔Artifacts: validate-7b0c310f: freshness: read-after-write README
  • ply↔Artifacts: validate-7b0c310f: freshness: commit-after-write
  • git↔Artifacts: loadgen-phase2-20261025: visibility_latency

transfer.test.js emulates a lagging ls-refs with a proxy; the reference server never lags, so there is no reference evidence.

concurrency.empty-report-under-contention

A receive-pack 200 that carries no report (no unpack or ref lines), whether an empty body or only a band-3 fatal such as the busy refusal Artifacts sends to concurrent same-repo pushes, is ambiguous, never landed; the server applied nothing for it.

Ops: src/push.ts push, src/push.ts classifyReport.

Tests:

  • test/push-unpack-host.test.js: an empty receive-pack report stays ambiguous (concurrent same-repo 200 with no unpack/ref lines)
  • test/mutant-kill.test.js: push outcome (SAFETY.md I36): the exact report shapes, the decision, and the fields the enumerator does not compare
  • test/probes/probes.test.js: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository

Evidence:

  • ply↔git: test/probes/probes.test.js
  • ply↔Artifacts: probes-20261114t2226-yyjq: concurrency.empty-report-under-contention#distinct-refs/art-ply
  • ply↔Artifacts: probes-20261114t2226-yyjq: concurrency.empty-report-under-contention#same-ref/art-ply
  • git↔Artifacts: probes-20261114t2226-yyjq: concurrency.empty-report-under-contention#distinct-refs/art-git
  • git↔Artifacts: probes-20261114t2226-yyjq: concurrency.empty-report-under-contention#same-ref/art-git
  • ply↔Artifacts: probes-20261114t2226-yyjq: concurrency.empty-report-under-contention#retry-after-busy/art-ply
  • git↔Artifacts: probes-20261114t2226-yyjq: concurrency.empty-report-under-contention#retry-after-busy/art-git

Probed with 8 concurrent pushes to one repository (8 distinct refs; one ref from 8 contenders); every push a client called landed is checked against the refs stock git reads back. Per-check outcomes are in the private run record.

Observed shape on Artifacts (probes run probes-20261114t1745-5jxl): HTTP 200 whose body is a single band-3 fatal (busy) and no report-status, for distinct refs as well as one ref; the refs read back show none of those pushes applied. Stock git reports it as the remote hanging up (exit 128).

Retry probe (run probes-20261114t1837-53b4): each push that did not land is sent again alone with the same zero old id, which the server would refuse had the first attempt been applied; per-check outcomes are in the private run record.

concurrency.two-transfer-runners

Two resumable transfers of one plan at once both finish with the planned head; each refused step is settled by reading refs.

Ops: src/transfer.ts runTransfer.

Tests:

  • test/transfer-outcomes.test.js: two runners on one plan at once, 20 times: both end done; the destination is the planned head

Evidence:

  • ply↔git: test/transfer-outcomes.test.js

No Artifacts evidence.

Tags (lightweight and annotated) (tags, 6)

idstatusevidenceply opstests
tags.lightweight-createverifiedply↔git, ply↔Artifacts, git↔Artifactspush, createTag2
tags.annotated-createverifiedply↔git, ply↔Artifacts, git↔Artifactspush, createTag2
tags.deleteverifiedply↔git, ply↔Artifacts, git↔Artifactspush, deleteTag2
tags.move-existing-tagverifiedply↔git, ply↔Artifacts, git↔Artifactspush1
tags.peel-chainverifiedply↔git, ply↔Artifacts, git↔ArtifactsreadFile, createBranch3
tags.many-tagsverifiedply↔git, ply↔Artifacts, git↔ArtifactslsRefs1
tags.lightweight-create

A lightweight tag is a ref create under refs/tags pointing at a commit.

Ops: src/push.ts push, src/refops.ts createTag.

Tests:

  • test/e2e-customer.test.js: createTag: lightweight and annotated (as git tag -a writes it), refusals
  • test/probes/probes.test.js: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository

Evidence:

  • ply↔git: test/e2e-customer.test.js
  • ply↔Artifacts: validate-7b0c310f: tag lightweight
  • ply↔git: test/probes/probes.test.js
  • ply↔Artifacts: probes-20261114t2226-yyjq: tags.lightweight-create#plain/art-ply
  • git↔Artifacts: probes-20261114t2226-yyjq: tags.lightweight-create#plain/art-git
tags.annotated-create

An annotated tag pushes a tag object with its ref, byte-equal to git tag -a.

Ops: src/push.ts push, src/refops.ts createTag.

Tests:

  • test/e2e-customer.test.js: createTag: lightweight and annotated (as git tag -a writes it), refusals
  • test/probes/probes.test.js: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository

Evidence:

  • ply↔git: test/e2e-customer.test.js
  • ply↔Artifacts: validate-7b0c310f: tag annotated
  • git↔Artifacts: validate-7b0c310f: git judge: fsck --strict, refs, history
  • ply↔git: test/probes/probes.test.js
  • ply↔Artifacts: probes-20261114t2226-yyjq: tags.annotated-create#plain/art-ply
  • git↔Artifacts: probes-20261114t2226-yyjq: tags.annotated-create#plain/art-git
tags.delete

A tag delete with the expected old id; a stale expected id is refused.

Ops: src/push.ts push, src/refops.ts deleteTag.

Tests:

  • test/e2e-customer.test.js: deleteTag
  • test/probes/probes.test.js: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository

Evidence:

  • ply↔git: test/e2e-customer.test.js
  • ply↔Artifacts: validate-7b0c310f: tag delete (CAS) + stale delete -> 409
  • git↔Artifacts: loadgen-compat-20261024: tag_push_delete/scratch/v2
  • ply↔git: test/probes/probes.test.js
  • ply↔Artifacts: probes-20261114t2226-yyjq: tags.delete#plain/art-ply
  • git↔Artifacts: probes-20261114t2226-yyjq: tags.delete#plain/art-git
  • ply↔Artifacts: probes-20261115t2113-phhp: tags.delete#annotated/art-ply
  • git↔Artifacts: probes-20261115t2113-phhp: tags.delete#annotated/art-git

The stale half of the validate check is refused by ply-web from ls-refs, not by Artifacts.

tags.move-existing-tag

An existing tag ref moved with its current old id (a non-fast-forward lightweight move, or one annotated tag replaced by another) is an ordinary ref update.

Ops: src/push.ts push.

Tests:

  • test/probes/probes.test.js: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository

Evidence:

  • ply↔git: test/probes/probes.test.js
  • ply↔Artifacts: probes-20261115t2113-phhp: tags.move-existing-tag#non-fast-forward/art-ply
  • git↔Artifacts: probes-20261115t2113-phhp: tags.move-existing-tag#non-fast-forward/art-git
  • ply↔Artifacts: probes-20261115t2113-phhp: tags.move-existing-tag#annotated-to-other-tag/art-ply
  • git↔Artifacts: probes-20261115t2113-phhp: tags.move-existing-tag#annotated-to-other-tag/art-git
tags.peel-chain

A ref given as an annotated tag (or a tag of a tag) is peeled to its commit for reads and branch creation.

Ops: src/read.ts readFile, src/refops.ts createBranch.

Tests:

  • test/e2e-customer.test.js: createBranch from a branch name, a short name, a peeled annotated tag
  • test/read.test.js: readFile bytes == git show <ref>:<path> for every blob path and every ref form
  • test/probes/probes.test.js: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository

Evidence:

  • ply↔git: test/read.test.js
  • ply↔Artifacts: validate-7b0c310f: read: tag name resolves (ref=v1)
  • ply↔git: test/probes/probes.test.js
  • ply↔Artifacts: probes-20261115t2113-phhp: tags.peel-chain#tag-of-tag/art-ply
  • git↔Artifacts: probes-20261115t2113-phhp: tags.peel-chain#tag-of-tag/art-git
tags.many-tags

A repository with many tags: listing, include-tag and fetch stay correct.

Ops: src/lsrefs.ts lsRefs.

Tests:

  • test/probes/wire.test.js: reference: ${plan.id} meets its answer with every sender

Evidence:

  • git↔Artifacts: loadgen-phase2-20261025: shape/manytags
  • ply↔git: test/probes/wire.test.js
  • ply↔Artifacts: wire-20261115t2116-1nam: refs.ls-refs-listing#two-thousand-refs/art-ply

ply lists a 500-tag repository (2001 refs) in the wire plans; include-tag and fetch across many tags are checked only with stock git.

Merges and rebases as ancestry exercisers (ancestry, 7)

idstatusevidenceply opstests
ancestry.merge-base-searchverifiedply↔git, ply↔ArtifactsmergeBase2
ancestry.merge-commit-pushverifiedply↔git, ply↔Artifacts, git↔Artifactspush, mergeBranch2
ancestry.fast-forward-and-up-to-dateverifiedply↔git, ply↔ArtifactsmergeBranch1
ancestry.rebase-chainverifiedply↔git, ply↔ArtifactsrebaseBranch1
ancestry.cherry-pick-revertverifiedply↔git, ply↔ArtifactscherryPick, revertCommit2
ancestry.log-walkverifiedply↔git, ply↔ArtifactsreadLog1
ancestry.cut-graphimplemented—mergeBase, mergeBranch1

Merge bases found by shallow windows over the server (deepen), equal to git merge-base --all within the cap.

Ops: src/merge.ts mergeBase.

Tests:

  • test/mergebase-space.test.js: merge-base outcome space: position × multiplicity × settled × server × op, every cell equal to git
  • test/space/merge-depth.test.js: merge-base cap: every relation × length × cap against git merge-base --all

Evidence:

  • ply↔git: test/mergebase-space.test.js
  • ply↔git: test/space/merge-depth.test.js
  • ply↔Artifacts: validate-7b0c310f: merge feat into main (true merge)
ancestry.merge-commit-push

A two-parent merge commit pushed as a fast-forward of the target; history visible to git as a merge.

Ops: src/push.ts push, src/merge.ts mergeBranch.

Tests:

  • test/merge.test.js: outcomes: up-to-date, fast-forward, ff-only refusal, no-ff merge commit, clean merge, conflict
  • test/probes/probes.test.js: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository

Evidence:

  • ply↔git: test/merge.test.js
  • ply↔Artifacts: validate-7b0c310f: merge feat into main (true merge)
  • ply↔Artifacts: loadgen-phase6-plyw-20261025: merge/true
  • ply↔Artifacts: loadgen-phase6-plyw-20261025: merge/verify
  • git↔Artifacts: loadgen-phase2-20261025: shape/merges
  • ply↔git: test/probes/probes.test.js
  • ply↔Artifacts: probes-20261114t2226-yyjq: ancestry.merge-commit-push#two-parents/art-ply
  • git↔Artifacts: probes-20261114t2226-yyjq: ancestry.merge-commit-push#two-parents/art-git
ancestry.fast-forward-and-up-to-date

Merging an ancestor is up to date (no push); merging a descendant fast-forwards the ref.

Ops: src/merge.ts mergeBranch.

Tests:

  • test/merge.test.js: outcomes: up-to-date, fast-forward, ff-only refusal, no-ff merge commit, clean merge, conflict

Evidence:

  • ply↔git: test/merge.test.js
  • ply↔Artifacts: validate-7b0c310f: merge again -> up_to_date
  • ply↔Artifacts: validate-7b0c310f: merge fast-forward (ff branch)
  • ply↔Artifacts: loadgen-phase6-plyw-20261025: merge/ff
ancestry.rebase-chain

A chain of commits replayed onto a moved base, pushed with the old tip as the expected id.

Ops: src/rebase.ts rebaseBranch.

Tests:

  • test/rebase.test.js: rebase: three commits onto a moved main

Evidence:

  • ply↔git: test/rebase.test.js
  • ply↔Artifacts: validate-7b0c310f: rebase topic onto main
ancestry.cherry-pick-revert

Cherry-pick and revert: one new commit whose tree equals git's; empty results stop or keep as git does.

Ops: src/rebase.ts cherryPick, src/rebase.ts revertCommit.

Tests:

  • test/rebase.test.js: cherry-pick and revert: trees equal git
  • test/pick-empty.test.js: cherry-pick --keep-redundant-commits and --allow-empty: commit bytes match git, stop writes nothing

Evidence:

  • ply↔git: test/rebase.test.js
  • ply↔Artifacts: validate-7b0c310f: cherry-pick f2 onto main
  • ply↔Artifacts: validate-7b0c310f: cherry-pick again -> empty noop
  • ply↔Artifacts: validate-7b0c310f: revert cherry-pick on main
ancestry.log-walk

First-parent history read in shallow windows equals git log --first-parent.

Ops: src/log.ts readLog.

Tests:

  • test/log.test.js: readLog: server × shape × limit × behaviour, every cell against git

Evidence:

  • ply↔git: test/log.test.js
  • ply↔Artifacts: loadgen-phase6-plyw-20261025: commit/deep

validate's log checks go through the viewer, which judges Artifacts history with git log, not readLog.

ancestry.cut-graph

A server that withholds ancestors without saying shallow: ply fails closed, nothing pushed.

Ops: src/merge.ts mergeBase, src/merge.ts mergeBranch.

Tests:

  • test/adversarial.test.js: #18 merge base over a cut graph: a server that withholds ancestors without a shallow line fails closed (pack_corrupt), nothing pushed

A proxy cuts the graph; no git or Artifacts server ever behaves this way on purpose.

Error conditions (auth, not found, limits, corrupt input) (errors, 7)

idstatusevidenceply opstests
errors.auth-missing-or-wrongverifiedply↔git, ply↔Artifacts, git↔Artifacts, wire↔ArtifactscreateTransport, lsRefs, push2
errors.receive-pack-forbiddenverifiedply↔git, ply↔Artifacts, git↔Artifactspush1
errors.repository-not-foundverifiedply↔ArtifactslsRefs, discover1
errors.http-status-classesverifiedply↔Artifacts, git↔Artifacts, wire↔ArtifactscreateTransport, fetchPack, push2
errors.err-pkt-lineverifiedply↔gitlsRefs, fetchPack3
errors.not-git-responseimplemented—createTransport2
errors.malformed-requests-to-serverunsupported (observed)wire↔Artifacts—0
errors.auth-missing-or-wrong

A missing or wrong credential is 401 and a typed auth error; nothing lands.

Ops: src/http.ts createTransport, src/lsrefs.ts lsRefs, src/push.ts push.

Tests:

  • test/custom-exchange.test.js: wrong credential: auth (401), typed, thrown from the iteration
  • test/adversarial.test.js: I6e the credential product: every source × user × password cell gets its stated header or typed refusal, equal to git where git has the input, and leaks nothing

Evidence:

  • ply↔git: test/adversarial.test.js
  • ply↔Artifacts: validate-7b0c310f: auth: wrong bearer -> 401
  • ply↔Artifacts: validate-7b0c310f: auth: revoked Git-Token (auto-minted) -> upstream 403 typed
  • ply↔Artifacts: loadgen-phase6-plyw-20261025: err/bad_git_token
  • wire↔Artifacts: loadgen-phase4-hostile-20261025: auth/missing
  • wire↔Artifacts: loadgen-phase4-hostile-20261025: auth/garbage_header
  • git↔Artifacts: loadgen-phase2-20261025: auth_paths

validate's 401 checks are ply-web's own bearer; only the revoked Git-Token check reaches Artifacts' auth through ply.

errors.receive-pack-forbidden

A read-only credential pushing: 403 on receive-pack (advertisement or POST) is auth, and no ref moves.

Ops: src/push.ts push.

Tests:

  • test/adversarial.test.js: receive-pack refused for this caller (403 on its POST and on its advertisement) is auth, and the ref did not move (#144)

Evidence:

  • ply↔git: test/adversarial.test.js
  • ply↔Artifacts: validate-7b0c310f: push rejected path (read-scoped token write)
  • git↔Artifacts: loadgen-phase2-20261025: read_only_token_push
errors.repository-not-found

A repository that does not exist: the advertisement answers 404, typed not_found.

Ops: src/lsrefs.ts lsRefs, src/discover.ts discover.

Tests:

  • test/adversarial.test.js: HTTP-level faults at every stage: statuses, non-git bodies, stall, drop, empty

Evidence:

  • ply↔Artifacts: loadgen-phase6-plyw-20261025: err/no_repo

The 404 class is tested only with injected statuses; git http-backend's own 404 for a missing repository is not cited by any test.

errors.http-status-classes

Statuses 4xx/5xx/429 at each stage map to ply's typed classes, and a refused optional feature is not retried for them.

Ops: src/http.ts createTransport, src/fetchpack.ts fetchPack, src/push.ts push.

Tests:

  • test/adversarial.test.js: HTTP-level faults at every stage: statuses, non-git bodies, stall, drop, empty
  • test/fetchobject-deepen-refusal.test.js: never asked again: 401, 403, 404, 429 and 500 stand as they are, with no advertisement read

Evidence:

  • ply↔Artifacts: wire-20261115t2038-ee4x: errors.http-status-classes#no-credential/art-ply
  • ply↔Artifacts: wire-20261115t2038-ee4x: errors.http-status-classes#bogus-token/art-ply
  • ply↔Artifacts: wire-20261115t2038-ee4x: errors.http-status-classes#revoked-token/art-ply
  • ply↔Artifacts: wire-20261115t2038-ee4x: errors.http-status-classes#missing-repo/art-ply
  • wire↔Artifacts: wire-20261115t2038-ee4x: errors.http-status-classes#no-credential/art-raw
  • wire↔Artifacts: wire-20261115t2038-ee4x: errors.http-status-classes#no-credential/art-curl
  • git↔Artifacts: wire-20261115t2038-ee4x: errors.http-status-classes#no-credential/art-git
  • wire↔Artifacts: wire-20261115t2038-ee4x: errors.http-status-classes#bogus-token/art-raw
  • wire↔Artifacts: wire-20261115t2038-ee4x: errors.http-status-classes#bogus-token/art-curl
  • git↔Artifacts: wire-20261115t2038-ee4x: errors.http-status-classes#bogus-token/art-git
  • wire↔Artifacts: wire-20261115t2038-ee4x: errors.http-status-classes#revoked-token/art-raw
  • wire↔Artifacts: wire-20261115t2038-ee4x: errors.http-status-classes#revoked-token/art-curl
  • git↔Artifacts: wire-20261115t2038-ee4x: errors.http-status-classes#revoked-token/art-git
  • wire↔Artifacts: wire-20261115t2038-ee4x: errors.http-status-classes#missing-repo/art-raw
  • wire↔Artifacts: wire-20261115t2038-ee4x: errors.http-status-classes#missing-repo/art-curl
  • git↔Artifacts: wire-20261115t2038-ee4x: errors.http-status-classes#missing-repo/art-git

The wire run checks the info/refs GET with no credential, an unminted token, a revoked token and a repository-scoped token on a path it does not cover, from ply, stock git, curl and a raw request. No recorded run checks what Artifacts sends under rate limiting or a 5xx.

errors.err-pkt-line

An ERR pkt-line anywhere in a response is a typed remote error carrying the scrubbed message.

Ops: src/lsrefs.ts lsRefs, src/fetchpack.ts fetchPack.

Tests:

  • test/mutant-kill-tree.test.js: ERR upload-pack: not our ref x
  • test/adversarial.test.js: I6b a credential echoed by the server reaches no error (any field) and no span: ERR, band 2/3, ng, hook output × 4 auth forms
  • test/err-pkt-git.test.js: real git ERR on a fetch of an id no one holds: the bytes carry ERR, ply says remote_error not_our_ref

Evidence:

  • ply↔git: test/err-pkt-git.test.js

Real ERR: git http-backend's ERR upload-pack: not our ref <id> on a fetch of an unknown id (captured as written; also probe fetch.want-unreachable-or-unknown#phantom), which ply reports as remote_error, reason not_our_ref. ERR at other stages (advertisement, ls-refs) is injected only.

errors.not-git-response

A 200 that is not git (HTML, wrong content type) is not_git, never parsed as protocol.

Ops: src/http.ts createTransport.

Tests:

  • test/custom-exchange.test.js: a server that is not git (HTML 200) is not_git
  • test/http-options.test.js: the advertisement: its GET asks redirect manual; a foreign content type is not_git
errors.malformed-requests-to-server

How the server answers malformed requests (bad pkt-line lengths, misplaced delimiters, unknown commands and capabilities).

Unsupported: ply only writes well-formed requests; it has no mode that sends malformed ones.

Observed:

  • wire↔Artifacts: loadgen-phase4-hostile-20261025: pkt/nonhex_length
  • wire↔Artifacts: loadgen-phase4-hostile-20261025: pkt/giant_length_claim
  • wire↔Artifacts: loadgen-phase4-hostile-20261025: pkt/missing_flush
  • wire↔Artifacts: loadgen-phase4-hostile-20261025: proto/v2_unknown_command
  • wire↔Artifacts: loadgen-phase4-hostile-20261025: proto/unknown_capability
  • wire↔Artifacts: wire-20261115t2038-ee4x: errors.malformed-requests-to-server#nonhex-length/art-raw
  • wire↔Artifacts: wire-20261115t2038-ee4x: errors.malformed-requests-to-server#nonhex-length/art-curl
  • wire↔Artifacts: wire-20261115t2038-ee4x: errors.malformed-requests-to-server#oversized-length/art-raw
  • wire↔Artifacts: wire-20261115t2038-ee4x: errors.malformed-requests-to-server#oversized-length/art-curl
  • wire↔Artifacts: wire-20261115t2038-ee4x: errors.malformed-requests-to-server#missing-flush/art-raw
  • wire↔Artifacts: wire-20261115t2038-ee4x: errors.malformed-requests-to-server#missing-flush/art-curl
  • wire↔Artifacts: wire-20261115t2038-ee4x: errors.malformed-requests-to-server#unknown-command/art-raw
  • wire↔Artifacts: wire-20261115t2038-ee4x: errors.malformed-requests-to-server#unknown-command/art-curl
  • wire↔Artifacts: wire-20261115t2038-ee4x: errors.malformed-requests-to-server#wrong-content-type/art-raw
  • wire↔Artifacts: wire-20261115t2038-ee4x: errors.malformed-requests-to-server#wrong-content-type/art-curl
  • wire↔Artifacts: wire-20261115t2038-ee4x: errors.malformed-requests-to-server#bad-service/art-raw
  • wire↔Artifacts: wire-20261115t2038-ee4x: errors.malformed-requests-to-server#bad-service/art-curl

Interrupted operations (interrupted, 6)

idstatusevidenceply opstests
interrupted.push-response-lostverifiedply↔git, ply↔Artifacts, git↔Artifactspush, runTransfer, editFile3
interrupted.push-body-cutverifiedply↔git, ply↔Artifacts, git↔Artifacts, wire↔Artifactspush, pushPack3
interrupted.fetch-dropped-mid-responseverifiedply↔git, ply↔Artifacts, git↔ArtifactsfetchPack, readFile3
interrupted.stall-timeoutsverifiedply↔git, ply↔Artifacts, git↔ArtifactsexchangeClock, createTransport3
interrupted.abort-during-pushverifiedply↔gitpush, pushPack, runTransfer2
interrupted.resumable-transferverifiedply↔gitrunTransfer1
interrupted.push-response-lost

The server applies a push but the response is lost: ply reports ambiguous, the refs show the push, a retry is safe.

Ops: src/push.ts push, src/transfer.ts runTransfer, src/edit.ts editFile.

Tests:

  • test/adversarial.test.js: ambiguous push (response lost after server applied it): ref == our commit; a naive retry is match_count, content correct
  • test/transfer-outcomes.test.js: a push applied whose response is dropped: the refs show it, the run goes on to done
  • test/probes/probes.test.js: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository

Evidence:

  • ply↔git: test/adversarial.test.js
  • ply↔git: test/transfer-outcomes.test.js
  • ply↔git: test/probes/probes.test.js
  • ply↔Artifacts: probes-20261114t2226-yyjq: interrupted.push-response-lost#cut/art-ply
  • git↔Artifacts: probes-20261114t2226-yyjq: interrupted.push-response-lost#cut/art-git

Probe: the recording proxy reads the server's whole answer, then cuts the connection. Stock git (libcurl) re-sends a POST whose reused connection closed with no answer; on git http-backend the replay is refused by compare-and-swap and git then finds the ref up to date (src/probe-scenarios.ts).

interrupted.push-body-cut

A push request body that fails midway: nothing lands; failure before the first body pull is definite, after it ambiguous.

Ops: src/push.ts push, src/receivecaps.ts pushPack.

Tests:

  • test/custom-exchange.test.js: a body stream that errors midway: a typed error from the iteration, the span records it, nothing lands
  • test/push-pack-preabort.test.js: push with a pack sent as bytes: a signal already fired is the definite aborted with no request; a rejected fetch stays ambiguous
  • test/probes/probes.test.js: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository

Evidence:

  • ply↔git: test/custom-exchange.test.js
  • wire↔Artifacts: loadgen-phase4-hostile-20261025: http/partial_send_once
  • wire↔Artifacts: loadgen-phase4-hostile-20261025: http/cl_larger_than_body
  • ply↔git: test/probes/probes.test.js
  • ply↔Artifacts: probes-20261114t2226-yyjq: interrupted.push-body-cut#half/art-ply
  • git↔Artifacts: probes-20261114t2226-yyjq: interrupted.push-body-cut#half/art-git
interrupted.fetch-dropped-mid-response

A fetch or advertisement response dropped or cut mid-body is a typed network error or pack_corrupt, never a partial result.

Ops: src/fetchpack.ts fetchPack, src/read.ts readFile.

Tests:

  • test/adversarial.test.js: HTTP-level faults at every stage: statuses, non-git bodies, stall, drop, empty
  • test/http-options.test.js: a body that fails mid-read is the network error it is
  • test/probes/probes.test.js: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository

Evidence:

  • ply↔git: test/space/pack-cut.test.js
  • ply↔git: test/probes/probes.test.js
  • ply↔Artifacts: probes-20261114t2226-yyjq: interrupted.fetch-dropped-mid-response#half/art-ply
  • git↔Artifacts: probes-20261114t2226-yyjq: interrupted.fetch-dropped-mid-response#half/art-git

The probe proxy drops an upload-pack response halfway, against the reference and Artifacts.

interrupted.stall-timeouts

A server that stalls before the first byte or mid-body is ended by the first-byte or idle timer, typed timeout.

Ops: src/deadline.ts exchangeClock, src/http.ts createTransport.

Tests:

  • test/http-options.test.js: the transport reads the parsed timeout: the span carries it and a stalled request ends at it
  • test/workerd.test.js: workerd: first-byte and idle timeouts; a long steady body or upload is not cut
  • test/probes/probes.test.js: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository

Evidence:

  • ply↔git: test/probes/probes.test.js
  • ply↔Artifacts: probes-20261114t2226-yyjq: interrupted.stall-timeouts#push-request-stall/art-ply
  • git↔Artifacts: probes-20261114t2226-yyjq: interrupted.stall-timeouts#push-request-stall/art-git
  • ply↔Artifacts: probes-20261114t2226-yyjq: interrupted.stall-timeouts#push-request-stall-10s/art-ply
  • git↔Artifacts: probes-20261114t2226-yyjq: interrupted.stall-timeouts#push-request-stall-10s/art-git
  • ply↔Artifacts: probes-20261114t2226-yyjq: interrupted.stall-timeouts#push-response-stall/art-ply
  • git↔Artifacts: probes-20261114t2226-yyjq: interrupted.stall-timeouts#push-response-stall/art-git
  • ply↔Artifacts: probes-20261114t2226-yyjq: interrupted.stall-timeouts#fetch-request-stall/art-ply
  • git↔Artifacts: probes-20261114t2226-yyjq: interrupted.stall-timeouts#fetch-request-stall/art-git
  • ply↔Artifacts: probes-20261114t2226-yyjq: interrupted.stall-timeouts#fetch-response-stall/art-ply
  • git↔Artifacts: probes-20261114t2226-yyjq: interrupted.stall-timeouts#fetch-response-stall/art-git

The probe proxy injects the stalls: request-body stalls of 10 s and 20 s and a response stall against a 1 s client timeout, on push and fetch; each check's outcome is kept in the private run record.

interrupted.abort-during-push

An external AbortSignal during a push: aborted if the body was never pulled, ambiguous once sent; git decides what landed.

Ops: src/push.ts push, src/receivecaps.ts pushPack, src/transfer.ts runTransfer.

Tests:

  • test/adversarial.test.js: external AbortSignal mid-stream
  • test/transfer-outcomes.test.js: a real AbortSignal fired during the final push: ambiguous once sent, aborted when the body was never pulled; git decides what landed

Evidence:

  • ply↔git: test/transfer-outcomes.test.js

No Artifacts evidence.

interrupted.resumable-transfer

A multi-step transfer paused or interrupted is resumed from refs, not from local state, and ends at the planned head.

Ops: src/transfer.ts runTransfer.

Tests:

  • test/transfer-outcomes.test.js: maxSteps: a push that gets no answer and does not land is ambiguous, never paused; a pause names its last push

Evidence:

  • ply↔git: test/transfer-outcomes.test.js

No Artifacts evidence.

HTTP transport (smart HTTP, sideband, keepalive, large bodies) (http, 10)

idstatusevidenceply opstests
http.smart-http-discoveryverifiedply↔git, ply↔Artifacts, git↔ArtifactscreateTransport, discover1
http.redirectsverifiedply↔gitredirectPolicy, createTransport2
http.credential-formsverifiedply↔git, wire↔ArtifactscreateTransport1
http.chunked-request-bodyverifiedply↔git, wire↔Artifactspush, pushPack1
http.large-response-bodyverifiedply↔git, ply↔Artifacts, git↔ArtifactsreadFile, fetchPack1
http.large-request-bodyverifiedply↔git, git↔ArtifactseditFile, push2
http.sideband-keepaliveverifiedply↔gitpush2
http.request-content-encodingunsupported (observed)wire↔Artifacts—0
http.content-length-framingunsupported (observed)git↔Artifacts, wire↔Artifacts—0
http.expect-continue-and-dumb-httpunsupported (observed)git↔Artifacts, wire↔Artifacts—0
http.smart-http-discovery

GET info/refs?service=… then POST to the service, with Git-Protocol: version=2 on upload-pack only.

Ops: src/http.ts createTransport, src/discover.ts discover.

Tests:

  • test/http-options.test.js: Git-Protocol: version=2 goes on upload-pack GET and POST, and on neither receive-pack request

Evidence:

  • ply↔git: test/space/advertisement.test.js
  • ply↔Artifacts: validate-7b0c310f: discover
  • ply↔Artifacts: loadgen-phase6-plyw-20261025: discover/small
  • git↔Artifacts: loadgen-phase2-20261025: http_version/HTTP/1.1
  • git↔Artifacts: loadgen-phase2-20261025: http_version/HTTP/2
http.redirects

A 3xx on the advertisement is followed as git follows it (within policy); a 3xx on a POST is never followed.

Ops: src/http.ts redirectPolicy, src/http.ts createTransport.

Tests:

  • test/redirect.test.js: git oracle: origin × auth × follow × kind
  • test/adversarial.test.js: I6c a 3xx is never followed: cross-origin on the GET and the POST

Evidence:

  • ply↔git: test/redirect.test.js

No Artifacts evidence: Artifacts has not been seen to redirect.

http.credential-forms

Bearer, Basic and URL-userinfo credentials produce the Authorization header git sends for the same input.

Ops: src/http.ts createTransport.

Tests:

  • test/adversarial.test.js: I6d URL userinfo authenticates fetch and push with the Authorization git sends for the same URL, byte for byte

Evidence:

  • ply↔git: test/adversarial.test.js
  • wire↔Artifacts: loadgen-phase4-hostile-20261025: auth/basic_empty
  • wire↔Artifacts: loadgen-phase4-hostile-20261025: auth/malformed_scheme
http.chunked-request-body

A large push body streamed with chunked transfer-encoding (duplex half).

Ops: src/push.ts push, src/receivecaps.ts pushPack.

Tests:

  • test/push-stream.test.js: a pack past INFLATE_CHUNK is streamed: duplex half, redirect error, chunked; git takes it

Evidence:

  • ply↔git: test/push-stream.test.js
  • wire↔Artifacts: loadgen-phase2-20261025: chunked_push/artifacts

ply's own streamed push to Artifacts is exercised by validate big20m only on the read side.

http.large-response-body

A large upload-pack response is streamed under the pack caps.

Ops: src/read.ts readFile, src/fetchpack.ts fetchPack.

Tests:

  • test/adversarial.test.js: I4 maxPackBytes bounds the streamed body on every path: limit_exceeded within one frame of the cap, not timeout

Evidence:

  • ply↔git: test/adversarial.test.js
  • ply↔Artifacts: validate-7b0c310f: big20m: first + warm n=25
  • ply↔Artifacts: loadgen-phase6-plyw-20261025: read/big
  • git↔Artifacts: loadgen-compat-20261024: clone_full/big/v2
http.large-request-body

A large push request body (tens of MiB) reaches the server whole.

Ops: src/edit.ts editFile, src/push.ts push.

Tests:

  • test/push-stream.test.js: memory: a 32 MiB streamed push holds well under one copy of the object (live arrayBuffers, gc-sampled)
  • test/workerd.test.js: workerd: edit small file, 24 MB file, cache hit on second edit; git-verified

Evidence:

  • ply↔git: test/push-stream.test.js
  • git↔Artifacts: loadgen-compat-20261024: large_blob_push_24m/scratch/v2

No ply push over a few MiB to Artifacts is recorded.

http.sideband-keepalive

Empty band-1 keepalives while a hook runs do not end the push read.

Ops: src/push.ts push.

Tests:

  • test/push-report-bound.test.js: 13,000 band-1 keepalives while a hook runs, then the report: landed
  • test/push-keepalive-git.test.js: real git keepalives while a pre-receive hook runs: band-1 empty packets, then the report; ply lands

Evidence:

  • ply↔git: test/push-keepalive-git.test.js

git http-backend with receive.keepAlive=1 and a 3 s silent pre-receive hook writes empty band-1 packets before the report; the test captures them. Whether Artifacts sends keepalives is unrecorded (it runs no hooks a client can arrange).

http.request-content-encoding

A gzip-encoded request body.

Unsupported: ply never compresses a request body.

Observed:

  • wire↔Artifacts: loadgen-phase2-20261025: gzip_request_body
  • wire↔Artifacts: loadgen-phase4-hostile-20261025: http/corrupt_gzip
  • wire↔Artifacts: wire-20261115t2038-ee4x: http.request-content-encoding#gzip-ls-refs/art-raw
  • wire↔Artifacts: wire-20261115t2038-ee4x: http.request-content-encoding#gzip-ls-refs/art-curl
  • wire↔Artifacts: wire-20261115t2038-ee4x: http.request-content-encoding#gzip-receive-pack/art-raw
  • wire↔Artifacts: wire-20261115t2038-ee4x: http.request-content-encoding#gzip-receive-pack/art-curl
  • wire↔Artifacts: wire-20261115t2038-ee4x: http.request-content-encoding#corrupt-gzip/art-raw
  • wire↔Artifacts: wire-20261115t2038-ee4x: http.request-content-encoding#corrupt-gzip/art-curl
http.content-length-framing

A request whose Content-Length disagrees with its body.

Unsupported: ply's fetch sets the length from the body; it cannot misframe one.

Observed:

  • wire↔Artifacts: loadgen-phase4-hostile-20261025: http/cl_smaller_than_body
  • wire↔Artifacts: loadgen-phase4-hostile-20261025: http/cl_larger_than_body
  • wire↔Artifacts: wire-20261115t2038-ee4x: http.content-length-framing#chunked-receive-pack/art-raw
  • wire↔Artifacts: wire-20261115t2038-ee4x: http.content-length-framing#chunked-receive-pack/art-curl
  • git↔Artifacts: wire-20261115t2038-ee4x: http.content-length-framing#chunked-receive-pack/art-git
  • wire↔Artifacts: wire-20261115t2038-ee4x: http.content-length-framing#length-short/art-raw
  • wire↔Artifacts: wire-20261115t2038-ee4x: http.content-length-framing#length-long/art-raw
http.expect-continue-and-dumb-http

Expect: 100-continue, and the dumb HTTP protocol.

Unsupported: ply speaks only smart HTTP and never sends Expect.

Observed:

  • wire↔Artifacts: loadgen-phase2-20261025: expect_100_continue
  • wire↔Artifacts: loadgen-phase2-20261025: dumb_http
  • wire↔Artifacts: wire-20261115t2038-ee4x: http.expect-continue-and-dumb-http#expect-100-receive-pack/art-raw
  • wire↔Artifacts: wire-20261115t2038-ee4x: http.expect-continue-and-dumb-http#expect-100-receive-pack/art-curl
  • wire↔Artifacts: wire-20261115t2116-1nam: http.expect-continue-and-dumb-http#dumb-info-refs/art-raw
  • git↔Artifacts: wire-20261115t2116-1nam: http.expect-continue-and-dumb-http#dumb-info-refs/art-git
  • wire↔Artifacts: wire-20261115t2116-1nam: http.expect-continue-and-dumb-http#dumb-head/art-raw
  • wire↔Artifacts: wire-20261115t2116-1nam: http.expect-continue-and-dumb-http#dumb-objects-info-packs/art-raw

Recorded runs

rundatekindschecksharness
validate-7b0c310f2026-11-12ply↔Artifacts, git↔Artifacts62ply-cd validate.mjs: ply f47bb75 inside ply-web (prod version 7b0c310f) against Artifacts; stock git clones the repository and judges (fsck --strict, ls-remote, rev-parse).
loadgen-compat-202610242026-10-24git↔Artifacts49ply-artifacts-loadgen compat: stock git 2.47 clients against Artifacts and against a local git http-backend baseline on identical fixtures; file:// upload-pack is the oracle.
loadgen-phase2-202610252026-10-25git↔Artifacts, wire↔Artifacts74ply-artifacts-loadgen phase 2 probes: stock git and alternate clients against Artifacts, raw advertisement and HTTP requests, each beside a git http-backend baseline.
loadgen-phase3-202610252026-10-25git↔Artifacts55ply-artifacts-loadgen phase 3: wants of reachable non-tip, unreachable and fake object ids by stock git (v0, v1, v2), alternate clients, push ceilings; git http-backend baseline.
loadgen-phase4-hostile-202610252026-10-25wire↔Artifacts58ply-artifacts-loadgen phase 4: hand-built malformed pkt-lines, wants, packs, ref names, HTTP framing and auth headers sent to Artifacts upload-pack and receive-pack beside a git http-backend baseline (namespace ply-loadgen, modest rate).
loadgen-phase4-hostile-write-202610252026-10-25wire↔Artifacts23ply-artifacts-loadgen phase 4, write side: malformed packs and ref names pushed to Artifacts receive-pack with a write token, beside a git http-backend baseline.
loadgen-phase5-delta-202610252026-10-25git↔Artifacts, wire↔Artifacts21ply-artifacts-loadgen phase 5: delta capabilities, hand-built OFS/REF/thin packs pushed to Artifacts, clones read back with stock git and git verify-pack.
loadgen-phase6-plyw-202610252026-10-25ply↔Artifacts39ply-artifacts-loadgen phase 6: the deployed ply Worker (ply-web) against Artifacts: reads, edits, CAS, races, merges, errors; stock git judges.
probes-20261114t1745-5jxl2026-11-14ply↔Artifacts, git↔Artifacts42ply differential probes (scripts/probes.mjs --artifacts; plans in test/probes/scenarios.ts, probe code d18a262915bc7c56): each scenario seeded with identical objects into a fresh Artifacts repository per client (namespace ply-loadgen) and into git http-backend with Artifacts' known policy; ply and stock git 2.47.3 run the same plan; a recording proxy injects the fault (held receive-pack while another writer moves refs, or a cut answer) and keeps the cf-ray of every request; stock git judges (ls-remote --symref, mirror clone, fsck --strict, rev-list --parents, merge-base); test/probes/evaluate.ts compares.
probes-20261114t1837-53b42026-11-14ply↔Artifacts, git↔Artifacts10ply differential probes, days 5-6 batch A (scripts/probes.mjs --artifacts, probe code b55fa846fcd21188 on ply 06042f8): race shapes (delete against an update, create against a create, delete against an update at once), a create of a ref that exists, and a retry of every push that did not land under contention; same harness as probes-20261114t1745-5jxl, with the proxy also keeping the commands of each receive-pack request and the refs of each advertisement; stock git 2.47.3.
probes-20261114t1909-sl8l2026-11-14ply↔Artifacts, git↔Artifacts30ply differential probes, days 5-6 batches B and C (scripts/probes.mjs --artifacts, probe code 7c155a159f2bda27 on ply 55205ae; since then one scenario comment reworded and, after ply c22b066, the stock git expectation dropped from the two response-stall scenarios because git's low-speed timer differs by build): hand-built packs sent through pushPack (a thin pack against a base the server has and one whose base it lacks, a commit naming a missing blob, a delta copying past its base, a bad trailer, bad zlib, a truncated pack), pushes from a shallow clone and from a blob:none partial clone, a push body cut halfway, request and response stalls on push and fetch against set client timeouts, and an upload-pack response dropped halfway; same harness as probes-20261114t1837-53b4, with the proxy also injecting request-side faults and recording the socket error of a failed upstream call; stock git git version 2.47.3.
probes-20261114t2226-yyjq2026-11-14ply↔Artifacts, git↔Artifacts81ply differential probes, full matrix (t229u days 9-10; scripts/probes.mjs --artifacts, probe code 744e85097786a1b0 on ply a78ed24 plus the two harness fixes committed with this entry: the run's signal handler also closes a repository still being created, and a stock git update carries its lease without a forced refspec): every scenario in src/probe-scenarios.ts, ply and stock git 2.47.3 (node 24.22.1), each against git http-backend with Artifacts' known policy and against a fresh Artifacts repository per scenario and client (namespace ply-loadgen, one at a time); same recording proxy and stock git judge as probes-20261114t1909-sl8l; cf-ray kept for every Artifacts request; every token revoked and probed, every repository deleted and checked by listing.
probes-20261115t1926-gfhc2026-11-15ply↔Artifacts, git↔Artifacts31ply differential probes, malformed packs and objects (scripts/probes.mjs --artifacts --only the 21 scenarios added in 24cafa1, probe code ca2eec66b288b4b2 on ply b9b33db): ply and, where it can send the input, stock git 2.47.3 (node 24.22.1), each against git http-backend with Artifacts' known policy and against a fresh Artifacts repository per scenario and client (namespace ply-loadgen, one at a time); same recording proxy and stock git judge as probes-20261114t2226-yyjq; cf-ray kept for every Artifacts request; every token revoked and probed, every repository deleted and checked by listing.
wire-20261115t2038-ee4x2026-11-15wire↔Artifacts, git↔Artifacts, ply↔Artifacts50ply HTTP-framing and malformed-request wire probes (scripts/wire-probes.mjs --artifacts, the 20 plans of test/probes/wire-plans.ts, probe code 19288b51af72a83f on ply 96b7a7d): each request sent directly to the target, without a proxy, from a raw socket (node net/tls, exact framing), curl 8.14.1, stock git 2.47.3 and ply where each can express it, against git http-backend with Artifacts' known policy and against a fresh Artifacts repository per plan (namespace ply-loadgen, one at a time, seeded and judged through the recording proxy's side and judge channels); credentials only from 0600 files (curl -H @file, git include.path); cf-ray kept for every Artifacts answer; every token revoked and probed, every repository deleted and checked by listing.
probes-20261115t2113-phhp2026-11-15ply↔Artifacts, git↔Artifacts12ply differential probes, ref and tag-object semantics (scripts/probes.mjs --artifacts --only the 10 scenarios of REF_SEMANTICS, probe code b726c69c5eaa6ecd on ply d5db942 plus the phase-4 harness): ply and, where it can send the push, stock git 2.47.3 (node 24.22.1), each against git http-backend with Artifacts' known policy and against a fresh Artifacts repository per scenario and client (namespace ply-loadgen, one at a time); same recording proxy and stock git judge as probes-20261114t2226-yyjq; cf-ray kept for every Artifacts request; every token revoked and probed, every repository deleted and checked by listing. The three directory/file scenarios stopped at the judge in this run and are recorded by probes-20261115t2126-d4jn.
probes-20261115t2126-d4jn2026-11-15ply↔Artifacts, git↔Artifacts6The three refs.directory-file-conflict scenarios again (probe code 5d7f4447288f58df), with the judge recording a repository stock git cannot mirror as such (its refs as listed, the clone's refusal as its fsck problem) instead of stopping; otherwise as probes-20261115t2113-phhp.
wire-20261115t2116-1nam2026-11-15wire↔Artifacts, git↔Artifacts, ply↔Artifacts75ply wire probes, ref names, unknown capabilities, dumb HTTP and a 2001-ref listing (scripts/wire-probes.mjs --artifacts, the 29 phase-4 plans of test/probes/wire-plans.ts, probe code e5af73ceefc0d6a8 on ply d5db942 plus the phase-4 harness): each request sent directly to the target from a raw socket, curl 8.14.1 where listed, stock git 2.47.3 and ply where each can express it, against git http-backend with Artifacts' known policy and a fresh Artifacts repository per plan (namespace ply-loadgen, one at a time); a sender that refuses a request itself is recorded as such and never reaches the server; credentials only from 0600 files; cf-ray kept for every Artifacts answer; every token revoked and probed, every repository deleted and checked by listing.
probes-20261115t2133-txqj2026-11-15ply↔Artifacts, git↔Artifacts8The three refs.directory-file-conflict scenarios and refs.symref-head#delete-default-branch again (probe code 60d752563bc119fa), with the recording proxy also keeping each receive-pack answer's per-command report (its unpack, ok and ng lines); otherwise as probes-20261115t2126-d4jn.
1# Git behaviour coverage
3<!-- generated by scripts/coverage-matrix.mjs --md from test/behaviours/matrix.ts and test/behaviours/runs.ts; test/behaviours/matrix.test.js fails if it drifts -->
5ply is a Git protocol conformance and behaviour-testing instrument for Cloudflare Artifacts as well as a client. This matrix counts **server behaviours**, not git commands: each row is a behaviour or failure mode of a Git server, the ply operations and tests that exercise it, and who has independently checked the server's answer.
7- **unsupported**: ply has no operation that exercises it. Stock git or hand-built wire probes may still have observed Artifacts.
8- **implemented**: ply exercises it, but only against fakes or its own expectations; nothing independent has judged the server.
9- **verified**: at least one independent check. The types make a verified row without evidence impossible.
11Evidence kinds:
13- `ply_vs_reference_git` (ply↔git): ply against git http-backend in this suite, with git's own output as the expected value; the cited file runs real git.
14- `ply_vs_artifacts` (ply↔Artifacts): ply against Artifacts in a recorded run.
15- `native_git_vs_artifacts` (git↔Artifacts): stock git against Artifacts in a recorded run, with git http-backend beside it as the baseline.
16- `wire_probe_vs_artifacts` (wire↔Artifacts): hand-built requests (pkt-lines, packs, HTTP framing) against Artifacts beside the same baseline. Neither ply nor stock git sends these bytes.
18Only Artifacts evidence says anything about Artifacts; reference evidence says ply's probe is right. Recorded runs are private (their harnesses hold credentials): `test/behaviours/runs.ts` keeps each run's id, date and check names, never its verdicts.
20## Summary
22**118** behaviours: **106** verified, **2** implemented, **10** unsupported. Of the verified, **84** carry some Artifacts evidence and **65** carry evidence of ply itself against Artifacts.
24| area | behaviours | verified | implemented | unsupported |
25|---|---:|---:|---:|---:|
26| refs | 9 | 8 | 0 | 1 |
27| caps | 9 | 6 | 0 | 3 |
28| fetch | 20 | 19 | 0 | 1 |
29| pack | 18 | 18 | 0 | 0 |
30| push | 19 | 18 | 0 | 1 |
31| concurrency | 7 | 7 | 0 | 0 |
32| tags | 6 | 6 | 0 | 0 |
33| ancestry | 7 | 6 | 1 | 0 |
34| errors | 7 | 5 | 1 | 1 |
35| interrupted | 6 | 6 | 0 | 0 |
36| http | 10 | 7 | 0 | 3 |
37| **all** | **118** | **106** | **2** | **10** |
39Verified behaviours by evidence kind (a behaviour counts once under each kind it has):
41| evidence kind | verified behaviours |
42|---|---:|
43| `ply_vs_reference_git` | 103 |
44| `ply_vs_artifacts` | 65 |
45| `native_git_vs_artifacts` | 58 |
46| `wire_probe_vs_artifacts` | 21 |
48## Gaps
50Each behaviour that is not verified by both ply↔git and ply↔Artifacts, filed under the first of these classes that holds:
52### Exercised by ply, judged by nothing independent (2)
54- `ancestry.cut-graph`: A server that withholds ancestors without saying shallow: ply fails closed, nothing pushed.
55- `errors.not-git-response`: A 200 that is not git (HTML, wrong content type) is not_git, never parsed as protocol.
57### Verified against git http-backend only: no evidence of any kind from Artifacts (22)
59- `refs.advertisement-shapes`: Unusual but legal listings (duplicate names, ordering, raw bytes in names) are read as git reads them.
60- `caps.required-capabilities`: A server missing a capability ply needs (ls-refs, fetch) is refused as unsupported before any operation.
61- `caps.object-format`: object-format=sha1 is accepted; any other object format is refused as unsupported.
62- `caps.filter-not-advertised`: A server whose fetch= line lists no `filter` (stock http-backend) gets no filter argument after one probe.
63- `fetch.acknowledgments-ready-packfile`: v2 response sections in order (acknowledgments, ready, shallow-info, packfile); a server that breaks the order is a protocol error, as it is for git.
64- `fetch.filter-combine`: filter combine:blob:none+tree:&lt;k> (a commit and the first levels of its path in one request).
65- `fetch.sideband-bands`: Side-band in the packfile section: band 1 data, band 2 progress, band 3 fatal error.
66- `pack.ofs-delta-resolve`: A served pack with OFS_DELTA chains resolves to the objects git verify-pack lists.
67- `pack.thin-ref-base`: A thin REF base supplied from outside the pack is checked against its claimed id before a delta applies.
68- `pack.truncated-served-pack`: A served pack cut at any byte is refused, typed, on every read path, where git index-pack refuses it.
69- `pack.corrupt-served-pack`: A served pack with a corrupt header field, zlib member, delta or checksum is refused exactly where git index-pack --strict refuses it.
70- `pack.served-pack-limits`: Hostile sizes in a served pack (object size, delta result, chain depth, inflated total) are refused before allocation.
71- `pack.push-duplicate-object`: A pushed pack never names one object twice (a strict receiver refuses it).
72- `push.report-status-v2`: report-status-v2: option lines after ok.
73- `push.sideband-hook-output`: side-band-64k on receive-pack: the report on band 1, hook output on band 2.
74- `push.hook-rejection`: A pre-receive or update hook that declines: ng with the hook's reason, ref unchanged.
75- `concurrency.two-transfer-runners`: Two resumable transfers of one plan at once both finish with the planned head; each refused step is settled by reading refs.
76- `errors.err-pkt-line`: An ERR pkt-line anywhere in a response is a typed remote error carrying the scrubbed message.
77- `interrupted.abort-during-push`: An external AbortSignal during a push: aborted if the body was never pulled, ambiguous once sent; git decides what landed.
78- `interrupted.resumable-transfer`: A multi-step transfer paused or interrupted is resumed from refs, not from local state, and ends at the planned head.
79- `http.redirects`: A 3xx on the advertisement is followed as git follows it (within policy); a 3xx on a POST is never followed.
80- `http.sideband-keepalive`: Empty band-1 keepalives while a hook runs do not end the push read.
82### Artifacts observed by stock git or wire probes, never by ply (19)
84- `caps.fetch-argument-gating`: ply sends a fetch argument (filter, shallow, include-tag, thin-pack, ofs-delta) only when the advertisement allows it, as git fetch does.
85- `caps.receive-pack-capabilities`: receive-pack capabilities (report-status, report-status-v2, side-band-64k, atomic, push-options, delete-refs, ofs-delta, object-format) are read and checked before the POST.
86- `fetch.want-tip-full-pack`: want of a tip with done and no filter: the pack holds exactly what pack-objects sends.
87- `fetch.want-have-line-syntax`: want/have/shallow lines: upload-pack's verdict on each class of id, and ply refusing non-ids before the wire.
88- `fetch.have-negotiation`: Multi-round have/ACK negotiation, then done: the server stops at common commits and sends only what is missing.
89- `fetch.filter-tree-depth`: filter tree:&lt;depth> (tree:0 commit only, tree:1, tree:2).
90- `fetch.filter-blob-limit`: filter blob:limit=&lt;n>.
91- `fetch.deepen-depth`: deepen &lt;n>: a shallow pack cut n commits below each want, with shallow-info naming the boundary.
92- `fetch.deepen-since`: deepen-since &lt;time>.
93- `fetch.deepen-not`: deepen-not &lt;ref>.
94- `fetch.deepen-relative-unshallow`: Fetch after a shallow clone: deepen-relative, a deeper depth, and unshallow, from the client's shallow list.
95- `fetch.include-tag`: include-tag: annotated tags that point into the pack are sent with it.
96- `fetch.thin-pack`: thin-pack with haves: deltas against objects the client has, resolved against external bases.
97- `fetch.ofs-delta-requested`: ofs-delta: OFS_DELTA entries only when asked for.
98- `pack.push-ofs-delta-accepted`: receive-pack accepts a pushed pack with OFS_DELTA entries when it advertises ofs-delta.
99- `push.push-options`: push-options: sent only when advertised; they reach the hook.
100- `http.credential-forms`: Bearer, Basic and URL-userinfo credentials produce the Authorization header git sends for the same input.
101- `http.chunked-request-body`: A large push body streamed with chunked transfer-encoding (duplex half).
102- `http.large-request-body`: A large push request body (tens of MiB) reaches the server whole.
104### Verified on Artifacts, but ply's probe is not checked against git http-backend (3)
106- `concurrency.read-after-write`: A landed push is visible at once to ls-refs and to fetch (no stale advertisement after a push).
107- `errors.repository-not-found`: A repository that does not exist: the advertisement answers 404, typed not_found.
108- `errors.http-status-classes`: Statuses 4xx/5xx/429 at each stage map to ply's typed classes, and a refused optional feature is not retried for them.
110### Not exercisable by ply (10)
112- `refs.v0-upload-pack-advertisement`: The v0/v1 upload-pack advertisement (refs and capabilities on the info/refs GET, no Git-Protocol header).
113- `caps.server-option`: v2 `server-option` arguments on ls-refs and fetch.
114- `caps.wait-for-done-packfile-uris-sideband-all`: v2 fetch features wait-for-done, packfile-uris and sideband-all.
115- `caps.object-info`: The v2 `object-info` command (object sizes without a pack).
116- `fetch.filter-sparse-oid`: filter sparse:oid=&lt;blob>.
117- `push.signed-push`: push-cert (signed pushes).
118- `errors.malformed-requests-to-server`: How the server answers malformed requests (bad pkt-line lengths, misplaced delimiters, unknown commands and capabilities).
119- `http.request-content-encoding`: A gzip-encoded request body.
120- `http.content-length-framing`: A request whose Content-Length disagrees with its body.
121- `http.expect-continue-and-dumb-http`: Expect: 100-continue, and the dumb HTTP protocol.
123## Behaviours
125### Ref advertisement and ls-refs (`refs`, 9)
127| id | status | evidence | ply ops | tests |
128|---|---|---|---|---:|
129| `refs.ls-refs-listing` | verified | ply↔git, ply↔Artifacts, git↔Artifacts, wire↔Artifacts | `lsRefs`, `listRefs` | 3 |
130| `refs.ref-prefix` | verified | ply↔git, ply↔Artifacts, git↔Artifacts | `lsRefs`, `listRefs` | 1 |
131| `refs.symref-head` | verified | ply↔git, ply↔Artifacts, git↔Artifacts | `lsRefs`, `push` | 2 |
132| `refs.directory-file-conflict` | verified | ply↔git, ply↔Artifacts, git↔Artifacts | `push` | 1 |
133| `refs.peeled-tags` | verified | ply↔git, ply↔Artifacts, git↔Artifacts | `lsRefs`, `listRefs` | 1 |
134| `refs.unborn-empty-repo` | verified | ply↔git, ply↔Artifacts | `lsRefs` | 2 |
135| `refs.advertisement-shapes` | verified | ply↔git | `lsRefs` | 2 |
136| `refs.v0-upload-pack-advertisement` | unsupported (observed) | git↔Artifacts, wire↔Artifacts | — | 0 |
137| `refs.receive-pack-advertisement` | verified | ply↔git, ply↔Artifacts, wire↔Artifacts | `receiveCaps`, `push` | 2 |
139#### `refs.ls-refs-listing`
141v2 ls-refs lists every ref with its object id.
143Ops: `src/lsrefs.ts` `lsRefs`, `src/refops.ts` `listRefs`.
145Tests:
147- `test/parity.test.js`: ls-refs == git ls-remote (prefixes, symrefs, peeled tags, many refs)
148- `test/e2e-customer.test.js`: listRefs is for-each-ref, before the deletes
149- `test/probes/wire.test.js`: reference: ${plan.id} meets its answer with every sender
151Evidence:
153- ply↔git: `test/parity.test.js`
154- ply↔Artifacts: validate-7b0c310f: `refs list (peeled tags)`
155- ply↔Artifacts: loadgen-phase6-plyw-20261025: `refs/small`
156- git↔Artifacts: loadgen-compat-20261024: `ls_remote/small/v2`
157- git↔Artifacts: validate-7b0c310f: `git judge: fsck --strict, refs, history`
158- ply↔git: `test/probes/wire.test.js`
159- ply↔Artifacts: wire-20261115t2116-1nam: `refs.ls-refs-listing#two-thousand-refs/art-ply`
160- git↔Artifacts: wire-20261115t2116-1nam: `refs.ls-refs-listing#two-thousand-refs/art-git`
161- wire↔Artifacts: wire-20261115t2116-1nam: `refs.ls-refs-listing#two-thousand-refs/art-raw`
162- wire↔Artifacts: wire-20261115t2116-1nam: `refs.ls-refs-listing#two-thousand-refs/art-curl`
163- wire↔Artifacts: wire-20261115t2116-1nam: `refs.ls-refs-listing#unknown-argument/art-raw`
164- wire↔Artifacts: wire-20261115t2116-1nam: `refs.ls-refs-listing#unknown-argument/art-curl`
166> The two-thousand-refs plan lists 1500 branches, 500 annotated tags and HEAD and compares a digest of the whole listing.
168#### `refs.ref-prefix`
170ls-refs `ref-prefix` arguments restrict the listing to refs under the given prefixes.
172Ops: `src/lsrefs.ts` `lsRefs`, `src/refops.ts` `listRefs`.
174Tests:
176- `test/parity.test.js`: ['refs/heads/main', 'refs/tags/v1'], ['HEAD']
178Evidence:
180- ply↔git: `test/parity.test.js`
181- ply↔Artifacts: loadgen-phase6-plyw-20261025: `refs/prefix`
182- ply↔Artifacts: loadgen-phase6-plyw-20261025: `refs/prefix_tags`
183- git↔Artifacts: loadgen-compat-20261024: `ls_remote_ref_prefix/small/v2`
185#### `refs.symref-head`
187ls-refs `symrefs` reports the target of HEAD, and the target is the default branch.
189Ops: `src/lsrefs.ts` `lsRefs`, `src/push.ts` `push`.
191Tests:
193- `test/parity.test.js`: ls-refs == git ls-remote (prefixes, symrefs, peeled tags, many refs)
194- `test/probes/probes.test.js`: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository
196Evidence:
198- ply↔git: `test/parity.test.js`
199- ply↔Artifacts: loadgen-phase6-plyw-20261025: `refs/n4_head`
200- ply↔Artifacts: loadgen-phase6-plyw-20261025: `refs/n4`
201- ply↔git: `test/probes/probes.test.js`
202- ply↔Artifacts: probes-20261115t2113-phhp: `refs.symref-head#delete-default-branch/art-ply`
203- git↔Artifacts: probes-20261115t2113-phhp: `refs.symref-head#delete-default-branch/art-git`
204- ply↔Artifacts: probes-20261115t2133-txqj: `refs.symref-head#delete-default-branch/art-ply`
205- git↔Artifacts: probes-20261115t2133-txqj: `refs.symref-head#delete-default-branch/art-git`
207> The delete-default-branch probe asks for a delete of the branch HEAD names and reads HEAD back with ls-remote --symref.
209#### `refs.directory-file-conflict`
211A ref cannot be both a name and a directory: creating refs/heads/a/b while refs/heads/a exists (or the reverse, or both in one push) is refused and leaves the existing ref as it was.
213Ops: `src/push.ts` `push`.
215Tests:
217- `test/probes/probes.test.js`: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository
219Evidence:
221- ply↔git: `test/probes/probes.test.js`
222- ply↔Artifacts: probes-20261115t2126-d4jn: `refs.directory-file-conflict#file-then-dir/art-ply`
223- git↔Artifacts: probes-20261115t2126-d4jn: `refs.directory-file-conflict#file-then-dir/art-git`
224- ply↔Artifacts: probes-20261115t2126-d4jn: `refs.directory-file-conflict#dir-then-file/art-ply`
225- git↔Artifacts: probes-20261115t2126-d4jn: `refs.directory-file-conflict#dir-then-file/art-git`
226- ply↔Artifacts: probes-20261115t2126-d4jn: `refs.directory-file-conflict#both-in-one-push/art-ply`
227- git↔Artifacts: probes-20261115t2126-d4jn: `refs.directory-file-conflict#both-in-one-push/art-git`
228- ply↔Artifacts: probes-20261115t2133-txqj: `refs.directory-file-conflict#file-then-dir/art-ply`
229- git↔Artifacts: probes-20261115t2133-txqj: `refs.directory-file-conflict#file-then-dir/art-git`
230- ply↔Artifacts: probes-20261115t2133-txqj: `refs.directory-file-conflict#dir-then-file/art-ply`
231- git↔Artifacts: probes-20261115t2133-txqj: `refs.directory-file-conflict#dir-then-file/art-git`
232- ply↔Artifacts: probes-20261115t2133-txqj: `refs.directory-file-conflict#both-in-one-push/art-ply`
233- git↔Artifacts: probes-20261115t2133-txqj: `refs.directory-file-conflict#both-in-one-push/art-git`
235#### `refs.peeled-tags`
237ls-refs `peel` attaches the peeled id to annotated tags, and only to them.
239Ops: `src/lsrefs.ts` `lsRefs`, `src/refops.ts` `listRefs`.
241Tests:
243- `test/parity.test.js`: ls-refs == git ls-remote (prefixes, symrefs, peeled tags, many refs)
245Evidence:
247- ply↔git: `test/parity.test.js`
248- ply↔Artifacts: validate-7b0c310f: `refs list (peeled tags)`
249- git↔Artifacts: loadgen-compat-20261024: `ls_remote_tags/small/v2`
251#### `refs.unborn-empty-repo`
253An empty repository lists no refs, and ls-refs `unborn` names the branch HEAD will be born on.
255Ops: `src/lsrefs.ts` `lsRefs`.
257Tests:
259- `test/lsrefs-unborn.test.js`: lsRefs unborn: the argument, the answer and the ref listing agree with git, across every cell
260- `test/lsrefs-unborn.test.js`: lsRefs unborn: an empty repository clones to the branch ply reports (git clone is the oracle)
262Evidence:
264- ply↔git: `test/lsrefs-unborn.test.js`
265- ply↔Artifacts: validate-7b0c310f: `refs (empty)`
266- ply↔Artifacts: loadgen-phase6-plyw-20261025: `refs/empty`
268#### `refs.advertisement-shapes`
270Unusual but legal listings (duplicate names, ordering, raw bytes in names) are read as git reads them.
272Ops: `src/lsrefs.ts` `lsRefs`.
274Tests:
276- `test/space/advertisement.test.js`: refs: every cell, judged by git ls-remote; a duplicate ref resolves to its first listing in git fetch
277- `test/git-bytes.test.js`: byte content × object field × operation
279Evidence:
281- ply↔git: `test/space/advertisement.test.js`
283> No Artifacts evidence: ply has never asked Artifacts to list a ref with non-UTF-8 or unusual bytes.
285#### `refs.v0-upload-pack-advertisement`
287The v0/v1 upload-pack advertisement (refs and capabilities on the info/refs GET, no Git-Protocol header).
289Unsupported: ply asks for protocol v2 on upload-pack and refuses a server that answers otherwise (src/caps.ts).
291Observed:
293- git↔Artifacts: loadgen-compat-20261024: `ls_remote/small/v0`
294- git↔Artifacts: loadgen-compat-20261024: `clone_full/small/v0`
295- git↔Artifacts: loadgen-compat-20261024: `depth_1/small/v0`
296- wire↔Artifacts: wire-20261115t2038-ee4x: `refs.v0-upload-pack-advertisement#no-protocol-header/art-raw`
297- wire↔Artifacts: wire-20261115t2038-ee4x: `refs.v0-upload-pack-advertisement#no-protocol-header/art-curl`
298- git↔Artifacts: wire-20261115t2038-ee4x: `refs.v0-upload-pack-advertisement#no-protocol-header/art-git`
299- wire↔Artifacts: wire-20261115t2116-1nam: `refs.v0-upload-pack-advertisement#two-thousand-refs/art-raw`
300- wire↔Artifacts: wire-20261115t2116-1nam: `refs.v0-upload-pack-advertisement#two-thousand-refs/art-curl`
301- git↔Artifacts: wire-20261115t2116-1nam: `refs.v0-upload-pack-advertisement#two-thousand-refs/art-git`
303> Stock git, raw requests and curl have probed v0 on Artifacts; ply has not.
305#### `refs.receive-pack-advertisement`
307The receive-pack advertisement (v0 form: capabilities on the first ref, `capabilities^{}` for an empty repository).
309Ops: `src/receivecaps.ts` `receiveCaps`, `src/push.ts` `push`.
311Tests:
313- `test/space/advertisement.test.js`: push: request × advertised atomic × advertised push-options × object-format, judged by git push
314- `test/push.test.js`: push matrix: configs × hooks × commands × caps, parity with git push
316Evidence:
318- ply↔git: `test/space/advertisement.test.js`
319- ply↔Artifacts: validate-7b0c310f: `write: root commit (edit changes)`
320- wire↔Artifacts: loadgen-phase2-20261025: `receive_caps/artifacts`
322### Capabilities and protocol v2 (`caps`, 9)
324| id | status | evidence | ply ops | tests |
325|---|---|---|---|---:|
326| `caps.v2-capability-advertisement` | verified | ply↔git, ply↔Artifacts, wire↔Artifacts | `discover`, `parseCapabilitiesV2` | 2 |
327| `caps.required-capabilities` | verified | ply↔git | `checkRequiredV2`, `discover` | 1 |
328| `caps.object-format` | verified | ply↔git | `decideObjectFormat`, `discover` | 1 |
329| `caps.fetch-argument-gating` | verified | ply↔git, wire↔Artifacts | `fetchPack`, `fetchRequest` | 1 |
330| `caps.filter-not-advertised` | verified | ply↔git | `fetchPack`, `readFile`, `listTree` | 1 |
331| `caps.receive-pack-capabilities` | verified | ply↔git, wire↔Artifacts | `receiveCaps`, `checkPushCaps` | 2 |
332| `caps.server-option` | unsupported (observed) | wire↔Artifacts | — | 0 |
333| `caps.wait-for-done-packfile-uris-sideband-all` | unsupported (observed) | wire↔Artifacts | — | 0 |
334| `caps.object-info` | unsupported (observed) | wire↔Artifacts | — | 0 |
336#### `caps.v2-capability-advertisement`
338The v2 capability advertisement: version 2, agent, ls-refs and fetch features, object-format, server-option, session-id.
340Ops: `src/discover.ts` `discover`, `src/caps.ts` `parseCapabilitiesV2`.
342Tests:
344- `test/space/advertisement.test.js`: caps: every cell through discover() (derived from the table)
345- `test/space/advertisement.test.js`: real git http-backend configurations advertise exactly what the renderer writes for their cell
347Evidence:
349- ply↔git: `test/space/advertisement.test.js`
350- ply↔Artifacts: validate-7b0c310f: `discover`
351- ply↔Artifacts: loadgen-phase6-plyw-20261025: `discover/v2_caps`
352- wire↔Artifacts: loadgen-phase2-20261025: `capability_table/v2`
353- wire↔Artifacts: loadgen-phase5-delta-20261025: `caps/v2_fetch_features`
354- wire↔Artifacts: wire-20261115t2116-1nam: `caps.v2-capability-advertisement#unknown-capability-line/art-raw`
355- wire↔Artifacts: wire-20261115t2116-1nam: `caps.v2-capability-advertisement#unknown-capability-line/art-curl`
357#### `caps.required-capabilities`
359A server missing a capability ply needs (ls-refs, fetch) is refused as unsupported before any operation.
361Ops: `src/closed.ts` `checkRequiredV2`, `src/discover.ts` `discover`.
363Tests:
365- `test/space/advertisement.test.js`: caps: every cell through discover() (derived from the table)
367Evidence:
369- ply↔git: `test/space/advertisement.test.js`
371> Artifacts advertises every required capability, so the refusal has never been reached against it.
373#### `caps.object-format`
375object-format=sha1 is accepted; any other object format is refused as unsupported.
377Ops: `src/closed.ts` `decideObjectFormat`, `src/discover.ts` `discover`.
379Tests:
381- `test/space/advertisement.test.js`: push: request × advertised atomic × advertised push-options × object-format, judged by git push
383Evidence:
385- ply↔git: `test/space/advertisement.test.js`
387> ply has not probed a sha256 repository on any server.
389#### `caps.fetch-argument-gating`
391ply sends a fetch argument (filter, shallow, include-tag, thin-pack, ofs-delta) only when the advertisement allows it, as git fetch does.
393Ops: `src/fetchpack.ts` `fetchPack`, `src/fetch.ts` `fetchRequest`.
395Tests:
397- `test/space/advertisement.test.js`: request: fetch arguments ply sends, judged by git fetch
399Evidence:
401- ply↔git: `test/space/advertisement.test.js`
402- wire↔Artifacts: wire-20261115t2116-1nam: `caps.fetch-argument-gating#unknown-fetch-argument/art-raw`
403- wire↔Artifacts: wire-20261115t2116-1nam: `caps.fetch-argument-gating#unknown-fetch-argument/art-curl`
405#### `caps.filter-not-advertised`
407A server whose fetch= line lists no `filter` (stock http-backend) gets no filter argument after one probe.
409Ops: `src/fetchpack.ts` `fetchPack`, `src/read.ts` `readFile`, `src/read.ts` `listTree`.
411Tests:
413- `test/no-filter.test.js`: reads: readFile, listTree, readCommit, readLog, checkoutTree answer the same on both; one probe, then no filter
415Evidence:
417- ply↔git: `test/no-filter.test.js`
419#### `caps.receive-pack-capabilities`
421receive-pack capabilities (report-status, report-status-v2, side-band-64k, atomic, push-options, delete-refs, ofs-delta, object-format) are read and checked before the POST.
423Ops: `src/receivecaps.ts` `receiveCaps`, `src/receivecaps.ts` `checkPushCaps`.
425Tests:
427- `test/space/advertisement.test.js`: push: request × advertised atomic × advertised push-options × object-format, judged by git push
428- `test/push-pack.test.js`: atomic the server does not advertise: unsupported, no POST, the pack unread
430Evidence:
432- ply↔git: `test/space/advertisement.test.js`
433- wire↔Artifacts: loadgen-phase2-20261025: `receive_caps/artifacts`
434- wire↔Artifacts: loadgen-phase5-delta-20261025: `caps/receive_pack_ofs_delta`
435- wire↔Artifacts: wire-20261115t2116-1nam: `caps.receive-pack-capabilities#unknown-capability-on-push/art-raw`
436- wire↔Artifacts: wire-20261115t2116-1nam: `caps.receive-pack-capabilities#unknown-capability-on-push/art-curl`
438#### `caps.server-option`
440v2 `server-option` arguments on ls-refs and fetch.
442Unsupported: discover() reads the capability; no ply operation sends a server-option.
444Observed:
446- wire↔Artifacts: loadgen-phase2-20261025: `capability_table/v2`
448#### `caps.wait-for-done-packfile-uris-sideband-all`
450v2 fetch features wait-for-done, packfile-uris and sideband-all.
452Unsupported: src/closed.ts names them only to classify an advertisement; ply never requests them.
454Observed:
456- wire↔Artifacts: loadgen-phase5-delta-20261025: `caps/v2_fetch_features`
458#### `caps.object-info`
460The v2 `object-info` command (object sizes without a pack).
462Unsupported: No ply operation sends command=object-info.
464Observed:
466- wire↔Artifacts: loadgen-phase2-20261025: `object_info/artifacts`
467- wire↔Artifacts: wire-20261115t2038-ee4x: `caps.object-info#size/art-raw`
468- wire↔Artifacts: wire-20261115t2038-ee4x: `caps.object-info#size/art-curl`
470### Fetch: negotiation, filters, shallow, include-tag, thin packs (`fetch`, 20)
472| id | status | evidence | ply ops | tests |
473|---|---|---|---|---:|
474| `fetch.want-tip-full-pack` | verified | ply↔git, git↔Artifacts | `fetchPack` | 1 |
475| `fetch.want-non-tip-object` | verified | ply↔git, ply↔Artifacts, git↔Artifacts | `fetchPack`, `fetchObject`, `readFile` | 2 |
476| `fetch.want-unreachable-or-unknown` | verified | ply↔git, ply↔Artifacts, git↔Artifacts, wire↔Artifacts | `fetchPack` | 2 |
477| `fetch.want-have-line-syntax` | verified | ply↔git, wire↔Artifacts | `fetchRequest`, `negotiate` | 1 |
478| `fetch.have-negotiation` | verified | ply↔git, git↔Artifacts | `negotiate`, `fetchPack` | 2 |
479| `fetch.acknowledgments-ready-packfile` | verified | ply↔git | `fetchPack` | 2 |
480| `fetch.filter-blob-none` | verified | ply↔git, ply↔Artifacts, git↔Artifacts | `fetchPack`, `fetchPackFiltered`, `readFile` | 2 |
481| `fetch.filter-tree-depth` | verified | ply↔git, git↔Artifacts | `fetchPack`, `readCommit` | 2 |
482| `fetch.filter-blob-limit` | verified | ply↔git, git↔Artifacts | `fetchPack` | 1 |
483| `fetch.filter-combine` | verified | ply↔git | `fetchPack`, `readFile` | 2 |
484| `fetch.filter-sparse-oid` | unsupported (observed) | git↔Artifacts, wire↔Artifacts | — | 0 |
485| `fetch.filter-refusal-fallback` | verified | ply↔git, ply↔Artifacts | `learnFilter`, `fetchPack`, `readFile` | 2 |
486| `fetch.deepen-depth` | verified | ply↔git, git↔Artifacts | `fetchPack`, `fetchObject` | 3 |
487| `fetch.deepen-since` | verified | ply↔git, git↔Artifacts | `fetchPack` | 1 |
488| `fetch.deepen-not` | verified | ply↔git, git↔Artifacts | `fetchPack` | 1 |
489| `fetch.deepen-relative-unshallow` | verified | ply↔git, git↔Artifacts | `fetchPack` | 1 |
490| `fetch.include-tag` | verified | ply↔git, git↔Artifacts | `fetchPack` | 1 |
491| `fetch.thin-pack` | verified | ply↔git, git↔Artifacts | `fetchPack`, `resolvePack` | 2 |
492| `fetch.ofs-delta-requested` | verified | ply↔git, wire↔Artifacts | `fetchPack`, `parsePack` | 1 |
493| `fetch.sideband-bands` | verified | ply↔git | `parseSideband`, `fetchPack` | 2 |
495#### `fetch.want-tip-full-pack`
497want of a tip with done and no filter: the pack holds exactly what pack-objects sends.
499Ops: `src/fetchpack.ts` `fetchPack`.
501Tests:
503- `test/protocol.test.js`: exhaustive fetch matrix: wants × haves × deepen × filter × server
505Evidence:
507- ply↔git: `test/protocol.test.js`
508- git↔Artifacts: loadgen-compat-20261024: `clone_full/small/v2`
509- git↔Artifacts: loadgen-compat-20261024: `clone_full/big/v2`
510- git↔Artifacts: validate-7b0c310f: `git judge: fsck --strict, refs, history`
512> On Artifacts only stock git has fetched full packs; ply always fetches there with a filter or a depth.
514#### `fetch.want-non-tip-object`
516want of an object that is not an advertised tip (an older commit, a tree, a blob, a tag) by id.
518Ops: `src/fetchpack.ts` `fetchPack`, `src/fetch.ts` `fetchObject`, `src/read.ts` `readFile`.
520Tests:
522- `test/protocol.test.js`: exhaustive fetch matrix: wants × haves × deepen × filter × server
523- `test/read.test.js`: readFile bytes == git show &lt;ref>:&lt;path> for every blob path and every ref form
525Evidence:
527- ply↔git: `test/protocol.test.js`
528- ply↔git: `test/read.test.js`
529- ply↔Artifacts: validate-7b0c310f: `read/blob README.md`
530- ply↔Artifacts: validate-7b0c310f: `tree (root, src)`
531- git↔Artifacts: loadgen-phase3-20261025: `reachable_nontip/v2/artifacts`
532- git↔Artifacts: loadgen-phase2-20261025: `fetch_reachable_sha`
534> The reference fixtures set uploadpack.allowAnySHA1InWant; a differential run must give the reference server the want policy Artifacts has.
536#### `fetch.want-unreachable-or-unknown`
538want of an unreachable or nonexistent id: the server refuses (ERR not our ref), and ply reports a typed remote_error.
540Ops: `src/fetchpack.ts` `fetchPack`.
542Tests:
544- `test/mutant-kill-tree.test.js`: ERR upload-pack: not our ref x
545- `test/probes/probes.test.js`: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository
547Evidence:
549- git↔Artifacts: loadgen-phase3-20261025: `unreachable_local/v2/artifacts`
550- git↔Artifacts: loadgen-phase3-20261025: `fake_sha/v2/artifacts`
551- wire↔Artifacts: loadgen-phase4-hostile-20261025: `proto/want_short_oid`
552- wire↔Artifacts: loadgen-phase4-hostile-20261025: `proto/want_nonhex_oid`
553- ply↔git: `test/probes/probes.test.js`
554- ply↔Artifacts: probes-20261115t1926-gfhc: `fetch.want-unreachable-or-unknown#phantom/art-ply`
556> ply sends an unknown want against git http-backend in the probes (#phantom, an id no one holds); an unreachable but present id is not probed.
558#### `fetch.want-have-line-syntax`
560want/have/shallow lines: upload-pack's verdict on each class of id, and ply refusing non-ids before the wire.
562Ops: `src/fetch.ts` `fetchRequest`, `src/negotiate.ts` `negotiate`.
564Tests:
566- `test/want-oracle.test.js`: want: git upload-pack and fetchRequest agree on every class
568Evidence:
570- ply↔git: `test/want-oracle.test.js`
571- wire↔Artifacts: loadgen-phase4-hostile-20261025: `proto/have_bad_oid`
572- wire↔Artifacts: loadgen-phase4-hostile-20261025: `proto/shallow_bad_oid`
574#### `fetch.have-negotiation`
576Multi-round have/ACK negotiation, then done: the server stops at common commits and sends only what is missing.
578Ops: `src/negotiate.ts` `negotiate`, `src/fetchpack.ts` `fetchPack`.
580Tests:
582- `test/protocol.test.js`: exhaustive fetch matrix: wants × haves × deepen × filter × server
583- `test/want-oracle.test.js`: negotiate: an acknowledgment that is not an object id
585Evidence:
587- ply↔git: `test/protocol.test.js`
588- git↔Artifacts: loadgen-compat-20261024: `incremental_fetch/scratch/v2`
590> On Artifacts only stock git has negotiated; no ply probe has sent haves there.
592#### `fetch.acknowledgments-ready-packfile`
594v2 response sections in order (acknowledgments, ready, shallow-info, packfile); a server that breaks the order is a protocol error, as it is for git.
596Ops: `src/fetchpack.ts` `fetchPack`.
598Tests:
600- `test/fetch-lying-server.test.js`: a fetch sent with done and answered with acknowledgments only is a protocol error, as it is for git
601- `test/fetch-lying-server.test.js`: a fetch sent with done and answered with acknowledgments before its packfile is a protocol error, as it is for git
603Evidence:
605- ply↔git: `test/fetch-lying-server.test.js`
607#### `fetch.filter-blob-none`
609filter blob:none: commits and trees, and blobs only when wanted by id.
611Ops: `src/fetchpack.ts` `fetchPack`, `src/fetchpack.ts` `fetchPackFiltered`, `src/read.ts` `readFile`.
613Tests:
615- `test/protocol.test.js`: exhaustive fetch matrix: wants × haves × deepen × filter × server
616- `test/log.test.js`: readLog on blob:none: the trees are harvested
618Evidence:
620- ply↔git: `test/protocol.test.js`
621- ply↔Artifacts: validate-7b0c310f: `read/blob README.md`
622- ply↔Artifacts: validate-7b0c310f: `tree (root, src)`
623- ply↔Artifacts: loadgen-phase6-plyw-20261025: `read/small`
624- git↔Artifacts: loadgen-compat-20261024: `filter_blob_none+lazy_checkout/deep/v2`
626#### `fetch.filter-tree-depth`
628filter tree:&lt;depth> (tree:0 commit only, tree:1, tree:2).
630Ops: `src/fetchpack.ts` `fetchPack`, `src/read.ts` `readCommit`.
632Tests:
634- `test/protocol.test.js`: exhaustive fetch matrix: wants × haves × deepen × filter × server
635- `test/read.test.js`: readCommit fetches the commit object only: one tree:0 deepen-1 fetch, no tree fetches
637Evidence:
639- ply↔git: `test/protocol.test.js`
640- git↔Artifacts: loadgen-compat-20261024: `filter_tree_0/deep/v2`
642#### `fetch.filter-blob-limit`
644filter blob:limit=&lt;n>.
646Ops: `src/fetchpack.ts` `fetchPack`.
648Tests:
650- `test/protocol.test.js`: exhaustive fetch matrix: wants × haves × deepen × filter × server
652Evidence:
654- ply↔git: `test/protocol.test.js`
655- git↔Artifacts: loadgen-compat-20261024: `filter_blob_limit_2m/big/v2`
657#### `fetch.filter-combine`
659filter combine:blob:none+tree:&lt;k> (a commit and the first levels of its path in one request).
661Ops: `src/fetchpack.ts` `fetchPack`, `src/read.ts` `readFile`.
663Tests:
665- `test/protocol.test.js`: exhaustive fetch matrix: wants × haves × deepen × filter × server
666- `test/path-trees.test.js`: a server that takes it: first contact is tree:0
668Evidence:
670- ply↔git: `test/protocol.test.js`
671- ply↔git: `test/path-trees.test.js`
673> No Artifacts evidence of any kind for combine filters.
675#### `fetch.filter-sparse-oid`
677filter sparse:oid=&lt;blob>.
679Unsupported: No ply operation builds a sparse:oid filter; the wire probe hands one to fetchPackFiltered only to watch it refused, which is not support.
681Observed:
683- git↔Artifacts: loadgen-compat-20261024: `filter_sparse_oid/wide/v2`
684- wire↔Artifacts: wire-20261115t2038-ee4x: `fetch.filter-sparse-oid#refused/art-raw`
685- wire↔Artifacts: wire-20261115t2038-ee4x: `fetch.filter-sparse-oid#refused/art-curl`
686- git↔Artifacts: wire-20261115t2038-ee4x: `fetch.filter-sparse-oid#refused/art-git`
688#### `fetch.filter-refusal-fallback`
690A server that advertises filter but refuses a filter spec with HTTP 400: ply records the refusal for that remote and falls back to blob:none.
692Ops: `src/transport.ts` `learnFilter`, `src/fetchpack.ts` `fetchPack`, `src/read.ts` `readFile`.
694Tests:
696- `test/artifacts-compat.test.js`: Unsupported Git fetch filter; only blob:none is supported.
697- `test/path-trees.test.js`: an Artifacts-like server (only blob:none): never asked for the deep fetch
699Evidence:
701- ply↔git: `test/artifacts-compat.test.js`
702- ply↔Artifacts: validate-7b0c310f: `read/blob README.md`
703- ply↔Artifacts: loadgen-phase6-plyw-20261025: `read/small`
705> The reference tests emulate the 400 with a proxy in front of git; git judges the results, not the refusal.
707#### `fetch.deepen-depth`
709deepen &lt;n>: a shallow pack cut n commits below each want, with shallow-info naming the boundary.
711Ops: `src/fetchpack.ts` `fetchPack`, `src/fetch.ts` `fetchObject`.
713Tests:
715- `test/protocol.test.js`: exhaustive fetch matrix: wants × haves × deepen × filter × server
716- `test/parity.test.js`: clone --depth N / --filter / --shallow-since / --shallow-exclude: same invocation, same shallow set, same objects
717- `test/fetchobject-deepen.test.js`: fetchObject costs one object
719Evidence:
721- ply↔git: `test/parity.test.js`
722- git↔Artifacts: loadgen-compat-20261024: `depth_1/small/v2`
723- git↔Artifacts: loadgen-compat-20261024: `depth_n/small/v2`
725#### `fetch.deepen-since`
727deepen-since &lt;time>.
729Ops: `src/fetchpack.ts` `fetchPack`.
731Tests:
733- `test/parity.test.js`: clone --depth N / --filter / --shallow-since / --shallow-exclude: same invocation, same shallow set, same objects
735Evidence:
737- ply↔git: `test/parity.test.js`
738- git↔Artifacts: loadgen-compat-20261024: `shallow_since/deep/v2`
740#### `fetch.deepen-not`
742deepen-not &lt;ref>.
744Ops: `src/fetchpack.ts` `fetchPack`.
746Tests:
748- `test/parity.test.js`: clone --depth N / --filter / --shallow-since / --shallow-exclude: same invocation, same shallow set, same objects
750Evidence:
752- ply↔git: `test/parity.test.js`
753- git↔Artifacts: loadgen-compat-20261024: `shallow_exclude/deep/v2`
755#### `fetch.deepen-relative-unshallow`
757Fetch after a shallow clone: deepen-relative, a deeper depth, and unshallow, from the client's shallow list.
759Ops: `src/fetchpack.ts` `fetchPack`.
761Tests:
763- `test/parity.test.js`: fetch after a shallow clone: --deepen (relative), --depth=N, --unshallow, --shallow-since, --shallow-exclude
765Evidence:
767- ply↔git: `test/parity.test.js`
768- git↔Artifacts: loadgen-phase2-20261025: `deepen_relative_v2`
769- git↔Artifacts: loadgen-compat-20261024: `unshallow/deep/v2`
770- git↔Artifacts: loadgen-phase2-20261025: `depth_beyond_history`
772#### `fetch.include-tag`
774include-tag: annotated tags that point into the pack are sent with it.
776Ops: `src/fetchpack.ts` `fetchPack`.
778Tests:
780- `test/parity.test.js`: includeTag: true
782Evidence:
784- ply↔git: `test/parity.test.js`
785- git↔Artifacts: loadgen-compat-20261024: `depth_1/wide/v2`
786- git↔Artifacts: loadgen-compat-20261024: `clone_full/small/v2`
788> ply's own operations never ask for include-tag; only a fetchPack caller that sets it does.
790#### `fetch.thin-pack`
792thin-pack with haves: deltas against objects the client has, resolved against external bases.
794Ops: `src/fetchpack.ts` `fetchPack`, `src/packresolve.ts` `resolvePack`.
796Tests:
798- `test/protocol.test.js`: exhaustive fetch matrix: wants × haves × deepen × filter × server
799- `test/edges.test.js`: thin-pack fetch with have resolves against external base
801Evidence:
803- ply↔git: `test/edges.test.js`
804- git↔Artifacts: loadgen-phase5-delta-20261025: `storage/thin_fetch`
806#### `fetch.ofs-delta-requested`
808ofs-delta: OFS_DELTA entries only when asked for.
810Ops: `src/fetchpack.ts` `fetchPack`, `src/packresolve.ts` `parsePack`.
812Tests:
814- `test/protocol.test.js`: exhaustive fetch matrix: wants × haves × deepen × filter × server
816Evidence:
818- ply↔git: `test/protocol.test.js`
819- wire↔Artifacts: loadgen-phase5-delta-20261025: `caps/upload_v0_ofs_thin`
821#### `fetch.sideband-bands`
823Side-band in the packfile section: band 1 data, band 2 progress, band 3 fatal error.
825Ops: `src/fetch.ts` `parseSideband`, `src/fetchpack.ts` `fetchPack`.
827Tests:
829- `test/adversarial.test.js`: { name: 'fetch band 3 (commit)'
830- `test/remote-text.test.js`: listRefs (ERR) and readFile (fetch ERR, fetch band 3) carry none of it
832Evidence:
834- ply↔git: `test/adversarial.test.js`
836> Band 3 is only ever injected by a proxy; no server has been made to send ply a fatal band-3 line.
838### Packfiles: OFS/REF deltas, thin bases, malformed packs (served and pushed) (`pack`, 18)
840| id | status | evidence | ply ops | tests |
841|---|---|---|---|---:|
842| `pack.ofs-delta-resolve` | verified | ply↔git | `parsePack`, `resolvePackRange`, `scanPack` | 1 |
843| `pack.ref-delta-resolve` | verified | ply↔git, ply↔Artifacts | `parsePack`, `resolvePackRange`, `scanPack` | 2 |
844| `pack.thin-ref-base` | verified | ply↔git | `resolvePack` | 1 |
845| `pack.truncated-served-pack` | verified | ply↔git | `parsePack`, `scanPack`, `resolvePackRange` | 1 |
846| `pack.corrupt-served-pack` | verified | ply↔git | `parsePack`, `scanPack`, `fetchPack` | 2 |
847| `pack.served-pack-limits` | verified | ply↔git | `parsePack`, `resolvePackRange` | 3 |
848| `pack.push-ofs-delta-accepted` | verified | ply↔git, wire↔Artifacts | `push`, `pushPack` | 2 |
849| `pack.push-thin-against-server-base` | verified | ply↔git, ply↔Artifacts, git↔Artifacts, wire↔Artifacts | `editFile`, `push` | 2 |
850| `pack.push-thin-missing-base` | verified | ply↔git, ply↔Artifacts, wire↔Artifacts | `pushPack` | 1 |
851| `pack.push-corrupt-pack-refused` | verified | ply↔git, ply↔Artifacts, wire↔Artifacts | `pushPack`, `classifyReport` | 4 |
852| `pack.push-duplicate-object` | verified | ply↔git | `push` | 1 |
853| `pack.push-malformed-object-refused` | verified | ply↔git, ply↔Artifacts, wire↔Artifacts | `pushPack` | 1 |
854| `pack.push-bad-header-refused` | verified | ply↔git, ply↔Artifacts | `pushPack` | 1 |
855| `pack.push-bad-entry-refused` | verified | ply↔git, ply↔Artifacts | `pushPack` | 1 |
856| `pack.push-duplicate-entries` | verified | ply↔git, ply↔Artifacts | `pushPack` | 1 |
857| `pack.push-fsck-tree-refused` | verified | ply↔git, ply↔Artifacts, git↔Artifacts | `push` | 1 |
858| `pack.push-fsck-commit-refused` | verified | ply↔git, ply↔Artifacts, git↔Artifacts | `push` | 1 |
859| `pack.push-decompression-ratio` | verified | ply↔git, ply↔Artifacts, git↔Artifacts | `push` | 1 |
861#### `pack.ofs-delta-resolve`
863A served pack with OFS_DELTA chains resolves to the objects git verify-pack lists.
865Ops: `src/packresolve.ts` `parsePack`, `src/packrangeresolve.ts` `resolvePackRange`, `src/pullstream.ts` `scanPack`.
867Tests:
869- `test/pack-range-resolve.test.js`: this repository's pack with OFS deltas matches git verify-pack
871Evidence:
873- ply↔git: `test/pack-range-resolve.test.js`
875> Artifacts sends REF_DELTA only, so no fetch from it reaches OFS resolution.
877#### `pack.ref-delta-resolve`
879A served pack of REF_DELTA entries only (what Artifacts sends) resolves in any order.
881Ops: `src/packresolve.ts` `parsePack`, `src/packrangeresolve.ts` `resolvePackRange`, `src/pullstream.ts` `scanPack`.
883Tests:
885- `test/pack-range-resolve.test.js`: this repository's pack, REF_DELTA only (what Artifacts sends)
886- `test/edges.test.js`: REF_DELTA packs (server without ofs-delta) resolve identically
888Evidence:
890- ply↔git: `test/pack-range-resolve.test.js`
891- ply↔Artifacts: validate-7b0c310f: `read/blob README.md`
892- ply↔Artifacts: validate-7b0c310f: `viewer: /r/ply blob (README.md)`
894#### `pack.thin-ref-base`
896A thin REF base supplied from outside the pack is checked against its claimed id before a delta applies.
898Ops: `src/packresolve.ts` `resolvePack`.
900Tests:
902- `test/space/thin-base.test.js`: thin REF base: every claim × byte form against git hash-object and index-pack --fix-thin
904Evidence:
906- ply↔git: `test/space/thin-base.test.js`
908#### `pack.truncated-served-pack`
910A served pack cut at any byte is refused, typed, on every read path, where git index-pack refuses it.
912Ops: `src/packresolve.ts` `parsePack`, `src/pullstream.ts` `scanPack`, `src/packrangeresolve.ts` `resolvePackRange`.
914Tests:
916- `test/space/pack-cut.test.js`: cut: every byte offset of every pack is refused, typed, on every path
918Evidence:
920- ply↔git: `test/space/pack-cut.test.js`
922#### `pack.corrupt-served-pack`
924A served pack with a corrupt header field, zlib member, delta or checksum is refused exactly where git index-pack --strict refuses it.
926Ops: `src/packresolve.ts` `parsePack`, `src/pullstream.ts` `scanPack`, `src/fetchpack.ts` `fetchPack`.
928Tests:
930- `test/space/pack-cut.test.js`: corrupt: every header-field class is refused exactly where git index-pack --strict refuses it, typed
931- `test/adversarial.test.js`: every protocol-aware mutator × every stage: typed error or git-verified success, never silent corruption
933Evidence:
935- ply↔git: `test/space/pack-cut.test.js`
937#### `pack.served-pack-limits`
939Hostile sizes in a served pack (object size, delta result, chain depth, inflated total) are refused before allocation.
941Ops: `src/packresolve.ts` `parsePack`, `src/packrangeresolve.ts` `resolvePackRange`.
943Tests:
945- `test/adversarial.test.js`: I4 limits: hostile sizes are rejected before allocation; memory does not grow
946- `test/delta-bound.test.js`: A delta that asks for a huge result must die before the output buffer exists
947- `test/space/pack-cut.test.js`: caps: maxObjectSize, maxInflatedTotal, maxDeltaChain at, and one under, what each real pack needs
949Evidence:
951- ply↔git: `test/space/pack-cut.test.js`
953#### `pack.push-ofs-delta-accepted`
955receive-pack accepts a pushed pack with OFS_DELTA entries when it advertises ofs-delta.
957Ops: `src/push.ts` `push`, `src/receivecaps.ts` `pushPack`.
959Tests:
961- `test/push-once.test.js`: push: an ofs delta whose base is a repeated object still names its base
962- `test/push-pack.test.js`: a stock git pack of known length: chunked stream, ref moves, fsck --strict clean, span counts the body
964Evidence:
966- ply↔git: `test/push-pack.test.js`
967- wire↔Artifacts: loadgen-phase5-delta-20261025: `push/ofs`
969#### `pack.push-thin-against-server-base`
971receive-pack completes a thin pushed pack whose REF bases it holds (every ply edit pushes blob and tree deltas this way).
973Ops: `src/edit.ts` `editFile`, `src/push.ts` `push`.
975Tests:
977- `test/edges.test.js`: push = commit + 100 tree deltas + blob delta
978- `test/probes/probes.test.js`: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository
980Evidence:
982- ply↔git: `test/edges.test.js`
983- ply↔Artifacts: validate-7b0c310f: `write: edit README find/replace (c1)`
984- wire↔Artifacts: loadgen-phase5-delta-20261025: `push/thin_ok`
985- ply↔git: `test/probes/probes.test.js`
986- ply↔Artifacts: probes-20261114t2226-yyjq: `pack.push-thin-against-server-base#literal-delta/art-ply`
987- git↔Artifacts: probes-20261114t2226-yyjq: `pack.push-thin-against-server-base#literal-delta/art-git`
989#### `pack.push-thin-missing-base`
991receive-pack refuses a thin pushed pack whose base it does not hold, and moves no ref.
993Ops: `src/receivecaps.ts` `pushPack`.
995Tests:
997- `test/probes/probes.test.js`: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository
999Evidence:
1001- wire↔Artifacts: loadgen-phase5-delta-20261025: `push/thin_missing`
1002- ply↔git: `test/probes/probes.test.js`
1003- ply↔Artifacts: probes-20261114t2226-yyjq: `pack.push-thin-missing-base#ghost-base/art-ply`
1005> pushPack carries a thin pack whose delta base the server lacks in the probes, against the reference and Artifacts.
1007#### `pack.push-corrupt-pack-refused`
1009receive-pack refuses a corrupt pushed pack (unpack error, ng for every ref) and moves no ref.
1011Ops: `src/receivecaps.ts` `pushPack`, `src/push.ts` `classifyReport`.
1013Tests:
1015- `test/push-pack.test.js`: a corrupt pack against stock git
1016- `test/custom-exchange.test.js`: a corrupt pack: the report is unpackFailed
1017- `test/push-unpack-host.test.js`: the echoed shape is unpackFailed and decides push_rejected; delete-only stays ambiguous
1018- `test/probes/probes.test.js`: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository
1020Evidence:
1022- ply↔git: `test/push-pack.test.js`
1023- wire↔Artifacts: loadgen-phase4-hostile-write-20261025: `pack/corrupt_zlib`
1024- wire↔Artifacts: loadgen-phase4-hostile-write-20261025: `pack/bad_checksum`
1025- wire↔Artifacts: loadgen-phase4-hostile-write-20261025: `pack/truncated`
1026- wire↔Artifacts: loadgen-phase4-hostile-write-20261025: `pack/bad_magic`
1027- wire↔Artifacts: loadgen-phase4-hostile-write-20261025: `pack/wrong_object_count`
1028- ply↔git: `test/probes/probes.test.js`
1029- ply↔Artifacts: probes-20261114t2226-yyjq: `pack.push-corrupt-pack-refused#bad-trailer/art-ply`
1030- ply↔Artifacts: probes-20261114t2226-yyjq: `pack.push-corrupt-pack-refused#bad-zlib/art-ply`
1031- ply↔Artifacts: probes-20261114t2226-yyjq: `pack.push-corrupt-pack-refused#truncated/art-ply`
1033> ply's reading of Artifacts' own unpack-failure report is tested on bytes copied from prod into a fake (push-unpack-host.test.js) and live by the corrupt-pack probes (bad trailer, bad zlib, truncated).
1035#### `pack.push-duplicate-object`
1037A pushed pack never names one object twice (a strict receiver refuses it).
1039Ops: `src/push.ts` `push`.
1041Tests:
1043- `test/push-once.test.js`: push: a list that names objects twice is one object each on the wire
1045Evidence:
1047- ply↔git: `test/push-once.test.js`
1049#### `pack.push-malformed-object-refused`
1051receive-pack refuses a well-framed pack that holds a malformed object or a delta with no base.
1053Ops: `src/receivecaps.ts` `pushPack`.
1055Tests:
1057- `test/probes/probes.test.js`: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository
1059Evidence:
1061- wire↔Artifacts: loadgen-phase4-hostile-write-20261025: `pack/invalid_commit_payload`
1062- wire↔Artifacts: loadgen-phase4-hostile-write-20261025: `pack/delta_missing_base`
1063- ply↔git: `test/probes/probes.test.js`
1064- ply↔Artifacts: probes-20261114t2226-yyjq: `pack.push-malformed-object-refused#missing-blob/art-ply`
1065- ply↔Artifacts: probes-20261114t2226-yyjq: `pack.push-malformed-object-refused#delta-copy-past-end/art-ply`
1066- ply↔Artifacts: probes-20261115t2113-phhp: `pack.push-malformed-object-refused#tag-type-mismatch/art-ply`
1068> ply's encoders never write a malformed object (the encode-*-fsck tests); the probes carry one through pushPack: a commit naming a missing blob, a delta copying past its base.
1070#### `pack.push-bad-header-refused`
1072receive-pack refuses a pushed pack whose header is wrong (signature, version, object count more or fewer than sent), moves no ref, and still serves the repository fsck-clean.
1074Ops: `src/receivecaps.ts` `pushPack`.
1076Tests:
1078- `test/probes/probes.test.js`: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository
1080Evidence:
1082- ply↔git: `test/probes/probes.test.js`
1083- ply↔Artifacts: probes-20261115t1926-gfhc: `pack.push-bad-header-refused#bad-signature/art-ply`
1084- ply↔Artifacts: probes-20261115t1926-gfhc: `pack.push-bad-header-refused#bad-version/art-ply`
1085- ply↔Artifacts: probes-20261115t1926-gfhc: `pack.push-bad-header-refused#count-more/art-ply`
1086- ply↔Artifacts: probes-20261115t1926-gfhc: `pack.push-bad-header-refused#count-fewer/art-ply`
1088> Probe packs are written by the harness with the trailer recomputed, so only the header is wrong; ply sends them through pushPack.
1090#### `pack.push-bad-entry-refused`
1092receive-pack refuses a pushed pack with a bad entry (stated size not what the zlib stream inflates to, a reserved object type, an OFS_DELTA reaching before the pack, a delta whose stated result size it does not write), moves no ref, and still serves the repository fsck-clean.
1094Ops: `src/receivecaps.ts` `pushPack`.
1096Tests:
1098- `test/probes/probes.test.js`: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository
1100Evidence:
1102- ply↔git: `test/probes/probes.test.js`
1103- ply↔Artifacts: probes-20261115t1926-gfhc: `pack.push-bad-entry-refused#size-header-mismatch/art-ply`
1104- ply↔Artifacts: probes-20261115t1926-gfhc: `pack.push-bad-entry-refused#bad-type/art-ply`
1105- ply↔Artifacts: probes-20261115t1926-gfhc: `pack.push-bad-entry-refused#ofs-delta-before-start/art-ply`
1106- ply↔Artifacts: probes-20261115t1926-gfhc: `pack.push-bad-entry-refused#delta-size-mismatch/art-ply`
1108#### `pack.push-duplicate-entries`
1110receive-pack with fsckObjects refuses a pushed pack that names every object twice (git index-pack --strict), moves no ref, and still serves the repository fsck-clean.
1112Ops: `src/receivecaps.ts` `pushPack`.
1114Tests:
1116- `test/probes/probes.test.js`: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository
1118Evidence:
1120- ply↔git: `test/probes/probes.test.js`
1121- ply↔Artifacts: probes-20261115t1926-gfhc: `pack.push-duplicate-entries#every-object-twice/art-ply`
1123> pack.push-duplicate-object is ply's side (it never sends one object twice); this is the server's answer to a pack that does.
1125#### `pack.push-fsck-tree-refused`
1127receive-pack with fsckObjects refuses a pushed tree git fsck calls an error (unsorted, a name twice, a `/` in a name, `.git`, a zero-padded mode), moves no ref, and still serves the repository fsck-clean.
1129Ops: `src/push.ts` `push`.
1131Tests:
1133- `test/probes/probes.test.js`: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository
1135Evidence:
1137- ply↔git: `test/probes/probes.test.js`
1138- ply↔Artifacts: probes-20261115t1926-gfhc: `pack.push-fsck-tree-refused#unsorted/art-ply`
1139- git↔Artifacts: probes-20261115t1926-gfhc: `pack.push-fsck-tree-refused#unsorted/art-git`
1140- ply↔Artifacts: probes-20261115t1926-gfhc: `pack.push-fsck-tree-refused#duplicate-name/art-ply`
1141- git↔Artifacts: probes-20261115t1926-gfhc: `pack.push-fsck-tree-refused#duplicate-name/art-git`
1142- ply↔Artifacts: probes-20261115t1926-gfhc: `pack.push-fsck-tree-refused#slash-in-name/art-ply`
1143- git↔Artifacts: probes-20261115t1926-gfhc: `pack.push-fsck-tree-refused#slash-in-name/art-git`
1144- ply↔Artifacts: probes-20261115t1926-gfhc: `pack.push-fsck-tree-refused#dot-git/art-ply`
1145- git↔Artifacts: probes-20261115t1926-gfhc: `pack.push-fsck-tree-refused#dot-git/art-git`
1146- ply↔Artifacts: probes-20261115t1926-gfhc: `pack.push-fsck-tree-refused#zero-padded-mode/art-ply`
1147- git↔Artifacts: probes-20261115t1926-gfhc: `pack.push-fsck-tree-refused#zero-padded-mode/art-git`
1149> Seeded byte for byte with git hash-object --literally and pushed by both ply and stock git, whose pack writers carry the object unchecked. A tree with mode 100664 (badFilemode) is only a warning to receive.fsckObjects and is not probed.
1151#### `pack.push-fsck-commit-refused`
1153receive-pack with fsckObjects refuses a pushed commit with a malformed author line (bad date, missing email, bad time zone, a date that overflows), moves no ref, and still serves the repository fsck-clean.
1155Ops: `src/push.ts` `push`.
1157Tests:
1159- `test/probes/probes.test.js`: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository
1161Evidence:
1163- ply↔git: `test/probes/probes.test.js`
1164- ply↔Artifacts: probes-20261115t1926-gfhc: `pack.push-fsck-commit-refused#bad-date/art-ply`
1165- git↔Artifacts: probes-20261115t1926-gfhc: `pack.push-fsck-commit-refused#bad-date/art-git`
1166- ply↔Artifacts: probes-20261115t1926-gfhc: `pack.push-fsck-commit-refused#missing-email/art-ply`
1167- git↔Artifacts: probes-20261115t1926-gfhc: `pack.push-fsck-commit-refused#missing-email/art-git`
1168- ply↔Artifacts: probes-20261115t1926-gfhc: `pack.push-fsck-commit-refused#bad-timezone/art-ply`
1169- git↔Artifacts: probes-20261115t1926-gfhc: `pack.push-fsck-commit-refused#bad-timezone/art-git`
1170- ply↔Artifacts: probes-20261115t1926-gfhc: `pack.push-fsck-commit-refused#date-overflow/art-ply`
1171- git↔Artifacts: probes-20261115t1926-gfhc: `pack.push-fsck-commit-refused#date-overflow/art-git`
1173#### `pack.push-decompression-ratio`
1175receive-pack takes a pushed blob that inflates about a thousandfold (16 MiB of one byte in about 16 KiB), under its object and pack caps, and serves it back.
1177Ops: `src/push.ts` `push`.
1179Tests:
1181- `test/probes/probes.test.js`: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository
1183Evidence:
1185- ply↔git: `test/probes/probes.test.js`
1186- ply↔Artifacts: probes-20261115t1926-gfhc: `pack.push-decompression-ratio#zeros-16mib/art-ply`
1187- git↔Artifacts: probes-20261115t1926-gfhc: `pack.push-decompression-ratio#zeros-16mib/art-git`
1189### Push and receive-pack (`push`, 19)
1191| id | status | evidence | ply ops | tests |
1192|---|---|---|---|---:|
1193| `push.create-ref` | verified | ply↔git, ply↔Artifacts, git↔Artifacts | `push`, `createBranch` | 3 |
1194| `push.first-commit-empty-repo` | verified | ply↔git, ply↔Artifacts, git↔Artifacts | `commitChanges`, `push` | 2 |
1195| `push.fast-forward-update` | verified | ply↔git, ply↔Artifacts, git↔Artifacts | `push`, `editFile` | 2 |
1196| `push.non-fast-forward` | verified | ply↔git, ply↔Artifacts, git↔Artifacts | `push` | 3 |
1197| `push.delete-ref` | verified | ply↔git, ply↔Artifacts, git↔Artifacts | `push`, `deleteBranch` | 3 |
1198| `push.atomic` | verified | ply↔git, ply↔Artifacts, git↔Artifacts | `push`, `pushPack`, `runTransfer` | 3 |
1199| `push.non-atomic-partial` | verified | ply↔git, ply↔Artifacts, git↔Artifacts | `push` | 2 |
1200| `push.report-status` | verified | ply↔git, ply↔Artifacts | `push`, `classifyReport` | 3 |
1201| `push.report-status-v2` | verified | ply↔git | `push` | 1 |
1202| `push.sideband-hook-output` | verified | ply↔git | `push` | 1 |
1203| `push.push-options` | verified | ply↔git, git↔Artifacts | `push`, `pushPack` | 2 |
1204| `push.hook-rejection` | verified | ply↔git | `push` | 1 |
1205| `push.ref-name-rules` | verified | ply↔git, ply↔Artifacts, git↔Artifacts, wire↔Artifacts | `push` | 2 |
1206| `push.ref-to-missing-object-refused` | verified | ply↔git, ply↔Artifacts | `pushPack` | 1 |
1207| `push.size-limits` | verified | ply↔git, ply↔Artifacts, git↔Artifacts, wire↔Artifacts | `push`, `pushPack` | 2 |
1208| `push.many-ref-updates` | verified | ply↔git, ply↔Artifacts, git↔Artifacts, wire↔Artifacts | `push` | 1 |
1209| `push.signed-push` | unsupported (observed) | git↔Artifacts | — | 0 |
1210| `push.from-shallow-clone` | verified | ply↔git, ply↔Artifacts, git↔Artifacts | `push` | 1 |
1211| `push.from-partial-clone` | verified | ply↔git, ply↔Artifacts, git↔Artifacts | `fetchPack`, `push` | 1 |
1213#### `push.create-ref`
1215A command with the zero old id creates a ref.
1217Ops: `src/push.ts` `push`, `src/refops.ts` `createBranch`.
1219Tests:
1221- `test/push.test.js`: 'create': t =>
1222- `test/e2e-customer.test.js`: createBranch from a branch name, a short name, a peeled annotated tag
1223- `test/probes/probes.test.js`: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository
1225Evidence:
1227- ply↔git: `test/push.test.js`
1228- ply↔Artifacts: validate-7b0c310f: `branch create (feat from c0)`
1229- ply↔Artifacts: loadgen-phase6-plyw-20261025: `branch/create`
1230- git↔Artifacts: loadgen-phase2-20261025: `new_branch`
1231- ply↔git: `test/probes/probes.test.js`
1232- ply↔Artifacts: probes-20261114t2226-yyjq: `push.create-ref#plain/art-ply`
1233- git↔Artifacts: probes-20261114t2226-yyjq: `push.create-ref#plain/art-git`
1234- ply↔Artifacts: probes-20261114t2226-yyjq: `push.create-ref#already-exists/art-ply`
1235- git↔Artifacts: probes-20261114t2226-yyjq: `push.create-ref#already-exists/art-git`
1237#### `push.first-commit-empty-repo`
1239The first push to an empty repository creates the default branch from a root commit.
1241Ops: `src/changes.ts` `commitChanges`, `src/push.ts` `push`.
1243Tests:
1245- `test/changes.test.js`: commitChanges: start × place × op against git cat-file and fsck --strict
1246- `test/probes/probes.test.js`: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository
1248Evidence:
1250- ply↔git: `test/changes.test.js`
1251- ply↔Artifacts: validate-7b0c310f: `write: root commit (edit changes)`
1252- ply↔git: `test/probes/probes.test.js`
1253- ply↔Artifacts: probes-20261114t2226-yyjq: `push.first-commit-empty-repo#root/art-ply`
1254- git↔Artifacts: probes-20261114t2226-yyjq: `push.first-commit-empty-repo#root/art-git`
1256#### `push.fast-forward-update`
1258A fast-forward update with the current old id lands.
1260Ops: `src/push.ts` `push`, `src/edit.ts` `editFile`.
1262Tests:
1264- `test/push.test.js`: push matrix: configs × hooks × commands × caps, parity with git push
1265- `test/probes/probes.test.js`: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository
1267Evidence:
1269- ply↔git: `test/push.test.js`
1270- ply↔Artifacts: validate-7b0c310f: `write: edit README find/replace (c1)`
1271- ply↔Artifacts: loadgen-phase6-plyw-20261025: `edit/ok`
1272- ply↔git: `test/probes/probes.test.js`
1273- ply↔Artifacts: probes-20261114t2226-yyjq: `push.fast-forward-update#plain/art-ply`
1274- git↔Artifacts: probes-20261114t2226-yyjq: `push.fast-forward-update#plain/art-git`
1276#### `push.non-fast-forward`
1278A non-fast-forward update: refused under receive.denyNonFastForwards, accepted as a forced update otherwise.
1280Ops: `src/push.ts` `push`.
1282Tests:
1284- `test/push.test.js`: 'nonff-update': t =>
1285- `test/push.test.js`: 'deny-nonff': { 'receive.denyNonFastForwards': 'true' }
1286- `test/probes/probes.test.js`: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository
1288Evidence:
1290- ply↔git: `test/push.test.js`
1291- git↔Artifacts: loadgen-phase2-20261025: `non_ff_reject`
1292- git↔Artifacts: loadgen-compat-20261024: `force_push/scratch/v2`
1293- ply↔git: `test/probes/probes.test.js`
1294- ply↔Artifacts: probes-20261114t2226-yyjq: `push.non-fast-forward#with-old-id/art-ply`
1295- git↔Artifacts: probes-20261114t2226-yyjq: `push.non-fast-forward#with-old-id/art-git`
1297#### `push.delete-ref`
1299A command with the zero new id deletes a ref (delete-refs); refused under receive.denyDeletes.
1301Ops: `src/push.ts` `push`, `src/refops.ts` `deleteBranch`.
1303Tests:
1305- `test/push.test.js`: 'delete': t =>
1306- `test/push.test.js`: 'deny-deletes': { 'receive.denyDeletes': 'true' }
1307- `test/probes/probes.test.js`: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository
1309Evidence:
1311- ply↔git: `test/push.test.js`
1312- ply↔Artifacts: validate-7b0c310f: `branch delete (CAS ok)`
1313- ply↔Artifacts: loadgen-phase6-plyw-20261025: `branch/delete`
1314- git↔Artifacts: loadgen-compat-20261024: `tag_push_delete/scratch/v2`
1315- ply↔git: `test/probes/probes.test.js`
1316- ply↔Artifacts: probes-20261114t2226-yyjq: `push.delete-ref#plain/art-ply`
1317- git↔Artifacts: probes-20261114t2226-yyjq: `push.delete-ref#plain/art-git`
1319#### `push.atomic`
1321atomic: several ref updates land together or not at all.
1323Ops: `src/push.ts` `push`, `src/receivecaps.ts` `pushPack`, `src/transfer.ts` `runTransfer`.
1325Tests:
1327- `test/push.test.js`: 'multi-atomic': t =>
1328- `test/push-pack.test.js`: atomic: checked against the advertisement, then sent; two refs land together
1329- `test/probes/probes.test.js`: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository
1331Evidence:
1333- ply↔git: `test/push-pack.test.js`
1334- git↔Artifacts: loadgen-compat-20261024: `atomic_push_multi_ref/scratch/v2`
1335- ply↔git: `test/probes/probes.test.js`
1336- ply↔Artifacts: probes-20261114t2226-yyjq: `push.atomic#all-land/art-ply`
1337- ply↔Artifacts: probes-20261114t2226-yyjq: `push.atomic#one-stale/art-ply`
1338- git↔Artifacts: probes-20261114t2226-yyjq: `push.atomic#all-land/art-git`
1339- git↔Artifacts: probes-20261114t2226-yyjq: `push.atomic#one-stale/art-git`
1341> The one-stale variant makes one command fail at the server: another writer moves its ref while the request is held.
1343#### `push.non-atomic-partial`
1345A non-atomic multi-ref push the server applies in part is push_partial, naming what landed.
1347Ops: `src/push.ts` `push`.
1349Tests:
1351- `test/push.test.js`: assert.equal(err.code, 'push_partial'
1352- `test/probes/probes.test.js`: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository
1354Evidence:
1356- ply↔git: `test/push.test.js`
1357- ply↔git: `test/probes/probes.test.js`
1358- ply↔Artifacts: probes-20261114t2226-yyjq: `push.non-atomic-partial#one-stale/art-ply`
1359- git↔Artifacts: probes-20261114t2226-yyjq: `push.non-atomic-partial#one-stale/art-git`
1361> Probed by a two-ref push while another writer moves one ref (src/probe-scenarios.ts). Per-check outcomes are in the private run record.
1363#### `push.report-status`
1365report-status: an unpack line (ok or a reason) and an ok or ng line per command, classified as landed, rejected, conflict or ambiguous.
1367Ops: `src/push.ts` `push`, `src/push.ts` `classifyReport`.
1369Tests:
1371- `test/space/push-ng.test.js`: push ng: cells observed from git
1372- `test/space/push-outcome.test.js`: The push-outcome enumerator
1373- `test/push.test.js`: push matrix: configs × hooks × commands × caps, parity with git push
1375Evidence:
1377- ply↔git: `test/push.test.js`
1378- ply↔Artifacts: validate-7b0c310f: `write: root commit (edit changes)`
1380> push-ng and push-outcome judge the class table over a fake transport; their git-observed cells are recorded bytes.
1382#### `push.report-status-v2`
1384report-status-v2: option lines after ok.
1386Ops: `src/push.ts` `push`.
1388Tests:
1390- `test/push.test.js`: reportV2: true
1392Evidence:
1394- ply↔git: `test/push.test.js`
1396> No Artifacts evidence: no recorded run says whether Artifacts advertises report-status-v2.
1398#### `push.sideband-hook-output`
1400side-band-64k on receive-pack: the report on band 1, hook output on band 2.
1402Ops: `src/push.ts` `push`.
1404Tests:
1406- `test/push.test.js`: hook stderr visible on band 2 when side-band is requested
1408Evidence:
1410- ply↔git: `test/push.test.js`
1412#### `push.push-options`
1414push-options: sent only when advertised; they reach the hook.
1416Ops: `src/push.ts` `push`, `src/receivecaps.ts` `pushPack`.
1418Tests:
1420- `test/push.test.js`: options reached the hook
1421- `test/push-pack.test.js`: push options: refused when not advertised, sent when they are
1423Evidence:
1425- ply↔git: `test/push.test.js`
1426- git↔Artifacts: loadgen-phase2-20261025: `push_options`
1428#### `push.hook-rejection`
1430A pre-receive or update hook that declines: ng with the hook's reason, ref unchanged.
1432Ops: `src/push.ts` `push`.
1434Tests:
1436- `test/push.test.js`: 'pre-receive-reject': ['pre-receive'
1438Evidence:
1440- ply↔git: `test/push.test.js`
1442> Artifacts runs no user hooks; this is reference-only by nature.
1444#### `push.ref-name-rules`
1446receive-pack's ref-name rules ("funny refname"): ply refuses before the wire exactly what receive-pack refuses, and also any name over 1024 bytes, which receive-pack accepts.
1448Ops: `src/push.ts` `push`.
1450Tests:
1452- `test/space/refname.test.js`: ref names: ply agrees with git check-ref-format and receive-pack on every cell
1453- `test/probes/wire.test.js`: reference: ${plan.id} meets its answer with every sender
1455Evidence:
1457- ply↔git: `test/space/refname.test.js`
1458- git↔Artifacts: loadgen-phase2-20261025: `invalid_ref_names`
1459- wire↔Artifacts: loadgen-phase4-hostile-write-20261025: `ref/dotdot`
1460- wire↔Artifacts: loadgen-phase4-hostile-write-20261025: `ref/control_char`
1461- wire↔Artifacts: loadgen-phase4-hostile-write-20261025: `ref/long_name`
1462- ply↔git: `test/probes/wire.test.js`
1463- ply↔Artifacts: wire-20261115t2116-1nam: `push.ref-name-rules#leading-dash/art-ply`
1464- ply↔Artifacts: wire-20261115t2116-1nam: `push.ref-name-rules#component-200/art-ply`
1465- ply↔Artifacts: wire-20261115t2116-1nam: `push.ref-name-rules#path-1000/art-ply`
1466- ply↔Artifacts: wire-20261115t2116-1nam: `push.ref-name-rules#component-300/art-ply`
1467- git↔Artifacts: wire-20261115t2116-1nam: `push.ref-name-rules#leading-dash/art-git`
1468- git↔Artifacts: wire-20261115t2116-1nam: `push.ref-name-rules#component-200/art-git`
1469- git↔Artifacts: wire-20261115t2116-1nam: `push.ref-name-rules#path-1000/art-git`
1470- git↔Artifacts: wire-20261115t2116-1nam: `push.ref-name-rules#component-300/art-git`
1471- git↔Artifacts: wire-20261115t2116-1nam: `push.ref-name-rules#path-4000/art-git`
1472- wire↔Artifacts: wire-20261115t2116-1nam: `push.ref-name-rules#dot-dot/art-raw`
1473- wire↔Artifacts: wire-20261115t2116-1nam: `push.ref-name-rules#at-brace/art-raw`
1474- wire↔Artifacts: wire-20261115t2116-1nam: `push.ref-name-rules#lock-suffix/art-raw`
1475- wire↔Artifacts: wire-20261115t2116-1nam: `push.ref-name-rules#control-char/art-raw`
1476- wire↔Artifacts: wire-20261115t2116-1nam: `push.ref-name-rules#del-char/art-raw`
1477- wire↔Artifacts: wire-20261115t2116-1nam: `push.ref-name-rules#space/art-raw`
1478- wire↔Artifacts: wire-20261115t2116-1nam: `push.ref-name-rules#colon/art-raw`
1479- wire↔Artifacts: wire-20261115t2116-1nam: `push.ref-name-rules#backslash/art-raw`
1480- wire↔Artifacts: wire-20261115t2116-1nam: `push.ref-name-rules#double-slash/art-raw`
1481- wire↔Artifacts: wire-20261115t2116-1nam: `push.ref-name-rules#trailing-slash/art-raw`
1482- wire↔Artifacts: wire-20261115t2116-1nam: `push.ref-name-rules#trailing-dot/art-raw`
1483- wire↔Artifacts: wire-20261115t2116-1nam: `push.ref-name-rules#dot-component/art-raw`
1484- wire↔Artifacts: wire-20261115t2116-1nam: `push.ref-name-rules#bare-head/art-raw`
1485- wire↔Artifacts: wire-20261115t2116-1nam: `push.ref-name-rules#refs-heads-at/art-raw`
1486- wire↔Artifacts: wire-20261115t2116-1nam: `push.ref-name-rules#refs-heads-head/art-raw`
1487- wire↔Artifacts: wire-20261115t2116-1nam: `push.ref-name-rules#path-4000/art-raw`
1488- wire↔Artifacts: wire-20261115t2116-1nam: `push.ref-name-rules#leading-dash/art-raw`
1489- wire↔Artifacts: wire-20261115t2116-1nam: `push.ref-name-rules#component-200/art-raw`
1490- wire↔Artifacts: wire-20261115t2116-1nam: `push.ref-name-rules#path-1000/art-raw`
1491- wire↔Artifacts: wire-20261115t2116-1nam: `push.ref-name-rules#component-300/art-raw`
1493> The wire plans send each refused name from a raw socket; stock git and ply refuse them before any request, so their Artifacts checks for those names say nothing about the server and are not cited. ply's 1024-byte cap (src/validate.ts) refuses the 4000-byte name receive-pack and stock git push.
1495#### `push.ref-to-missing-object-refused`
1497receive-pack refuses a command whose new id is in neither the pack nor the repository (missing necessary objects), moves no ref, and still serves the repository fsck-clean.
1499Ops: `src/receivecaps.ts` `pushPack`.
1501Tests:
1503- `test/probes/probes.test.js`: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository
1505Evidence:
1507- ply↔git: `test/probes/probes.test.js`
1508- ply↔Artifacts: probes-20261115t1926-gfhc: `push.ref-to-missing-object-refused#not-in-pack-or-repo/art-ply`
1509- ply↔Artifacts: probes-20261115t2113-phhp: `push.ref-to-missing-object-refused#tag-of-missing-object/art-ply`
1511> Stock git refuses such a push client side, so only ply (pushPack with a pack of no objects) sends it.
1513#### `push.size-limits`
1515A push over the server's object or pack size cap is refused with a report ply classifies as limit_exceeded.
1517Ops: `src/push.ts` `push`, `src/receivecaps.ts` `pushPack`.
1519Tests:
1521- `test/push-unpack-host.test.js`: Artifacts 64 MiB cap is limit_exceeded with got/max in bytes, not push_rejected or ambiguous
1522- `test/probes/probes.test.js`: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository
1524Evidence:
1526- git↔Artifacts: loadgen-phase2-20261025: `blob_push_ceiling`
1527- git↔Artifacts: loadgen-compat-20261024: `large_blob_push_24m/scratch/v2`
1528- wire↔Artifacts: loadgen-phase4-hostile-write-20261025: `pack/zlib_bomb_40m`
1529- ply↔git: `test/probes/probes.test.js`
1530- ply↔Artifacts: probes-20261114t2226-yyjq: `push.size-limits#pack-over-cap/art-ply`
1531- git↔Artifacts: probes-20261114t2226-yyjq: `push.size-limits#pack-over-cap/art-git`
1533> A 66 MiB pack against a 64 MiB cap. ply classifies the server's stated cap as limit_exceeded; git http-backend (receive.maxInputSize) refuses with `unpacker error`, its reason on band 2 only, which ply reports as push_rejected: an expected difference, src/probe-allow.ts.
1535#### `push.many-ref-updates`
1537One push carrying many ref updates.
1539Ops: `src/push.ts` `push`.
1541Tests:
1543- `test/probes/probes.test.js`: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository
1545Evidence:
1547- git↔Artifacts: loadgen-phase2-20261025: `many_refs_5000`
1548- wire↔Artifacts: loadgen-phase4-hostile-write-20261025: `ref/fifty_updates`
1549- ply↔git: `test/probes/probes.test.js`
1550- ply↔Artifacts: probes-20261114t2226-yyjq: `push.many-ref-updates#fifty-creates/art-ply`
1551- git↔Artifacts: probes-20261114t2226-yyjq: `push.many-ref-updates#fifty-creates/art-git`
1553> The probe sends 50 creates in one push; no other test sends more than a few.
1555#### `push.signed-push`
1557push-cert (signed pushes).
1559Unsupported: ply signs commits (src/sign.ts) but never sends a push certificate.
1561Observed:
1563- git↔Artifacts: loadgen-phase2-20261025: `signed_push`
1565#### `push.from-shallow-clone`
1567A push from a shallow clone: when the server holds the boundary commit the push lands; when it lacks the history below the boundary the push is refused and no ref moves.
1569Ops: `src/push.ts` `push`.
1571Tests:
1573- `test/probes/probes.test.js`: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository
1575Evidence:
1577- ply↔git: `test/probes/probes.test.js`
1578- ply↔Artifacts: probes-20261114t2226-yyjq: `push.from-shallow-clone#boundary-held/art-ply`
1579- git↔Artifacts: probes-20261114t2226-yyjq: `push.from-shallow-clone#boundary-held/art-git`
1580- ply↔Artifacts: probes-20261114t2226-yyjq: `push.from-shallow-clone#history-missing/art-ply`
1581- git↔Artifacts: probes-20261114t2226-yyjq: `push.from-shallow-clone#shallow-update/art-git`
1583> ply keeps no shallow state; its form of the push is the same objects without the history below the boundary.
1585> The stock git push into a repository without the boundary history is compared against git http-backend with receive.shallowUpdate=true.
1587#### `push.from-partial-clone`
1589A push from a blob:none partial clone sends only the new objects, including a tree that names a blob the client never fetched, and lands.
1591Ops: `src/fetchpack.ts` `fetchPack`, `src/push.ts` `push`.
1593Tests:
1595- `test/probes/probes.test.js`: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository
1597Evidence:
1599- ply↔git: `test/probes/probes.test.js`
1600- ply↔Artifacts: probes-20261114t2226-yyjq: `push.from-partial-clone#blob-none/art-ply`
1601- git↔Artifacts: probes-20261114t2226-yyjq: `push.from-partial-clone#blob-none/art-git`
1602- ply↔Artifacts: probes-20261114t2226-yyjq: `push.from-partial-clone#reuse-absent-blob/art-ply`
1603- git↔Artifacts: probes-20261114t2226-yyjq: `push.from-partial-clone#reuse-absent-blob/art-git`
1605### Concurrent updates and stale refs (`concurrency`, 7)
1607| id | status | evidence | ply ops | tests |
1608|---|---|---|---|---:|
1609| `concurrency.stale-old-oid` | verified | ply↔git, ply↔Artifacts, git↔Artifacts | `push`, `pushPack`, `editFile` | 4 |
1610| `concurrency.concurrent-writers` | verified | ply↔git, ply↔Artifacts, git↔Artifacts | `editFile`, `push` | 3 |
1611| `concurrency.ref-created-between-read-and-push` | verified | ply↔git, ply↔Artifacts, git↔Artifacts | `push`, `createBranch`, `createTag`, `commitChanges` | 3 |
1612| `concurrency.ref-deleted-between-read-and-push` | verified | ply↔git, ply↔Artifacts, git↔Artifacts | `push`, `commitChanges` | 2 |
1613| `concurrency.read-after-write` | verified | ply↔Artifacts, git↔Artifacts | `lsRefs`, `readFile`, `readCommit` | 1 |
1614| `concurrency.empty-report-under-contention` | verified | ply↔git, ply↔Artifacts, git↔Artifacts | `push`, `classifyReport` | 3 |
1615| `concurrency.two-transfer-runners` | verified | ply↔git | `runTransfer` | 1 |
1617#### `concurrency.stale-old-oid`
1619A push whose old id is no longer the ref's value is refused (compare-and-swap) and the ref is unchanged.
1621Ops: `src/push.ts` `push`, `src/receivecaps.ts` `pushPack`, `src/edit.ts` `editFile`.
1623Tests:
1625- `test/push.test.js`: 'stale-old': t =>
1626- `test/push-pack.test.js`: a stale old oid is cas_conflict, as push reports it
1627- `test/custom-exchange.test.js`: receive-pack refuses a command (stale old id)
1628- `test/probes/probes.test.js`: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository
1630Evidence:
1632- ply↔git: `test/push.test.js`
1633- ply↔git: `test/push-pack.test.js`
1634- git↔Artifacts: loadgen-phase2-20261025: `force_with_lease_stale`
1635- ply↔git: `test/probes/probes.test.js`
1636- ply↔Artifacts: probes-20261114t2226-yyjq: `concurrency.stale-old-oid#race/art-ply`
1637- ply↔Artifacts: probes-20261114t2226-yyjq: `concurrency.stale-old-oid#direct/art-ply`
1638- git↔Artifacts: probes-20261114t2226-yyjq: `concurrency.stale-old-oid#race/art-git`
1639- ply↔Artifacts: probes-20261114t2226-yyjq: `concurrency.stale-old-oid#delete-vs-update/art-ply`
1640- git↔Artifacts: probes-20261114t2226-yyjq: `concurrency.stale-old-oid#delete-vs-update/art-git`
1642> The validate CAS checks (stale head, stale delete) are refused by ply-web from ls-refs, before any push. The probe run sends the stale old id to Artifacts itself: directly from ply, and from a race (another writer moves the ref while the receive-pack request is held) from ply and stock git.
1644#### `concurrency.concurrent-writers`
1646Concurrent writers on one ref: one wins each round, the rest are refused as stale and retry; nothing is lost.
1648Ops: `src/edit.ts` `editFile`, `src/push.ts` `push`.
1650Tests:
1652- `test/probes/probes.test.js`: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository
1653- `test/concurrency.test.js`: concurrent CAS writers converge; conflicts are observed and retried, never lost
1654- `test/edit-race-f34.test.js`: same-file edit race ×1000 attempts: only ok and cas_conflict
1656Evidence:
1658- ply↔git: `test/probes/probes.test.js`
1659- ply↔git: `test/concurrency.test.js`
1660- ply↔git: `test/edit-race-f34.test.js`
1661- ply↔Artifacts: loadgen-phase6-plyw-20261025: `edit/race_same_file`
1662- ply↔Artifacts: loadgen-phase6-plyw-20261025: `edit/race_diff_files`
1663- git↔Artifacts: loadgen-phase2-20261025: `fetch_push_race`
1664- ply↔Artifacts: probes-20261114t2226-yyjq: `concurrency.concurrent-writers#create-vs-create/art-ply`
1665- git↔Artifacts: probes-20261114t2226-yyjq: `concurrency.concurrent-writers#create-vs-create/art-git`
1666- ply↔Artifacts: probes-20261114t2226-yyjq: `concurrency.concurrent-writers#delete-vs-update/art-ply`
1667- git↔Artifacts: probes-20261114t2226-yyjq: `concurrency.concurrent-writers#delete-vs-update/art-git`
1669#### `concurrency.ref-created-between-read-and-push`
1671Another writer creates the target ref between ply's ls-refs and its receive-pack: the create is refused, naming the winner.
1673Ops: `src/push.ts` `push`, `src/refops.ts` `createBranch`, `src/refops.ts` `createTag`, `src/changes.ts` `commitChanges`.
1675Tests:
1677- `test/e2e-customer.test.js`: createBranch and createTag lose a race to a ref made between ls-refs and receive-pack: cas_conflict naming the winner
1678- `test/changes-create-race.test.js`: commitChanges creating a ref from a base
1679- `test/probes/probes.test.js`: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository
1681Evidence:
1683- ply↔git: `test/e2e-customer.test.js`
1684- ply↔git: `test/probes/probes.test.js`
1685- ply↔Artifacts: probes-20261114t2226-yyjq: `concurrency.ref-created-between-read-and-push#race/art-ply`
1686- git↔Artifacts: probes-20261114t2226-yyjq: `concurrency.ref-created-between-read-and-push#race/art-git`
1688> validate's duplicate-branch check is refused by ply-web from ls-refs, before receive-pack; the probe run's race reaches receive-pack.
1690#### `concurrency.ref-deleted-between-read-and-push`
1692Another writer deletes the target ref between ply's read and its push.
1694Ops: `src/push.ts` `push`, `src/changes.ts` `commitChanges`.
1696Tests:
1698- `test/changes-delete-race.test.js`: head pinned to the base: a target deleted mid-call is cas_conflict and stays deleted
1699- `test/probes/probes.test.js`: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository
1701Evidence:
1703- ply↔git: `test/changes-delete-race.test.js`
1704- ply↔git: `test/probes/probes.test.js`
1705- ply↔Artifacts: probes-20261114t2226-yyjq: `concurrency.ref-deleted-between-read-and-push#race/art-ply`
1706- git↔Artifacts: probes-20261114t2226-yyjq: `concurrency.ref-deleted-between-read-and-push#race/art-git`
1708#### `concurrency.read-after-write`
1710A landed push is visible at once to ls-refs and to fetch (no stale advertisement after a push).
1712Ops: `src/lsrefs.ts` `lsRefs`, `src/read.ts` `readFile`, `src/read.ts` `readCommit`.
1714Tests:
1716- `test/transfer.test.js`: ls-refs that lags a push: settled by reading again, not by sending again
1718Evidence:
1720- ply↔Artifacts: validate-7b0c310f: `freshness: refs-after-write`
1721- ply↔Artifacts: validate-7b0c310f: `freshness: read-after-write README`
1722- ply↔Artifacts: validate-7b0c310f: `freshness: commit-after-write`
1723- git↔Artifacts: loadgen-phase2-20261025: `visibility_latency`
1725> transfer.test.js emulates a lagging ls-refs with a proxy; the reference server never lags, so there is no reference evidence.
1727#### `concurrency.empty-report-under-contention`
1729A receive-pack 200 that carries no report (no unpack or ref lines), whether an empty body or only a band-3 fatal such as the busy refusal Artifacts sends to concurrent same-repo pushes, is ambiguous, never landed; the server applied nothing for it.
1731Ops: `src/push.ts` `push`, `src/push.ts` `classifyReport`.
1733Tests:
1735- `test/push-unpack-host.test.js`: an empty receive-pack report stays ambiguous (concurrent same-repo 200 with no unpack/ref lines)
1736- `test/mutant-kill.test.js`: push outcome (SAFETY.md I36): the exact report shapes, the decision, and the fields the enumerator does not compare
1737- `test/probes/probes.test.js`: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository
1739Evidence:
1741- ply↔git: `test/probes/probes.test.js`
1742- ply↔Artifacts: probes-20261114t2226-yyjq: `concurrency.empty-report-under-contention#distinct-refs/art-ply`
1743- ply↔Artifacts: probes-20261114t2226-yyjq: `concurrency.empty-report-under-contention#same-ref/art-ply`
1744- git↔Artifacts: probes-20261114t2226-yyjq: `concurrency.empty-report-under-contention#distinct-refs/art-git`
1745- git↔Artifacts: probes-20261114t2226-yyjq: `concurrency.empty-report-under-contention#same-ref/art-git`
1746- ply↔Artifacts: probes-20261114t2226-yyjq: `concurrency.empty-report-under-contention#retry-after-busy/art-ply`
1747- git↔Artifacts: probes-20261114t2226-yyjq: `concurrency.empty-report-under-contention#retry-after-busy/art-git`
1749> Probed with 8 concurrent pushes to one repository (8 distinct refs; one ref from 8 contenders); every push a client called landed is checked against the refs stock git reads back. Per-check outcomes are in the private run record.
1751> Observed shape on Artifacts (probes run probes-20261114t1745-5jxl): HTTP 200 whose body is a single band-3 fatal (busy) and no report-status, for distinct refs as well as one ref; the refs read back show none of those pushes applied. Stock git reports it as the remote hanging up (exit 128).
1753> Retry probe (run probes-20261114t1837-53b4): each push that did not land is sent again alone with the same zero old id, which the server would refuse had the first attempt been applied; per-check outcomes are in the private run record.
1755#### `concurrency.two-transfer-runners`
1757Two resumable transfers of one plan at once both finish with the planned head; each refused step is settled by reading refs.
1759Ops: `src/transfer.ts` `runTransfer`.
1761Tests:
1763- `test/transfer-outcomes.test.js`: two runners on one plan at once, 20 times: both end done; the destination is the planned head
1765Evidence:
1767- ply↔git: `test/transfer-outcomes.test.js`
1769> No Artifacts evidence.
1771### Tags (lightweight and annotated) (`tags`, 6)
1773| id | status | evidence | ply ops | tests |
1774|---|---|---|---|---:|
1775| `tags.lightweight-create` | verified | ply↔git, ply↔Artifacts, git↔Artifacts | `push`, `createTag` | 2 |
1776| `tags.annotated-create` | verified | ply↔git, ply↔Artifacts, git↔Artifacts | `push`, `createTag` | 2 |
1777| `tags.delete` | verified | ply↔git, ply↔Artifacts, git↔Artifacts | `push`, `deleteTag` | 2 |
1778| `tags.move-existing-tag` | verified | ply↔git, ply↔Artifacts, git↔Artifacts | `push` | 1 |
1779| `tags.peel-chain` | verified | ply↔git, ply↔Artifacts, git↔Artifacts | `readFile`, `createBranch` | 3 |
1780| `tags.many-tags` | verified | ply↔git, ply↔Artifacts, git↔Artifacts | `lsRefs` | 1 |
1782#### `tags.lightweight-create`
1784A lightweight tag is a ref create under refs/tags pointing at a commit.
1786Ops: `src/push.ts` `push`, `src/refops.ts` `createTag`.
1788Tests:
1790- `test/e2e-customer.test.js`: createTag: lightweight and annotated (as git tag -a writes it), refusals
1791- `test/probes/probes.test.js`: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository
1793Evidence:
1795- ply↔git: `test/e2e-customer.test.js`
1796- ply↔Artifacts: validate-7b0c310f: `tag lightweight`
1797- ply↔git: `test/probes/probes.test.js`
1798- ply↔Artifacts: probes-20261114t2226-yyjq: `tags.lightweight-create#plain/art-ply`
1799- git↔Artifacts: probes-20261114t2226-yyjq: `tags.lightweight-create#plain/art-git`
1801#### `tags.annotated-create`
1803An annotated tag pushes a tag object with its ref, byte-equal to git tag -a.
1805Ops: `src/push.ts` `push`, `src/refops.ts` `createTag`.
1807Tests:
1809- `test/e2e-customer.test.js`: createTag: lightweight and annotated (as git tag -a writes it), refusals
1810- `test/probes/probes.test.js`: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository
1812Evidence:
1814- ply↔git: `test/e2e-customer.test.js`
1815- ply↔Artifacts: validate-7b0c310f: `tag annotated`
1816- git↔Artifacts: validate-7b0c310f: `git judge: fsck --strict, refs, history`
1817- ply↔git: `test/probes/probes.test.js`
1818- ply↔Artifacts: probes-20261114t2226-yyjq: `tags.annotated-create#plain/art-ply`
1819- git↔Artifacts: probes-20261114t2226-yyjq: `tags.annotated-create#plain/art-git`
1821#### `tags.delete`
1823A tag delete with the expected old id; a stale expected id is refused.
1825Ops: `src/push.ts` `push`, `src/refops.ts` `deleteTag`.
1827Tests:
1829- `test/e2e-customer.test.js`: deleteTag
1830- `test/probes/probes.test.js`: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository
1832Evidence:
1834- ply↔git: `test/e2e-customer.test.js`
1835- ply↔Artifacts: validate-7b0c310f: `tag delete (CAS) + stale delete -> 409`
1836- git↔Artifacts: loadgen-compat-20261024: `tag_push_delete/scratch/v2`
1837- ply↔git: `test/probes/probes.test.js`
1838- ply↔Artifacts: probes-20261114t2226-yyjq: `tags.delete#plain/art-ply`
1839- git↔Artifacts: probes-20261114t2226-yyjq: `tags.delete#plain/art-git`
1840- ply↔Artifacts: probes-20261115t2113-phhp: `tags.delete#annotated/art-ply`
1841- git↔Artifacts: probes-20261115t2113-phhp: `tags.delete#annotated/art-git`
1843> The stale half of the validate check is refused by ply-web from ls-refs, not by Artifacts.
1845#### `tags.move-existing-tag`
1847An existing tag ref moved with its current old id (a non-fast-forward lightweight move, or one annotated tag replaced by another) is an ordinary ref update.
1849Ops: `src/push.ts` `push`.
1851Tests:
1853- `test/probes/probes.test.js`: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository
1855Evidence:
1857- ply↔git: `test/probes/probes.test.js`
1858- ply↔Artifacts: probes-20261115t2113-phhp: `tags.move-existing-tag#non-fast-forward/art-ply`
1859- git↔Artifacts: probes-20261115t2113-phhp: `tags.move-existing-tag#non-fast-forward/art-git`
1860- ply↔Artifacts: probes-20261115t2113-phhp: `tags.move-existing-tag#annotated-to-other-tag/art-ply`
1861- git↔Artifacts: probes-20261115t2113-phhp: `tags.move-existing-tag#annotated-to-other-tag/art-git`
1863#### `tags.peel-chain`
1865A ref given as an annotated tag (or a tag of a tag) is peeled to its commit for reads and branch creation.
1867Ops: `src/read.ts` `readFile`, `src/refops.ts` `createBranch`.
1869Tests:
1871- `test/e2e-customer.test.js`: createBranch from a branch name, a short name, a peeled annotated tag
1872- `test/read.test.js`: readFile bytes == git show &lt;ref>:&lt;path> for every blob path and every ref form
1873- `test/probes/probes.test.js`: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository
1875Evidence:
1877- ply↔git: `test/read.test.js`
1878- ply↔Artifacts: validate-7b0c310f: `read: tag name resolves (ref=v1)`
1879- ply↔git: `test/probes/probes.test.js`
1880- ply↔Artifacts: probes-20261115t2113-phhp: `tags.peel-chain#tag-of-tag/art-ply`
1881- git↔Artifacts: probes-20261115t2113-phhp: `tags.peel-chain#tag-of-tag/art-git`
1883#### `tags.many-tags`
1885A repository with many tags: listing, include-tag and fetch stay correct.
1887Ops: `src/lsrefs.ts` `lsRefs`.
1889Tests:
1891- `test/probes/wire.test.js`: reference: ${plan.id} meets its answer with every sender
1893Evidence:
1895- git↔Artifacts: loadgen-phase2-20261025: `shape/manytags`
1896- ply↔git: `test/probes/wire.test.js`
1897- ply↔Artifacts: wire-20261115t2116-1nam: `refs.ls-refs-listing#two-thousand-refs/art-ply`
1899> ply lists a 500-tag repository (2001 refs) in the wire plans; include-tag and fetch across many tags are checked only with stock git.
1901### Merges and rebases as ancestry exercisers (`ancestry`, 7)
1903| id | status | evidence | ply ops | tests |
1904|---|---|---|---|---:|
1905| `ancestry.merge-base-search` | verified | ply↔git, ply↔Artifacts | `mergeBase` | 2 |
1906| `ancestry.merge-commit-push` | verified | ply↔git, ply↔Artifacts, git↔Artifacts | `push`, `mergeBranch` | 2 |
1907| `ancestry.fast-forward-and-up-to-date` | verified | ply↔git, ply↔Artifacts | `mergeBranch` | 1 |
1908| `ancestry.rebase-chain` | verified | ply↔git, ply↔Artifacts | `rebaseBranch` | 1 |
1909| `ancestry.cherry-pick-revert` | verified | ply↔git, ply↔Artifacts | `cherryPick`, `revertCommit` | 2 |
1910| `ancestry.log-walk` | verified | ply↔git, ply↔Artifacts | `readLog` | 1 |
1911| `ancestry.cut-graph` | implemented | — | `mergeBase`, `mergeBranch` | 1 |
1913#### `ancestry.merge-base-search`
1915Merge bases found by shallow windows over the server (deepen), equal to git merge-base --all within the cap.
1917Ops: `src/merge.ts` `mergeBase`.
1919Tests:
1921- `test/mergebase-space.test.js`: merge-base outcome space: position × multiplicity × settled × server × op, every cell equal to git
1922- `test/space/merge-depth.test.js`: merge-base cap: every relation × length × cap against git merge-base --all
1924Evidence:
1926- ply↔git: `test/mergebase-space.test.js`
1927- ply↔git: `test/space/merge-depth.test.js`
1928- ply↔Artifacts: validate-7b0c310f: `merge feat into main (true merge)`
1930#### `ancestry.merge-commit-push`
1932A two-parent merge commit pushed as a fast-forward of the target; history visible to git as a merge.
1934Ops: `src/push.ts` `push`, `src/merge.ts` `mergeBranch`.
1936Tests:
1938- `test/merge.test.js`: outcomes: up-to-date, fast-forward, ff-only refusal, no-ff merge commit, clean merge, conflict
1939- `test/probes/probes.test.js`: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository
1941Evidence:
1943- ply↔git: `test/merge.test.js`
1944- ply↔Artifacts: validate-7b0c310f: `merge feat into main (true merge)`
1945- ply↔Artifacts: loadgen-phase6-plyw-20261025: `merge/true`
1946- ply↔Artifacts: loadgen-phase6-plyw-20261025: `merge/verify`
1947- git↔Artifacts: loadgen-phase2-20261025: `shape/merges`
1948- ply↔git: `test/probes/probes.test.js`
1949- ply↔Artifacts: probes-20261114t2226-yyjq: `ancestry.merge-commit-push#two-parents/art-ply`
1950- git↔Artifacts: probes-20261114t2226-yyjq: `ancestry.merge-commit-push#two-parents/art-git`
1952#### `ancestry.fast-forward-and-up-to-date`
1954Merging an ancestor is up to date (no push); merging a descendant fast-forwards the ref.
1956Ops: `src/merge.ts` `mergeBranch`.
1958Tests:
1960- `test/merge.test.js`: outcomes: up-to-date, fast-forward, ff-only refusal, no-ff merge commit, clean merge, conflict
1962Evidence:
1964- ply↔git: `test/merge.test.js`
1965- ply↔Artifacts: validate-7b0c310f: `merge again -> up_to_date`
1966- ply↔Artifacts: validate-7b0c310f: `merge fast-forward (ff branch)`
1967- ply↔Artifacts: loadgen-phase6-plyw-20261025: `merge/ff`
1969#### `ancestry.rebase-chain`
1971A chain of commits replayed onto a moved base, pushed with the old tip as the expected id.
1973Ops: `src/rebase.ts` `rebaseBranch`.
1975Tests:
1977- `test/rebase.test.js`: rebase: three commits onto a moved main
1979Evidence:
1981- ply↔git: `test/rebase.test.js`
1982- ply↔Artifacts: validate-7b0c310f: `rebase topic onto main`
1984#### `ancestry.cherry-pick-revert`
1986Cherry-pick and revert: one new commit whose tree equals git's; empty results stop or keep as git does.
1988Ops: `src/rebase.ts` `cherryPick`, `src/rebase.ts` `revertCommit`.
1990Tests:
1992- `test/rebase.test.js`: cherry-pick and revert: trees equal git
1993- `test/pick-empty.test.js`: cherry-pick --keep-redundant-commits and --allow-empty: commit bytes match git, stop writes nothing
1995Evidence:
1997- ply↔git: `test/rebase.test.js`
1998- ply↔Artifacts: validate-7b0c310f: `cherry-pick f2 onto main`
1999- ply↔Artifacts: validate-7b0c310f: `cherry-pick again -> empty noop`
2000- ply↔Artifacts: validate-7b0c310f: `revert cherry-pick on main`
2002#### `ancestry.log-walk`
2004First-parent history read in shallow windows equals git log --first-parent.
2006Ops: `src/log.ts` `readLog`.
2008Tests:
2010- `test/log.test.js`: readLog: server × shape × limit × behaviour, every cell against git
2012Evidence:
2014- ply↔git: `test/log.test.js`
2015- ply↔Artifacts: loadgen-phase6-plyw-20261025: `commit/deep`
2017> validate's log checks go through the viewer, which judges Artifacts history with git log, not readLog.
2019#### `ancestry.cut-graph`
2021A server that withholds ancestors without saying shallow: ply fails closed, nothing pushed.
2023Ops: `src/merge.ts` `mergeBase`, `src/merge.ts` `mergeBranch`.
2025Tests:
2027- `test/adversarial.test.js`: #18 merge base over a cut graph: a server that withholds ancestors without a shallow line fails closed (pack_corrupt), nothing pushed
2029> A proxy cuts the graph; no git or Artifacts server ever behaves this way on purpose.
2031### Error conditions (auth, not found, limits, corrupt input) (`errors`, 7)
2033| id | status | evidence | ply ops | tests |
2034|---|---|---|---|---:|
2035| `errors.auth-missing-or-wrong` | verified | ply↔git, ply↔Artifacts, git↔Artifacts, wire↔Artifacts | `createTransport`, `lsRefs`, `push` | 2 |
2036| `errors.receive-pack-forbidden` | verified | ply↔git, ply↔Artifacts, git↔Artifacts | `push` | 1 |
2037| `errors.repository-not-found` | verified | ply↔Artifacts | `lsRefs`, `discover` | 1 |
2038| `errors.http-status-classes` | verified | ply↔Artifacts, git↔Artifacts, wire↔Artifacts | `createTransport`, `fetchPack`, `push` | 2 |
2039| `errors.err-pkt-line` | verified | ply↔git | `lsRefs`, `fetchPack` | 3 |
2040| `errors.not-git-response` | implemented | — | `createTransport` | 2 |
2041| `errors.malformed-requests-to-server` | unsupported (observed) | wire↔Artifacts | — | 0 |
2043#### `errors.auth-missing-or-wrong`
2045A missing or wrong credential is 401 and a typed auth error; nothing lands.
2047Ops: `src/http.ts` `createTransport`, `src/lsrefs.ts` `lsRefs`, `src/push.ts` `push`.
2049Tests:
2051- `test/custom-exchange.test.js`: wrong credential: auth (401), typed, thrown from the iteration
2052- `test/adversarial.test.js`: I6e the credential product: every source × user × password cell gets its stated header or typed refusal, equal to git where git has the input, and leaks nothing
2054Evidence:
2056- ply↔git: `test/adversarial.test.js`
2057- ply↔Artifacts: validate-7b0c310f: `auth: wrong bearer -> 401`
2058- ply↔Artifacts: validate-7b0c310f: `auth: revoked Git-Token (auto-minted) -> upstream 403 typed`
2059- ply↔Artifacts: loadgen-phase6-plyw-20261025: `err/bad_git_token`
2060- wire↔Artifacts: loadgen-phase4-hostile-20261025: `auth/missing`
2061- wire↔Artifacts: loadgen-phase4-hostile-20261025: `auth/garbage_header`
2062- git↔Artifacts: loadgen-phase2-20261025: `auth_paths`
2064> validate's 401 checks are ply-web's own bearer; only the revoked Git-Token check reaches Artifacts' auth through ply.
2066#### `errors.receive-pack-forbidden`
2068A read-only credential pushing: 403 on receive-pack (advertisement or POST) is auth, and no ref moves.
2070Ops: `src/push.ts` `push`.
2072Tests:
2074- `test/adversarial.test.js`: receive-pack refused for this caller (403 on its POST and on its advertisement) is auth, and the ref did not move (#144)
2076Evidence:
2078- ply↔git: `test/adversarial.test.js`
2079- ply↔Artifacts: validate-7b0c310f: `push rejected path (read-scoped token write)`
2080- git↔Artifacts: loadgen-phase2-20261025: `read_only_token_push`
2082#### `errors.repository-not-found`
2084A repository that does not exist: the advertisement answers 404, typed not_found.
2086Ops: `src/lsrefs.ts` `lsRefs`, `src/discover.ts` `discover`.
2088Tests:
2090- `test/adversarial.test.js`: HTTP-level faults at every stage: statuses, non-git bodies, stall, drop, empty
2092Evidence:
2094- ply↔Artifacts: loadgen-phase6-plyw-20261025: `err/no_repo`
2096> The 404 class is tested only with injected statuses; git http-backend's own 404 for a missing repository is not cited by any test.
2098#### `errors.http-status-classes`
2100Statuses 4xx/5xx/429 at each stage map to ply's typed classes, and a refused optional feature is not retried for them.
2102Ops: `src/http.ts` `createTransport`, `src/fetchpack.ts` `fetchPack`, `src/push.ts` `push`.
2104Tests:
2106- `test/adversarial.test.js`: HTTP-level faults at every stage: statuses, non-git bodies, stall, drop, empty
2107- `test/fetchobject-deepen-refusal.test.js`: never asked again: 401, 403, 404, 429 and 500 stand as they are, with no advertisement read
2109Evidence:
2111- ply↔Artifacts: wire-20261115t2038-ee4x: `errors.http-status-classes#no-credential/art-ply`
2112- ply↔Artifacts: wire-20261115t2038-ee4x: `errors.http-status-classes#bogus-token/art-ply`
2113- ply↔Artifacts: wire-20261115t2038-ee4x: `errors.http-status-classes#revoked-token/art-ply`
2114- ply↔Artifacts: wire-20261115t2038-ee4x: `errors.http-status-classes#missing-repo/art-ply`
2115- wire↔Artifacts: wire-20261115t2038-ee4x: `errors.http-status-classes#no-credential/art-raw`
2116- wire↔Artifacts: wire-20261115t2038-ee4x: `errors.http-status-classes#no-credential/art-curl`
2117- git↔Artifacts: wire-20261115t2038-ee4x: `errors.http-status-classes#no-credential/art-git`
2118- wire↔Artifacts: wire-20261115t2038-ee4x: `errors.http-status-classes#bogus-token/art-raw`
2119- wire↔Artifacts: wire-20261115t2038-ee4x: `errors.http-status-classes#bogus-token/art-curl`
2120- git↔Artifacts: wire-20261115t2038-ee4x: `errors.http-status-classes#bogus-token/art-git`
2121- wire↔Artifacts: wire-20261115t2038-ee4x: `errors.http-status-classes#revoked-token/art-raw`
2122- wire↔Artifacts: wire-20261115t2038-ee4x: `errors.http-status-classes#revoked-token/art-curl`
2123- git↔Artifacts: wire-20261115t2038-ee4x: `errors.http-status-classes#revoked-token/art-git`
2124- wire↔Artifacts: wire-20261115t2038-ee4x: `errors.http-status-classes#missing-repo/art-raw`
2125- wire↔Artifacts: wire-20261115t2038-ee4x: `errors.http-status-classes#missing-repo/art-curl`
2126- git↔Artifacts: wire-20261115t2038-ee4x: `errors.http-status-classes#missing-repo/art-git`
2128> The wire run checks the info/refs GET with no credential, an unminted token, a revoked token and a repository-scoped token on a path it does not cover, from ply, stock git, curl and a raw request. No recorded run checks what Artifacts sends under rate limiting or a 5xx.
2130#### `errors.err-pkt-line`
2132An ERR pkt-line anywhere in a response is a typed remote error carrying the scrubbed message.
2134Ops: `src/lsrefs.ts` `lsRefs`, `src/fetchpack.ts` `fetchPack`.
2136Tests:
2138- `test/mutant-kill-tree.test.js`: ERR upload-pack: not our ref x
2139- `test/adversarial.test.js`: I6b a credential echoed by the server reaches no error (any field) and no span: ERR, band 2/3, ng, hook output × 4 auth forms
2140- `test/err-pkt-git.test.js`: real git ERR on a fetch of an id no one holds: the bytes carry ERR, ply says remote_error not_our_ref
2142Evidence:
2144- ply↔git: `test/err-pkt-git.test.js`
2146> Real ERR: git http-backend's `ERR upload-pack: not our ref &lt;id>` on a fetch of an unknown id (captured as written; also probe fetch.want-unreachable-or-unknown#phantom), which ply reports as remote_error, reason not_our_ref. ERR at other stages (advertisement, ls-refs) is injected only.
2148#### `errors.not-git-response`
2150A 200 that is not git (HTML, wrong content type) is not_git, never parsed as protocol.
2152Ops: `src/http.ts` `createTransport`.
2154Tests:
2156- `test/custom-exchange.test.js`: a server that is not git (HTML 200) is not_git
2157- `test/http-options.test.js`: the advertisement: its GET asks redirect manual; a foreign content type is not_git
2159#### `errors.malformed-requests-to-server`
2161How the server answers malformed requests (bad pkt-line lengths, misplaced delimiters, unknown commands and capabilities).
2163Unsupported: ply only writes well-formed requests; it has no mode that sends malformed ones.
2165Observed:
2167- wire↔Artifacts: loadgen-phase4-hostile-20261025: `pkt/nonhex_length`
2168- wire↔Artifacts: loadgen-phase4-hostile-20261025: `pkt/giant_length_claim`
2169- wire↔Artifacts: loadgen-phase4-hostile-20261025: `pkt/missing_flush`
2170- wire↔Artifacts: loadgen-phase4-hostile-20261025: `proto/v2_unknown_command`
2171- wire↔Artifacts: loadgen-phase4-hostile-20261025: `proto/unknown_capability`
2172- wire↔Artifacts: wire-20261115t2038-ee4x: `errors.malformed-requests-to-server#nonhex-length/art-raw`
2173- wire↔Artifacts: wire-20261115t2038-ee4x: `errors.malformed-requests-to-server#nonhex-length/art-curl`
2174- wire↔Artifacts: wire-20261115t2038-ee4x: `errors.malformed-requests-to-server#oversized-length/art-raw`
2175- wire↔Artifacts: wire-20261115t2038-ee4x: `errors.malformed-requests-to-server#oversized-length/art-curl`
2176- wire↔Artifacts: wire-20261115t2038-ee4x: `errors.malformed-requests-to-server#missing-flush/art-raw`
2177- wire↔Artifacts: wire-20261115t2038-ee4x: `errors.malformed-requests-to-server#missing-flush/art-curl`
2178- wire↔Artifacts: wire-20261115t2038-ee4x: `errors.malformed-requests-to-server#unknown-command/art-raw`
2179- wire↔Artifacts: wire-20261115t2038-ee4x: `errors.malformed-requests-to-server#unknown-command/art-curl`
2180- wire↔Artifacts: wire-20261115t2038-ee4x: `errors.malformed-requests-to-server#wrong-content-type/art-raw`
2181- wire↔Artifacts: wire-20261115t2038-ee4x: `errors.malformed-requests-to-server#wrong-content-type/art-curl`
2182- wire↔Artifacts: wire-20261115t2038-ee4x: `errors.malformed-requests-to-server#bad-service/art-raw`
2183- wire↔Artifacts: wire-20261115t2038-ee4x: `errors.malformed-requests-to-server#bad-service/art-curl`
2185### Interrupted operations (`interrupted`, 6)
2187| id | status | evidence | ply ops | tests |
2188|---|---|---|---|---:|
2189| `interrupted.push-response-lost` | verified | ply↔git, ply↔Artifacts, git↔Artifacts | `push`, `runTransfer`, `editFile` | 3 |
2190| `interrupted.push-body-cut` | verified | ply↔git, ply↔Artifacts, git↔Artifacts, wire↔Artifacts | `push`, `pushPack` | 3 |
2191| `interrupted.fetch-dropped-mid-response` | verified | ply↔git, ply↔Artifacts, git↔Artifacts | `fetchPack`, `readFile` | 3 |
2192| `interrupted.stall-timeouts` | verified | ply↔git, ply↔Artifacts, git↔Artifacts | `exchangeClock`, `createTransport` | 3 |
2193| `interrupted.abort-during-push` | verified | ply↔git | `push`, `pushPack`, `runTransfer` | 2 |
2194| `interrupted.resumable-transfer` | verified | ply↔git | `runTransfer` | 1 |
2196#### `interrupted.push-response-lost`
2198The server applies a push but the response is lost: ply reports ambiguous, the refs show the push, a retry is safe.
2200Ops: `src/push.ts` `push`, `src/transfer.ts` `runTransfer`, `src/edit.ts` `editFile`.
2202Tests:
2204- `test/adversarial.test.js`: ambiguous push (response lost after server applied it): ref == our commit; a naive retry is match_count, content correct
2205- `test/transfer-outcomes.test.js`: a push applied whose response is dropped: the refs show it, the run goes on to done
2206- `test/probes/probes.test.js`: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository
2208Evidence:
2210- ply↔git: `test/adversarial.test.js`
2211- ply↔git: `test/transfer-outcomes.test.js`
2212- ply↔git: `test/probes/probes.test.js`
2213- ply↔Artifacts: probes-20261114t2226-yyjq: `interrupted.push-response-lost#cut/art-ply`
2214- git↔Artifacts: probes-20261114t2226-yyjq: `interrupted.push-response-lost#cut/art-git`
2216> Probe: the recording proxy reads the server's whole answer, then cuts the connection. Stock git (libcurl) re-sends a POST whose reused connection closed with no answer; on git http-backend the replay is refused by compare-and-swap and git then finds the ref up to date (src/probe-scenarios.ts).
2218#### `interrupted.push-body-cut`
2220A push request body that fails midway: nothing lands; failure before the first body pull is definite, after it ambiguous.
2222Ops: `src/push.ts` `push`, `src/receivecaps.ts` `pushPack`.
2224Tests:
2226- `test/custom-exchange.test.js`: a body stream that errors midway: a typed error from the iteration, the span records it, nothing lands
2227- `test/push-pack-preabort.test.js`: push with a pack sent as bytes: a signal already fired is the definite aborted with no request; a rejected fetch stays ambiguous
2228- `test/probes/probes.test.js`: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository
2230Evidence:
2232- ply↔git: `test/custom-exchange.test.js`
2233- wire↔Artifacts: loadgen-phase4-hostile-20261025: `http/partial_send_once`
2234- wire↔Artifacts: loadgen-phase4-hostile-20261025: `http/cl_larger_than_body`
2235- ply↔git: `test/probes/probes.test.js`
2236- ply↔Artifacts: probes-20261114t2226-yyjq: `interrupted.push-body-cut#half/art-ply`
2237- git↔Artifacts: probes-20261114t2226-yyjq: `interrupted.push-body-cut#half/art-git`
2239#### `interrupted.fetch-dropped-mid-response`
2241A fetch or advertisement response dropped or cut mid-body is a typed network error or pack_corrupt, never a partial result.
2243Ops: `src/fetchpack.ts` `fetchPack`, `src/read.ts` `readFile`.
2245Tests:
2247- `test/adversarial.test.js`: HTTP-level faults at every stage: statuses, non-git bodies, stall, drop, empty
2248- `test/http-options.test.js`: a body that fails mid-read is the network error it is
2249- `test/probes/probes.test.js`: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository
2251Evidence:
2253- ply↔git: `test/space/pack-cut.test.js`
2254- ply↔git: `test/probes/probes.test.js`
2255- ply↔Artifacts: probes-20261114t2226-yyjq: `interrupted.fetch-dropped-mid-response#half/art-ply`
2256- git↔Artifacts: probes-20261114t2226-yyjq: `interrupted.fetch-dropped-mid-response#half/art-git`
2258> The probe proxy drops an upload-pack response halfway, against the reference and Artifacts.
2260#### `interrupted.stall-timeouts`
2262A server that stalls before the first byte or mid-body is ended by the first-byte or idle timer, typed timeout.
2264Ops: `src/deadline.ts` `exchangeClock`, `src/http.ts` `createTransport`.
2266Tests:
2268- `test/http-options.test.js`: the transport reads the parsed timeout: the span carries it and a stalled request ends at it
2269- `test/workerd.test.js`: workerd: first-byte and idle timeouts; a long steady body or upload is not cut
2270- `test/probes/probes.test.js`: probe ${s.id}: ply and stock git against the reference meet the expectation and leave the same repository
2272Evidence:
2274- ply↔git: `test/probes/probes.test.js`
2275- ply↔Artifacts: probes-20261114t2226-yyjq: `interrupted.stall-timeouts#push-request-stall/art-ply`
2276- git↔Artifacts: probes-20261114t2226-yyjq: `interrupted.stall-timeouts#push-request-stall/art-git`
2277- ply↔Artifacts: probes-20261114t2226-yyjq: `interrupted.stall-timeouts#push-request-stall-10s/art-ply`
2278- git↔Artifacts: probes-20261114t2226-yyjq: `interrupted.stall-timeouts#push-request-stall-10s/art-git`
2279- ply↔Artifacts: probes-20261114t2226-yyjq: `interrupted.stall-timeouts#push-response-stall/art-ply`
2280- git↔Artifacts: probes-20261114t2226-yyjq: `interrupted.stall-timeouts#push-response-stall/art-git`
2281- ply↔Artifacts: probes-20261114t2226-yyjq: `interrupted.stall-timeouts#fetch-request-stall/art-ply`
2282- git↔Artifacts: probes-20261114t2226-yyjq: `interrupted.stall-timeouts#fetch-request-stall/art-git`
2283- ply↔Artifacts: probes-20261114t2226-yyjq: `interrupted.stall-timeouts#fetch-response-stall/art-ply`
2284- git↔Artifacts: probes-20261114t2226-yyjq: `interrupted.stall-timeouts#fetch-response-stall/art-git`
2286> The probe proxy injects the stalls: request-body stalls of 10 s and 20 s and a response stall against a 1 s client timeout, on push and fetch; each check's outcome is kept in the private run record.
2288#### `interrupted.abort-during-push`
2290An external AbortSignal during a push: aborted if the body was never pulled, ambiguous once sent; git decides what landed.
2292Ops: `src/push.ts` `push`, `src/receivecaps.ts` `pushPack`, `src/transfer.ts` `runTransfer`.
2294Tests:
2296- `test/adversarial.test.js`: external AbortSignal mid-stream
2297- `test/transfer-outcomes.test.js`: a real AbortSignal fired during the final push: ambiguous once sent, aborted when the body was never pulled; git decides what landed
2299Evidence:
2301- ply↔git: `test/transfer-outcomes.test.js`
2303> No Artifacts evidence.
2305#### `interrupted.resumable-transfer`
2307A multi-step transfer paused or interrupted is resumed from refs, not from local state, and ends at the planned head.
2309Ops: `src/transfer.ts` `runTransfer`.
2311Tests:
2313- `test/transfer-outcomes.test.js`: maxSteps: a push that gets no answer and does not land is ambiguous, never paused; a pause names its last push
2315Evidence:
2317- ply↔git: `test/transfer-outcomes.test.js`
2319> No Artifacts evidence.
2321### HTTP transport (smart HTTP, sideband, keepalive, large bodies) (`http`, 10)
2323| id | status | evidence | ply ops | tests |
2324|---|---|---|---|---:|
2325| `http.smart-http-discovery` | verified | ply↔git, ply↔Artifacts, git↔Artifacts | `createTransport`, `discover` | 1 |
2326| `http.redirects` | verified | ply↔git | `redirectPolicy`, `createTransport` | 2 |
2327| `http.credential-forms` | verified | ply↔git, wire↔Artifacts | `createTransport` | 1 |
2328| `http.chunked-request-body` | verified | ply↔git, wire↔Artifacts | `push`, `pushPack` | 1 |
2329| `http.large-response-body` | verified | ply↔git, ply↔Artifacts, git↔Artifacts | `readFile`, `fetchPack` | 1 |
2330| `http.large-request-body` | verified | ply↔git, git↔Artifacts | `editFile`, `push` | 2 |
2331| `http.sideband-keepalive` | verified | ply↔git | `push` | 2 |
2332| `http.request-content-encoding` | unsupported (observed) | wire↔Artifacts | — | 0 |
2333| `http.content-length-framing` | unsupported (observed) | git↔Artifacts, wire↔Artifacts | — | 0 |
2334| `http.expect-continue-and-dumb-http` | unsupported (observed) | git↔Artifacts, wire↔Artifacts | — | 0 |
2336#### `http.smart-http-discovery`
2338GET info/refs?service=… then POST to the service, with Git-Protocol: version=2 on upload-pack only.
2340Ops: `src/http.ts` `createTransport`, `src/discover.ts` `discover`.
2342Tests:
2344- `test/http-options.test.js`: Git-Protocol: version=2 goes on upload-pack GET and POST, and on neither receive-pack request
2346Evidence:
2348- ply↔git: `test/space/advertisement.test.js`
2349- ply↔Artifacts: validate-7b0c310f: `discover`
2350- ply↔Artifacts: loadgen-phase6-plyw-20261025: `discover/small`
2351- git↔Artifacts: loadgen-phase2-20261025: `http_version/HTTP/1.1`
2352- git↔Artifacts: loadgen-phase2-20261025: `http_version/HTTP/2`
2354#### `http.redirects`
2356A 3xx on the advertisement is followed as git follows it (within policy); a 3xx on a POST is never followed.
2358Ops: `src/http.ts` `redirectPolicy`, `src/http.ts` `createTransport`.
2360Tests:
2362- `test/redirect.test.js`: git oracle: origin × auth × follow × kind
2363- `test/adversarial.test.js`: I6c a 3xx is never followed: cross-origin on the GET and the POST
2365Evidence:
2367- ply↔git: `test/redirect.test.js`
2369> No Artifacts evidence: Artifacts has not been seen to redirect.
2371#### `http.credential-forms`
2373Bearer, Basic and URL-userinfo credentials produce the Authorization header git sends for the same input.
2375Ops: `src/http.ts` `createTransport`.
2377Tests:
2379- `test/adversarial.test.js`: I6d URL userinfo authenticates fetch and push with the Authorization git sends for the same URL, byte for byte
2381Evidence:
2383- ply↔git: `test/adversarial.test.js`
2384- wire↔Artifacts: loadgen-phase4-hostile-20261025: `auth/basic_empty`
2385- wire↔Artifacts: loadgen-phase4-hostile-20261025: `auth/malformed_scheme`
2387#### `http.chunked-request-body`
2389A large push body streamed with chunked transfer-encoding (duplex half).
2391Ops: `src/push.ts` `push`, `src/receivecaps.ts` `pushPack`.
2393Tests:
2395- `test/push-stream.test.js`: a pack past INFLATE_CHUNK is streamed: duplex half, redirect error, chunked; git takes it
2397Evidence:
2399- ply↔git: `test/push-stream.test.js`
2400- wire↔Artifacts: loadgen-phase2-20261025: `chunked_push/artifacts`
2402> ply's own streamed push to Artifacts is exercised by validate big20m only on the read side.
2404#### `http.large-response-body`
2406A large upload-pack response is streamed under the pack caps.
2408Ops: `src/read.ts` `readFile`, `src/fetchpack.ts` `fetchPack`.
2410Tests:
2412- `test/adversarial.test.js`: I4 maxPackBytes bounds the streamed body on every path: limit_exceeded within one frame of the cap, not timeout
2414Evidence:
2416- ply↔git: `test/adversarial.test.js`
2417- ply↔Artifacts: validate-7b0c310f: `big20m: first + warm n=25`
2418- ply↔Artifacts: loadgen-phase6-plyw-20261025: `read/big`
2419- git↔Artifacts: loadgen-compat-20261024: `clone_full/big/v2`
2421#### `http.large-request-body`
2423A large push request body (tens of MiB) reaches the server whole.
2425Ops: `src/edit.ts` `editFile`, `src/push.ts` `push`.
2427Tests:
2429- `test/push-stream.test.js`: memory: a 32 MiB streamed push holds well under one copy of the object (live arrayBuffers, gc-sampled)
2430- `test/workerd.test.js`: workerd: edit small file, 24 MB file, cache hit on second edit; git-verified
2432Evidence:
2434- ply↔git: `test/push-stream.test.js`
2435- git↔Artifacts: loadgen-compat-20261024: `large_blob_push_24m/scratch/v2`
2437> No ply push over a few MiB to Artifacts is recorded.
2439#### `http.sideband-keepalive`
2441Empty band-1 keepalives while a hook runs do not end the push read.
2443Ops: `src/push.ts` `push`.
2445Tests:
2447- `test/push-report-bound.test.js`: 13,000 band-1 keepalives while a hook runs, then the report: landed
2448- `test/push-keepalive-git.test.js`: real git keepalives while a pre-receive hook runs: band-1 empty packets, then the report; ply lands
2450Evidence:
2452- ply↔git: `test/push-keepalive-git.test.js`
2454> git http-backend with receive.keepAlive=1 and a 3 s silent pre-receive hook writes empty band-1 packets before the report; the test captures them. Whether Artifacts sends keepalives is unrecorded (it runs no hooks a client can arrange).
2456#### `http.request-content-encoding`
2458A gzip-encoded request body.
2460Unsupported: ply never compresses a request body.
2462Observed:
2464- wire↔Artifacts: loadgen-phase2-20261025: `gzip_request_body`
2465- wire↔Artifacts: loadgen-phase4-hostile-20261025: `http/corrupt_gzip`
2466- wire↔Artifacts: wire-20261115t2038-ee4x: `http.request-content-encoding#gzip-ls-refs/art-raw`
2467- wire↔Artifacts: wire-20261115t2038-ee4x: `http.request-content-encoding#gzip-ls-refs/art-curl`
2468- wire↔Artifacts: wire-20261115t2038-ee4x: `http.request-content-encoding#gzip-receive-pack/art-raw`
2469- wire↔Artifacts: wire-20261115t2038-ee4x: `http.request-content-encoding#gzip-receive-pack/art-curl`
2470- wire↔Artifacts: wire-20261115t2038-ee4x: `http.request-content-encoding#corrupt-gzip/art-raw`
2471- wire↔Artifacts: wire-20261115t2038-ee4x: `http.request-content-encoding#corrupt-gzip/art-curl`
2473#### `http.content-length-framing`
2475A request whose Content-Length disagrees with its body.
2477Unsupported: ply's fetch sets the length from the body; it cannot misframe one.
2479Observed:
2481- wire↔Artifacts: loadgen-phase4-hostile-20261025: `http/cl_smaller_than_body`
2482- wire↔Artifacts: loadgen-phase4-hostile-20261025: `http/cl_larger_than_body`
2483- wire↔Artifacts: wire-20261115t2038-ee4x: `http.content-length-framing#chunked-receive-pack/art-raw`
2484- wire↔Artifacts: wire-20261115t2038-ee4x: `http.content-length-framing#chunked-receive-pack/art-curl`
2485- git↔Artifacts: wire-20261115t2038-ee4x: `http.content-length-framing#chunked-receive-pack/art-git`
2486- wire↔Artifacts: wire-20261115t2038-ee4x: `http.content-length-framing#length-short/art-raw`
2487- wire↔Artifacts: wire-20261115t2038-ee4x: `http.content-length-framing#length-long/art-raw`
2489#### `http.expect-continue-and-dumb-http`
2491Expect: 100-continue, and the dumb HTTP protocol.
2493Unsupported: ply speaks only smart HTTP and never sends Expect.
2495Observed:
2497- wire↔Artifacts: loadgen-phase2-20261025: `expect_100_continue`
2498- wire↔Artifacts: loadgen-phase2-20261025: `dumb_http`
2499- wire↔Artifacts: wire-20261115t2038-ee4x: `http.expect-continue-and-dumb-http#expect-100-receive-pack/art-raw`
2500- wire↔Artifacts: wire-20261115t2038-ee4x: `http.expect-continue-and-dumb-http#expect-100-receive-pack/art-curl`
2501- wire↔Artifacts: wire-20261115t2116-1nam: `http.expect-continue-and-dumb-http#dumb-info-refs/art-raw`
2502- git↔Artifacts: wire-20261115t2116-1nam: `http.expect-continue-and-dumb-http#dumb-info-refs/art-git`
2503- wire↔Artifacts: wire-20261115t2116-1nam: `http.expect-continue-and-dumb-http#dumb-head/art-raw`
2504- wire↔Artifacts: wire-20261115t2116-1nam: `http.expect-continue-and-dumb-http#dumb-objects-info-packs/art-raw`
2506## Recorded runs
2508| run | date | kinds | checks | harness |
2509|---|---|---|---:|---|
2510| `validate-7b0c310f` | 2026-11-12 | ply↔Artifacts, git↔Artifacts | 62 | ply-cd validate.mjs: ply f47bb75 inside ply-web (prod version 7b0c310f) against Artifacts; stock git clones the repository and judges (fsck --strict, ls-remote, rev-parse). |
2511| `loadgen-compat-20261024` | 2026-10-24 | git↔Artifacts | 49 | ply-artifacts-loadgen compat: stock git 2.47 clients against Artifacts and against a local git http-backend baseline on identical fixtures; file:// upload-pack is the oracle. |
2512| `loadgen-phase2-20261025` | 2026-10-25 | git↔Artifacts, wire↔Artifacts | 74 | ply-artifacts-loadgen phase 2 probes: stock git and alternate clients against Artifacts, raw advertisement and HTTP requests, each beside a git http-backend baseline. |
2513| `loadgen-phase3-20261025` | 2026-10-25 | git↔Artifacts | 55 | ply-artifacts-loadgen phase 3: wants of reachable non-tip, unreachable and fake object ids by stock git (v0, v1, v2), alternate clients, push ceilings; git http-backend baseline. |
2514| `loadgen-phase4-hostile-20261025` | 2026-10-25 | wire↔Artifacts | 58 | ply-artifacts-loadgen phase 4: hand-built malformed pkt-lines, wants, packs, ref names, HTTP framing and auth headers sent to Artifacts upload-pack and receive-pack beside a git http-backend baseline (namespace ply-loadgen, modest rate). |
2515| `loadgen-phase4-hostile-write-20261025` | 2026-10-25 | wire↔Artifacts | 23 | ply-artifacts-loadgen phase 4, write side: malformed packs and ref names pushed to Artifacts receive-pack with a write token, beside a git http-backend baseline. |
2516| `loadgen-phase5-delta-20261025` | 2026-10-25 | git↔Artifacts, wire↔Artifacts | 21 | ply-artifacts-loadgen phase 5: delta capabilities, hand-built OFS/REF/thin packs pushed to Artifacts, clones read back with stock git and git verify-pack. |
2517| `loadgen-phase6-plyw-20261025` | 2026-10-25 | ply↔Artifacts | 39 | ply-artifacts-loadgen phase 6: the deployed ply Worker (ply-web) against Artifacts: reads, edits, CAS, races, merges, errors; stock git judges. |
2518| `probes-20261114t1745-5jxl` | 2026-11-14 | ply↔Artifacts, git↔Artifacts | 42 | ply differential probes (scripts/probes.mjs --artifacts; plans in test/probes/scenarios.ts, probe code d18a262915bc7c56): each scenario seeded with identical objects into a fresh Artifacts repository per client (namespace ply-loadgen) and into git http-backend with Artifacts' known policy; ply and stock git 2.47.3 run the same plan; a recording proxy injects the fault (held receive-pack while another writer moves refs, or a cut answer) and keeps the cf-ray of every request; stock git judges (ls-remote --symref, mirror clone, fsck --strict, rev-list --parents, merge-base); test/probes/evaluate.ts compares. |
2519| `probes-20261114t1837-53b4` | 2026-11-14 | ply↔Artifacts, git↔Artifacts | 10 | ply differential probes, days 5-6 batch A (scripts/probes.mjs --artifacts, probe code b55fa846fcd21188 on ply 06042f8): race shapes (delete against an update, create against a create, delete against an update at once), a create of a ref that exists, and a retry of every push that did not land under contention; same harness as probes-20261114t1745-5jxl, with the proxy also keeping the commands of each receive-pack request and the refs of each advertisement; stock git 2.47.3. |
2520| `probes-20261114t1909-sl8l` | 2026-11-14 | ply↔Artifacts, git↔Artifacts | 30 | ply differential probes, days 5-6 batches B and C (scripts/probes.mjs --artifacts, probe code 7c155a159f2bda27 on ply 55205ae; since then one scenario comment reworded and, after ply c22b066, the stock git expectation dropped from the two response-stall scenarios because git's low-speed timer differs by build): hand-built packs sent through pushPack (a thin pack against a base the server has and one whose base it lacks, a commit naming a missing blob, a delta copying past its base, a bad trailer, bad zlib, a truncated pack), pushes from a shallow clone and from a blob:none partial clone, a push body cut halfway, request and response stalls on push and fetch against set client timeouts, and an upload-pack response dropped halfway; same harness as probes-20261114t1837-53b4, with the proxy also injecting request-side faults and recording the socket error of a failed upstream call; stock git git version 2.47.3. |
2521| `probes-20261114t2226-yyjq` | 2026-11-14 | ply↔Artifacts, git↔Artifacts | 81 | ply differential probes, full matrix (t229u days 9-10; scripts/probes.mjs --artifacts, probe code 744e85097786a1b0 on ply a78ed24 plus the two harness fixes committed with this entry: the run's signal handler also closes a repository still being created, and a stock git update carries its lease without a forced refspec): every scenario in src/probe-scenarios.ts, ply and stock git 2.47.3 (node 24.22.1), each against git http-backend with Artifacts' known policy and against a fresh Artifacts repository per scenario and client (namespace ply-loadgen, one at a time); same recording proxy and stock git judge as probes-20261114t1909-sl8l; cf-ray kept for every Artifacts request; every token revoked and probed, every repository deleted and checked by listing. |
2522| `probes-20261115t1926-gfhc` | 2026-11-15 | ply↔Artifacts, git↔Artifacts | 31 | ply differential probes, malformed packs and objects (scripts/probes.mjs --artifacts --only the 21 scenarios added in 24cafa1, probe code ca2eec66b288b4b2 on ply b9b33db): ply and, where it can send the input, stock git 2.47.3 (node 24.22.1), each against git http-backend with Artifacts' known policy and against a fresh Artifacts repository per scenario and client (namespace ply-loadgen, one at a time); same recording proxy and stock git judge as probes-20261114t2226-yyjq; cf-ray kept for every Artifacts request; every token revoked and probed, every repository deleted and checked by listing. |
2523| `wire-20261115t2038-ee4x` | 2026-11-15 | wire↔Artifacts, git↔Artifacts, ply↔Artifacts | 50 | ply HTTP-framing and malformed-request wire probes (scripts/wire-probes.mjs --artifacts, the 20 plans of test/probes/wire-plans.ts, probe code 19288b51af72a83f on ply 96b7a7d): each request sent directly to the target, without a proxy, from a raw socket (node net/tls, exact framing), curl 8.14.1, stock git 2.47.3 and ply where each can express it, against git http-backend with Artifacts' known policy and against a fresh Artifacts repository per plan (namespace ply-loadgen, one at a time, seeded and judged through the recording proxy's side and judge channels); credentials only from 0600 files (curl -H @file, git include.path); cf-ray kept for every Artifacts answer; every token revoked and probed, every repository deleted and checked by listing. |
2524| `probes-20261115t2113-phhp` | 2026-11-15 | ply↔Artifacts, git↔Artifacts | 12 | ply differential probes, ref and tag-object semantics (scripts/probes.mjs --artifacts --only the 10 scenarios of REF_SEMANTICS, probe code b726c69c5eaa6ecd on ply d5db942 plus the phase-4 harness): ply and, where it can send the push, stock git 2.47.3 (node 24.22.1), each against git http-backend with Artifacts' known policy and against a fresh Artifacts repository per scenario and client (namespace ply-loadgen, one at a time); same recording proxy and stock git judge as probes-20261114t2226-yyjq; cf-ray kept for every Artifacts request; every token revoked and probed, every repository deleted and checked by listing. The three directory/file scenarios stopped at the judge in this run and are recorded by probes-20261115t2126-d4jn. |
2525| `probes-20261115t2126-d4jn` | 2026-11-15 | ply↔Artifacts, git↔Artifacts | 6 | The three refs.directory-file-conflict scenarios again (probe code 5d7f4447288f58df), with the judge recording a repository stock git cannot mirror as such (its refs as listed, the clone's refusal as its fsck problem) instead of stopping; otherwise as probes-20261115t2113-phhp. |
2526| `wire-20261115t2116-1nam` | 2026-11-15 | wire↔Artifacts, git↔Artifacts, ply↔Artifacts | 75 | ply wire probes, ref names, unknown capabilities, dumb HTTP and a 2001-ref listing (scripts/wire-probes.mjs --artifacts, the 29 phase-4 plans of test/probes/wire-plans.ts, probe code e5af73ceefc0d6a8 on ply d5db942 plus the phase-4 harness): each request sent directly to the target from a raw socket, curl 8.14.1 where listed, stock git 2.47.3 and ply where each can express it, against git http-backend with Artifacts' known policy and a fresh Artifacts repository per plan (namespace ply-loadgen, one at a time); a sender that refuses a request itself is recorded as such and never reaches the server; credentials only from 0600 files; cf-ray kept for every Artifacts answer; every token revoked and probed, every repository deleted and checked by listing. |
2527| `probes-20261115t2133-txqj` | 2026-11-15 | ply↔Artifacts, git↔Artifacts | 8 | The three refs.directory-file-conflict scenarios and refs.symref-head#delete-default-branch again (probe code 60d752563bc119fa), with the recording proxy also keeping each receive-pack answer's per-command report (its unpack, ok and ng lines); otherwise as probes-20261115t2126-d4jn. |
Diagnostics5 git calls · 344 ms
CallStatusSizeTime0344 ms
discover200191 B2 ms
git.upload-pack discover
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=ls-refs
git.upstream.dur_ms=2
git.response.bytes=191
git.server.agent=git/github-9922ec520325-Linux
git.server.object_format=sha1
git.server.caps=agent ls-refs fetch server-option object-format
git.server.fetch=shallow wait-for-done filter
git.protocol.version=2
git.pkt.frames=9
git.pkt.data=7
git.pkt.flush=2
git.pkt.delim=0
git.pkt.bytes=191
git.pkt.payload.max=36
ls-refs20012 KiB · hit2 ms
git.upload-pack ls-refs
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=ls-refs
git.upstream.dur_ms=2
git.response.bytes=11990
git.response.cache=HIT
git.response.duration_ms=2
git.protocol.version=2
git.pkt.frames=152
git.pkt.data=151
git.pkt.flush=1
git.pkt.delim=0
git.pkt.bytes=11990
git.pkt.payload.max=122
git.ls_refs.count=151
git.ls_refs.head=refs/heads/main
fetchtree:0 · deepen 102004.2 KiB · hit2 ms
git.upload-pack fetch
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=2
git.response.bytes=4347
git.response.cache=HIT
git.response.duration_ms=2
git.fetch.filter=tree:0
git.fetch.wants=19912563f540228593df0c489082e5e2508e21e4
git.fetch.haves.count=0
git.fetch.deepen=10
git.fetch.thin_pack=false
git.fetch.ofs_delta=true
git.protocol.version=2
git.pkt.frames=7
git.pkt.data=5
git.pkt.flush=1
git.pkt.delim=1
git.pkt.bytes=4347
git.pkt.payload.max=4247
git.sideband.band1.bytes=4247
git.sideband.band2.bytes=0
git.sideband.band3.bytes=0
git.pack.objects=10
git.pack.bytes=4247
git.pack.ofs_delta=0
git.pack.ref_delta=0
git.pack.chain.max=0
git.pack.trailer=a6caf8e129bea82c9bae4cbc7c130c9205add400
git.pack.full=10
Open pack map
fetchtree:0200919 B · hit2 ms
git.upload-pack fetch
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=2
git.response.bytes=919
git.response.cache=HIT
git.response.duration_ms=2
git.fetch.filter=tree:0
git.fetch.wants=800d30ba8923860bfc460ca884b7f9ba22083588
git.fetch.haves.count=0
git.fetch.deepen=0
git.fetch.thin_pack=false
git.fetch.ofs_delta=true
git.protocol.version=2
git.pkt.frames=4
git.pkt.data=3
git.pkt.flush=1
git.pkt.delim=0
git.pkt.bytes=919
git.pkt.payload.max=892
git.sideband.band1.bytes=892
git.sideband.band2.bytes=0
git.sideband.band3.bytes=0
git.pack.objects=1
git.pack.bytes=892
git.pack.trailer=5323b9266eea5ded637285d1c5320699f12be76e
Open pack map
fetch20031 KiB338 ms
git.upload-pack fetch
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=337
git.response.bytes=31538
git.response.cache=MISS
git.response.duration_ms=338
git.fetch.wants=b335a9adafd8cb96bec4aa775c42e23679205364
git.fetch.haves.count=0
git.fetch.deepen=0
git.fetch.thin_pack=false
git.fetch.ofs_delta=true
git.protocol.version=2
git.pkt.frames=5
git.pkt.data=4
git.pkt.flush=1
git.pkt.delim=0
git.pkt.bytes=31538
git.pkt.payload.max=23315
git.sideband.band1.bytes=31506
git.sideband.band2.bytes=0
git.sideband.band3.bytes=0

Each row is one HTTP round trip ply made to the git server for this page, on one timeline. discover asks what the server speaks, ls-refs lists branch tips, fetch brings objects by id. A hit was served by Workers Cache. Tap a row for its wire details.

Remote
https://github.com/ivarvong/ply
Ref
refs/heads/main
Commit
19912563f540228593df0c489082e5e2508e21e4
cf-ray
a5e0e9651b92a140
Request
ffbf8435…
Protocol
v2 · sha1
Agent
git/github-9922ec520325-Linux
Filter
advertised
Fetch
shallow wait-for-done filter
Capabilities
agent ls-refs fetch server-option object-format