You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit b2da20c
Browse filesBrowse the repository at this point in the historyBrowse files
test: list the consumer half of the auxiliary HTTP boundaries (#1432)
Addresses the remaining review P1 on #1717. The manifest claimed both sides of
response/upload/artifact framing while listing nothing from upload-client.ts,
daemon-artifacts.ts, or the health consumer in daemon-client-transport.ts, so
those parsers could narrow without moving a listed digest or protocol 2.
Now listed (117 -> 141 declarations):
- /health consumer: RemoteDaemonHealth, readHealthPayload, readDaemonHttpHealth,
readRemoteDaemonHealth. This is the sharpest of the three — narrowing the
reader or the comparison disables the very refusal ADR 0006 exists to
guarantee, and nothing else in the repo would notice.
- /upload consumer: UploadResponse, UploadPreflightResponse, UploadPreflightResult,
parseUploadPreflightResult, requestUploadPreflight, uploadDirectArtifact,
tryDirectUploadWithResume, shouldRetryDirectUpload, finalizeDirectUpload,
uploadLegacyArtifact, ARTIFACT_HASH_ALGORITHM, isStringRecord, and
PreparedUploadArtifact — whose sha256/sizeBytes/fileName/artifactType/
contentType fields ARE the preflight body the daemon parses.
- /artifacts/* consumer: DaemonArtifactEndpoint, buildDaemonArtifactUrl,
isRemoteDaemon, DownloadRemoteArtifactParams, downloadRemoteArtifact,
materializeRemoteArtifacts, resolveMaterializedArtifactPath.
Running the closure fail-closed over the new files surfaced three more stops,
each decided rather than skipped: PreparedUploadArtifact listed (it is payload),
UploadProgressSink waived (client-local rendering, never leaves the process),
and src/daemon/types.ts#DaemonArtifact waived as a re-export alias of the listed
kernel type, matching its DaemonRequest/DaemonResponse siblings.
10 more planted-red mutations cover the new seams: health version-read and
mismatch-refusal defeated, RemoteDaemonHealth field dropped, preflight parser
narrowed, preflight/legacy response shapes narrowed, finalize body key renamed,
ticket field renamed, artifact tenant header dropped, artifact URL moved. A
fourth closure probe proves the upload-consumer files are genuinely reached by
the walk rather than merely listed. 22 -> 33 tests.
The README now states the coverage as a producer/consumer table per boundary,
so the claim is checkable at a glance instead of asserted in prose.
'A callback for client-local upload progress rendering. Its events never leave the client, unlike the daemon progress stream, whose envelope and events are listed.',
0 commit comments