Curly Message Format 1.0.1

The message's key is the message's id, and it names the message for
diagnostics only: reports carry it (section 14.3) and no step of resolution
reads it.

• The chain a message that does not exist took — the payload's own default
  entry, then the key echoed verbatim — is gone. A caller that supplies no
  message has supplied nothing to resolve, and the resolution is the empty
  string (section 4). What a host shows where its catalogue holds no message is
  the host's own, which section 1 already declined to specify along with the
  catalogue itself, and a host that shows the identifier keeps it out of
  resolution by construction.
• Ruling A.17 is revised rather than dropped. The divergence it records is the
  key being resolved over instead of echoed; the echo it ruled for is what this
  revision removes, and the entry now says what an implementation written
  against revision 1.0.0 does differently.
• What curly-message-1 settles is stated more precisely in the header: the
  promise is about messages, and a caller that supplied none wrote nothing for
  the document to settle. Every message that exists resolves exactly as it did
  under revision 1.0.0 — the change is observable only where a caller supplies
  no message at all.
• Section 2 no longer says the conformance set is unpublished. It is released
  from this repository.

@curly-message/conformance@1.0.1

Targets revision 1.0.1 of the specification, where the message's key became the
message's id and stopped reaching the output.

• A case names the message's id under messageId rather than key, spelled out
  because a case's own id names the case, and an expected report names it
  under id. An adapter is handed id in place of key.
• The cases for the chain a missing message took are gone, and section 4's
  cases say what replaces it: a message the caller did not supply resolves to
  the empty string, whatever the payload's default holds, and nothing is read
  or reported on its account. An id carrying a placeholder is neither echoed nor
  resolved over, because no step of resolution reads it.
• The release carries the set as conformance-<version>.zip — the fixtures,
  the manifest and the schema — so an implementation in a language npm does not
  reach has the same files the runner reads.

The release carries conformance-1.0.1.zip for anything that does not install from npm. sha256 9a353a95317ef41a9e97912b8e96ec29420e7a5d845e7e2474c93c77947d7ee4

Curly Message Format 1.0.0

First stable revision. SPEC.md states version 1 of the Curly Message Format:
the grammar, the escaping and whitespace rules, the order a message resolves
in, the modifiers and what each one answers, the fallback chain, the error
behavior, the conformance levels an implementation claims, and the adapter the
conformance set drives an implementation through. Appendix A records each
divergence found while the document was written against the pre-3.0 reference
parser, together with the ruling that resolved it.

@curly-message/conformance@1.0.0

First stable release. The set targets curly-message-1 — version 1 of the
Curly Message Format, which the specification states is stable — so what a
fixture expects is settled with it.

• The key of an expected report is text. A tagged value is read on a case's
  inputs and never in its expectations, so one written in an expectation would
  have been compared as the object it is spelled as; the schema now rules it
  out, and a case whose key is not text leaves the key unobserved.
• A case for what a host-defined modifier receives as its locale where the
  caller supplied an empty one, which section 11.3 now states.

@curly-message/conformance@1.0.0-next.2

• The version bump regenerates the manifest, so index.json cannot fall
  behind package.json the way the shipped 1.0.0-next.1 does.

@curly-message/conformance@1.0.0-next.1

See conformance/CHANGELOG.md