Files
reverse-engineering-anything/tests/fixtures/golden
Lewis WongandClaude Opus 5.5 2d182f865f fix(apple): report the declared archiver of a keyed archive
Keyed archives may now name another archiver, so the name is source
metadata a caller needs: a SceneKit scene says SCNKeyedArchiver. The
keyed-archive result gains `archiver`, the declared `$archiver` string, and
the inspect_keyed_archive contract describes archives written by
NSKeyedArchiver or a subclass archiver such as SCNKeyedArchiver instead of
NSKeyedArchiver plists only.

The reviewed golden graph adds `"archiver": "NSKeyedArchiver"` for its
capture; only its provenance digest changes, and the captured XML does not.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-21 19:51:56 +01:00
..

Captured format and protocol fixtures

These are actual tool outputs, not records assembled to match the parser. provenance.json records the capture host, producer versions, source digests and immutable capture/expectation digests. Compiled binaries and catalogs are not committed.

Foundation archive

keyed-archive/foundation.xml is the XML representation of a binary archive written by Foundation NSKeyedArchiver, using the source-owned Swift fixture. plutil represents binary UID entries as CF$UID dictionaries. The captured archive has six objects: nil, the root NSArray, one shared custom record, its four-byte data payload and two class descriptors.

keyed-archive/graph.json is the reviewed complete expected graph. The source establishes two references from the array to object 2, object 2's self-cycle, its nil conditional reference and the payload 00 01 02 ff. The reader reports serialized classes as unknown and does not instantiate them. The synthetic malformed-reference tests remain separate.

Object 3 is a plist <data> value in the captured XML, produced by the Swift fixture's Data([0, 1, 2, 255]). Its reviewed graph kind is scalar; the JSON $plist_type wrapper does not make it a serialized dictionary. This expectation correction updates only the graph digest in provenance.json, without recapturing or changing the original XML or its producer metadata.

The graph's archiver is the archive's declared $archiver, NSKeyedArchiver for this capture. Adding that reported field likewise updates only the graph digest.

To recapture the input on an approved macOS host:

capture_root=$(mktemp -d)
xcrun swift -module-cache-path "$capture_root/modules" \
  tests/conformance/native/keyed-archive.swift "$capture_root/model.plist"
plutil -convert xml1 -o tests/fixtures/golden/keyed-archive/foundation.xml \
  "$capture_root/model.plist"
rm -rf "$capture_root"

Review expected graph changes against the source and XML before updating the expectation or provenance. Tests never rewrite the golden.

Asset catalog

assetutil.json is the unmodified output of /usr/bin/assetutil --info for an actual actool catalog. The source colorset defines FixtureColor with sRGB components [0.125, 0.5, 0.875, 1]. Preserve private fields and producer metadata in this fixed input, including its original timestamp; the test checks that the projection does not discard them.

capture_root=$(mktemp -d)
xcrun actool tests/conformance/native/Assets.xcassets \
  --compile "$capture_root" --platform macosx --minimum-deployment-target 12.0
/usr/bin/assetutil --info "$capture_root/Assets.car" \
  > tests/fixtures/golden/assetutil.json
rm -rf "$capture_root"

The real E2E lane builds fresh catalogs and compares all their metadata against the live utility output. It does not compare volatile timestamps or producer versions against this historical capture.

MCP JSON-RPC request

mcp-initialize.json captures the initialize request emitted by the pinned @modelcontextprotocol/client 2.0.0 SDK on 2026-10-04. The client connected to the actual scripts/rea.mjs mcp subprocess and completed listTools (the current catalog). The recorder intercepted transport.send, serialized the message, and delegated the unchanged message to the real SDK transport. The committed JSON is formatted for review; whitespace is not a wire identity claim. No provider was launched.

The decoder expectation separately specifies every field path, JSON value and observed-versus-inferred status. It is a captured decoder regression, not proof of a live protocol-capture product workflow.