v1.6.0

Minor Changes

• #266 4283a45 Thanks @holkexyz! - Add an optional langs field, an array of up to three BCP-47 language tags, to org.hypercerts.collection, org.hypercerts.claim.activity, org.hypercerts.context.attachment, org.hypercerts.entity.feature, app.certified.actor.profile and app.certified.actor.organization, declaring the language(s) the record's text was written in. Same shape as Bluesky's app.bsky.feed.post langs. Writing apps set it from the text the author wrote, with the author able to correct it, never from the interface language or a profile preference alone. Readers treat it as a hint, not a guarantee, and must not hide a record because it lacks the field. Existing records remain valid.

• #267 216591d Thanks @holkexyz! - Attachment: state that a standalone update by its author (a personal or organization post not about any particular project) is an org.hypercerts.context.attachment whose subjects point at the author's own app.certified.actor.profile, for people and organizations alike, and that project updates are the same record with subjects pointing at the project; add update to the contentType known values for narrative updates; and say to match a profile subject by uri, since profiles are edited. No schema shape changes: every existing record remains valid. Resolves the standalone-post question without a new post lexicon.

• #263 c7c3df8 Thanks @holkexyz! - Funding receipt: define amount as the gross the sender paid and make amount and currency optional, so a receipt can omit them when only the received amount is known; add optional netAmount / netCurrency for what the recipient received; add an optional type (donation, match, grant) saying what the payment is; add an optional via naming the intermediary that facilitated or processed the payment; state that a receipt may be updated in place, e.g. to add or remove from, and what that does and does not hide; give paymentRail an open knownValues vocabulary; define paymentNetwork as where transactionId can be looked up (CAIP-2 chain ID for onchain payments); add privacy guidance to transactionId; and state how to record payments that pass through platforms, hosts, or regrantors. Existing receipts remain valid. Readers can no longer assume amount or currency is present: the generated types are now amount?: string and currency?: string.

• #268 1394411 Thanks @holkexyz! - Add app.certified.signature.defs#createdVia, an inline signature by the application that wrote this version of a record, and fix the documented signing procedure. $sig is the signature entry without its signature bytes, plus the DID of the repository that holds the record, so it includes key. Signatures built from the previous README example do not verify under the ATProtocol Attestation Specification. Remote proof CIDs likewise use the proof record without cid as $sig.