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>
90 lines
3.9 KiB
TypeScript
90 lines
3.9 KiB
TypeScript
/**
|
|
* Does the daemon RPC wire surface's drift since the last RELEASED version
|
|
* carry the justification ADR 0006 requires? (#1432)
|
|
*
|
|
* Pure comparison, no git and no filesystem, so the bump / ack / removal rules
|
|
* are provable from fixtures instead of only from whatever the repository's
|
|
* tags happen to contain today — the `scripts/<name>/{model,run}.ts` split
|
|
* check-affected and coverage-changed already use.
|
|
*
|
|
* Division of labour with the unit lane: `test/wire-compat/wire-compat.test.ts`
|
|
* ties the ledger to the SOURCE it describes (and to
|
|
* `DAEMON_RPC_PROTOCOL_VERSION`), which is why nothing here re-checks that.
|
|
* This model only ties one ledger to another.
|
|
*/
|
|
|
|
import type { WireLedger } from '../../test/wire-compat/ledger.ts';
|
|
|
|
export type WireComparisonInput = {
|
|
/** Released tag the baseline ledger came from, for failure messages. */
|
|
baselineTag: string;
|
|
released: WireLedger;
|
|
current: WireLedger;
|
|
/** Digests recomputed from today's source, keyed `<file>#<name>`. */
|
|
digests: ReadonlyMap<string, string>;
|
|
};
|
|
|
|
export type WireComparison = {
|
|
/** Declarations whose digest moved since the baseline. */
|
|
changed: readonly string[];
|
|
/** Declarations the baseline had and the current wire surface does not. */
|
|
removed: readonly string[];
|
|
/** Declarations added since the baseline; additive, so never a failure. */
|
|
added: readonly string[];
|
|
/** Whether the protocol version advanced since the baseline. */
|
|
bumped: boolean;
|
|
/** Empty when the drift is justified. */
|
|
failures: readonly string[];
|
|
};
|
|
|
|
export function compareWireLedgers(input: WireComparisonInput): WireComparison {
|
|
const { baselineTag, released, current, digests } = input;
|
|
const bumped = current.protocolVersion > released.protocolVersion;
|
|
|
|
const changed: string[] = [];
|
|
const removed: string[] = [];
|
|
for (const [key, releasedDigest] of Object.entries(released.declarations)) {
|
|
const digest = digests.get(key);
|
|
if (digest === undefined) removed.push(key);
|
|
else if (digest !== releasedDigest) changed.push(key);
|
|
}
|
|
const added = Object.keys(current.declarations).filter((key) => !(key in released.declarations));
|
|
|
|
const failures: string[] = [];
|
|
const stillAt = `still ${current.protocolVersion}`;
|
|
|
|
// A declaration the released wire surface had and this one does not is a
|
|
// break by definition: a peer on the old protocol can still send it. There is
|
|
// no additive reading of a removal, so no ack can cover one — only a bump.
|
|
if (removed.length > 0 && !bumped) {
|
|
failures.push(
|
|
`Dropped since ${baselineTag} without bumping DAEMON_RPC_PROTOCOL_VERSION (${stillAt}):\n` +
|
|
`${removed.map((key) => ` - ${key}`).join('\n')}\n` +
|
|
` Removing wire surface a released peer still sends is breaking; an ack cannot cover it.`,
|
|
);
|
|
}
|
|
|
|
if (changed.length > 0 && !bumped) {
|
|
// An ack is keyed by the digest the declaration moved TO, so it covers one
|
|
// specific post-change shape and cannot be recycled for the next change.
|
|
const acked = new Map(current.compatibleChanges.map((ack) => [ack.declaration, ack]));
|
|
const unacked = changed.filter((key) => {
|
|
const ack = acked.get(key);
|
|
return ack?.digest !== digests.get(key) || ack.rationale.trim().length === 0;
|
|
});
|
|
if (unacked.length > 0) {
|
|
failures.push(
|
|
`Changed since ${baselineTag} without bumping DAEMON_RPC_PROTOCOL_VERSION (${stillAt}):\n` +
|
|
`${unacked.map((key) => ` - ${key}`).join('\n')}\n` +
|
|
` Read ADR 0006. If a peer on protocol ${released.protocolVersion} would misinterpret ` +
|
|
`the new payload, bump the constant and the ledger's protocolVersion. If the change is ` +
|
|
`additive — a new optional field the other side ignores — add a compatibleChanges entry ` +
|
|
`per declaration carrying its current digest and the reason it stays compatible. ` +
|
|
`test/wire-compat/README.md walks both.`,
|
|
);
|
|
}
|
|
}
|
|
|
|
return { changed, removed, added, bumped, failures };
|
|
}
|