Console JSON is a schema: .NET 10 dropped the duplicate State.Message, and parsers go quiet

The failure is quiet because JSON extraction usually is. An extractor that walks to `State` and then to `Message` returns null when the nested key is absent rather than raising anything ^[2], and null is a plausible value for a log line. The record still arrives with its level and timestamp and lands in the index with an empty body. Nothing downstream can tell the difference between an event that had no text and a parser that stopped looking in the right place.

The delta itself is one deleted duplicate. In the before-and-after pair published in the dev.to writeup, `State` goes from four properties to three, and the rendered sentence appears once in the record instead of twice ^[3][4][1]. Everything a query would actually filter on stays where it was: `OrderId`, `Status`, and the `{OriginalFormat}` template ^[7]. Searching a rendered sentence for an order ID was always throwing away the reason to emit JSON in the first place ^[15].

Read order matters more than it looks. The writeup's rule is top-level first, nested as fallback, and the fallback exists for stored .NET 9-era records or mixed-version fleets rather than as a permanent anchor ^[8]. That ordering is not decoration: Microsoft's compatibility note says `State.Message` can still appear when its content differs from the top-level value ^[6], and in that case the top-level field is canonical ^[9]. A parser that checks the nested location first will therefore pick the wrong string in precisely the records where the two strings disagree.

The transferable part is the test, not the field name. The author treats console JSON as a schema whenever another process parses it, which makes a runtime upgrade a contract change rather than something to eyeball in a terminal ^[10]. What makes his sample useful is where the current side of the contract comes from: an emitter configured with `AddJsonConsole` runs under the installed runtime, and a verifier captures its single line and checks semantics rather than property order or timestamp text ^[11][12]. Two hand-authored fixtures would have sailed through this upgrade agreeing with each other and with nothing else. The test is deterministic and offline after restore, with no logging backend, account, or credential involved ^[13].

Scope is worth keeping narrow. The sample was verified on SDK 10.0.303 and runtime 10.0.11, though the contract change belongs to .NET 10 generally rather than that patch ^[14]. Other `AddJsonConsole` options for timestamps, scopes, and JSON handling can reshape other parts of a record, which is why the contract covers only the fields the consuming pipeline reads ^[16]. And if the pipeline goes through a provider or an OpenTelemetry exporter, that schema is better defined and should be tested directly instead of being translated into the console formatter's shape ^[17]. Anyone parsing the built-in formatter has a dependency on an implementation detail that ships breaking changes on the major-version cadence, and the cheapest defense available is a test that runs the formatter and reads what comes out.