mirror of
https://github.com/callstack/agent-device.git
synced 2026-09-14 20:06:34 +08:00
05a1d76f2e
* test: gate daemon RPC wire compatibility against the last released tag (#1432) ADR 0006 fixes exactly when DAEMON_RPC_PROTOCOL_VERSION must be bumped, and nothing checked that it was. The runtime guard (readRemoteDaemonHealth) refuses a mismatched peer, but only fires when someone remembered the bump — a wire change that skipped it left both sides advertising protocol 2 while parsing different payloads, which is the failure ADR 0006 exists to prevent. Local daemons cannot skew (isReusableDaemonInfo takes over on any package version mismatch). Cross-machine is skewed by design — proxy, cloud/limrun, a remote macOS host — and ADR 0006 explicitly rules package version out as the compatibility gate there, so the one boundary where skew is intended was the one boundary with no gate. test/wire-compat/surface.ts declares the wire surface grouped by the ADR bullet each group serves, quoting it, with an `uncovered` note where a bullet is only partly digestible (the /health and /rpc literals inside http-server.ts stay reviewer-owned: a moved route 404s at connect time rather than misparsing). ledger.json records what each declaration hashes to, at which protocol version. Two gates, split for the same reason the replay-compat corpus splits: - unit-core holds the ledger to its source and prints the digest to paste; - Released-Surface Compatibility reads the ledger at the last RELEASED tag and requires the drift since then to carry a bump or a compatibleChanges ack. From one commit a bumped ledger and an unbumped one are both just an edited file, so only a released baseline can tell them apart. Acks are keyed by the digest they cover, so one "added an optional field" cannot launder later changes. Digests ignore comments and formatting; the manifest's closure is derived from the AST, so a field typed by an unlisted sibling fails rather than sitting outside the gate. CI cost: one added job (checkout + toolchain + two node scripts, ~1 min), mirroring the existing full-history replay-compat job. * test: close wire-surface overclaim and make the closure fail closed (#1432) Addresses both review P1s on #1717. P1 — the manifest materially overclaimed ADR 0006 coverage. It quoted all four bullets while digesting only the payload TYPES, so the producer and consumer seams could break a skewed peer without moving a listed digest. Now listed on both sides of every boundary: JSON-RPC method sets and the projections that turn each method's params into a DaemonRequest, createRpcError/sendJson/ writeRpcResponseEnvelope, resolveToken and the auth-hook types, upload preflight/finalize/308 handlers and the resumable ticket shape, artifact route and download/inventory framing, REST error mapping, and the client's own payload builder, lease-method mapping, response parser and error projection. 57 -> 117 declarations. What stays out is now named rather than implied: createDaemonHttpServer's dispatch wiring and the /health and /rpc literals inside it. Everything it dispatches WITH is digested individually, and a moved route 404s at connect time rather than misparsing — the loud failure, not the silent one. P1 — imported and re-exported payload shapes escaped the closure. declarationHomes() scanned only the manifest's own files and the walk continued silently when a name could not be placed, so a listed type could gain foo?: ImportedShape from a new module and stay green. Resolution is now explicit and fails closed: relative imports, workspace specifiers (through the owning package's own exports map, so a re-pointed export cannot drop a type), and facade re-export chains. Every referenced name must land on a listed declaration, a waiver with a written reason, a declared external module, or the TS/Node global set. Fixed two extractor blind spots the walk exposed: a declaration's own generic parameters and `as const` were being reported as references. Planted-red proofs (wire-mutations.test.ts): 13 cases independently mutate method naming, response serialization, response parsing, auth projection, upload ticket shape, 308 framing, artifact framing, REST error mapping, and progress framing, each asserting the digest moves; 3 probes prove the closure really reaches across a package boundary, a facade re-export, and a plain relative import. Mutations apply inside the declaration's own span — a whole-file replace silently hit a sibling sharing the substring, which is how the first draft of one case passed vacuously. The largest waiver pair (InternalRequestOptions, CommandFlags) rests on ADR 0006's own additive rule: they reach the peer inside DaemonRequest's untyped flags/input bags, and the decision says a new flag needs no bump. Digesting them would fire the gate on every new CLI flag and train reviewers to rubber-stamp acks. * 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. * test: list the client half of the resumable 308 contract (#1432) Addresses the third review P1 on #1717. Listing the daemon's handleResumableUpload proved it still PRODUCES 308; nothing proved the client still CONSUMES the released one. src/remote/upload-stream.ts owns that half and was entirely outside the manifest, so a newer client could stop accepting `upload-offset`, change how it reads `Range: bytes=0-N`, or emit a different resumed `Content-Range` without moving one of the 141 listed digests. Now listed (141 -> 151): UploadStreamResponse, streamFileToHttpRequest, streamFileToHttpRequestAttempt, buildUploadRequestHeaders, isUploadResumeStatus, isUploadRedirectStatus, parseUploadResumeOffset, parseNonNegativeIntegerHeader, firstHeaderValue, MAX_UPLOAD_REDIRECTS. streamFileToHttpRequestAttempt is listed despite its size, unlike createDaemonHttpServer which stays in `uncovered`. The distinction is stated at the declaration: the HTTP server only dispatches to handlers that are each digested, while the attempt loop IS the resume state machine — it decides whether a 308 continues the upload and what the next request carries, so its sequencing alone can break a released daemon while every helper keeps its digest. 6 new planted-red mutations prove the client half moves the ledger: a dropped `upload-offset` fallback, narrowed Range parsing, a changed resumed Content-Range, 308 no longer treated as continue, a narrowed UploadStreamResponse, and dropped header-value coercion. 33 -> 39 tests. Closure fail-closed surfaced two more stops: UploadStreamProgressOptions waived (local byte-progress rendering) and URL/URLSearchParams added to the global set. README now carries a `/upload` resume row in the producer/consumer table, and names the pattern behind three rounds of review: the coverage sentence kept getting written ahead of the coverage, so the table and the `uncovered` notes are the claims to trust — they are checkable against surface.ts, prose is not. --------- Co-authored-by: Claude <noreply@anthropic.com>
87 lines
5.4 KiB
TypeScript
87 lines
5.4 KiB
TypeScript
/**
|
|
* What the wire-surface closure is allowed to stop at (#1432, review P1).
|
|
*
|
|
* The closure walk fails closed: every type name a listed declaration
|
|
* references must resolve to a listed declaration, or to an entry here. There
|
|
* is no silent skip, because the silent skip WAS the defect — a listed type
|
|
* could grow `foo?: ImportedShape` from an unlisted module and stay green.
|
|
*
|
|
* Two kinds of stop, kept apart because they are different claims:
|
|
*
|
|
* - an EXTERNAL MODULE is outside this repository, so there is no declaration
|
|
* to digest and no way for a change to it to ship in our tarball;
|
|
* - a WAIVER is a repo declaration the walk reaches that is genuinely not
|
|
* payload — transport plumbing, a local error class, a callback type. Each
|
|
* one is a claim someone has to defend in review, which is the point.
|
|
*
|
|
* A waiver stops the walk. If a waived type later starts carrying payload,
|
|
* moving it into `surface.ts` is the fix, not widening this file.
|
|
*/
|
|
|
|
/**
|
|
* Module specifiers whose types have no declaration site in this repo. Prefix
|
|
* match, so `node:http` covers `node:http2` only if spelled out — keep them
|
|
* exact enough to mean something.
|
|
*/
|
|
const WIRE_EXTERNAL_MODULES: Readonly<Record<string, string>> = {
|
|
'node:http': 'Node HTTP request/response objects are the transport, not the payload on it.',
|
|
'node:stream': 'Stream plumbing carries bytes; the bytes themselves are digested elsewhere.',
|
|
undici: 'HTTP client types belong to the transport library, not to our wire contract.',
|
|
};
|
|
|
|
/**
|
|
* Repo declarations the closure reaches that are deliberately not wire
|
|
* surface. Key is `<file>#<name>`; the value has to say why a change to it
|
|
* cannot change what a skewed peer parses.
|
|
*/
|
|
export const WIRE_CLOSURE_WAIVERS: Readonly<Record<string, string>> = {
|
|
'packages/kernel/src/errors.ts#AppError':
|
|
'The local error CLASS. Only its projection onto the wire is contractual, and that projection is DaemonError, which is listed.',
|
|
'packages/kernel/src/errors.ts#AppErrorCode':
|
|
'Error-code vocabulary is carried as a plain string in DaemonError.code; adding a code cannot change the envelope a peer parses.',
|
|
'packages/kernel/src/errors.ts#AppErrorDetails':
|
|
'Local detail bag behind AppError; the wire form is DaemonError.details, typed as Record<string, unknown> and listed.',
|
|
'src/daemon/client/daemon-client-metadata.ts#DaemonInfo':
|
|
'Client-side record of where a daemon is listening (pid, ports, state dir). Never serialized into a request or response.',
|
|
'src/daemon/types.ts#DaemonRequest':
|
|
'Re-export alias of the listed kernel DaemonRequest; the declaration that fixes the shape is packages/kernel/src/contracts.ts#DaemonRequest.',
|
|
'src/daemon/types.ts#DaemonResponse':
|
|
'Re-export alias of the listed kernel DaemonResponse; the shape is fixed by packages/kernel/src/contracts.ts#DaemonResponse.',
|
|
'src/daemon/types.ts#DaemonArtifact':
|
|
'Re-export alias of the listed kernel DaemonArtifact; the shape is fixed by packages/kernel/src/contracts.ts#DaemonArtifact.',
|
|
'src/remote/upload-stream.ts#UploadStreamProgressOptions':
|
|
'Byte-progress callback options for local upload rendering. The bytes counted are digested through the request/response declarations; these options never cross the wire.',
|
|
'src/remote/upload-progress.ts#UploadProgressSink':
|
|
'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.',
|
|
'packages/contracts/src/request-progress.ts#RequestProgressSink':
|
|
'A callback type (event) => void. The event it receives is RequestProgressEvent, which is listed; the sink itself never crosses the wire.',
|
|
|
|
// The CLI flag/option vocabulary embedded in DaemonCommandRequest. This is
|
|
// the one waiver pair that stops a large subtree, so it is the one to
|
|
// challenge first — the reasoning is ADR 0006's own, not convenience.
|
|
//
|
|
// These types are the CLI-SIDE projection. They do not cross the boundary as
|
|
// typed fields: DaemonRequest carries `input?: Record<string, unknown>` and
|
|
// `flags?: Record<string, unknown>`, both listed, and the flag vocabulary
|
|
// lands inside those bags as plain keys. ADR 0006 then classifies a new flag
|
|
// as additive ("new optional request fields or flags that older daemons can
|
|
// ignore or reject with a normal command error"), explicitly NOT a bump. So
|
|
// digesting them would fire the gate on every new CLI flag for a change the
|
|
// decision says needs no acknowledgment — and a gate that cries wolf gets
|
|
// its acks rubber-stamped, which costs more than the coverage buys.
|
|
//
|
|
// If a flag ever becomes a typed field on DaemonRequest, that changes
|
|
// DaemonRequest's own digest, and the right fix is to list the type here
|
|
// rather than widen this waiver.
|
|
'packages/contracts/src/client-request.ts#InternalRequestOptions':
|
|
'CLI-side option projection; reaches the peer inside DaemonRequest.input/flags (Record<string, unknown>, both listed), and ADR 0006 calls new flags additive.',
|
|
'packages/contracts/src/command-flags.ts#CommandFlags':
|
|
'CLI-side flag vocabulary; reaches the peer inside DaemonRequest.flags (Record<string, unknown>, listed), and ADR 0006 calls new flags additive.',
|
|
};
|
|
|
|
export function isExternalWireSpecifier(specifier: string): boolean {
|
|
return Object.keys(WIRE_EXTERNAL_MODULES).some(
|
|
(prefix) => specifier === prefix || specifier.startsWith(`${prefix}/`),
|
|
);
|
|
}
|