# @variance-authority/wire ## 0.20.0 Lockstep release — nothing in this package changed. Every `@variance-authority/*` package shares one version. ## 0.19.0 Lockstep release — nothing in this package changed. Every `@variance-authority/*` package shares one version. ## 0.18.0 Lockstep release — nothing in this package changed. Every `@variance-authority/*` package shares one version. ## 0.17.1 Lockstep release — nothing in this package changed. Every `@variance-authority/*` package shares one version. ## 0.17.0 Lockstep release — nothing in this package changed. Every `@variance-authority/*` package shares one version. ## 0.16.0 Lockstep release — nothing in this package changed. Every `@variance-authority/*` package shares one version. ## 0.15.0 ### Patch Changes - ef496ad: READMEs name what the program does The package READMEs, and the `@variance-authority/vantage` and `@variance-authority/playwright-test` descriptions, no longer write a test, a record or a run as something that says, asks or knows. Each sentence names what the program does: a command prints, a record holds a field, a test runs or covers. Where a value is filled in from configuration or a default rather than recorded, the README says so. Four renamed headings change their anchors: `help`'s "Where the declaration is undocumented", `playwright`'s "Where a component is declared, read from the engine", `storybook`'s "What a pass sends the preview" and `sense`'s "Correct what a file's text declares it imports". ## 0.14.0 Lockstep release — nothing in this package changed. Every `@variance-authority/*` package shares one version. ## 0.13.0 Lockstep release — nothing in this package changed. Every `@variance-authority/*` package shares one version. ## 0.12.0 Lockstep release — nothing in this package changed. Every `@variance-authority/*` package shares one version. ## 0.11.0 Lockstep release — nothing in this package changed. Every `@variance-authority/*` package shares one version. ## 0.10.0 Lockstep release — nothing in this package changed. Every `@variance-authority/*` package shares one version. ## 0.9.0 Lockstep release — nothing in this package changed. Every `@variance-authority/*` package shares one version. ## 0.8.1 Lockstep release — nothing in this package changed. Every `@variance-authority/*` package shares one version. ## 0.8.0 Lockstep release — nothing in this package changed. Every `@variance-authority/*` package shares one version. ## 0.7.0 ### Minor Changes - 23123e6: A driver a head first hears from late still gets every subject's initialization A head reported what ran outside any request, and what a module ran while it initialized, to whichever driver's request happened to be open. Under two workers the second never heard it, so its subjects missed the lines every request depends on, and a change to a module's top level could skip them. A head now keeps that account and sends each driver the part it has not been told, the first time that driver's request settles. `Channel.home` names the driver a channel reaches, which is what the head keys on. ## 0.6.0 Lockstep release — nothing in this package changed. Every `@variance-authority/*` package shares one version. ## 0.5.10 Lockstep release — nothing in this package changed. Every `@variance-authority/*` package shares one version. ## 0.5.9 Lockstep release — nothing in this package changed. Every `@variance-authority/*` package shares one version. ## 0.5.8 Lockstep release — nothing in this package changed. Every `@variance-authority/*` package shares one version. ## 0.5.7 Lockstep release — nothing in this package changed. Every `@variance-authority/*` package shares one version. ## 0.5.6 Lockstep release — nothing in this package changed. Every `@variance-authority/*` package shares one version. ## 0.5.5 Lockstep release — nothing in this package changed. Every `@variance-authority/*` package shares one version. ## 0.5.4 Lockstep release — nothing in this package changed. Every `@variance-authority/*` package shares one version. ## 0.5.3 Lockstep release — nothing in this package changed. Every `@variance-authority/*` package shares one version. ## 0.5.2 Lockstep release — nothing in this package changed. Every `@variance-authority/*` package shares one version. ## 0.5.1 Lockstep release — nothing in this package changed. Every `@variance-authority/*` package shares one version. ## 0.5.0 Lockstep release — nothing in this package changed. Every `@variance-authority/*` package shares one version. ## 0.4.1 Lockstep release — nothing in this package changed. Every `@variance-authority/*` package shares one version. ## 0.4.0 Lockstep release — nothing in this package changed. Every `@variance-authority/*` package shares one version. ## 0.3.0 Lockstep release — nothing in this package changed. Every `@variance-authority/*` package shares one version. ## 0.2.0 Lockstep release — nothing in this package changed. Every `@variance-authority/*` package shares one version. ## 0.1.1 Lockstep release — nothing in this package changed. Every `@variance-authority/*` package shares one version. ## 0.1.0 ### Minor Changes - f09528d: Carry announcements and coverage on one medium, under one execution id. A run said two kinds of things about the same execution and had two ways of saying them: journeys reported coverage, events announced decisions, and each had its own idea of where home was. Configuring one did not configure the other, and a service that could talk about what it decided still could not say what it executed. `@variance-authority/wire` is that one medium. It resolves the carrier from the realm — a sink the driver installed, for a server the suite started inside itself, or a loopback return address the request arrived with on a cookie — so the same `collectEvents()` and `collectJourneys()` calls serve a page, a service in another process, and an in-process server without knowing which they are in. Told neither, a participant reports to nobody, which is what a request the run did not drive should do. The return address is refused unless it is `http:` on loopback, because whoever is talking to the service writes that cookie. Two guarantees ride the one wire, chosen by what a loss costs. An announcement is fire-and-forget with per-endpoint ordering: a lost one is a wait that times out loudly in the driver, holding the diagnosis. A coverage account is acknowledged and retried: a lost one is a test silently skipped on the next run, so a head counts what it lost and carries the count on later accounts, and a head that lost everything is silent, which already retires the run. Nothing at this level writes a file. A service is handed a `Cookie` header naming the execution and where to answer, and nothing else; the driver alone writes the coverage index. - a87d008: Hold what a running suite is saying in a process an agent can ask, so a test in flight is something to look at rather than something to wait for. A suite already knows what nothing outside it can see: which realms answered and in what order, which work began and never finished, that a service is plainly talking while the test hearing it hears nothing. All of it is spent settling waits and then discarded, so nobody can ask it while it is true. A runner's timeout reports what a test *wanted* — the last thing the failure knows and the first thing the reader already knew. `@variance-authority/vantage` is the second reader. A watching process listens, the run reports, and the signals live in memory that outlives the test. `variance-authority-mcp --watch` is that process for an agent: it prints the one line the suite has to be started with, then answers `variance_run_signals` for where the run has got to and `variance_test_signals` for everything one execution has heard, in order, with the realm that said each and the work that started and never ended. Both answer while the test is still running, which is the point. The address is in the handshake, not only on stderr. A `Served` may carry `instructions`, and the watching one does: a set of tools about a run nobody has started yet reads as broken, and an agent told the variable after it has started the suite has been told one run too late. None of it is about visual regression. A test that takes no screenshot reports exactly what one that does reports, and a run started without `VARIANCE_AUTHORITY_VANTAGE` pays one environment read per worker. The medium is the wire the announcements already travel: one participant, `run`, and `channelTo` for a participant handed an address rather than sent one. `createEventLog` takes `onRecord` and `onRemark`, called at the moment of recording rather than at teardown — an answer that arrives when the test finishes answers a different question. `varianceWatched` is automatic so a listing has no holes. Still nothing written down. There is no report directory and no artifact to mistake for evidence later; what changes is only how long one execution lasts when somebody is watching.